Pong01: project facts
- Project
- Pong01
- Period
- 2025
- Role
- Solo Developer
- Summary
- Three.js pong game that mints testnet rewards
- Description
- A browser-based 3D pong game on Huddle01 testnet where players connect a wallet, bounce a physics-driven ball with a paddle, and earn $PONG ERC-20 tokens based on score. It exists to drive real transactions and engagement on our testnet while feeding the Huddleverse quest system.
- Domains
- Web3 Gaming, Testnet Growth, 3D UX, Token Incentives
- Technologies
- Next.js, React Three Fiber, Rapier, tRPC, Drizzle, viem, Hardhat, ERC-20
- Ownership
- Three.js game scene, physics, audio, and score UX
- Ownership
- Wallet connect and NextAuth session wiring
- Ownership
- tRPC reward pipeline with server-side validation
- Ownership
- PongToken smart contract and deployment on testnet
- Ownership
- Leaderboard and referral bonus logic
- Learning
- Gamified testnets still need boring backend rigor. Players only trust rewards when validation and mint failures are handled clearly in the UI.
- Professional signal
- I like mixing playful frontend craft with real on-chain incentives when the goal is ecosystem growth, not just a demo.
a browser-based 3D pong game on Huddle01 testnet where players connect a wallet, bounce a physics-driven ball with a paddle, and earn $PONG ERC-20 tokens based on score. it exists to drive real transactions and engagement on our testnet while feeding the Huddleverse quest system.
testnets die without usage. we needed something fun that still exercised wallets, minting, leaderboards, and referrals, not another faucet form.
i built the game loop with @react-three/rapier for ball and paddle collisions, score multipliers tied to rally count, and a modal flow for wallet connect via Reown. the backend validates game duration and score, mints PongToken on chain, and stores leaderboard rows in Postgres. referrals double the first-game reward to encourage sharing.
pong01 runs at pong01.com with Huddle testnet branding, leaderboard APIs, and integration as a SPARTANS quest in Huddleverse (`pongValidator` checks weekly leaderboard rank). it helped push real testnet transaction volume during Huddle campaigns.
- ·three.js game scene, physics, audio, and score UX
- ·wallet connect and NextAuth session wiring
- ·tRPC reward pipeline with server-side validation
- ·pongToken smart contract and deployment on testnet
- ·leaderboard and referral bonus logic
- ·the game had to feel good in the browser with Rapier physics and React Three Fiber without melting laptops.
- ·rewards needed anti-cheat checks so scores could not be spoofed from the client.
- ·we had to connect on-chain minting, session auth, and weekly quest validation in Huddleverse.
gamified testnets still need boring backend rigor. players only trust rewards when validation and mint failures are handled clearly in the UI.
referral doubling on the first game moved more wallets than tweaking token amounts did.
- ·low testnet transaction counts
- ·one-off faucet interactions
- ·no playful reason to connect wallets
- ·repeatable game sessions with mints
- ·leaderboard competition
- ·quest-linked weekly rewards in Huddleverse
if you want chain activity, ship a toy people want to replay, not another dashboard.
i would add server-side replay sampling for suspicious scores and move more game state off the client. a lighter mobile path would help, since the full 3D scene is desktop-first today.
- ·tuning paddle collision audio volume by ball velocity was weirdly satisfying.
- ·the conference-room background in the scene was one of several HDR-style room assets I tried before shipping.
i like mixing playful frontend craft with real on-chain incentives when the goal is ecosystem growth, not just a demo.
More from the Huddle01 platform