ForgeDon't trust the anvil. Replay it.
Your browser just downloaded every coin's trades and the engine file, forge.mjs, the same one our server runs. It replays each coin at the server's instant and compares the result, block for block.
| Coin | Trades | Blows | Ingots due | Server hash | Your hash | Match |
|---|---|---|---|---|---|---|
| Replaying… | ||||||
What the hash covers
Blows, ingots forged and pending, each ingot's size, due time and cause, the dev balance, and every trade with its blows. Change one sell by one token and the hash changes.
Tests that must be able to fail
Before each release the engine is checked against a second implementation written separately, second by second. Each test is also run in a tampered mode, where it must fail: a test that cannot fail proves nothing.
| Test | Result | Tampered |
|---|---|---|
| Second implementation, 9 histories (including a real Stonks coin) | 446 checks pass, same hash on two replays | 24 failures |
| 12 durable nonces, late burns, dev sell (Solana runtime) | pass | 2 failures |
| Full launch on a copy of mainnet: creation, dev buy, 12 burns to the token | 10 of 10 | fails |
| Studio and watcher, real API | 19 of 19 | fails |
| Indexer on real Stonks curves (balances, holders, replay) | 3 curves pass | — |
Every burn has a transaction
On a live coin, each burned ingot links to its transaction on Solscan. A burn moves tokens from the dev wallet to nowhere, signed by the dev before launch. Forge never signs.