I build Token launches, Web3 Games & Blockchain products | 700+ Smart contracts & 200+ Web3 Dapps deployed | Official Dev partner of @Pyrand_coin | DMs Open
We built Lunar Dominion for @Pyrand_coin, a 3D web3 strategy game where players buy & trade land on the Moon.
All 5,000+ Moon tiles sold out.
So for Season 4 we built Venus: a full planet surface split into 15,000 tiles, plus a merged marketplace.
How it works:
→ Players connect their wallet to play
→ They buy HE3, the in-game currency, with $PYRT or $PYRX tokens.
→ Gameplay runs off-chain, so it's fast and players don't pay gas for every move
→ Rewards go to winners on-chain, so every payout is verifiable
The game is On-chain where trust matters. Off-chain where speed matters.
See it live here: https://t.co/TxHOYIeyVx
At Infinity Blockchain, we build what your players and investors can trust, and what your community actually wants to use.
We have launched 700+ Smart contracts and 200+ dApps.
Building a web3 game, token or a presale? Send me a DM.
Stablecoins aren’t the same on every chain.
USDC and USDT use 6 decimals on Ethereum.
On BNB Chain they use 18.
Hardcode 1e18 and your contract is off by a factor of a trillion on one of them.
Read decimals(). Every time.
@theo_solidity underrated point. a test suite built on a wrong spec just proves the wrong thing works. a lot of “bugs” are the contract doing exactly what the spec said, just not what anyone meant
How we test a smart contract before deployment:
1. Foundry unit tests (success and revert paths)
2. Invariant tests: what must always be true
3. Slither for common bugs
4. Forge coverage to find untested branches
5. Testnet deployments to check the full user flow
None of this replaces an independent audit. It catches the bugs a second reviewer shouldn't have to spend time on. What does your testing flow look like?
3 bugs I keep finding in smart contracts that already passed their tests:
1. A function meant to be called only by your app, with no signature check, so anyone can call it directly
2. Dividing before multiplying, so the math rounds down to zero
3. Making external calls before updating state
Tests check what you expected. Bugs live in what you didn't.
Follow for more from real code reviews.
The 5 bugs I see most in smart contracts that already passed their tests:
1. An admin function with no access control, so anyone can call it
2. A decimals mismatch, like treating USDC (6 decimals) as an 18-decimal token
3. Dividing before multiplying, so reward math rounds down, sometimes to zero
4. Assuming every token transfers the full amount. Fee-on-transfer tokens break your accounting
5. Sending funds before updating balances in claim or withdraw functions
Tests pass because they check what you expected. Bugs live in what you didn't.
What's the worst one you've caught before mainnet?
@ProjectSmolDen curious to know if you guys ever thought about a game about running a dragon farm and then using them to battle other players. Would really suit the project.
@CLASHINU Really love the comic series 😂
I saw on your website that the INU game and arena are still in the works. We build web3 games for meme communities.
DM me if you want help bringing it to life.
Just checked out the BOTZ Arcade 🤖
You've got solo games covered with Coin Rush and Moon Mission. What's missing is a team game, and Good BOTZ vs Bad BOTZ is made for one: holders vote for their side, and the top voter on the winning team wins $BOTZ. Sort of like a Tug a war.
We've already built and launched this exact game for another project. DM me and I'll show you how it works.