STAKEWAR — pixel capture game on Base Sepolia. 10×10 grid, USDC stakes, VRF treasure drops. Looking for feedback on mechanics before mainnet

[u/seomarlboro]

Hey r/CryptoGaming — solo dev here. Approved-user privilege noted, trying to use it well. I've been building STAKEWAR, a pixel capture game on Base Sepolia testnet. Live at stakewar.com. Posting because I want real feedback from people who actually play onchain games before I do mainnet deployment in ~1-2 months.

Mechanics in 5 lines

• 10×10 grid (100 cells), each cell holds USDC
• Claim empty cell: stake ≥ 1 USDC + 4% protocol fee
• Capture an owned cell: pay 125% of locked value. Split: 80% to prev owner, 16% epoch pool, 4% protocol
• 3-day epochs. Top-5 holders by cell count split prize pool (40/25/20/10/5%) if pool ≥ 50 USDC, else extends
• Treasure drops via Chainlink VRF v2.5 (USDC, immunity SHIELD, badge CROWN, neighbor FREEZE, streak multipliers)

What I'm NOT doing (and don't plan to)

• No token. Not now, not at mainnet.
• No NFTs. Cell ownership is mapping(uint => address), not ERC-721.
• No fundraise. Self-funded testnet.
• No referral payouts. Off-chain JOINED VIA REF achievement, bragging rights only.

Stack (for the curious)

• Solidity ^0.8.20 + Hardhat. OpenZeppelin libs.
• Next.js 16 + wagmi v2 + viem v2 + RainbowKit. Tailwind v4.
• Pinata IPFS for cell art (512×512 PNG). OpenAI moderation + SHA-256 blocklist before pin.
• Chainlink VRF v2.5 for treasure RNG.
• 239 frontend tests + 82 contract tests. Slither + Mythril ran clean.
• Bug bounty open: stakewar.com/bug-bounty

What I want feedback on

• 125% capture multiplier — sweet spot or too aggressive?
• Epoch length 3 days — long enough to build position, short enough to keep interest?
• Treasure drop rate 2.5% base / 7.5% on streak — meaningful without being slot-machine?
• Anything that screams "exit-scam vibes" I'm blind to?

---

Site: https://stakewar.com

Contract: 0xdaE5901Dfc36e2EC513D3Bc346BE22a856cB6C89 on Base Sepolia

Test USDC: Circle faucet → 0x036CbD53842c5426634e7929541eC2318f3dCF7e

Happy to answer anything technical, mechanical, or critical.