Fairness and safety
Your wallet assets are recorded in contracts. The game server runs battles, teams, keys and reward calculations. Knowing which part decides a result helps you understand what you can check.
What the contracts enforce
| Action | What is checked |
|---|---|
| Owning cards | The card contract records the wallet owner, rarity, basic mining HP, level, XP and shiny flag. Combat stats are calculated from game rules. |
| Opening boxes or chests | The contract turns the supplied random result into cards using its drop rules and limits. The randomness provider matters; see below. |
| Buying or selling | The chosen payment contract checks payment, ownership and fees. A market sale transfers the card and pays the seller in one transaction. |
| Delayed random result | While an order still has no random result, its buyer can refund after 24 hours. The original network fees are not refunded. |
| Claiming rewards | A published account proof, available reserve, reward caps and the normal 12-hour waiting period are checked. The proof confirms inclusion in the published reward list. |
| Releasing or unlocking | The reward contract applies the unlock schedule and any early-unlock burn. Staking has its own lock and early-exit rules. |
Some prices and limits live in an adjustable contract registry. Live Shop reads its USDC prices there; guide tables describe code defaults. Contract administrators also have roles such as pausing actions and changing supported settings. The presence of these controls does not prove who currently holds every live role.
What still relies on the server
| Game data | Server responsibility |
|---|---|
| Battles and rating | Chooses opponents, runs fights, records results and updates rating. |
| Tickets, keys and teams | Tracks your game balances, declared teams, daily resets and eligibility. |
| Reward amounts | Calculates mining HP snapshots, daily pools and ranking prizes, then publishes an account reward list. |
| Vouchers | Approves welcome-box eligibility, spends keys for chests and signs earned-item claims. |
| Wallet activity in the app | Reads contract events so the collection, orders, market and shop balances can update. |
Contracts limit voucher use, item claims and published rewards, but a server outage can still delay play, syncing, vouchers and new rewards. Cards already held in your wallet remain recorded on-chain. Some recovery actions can be made directly from Boxes; see delayed orders.
Check the randomness label
- Chainlink VRF: the configured contract requests a random number with a verifiable proof from Chainlink.
- Test randomness: a test coordinator is answered by the game server. Its results are useful for testing but do not have Chainlink's randomness guarantee.
- Checking or unverified: the app has not confirmed the provider. Do not read that label as a verified Chainlink draw.
The Boxes page checks its configured provider. A page animation, a random-looking number or a contract address alone is not proof of an independent random draw.
What a battle replay proves
- 1Battle startsThe server creates a match seed
- 2Engine calculatesThe seed and fighter stats determine the fight
- 3Result is shownThe result contains the seed and battle log
- 4ReplayThe same inputs reproduce the same result
The replay shows the fight that was already calculated; animation timing does not change the winner. Someone checking the game engine with the same seed, fighters and rules can reproduce the result.
This checks consistency of the calculation. It does not prove that the server chose the seed independently or without bias. Battles use server seeds; they do not use Chainlink VRF.
Configured contracts on Base Sepolia
Open Contracts and addresses for the full configured list, an explanation of each contract, project account roles and links to the network explorer. It includes tokens, purchases, rewards, vesting and swap infrastructure.
The list uses the same configuration as this app. Configuration alone does not confirm an external audit, working liquidity, current signer permissions or the availability of every action.
Before confirming in your wallet
- Check the network, amount and contract. A sign-in message proves you control the wallet; a transaction can spend assets and requires a network fee.
- USDC and ZOO payment approvals allow a named contract to spend the approved amount. Card and item approvals can authorize that operator for the whole collection; read the wallet prompt.
- Approvals can be reviewed and revoked through your wallet's supported tools. Disconnecting from the website does not revoke them.
- Never share your recovery phrase or private key. The app does not need either.
- Base Sepolia uses test tokens with no real value.
For a stuck purchase or missing balance, start with Help.
This guide describes the current code and its defaults. Some app previews also use defaults; deployed settings can differ. Review the network, amount and action before confirming.