Transparency: betting contract

Reading data from the blockchain…

USDC held by the contract (stakes in games and unclaimed winnings)

…

Games created in total

…

Current bet cap

…

Project fee on the pot

…

Contract owner

…

Oracle address (records game results)

…

Fee recipient

…

Open the contract on PolygonscanUSDC on Polygonscan

What is fixed in the code

• •A bet is 0.5 to 500 USDC in steps of 0.5. Nobody can set a bet above 500 USDC.
• •The fee cannot exceed 10% of the pot. A draw returns both stakes in full with no fee.
• •Winners and refunds are collected by the player with the Claim button, and the money goes only to that player's wallet.
• •The owner cannot withdraw players' stakes: the contract has no such function.
• •If no result is recorded, after 2 × the game time + 3 days anyone can return both stakes to the players.

Who can do what

Owner

changes the oracle address, the fee (up to 10%) and the bet cap (up to 500 USDC). Cannot touch players' money or change a game result.

Oracle

records the winner of a game. It can only name one of the two players of that game, or a draw, and cannot send money to a third party. This is a trust point: while our server decides game results, you trust that server.

Honest risks

• •The contract has not had a paid audit. We did our own review, an independent review by a separate AI assistant, and 45 automated tests. This is not a substitute for an audit.
• •The contract source code is published and verified on Polygonscan, so anyone can read it and compare it with the deployed code.
• •If the oracle key were stolen, an attacker could record winners. That is why the bet cap is limited and the key is stored separately.
• •USDC belongs to Circle, which can block addresses. A blocked player cannot receive a payout.
• •Only play with amounts you can afford to lose.