Trust
Verification
What was tested, how, and what was not.
Done
| Check | Result |
|---|---|
| Foundry tests | 16 of 16 pass: eight wallets buy in one transaction, no gas money in the wallets, altered calls, a signature from another wallet, replay, expiry, atomic revert, non-atomic skip, a wallet that never delegated, a wallet delegated elsewhere, per-wallet domain, namespaced nonce slot, one arm with several calls. |
| JavaScript tests | 9 of 9 pass. The execute digest matches Foundry's output byte for byte. |
| Local node, real type-4 transaction | Eight fresh wallets (nonce 0, no gas) bought in one transaction in one block. The curve saw eight distinct callers. A replay was refused. |
| Real chain (4663), simulation | Eight fresh wallets bought on a live Pons curve through an eth_call that carries a signed authorization list. The price rose from one buy to the next. Four forgeries were refused. |
How the real-chain run works
Nothing is deployed and no transaction is sent. A helper contract's bytecode is placed at an address through the eth_call state-override feature. The call carries a real authorization list signed by eight fresh wallets, deploys the coordinator and implementation inside the call, and fires.
node scripts/real-chain-check.mjs
Not done
- An outside audit.
- Deployment, and a real type-4 transaction on the live chain.
- Fuzzing and formal verification.
- Wallet and launchpad integrations beyond the curve interface used in tests.