Don't take our word for it. Check it yourself.

1 · Is the token real and unchanged?

FOMOEgg's contract address is a single, fixed street address on the blockchain — a public ledger that anyone can read but no one can quietly edit. If the address ever changed, that would be a red flag. Below is the address FOMOEgg is using, and a link to look it up yourself on the block explorer (a public website that shows anyone's transactions).

2 · How many tokens are burned, and is that number honest?

"Burning" means tokens are sent to an address nobody controls and nobody can ever spend from — permanently removed from circulation, forever. The more that's burned, the smaller the remaining supply. Below, FOMOEgg reports a number. Your browser can re-check that exact number by asking the public blockchain directly — a request your own device makes, that never passes through FOMOEgg's server.

Dead address (where burned tokens are sent, and can never be spent from): —

3 · Can the Race be rigged?

Before a Race's entries even close, FOMOEgg locks in a secret and publishes its commit fingerprint: sha256("fomoegg:" + secret). After the round closes it reveals that secret. Your browser checks three things only: the commit matches the revealed secret, the track seed matches sha256("fomoegg-track:" + secret) (first 4 bytes; the block hash is recorded but not mixed in), and the stored finish rank matches the stored winner. This page does not re-run the marble-run or calculate a winner in the browser — that physics check is what scripts/verify_race.py does offline with the Node sim. This is called commit–reveal.

4 · Where does the money go?

Any funds the project holds sit in a treasury wallet — an address on the public blockchain, visible to everyone, the same way the token contract is. Every dollar in and every dollar out is supposed to be recorded and reconciled against what's actually on-chain.

5 · Can the team change the rules quietly?

Rules that affect payouts (like how burns are sized, or how the treasury is allocated) are versioned — every change gets a new version number, an effective date, and a written reason, and old versions are never deleted or hidden. Changes are also written to an append-only, tamper-evident log: a record where every entry is cryptographically linked to the one before it, so editing an old entry breaks the chain in a way that's detectable.

6 · What do I still have to take on trust?

Honesty, not marketing: FOMOEgg's own server runs on a database that the person operating it can technically edit directly. No public code, including this one, can make that structurally impossible when everything lives on one server. What this project has done is make almost every one of those edits detectable rather than invisible: