Games where the items, the currency and the rewards are contracts — and the game client is one view onto them.
The hard problem here isn't rendering. It's that an economy with real withdrawable value has to survive players optimising against it: item supply, token sinks and marketplace fees stop being balance decisions and become monetary policy. And the moment an asset is worth money, the client can no longer be trusted to say what happened.
A browser-based 3D space station — mining, crafting, factions and real-time multiplayer, with ownership onchain.
ERC-721 and ERC-1155 asset ownership, an escrowed marketplace, and an EIP-712 reward vault so payouts are signed rather than self-declared. 11 Solidity contracts, 269 files, 38 test files behind a stated 415 tests, running against both a local chain and testnet. CI green.
The interesting constraint is that a persistent multiplayer world and an onchain economy pull in opposite directions — the world needs fast mutable state, the economy needs slow settled state. The split between the Fastify backend and the contracts is where that gets resolved.
Tech: Next.js, React Three Fiber, Fastify, Solidity · MIT
https://github.com/pranay123-stack/nova-station-web3-metaverse
Onchain card ownership with server-authoritative gameplay — the design decision that makes a Web3 card game actually work.
Cards are ERC-1155, but battles resolve on a deterministic engine the server owns, because a client that computes its own combat result will lie about it. EIP-712 starter-pack vouchers, an escrowed NFT marketplace using pull payments (so a malicious buyer contract cannot block a sale), real-time PvP. 14 contracts, 328 files, 48 test files behind a stated 411 tests. CI green.
Tech: Next.js, TypeScript, Solidity, Foundry · MIT
https://github.com/pranay123-stack/web3-trading-card-game
A Three.js endless runner where rewards are real onchain tokens. The anti-cheat boundary is the point: runs are attested by a server that signs an EIP-712 receipt, and the reward vault only pays against that signature, so the browser can never mint its own payout.
Three contracts (RunRewardVault, RushToken, RushVestingWallet), a Node attestation
service with its own anti-cheat module, and a full game client. 159 tests. Live on Base
Sepolia with a real validated run claimed onchain. Self-declared testnet MVP — not audited,
not on mainnet.
Tech: Three.js, Solidity, Hardhat, Node.js, EIP-712
https://github.com/pranay123-stack/onchain-endless-runner
A farming game where land, crops and currency are all onchain assets, playable in the browser. Five contracts covering tokenized land plots, in-game item NFTs, the game currency, core progression state, and a peer-to-peer marketplace.
The client is a real game loop — a canvas and scene system rather than a dashboard with a wallet button — over a Node backend for state the chain shouldn't hold.
No tests. For a codebase that mints and trades value-bearing assets, that is the gap worth fixing first, and it is the reason this sits last here rather than alongside the three above.
Tech: Solidity, Hardhat, Next.js, TypeScript, Node.js
https://github.com/pranay123-stack/web3-farming-game
Related: Web3 NFT · Web3 Infrastructure · Full-Stack Product Engineering