Start
Release status
What exists in source, what has been independently evidenced, and what is not yet deployed.
Functional Testnet GO · Formal Certification deferredRepository snapshot
| Layer | Status | Meaning |
|---|---|---|
| Reviewed application baseline | 8c4f8bb5b23056799be055e1ec52f71ec60f972d | Recorded by functional-a9d0e6f28f8e on chain 46630. |
| V3 Functional Testnet | GO | Real Coin, funded Manual Parity, JIT, Holder/Claim and RWA loops passed the fixed functional report. |
| Provider 4 | 9/9 | 0 pending at the fixed observation. |
| Formal Accepted Testnet release | Not published | Formal H3–H11 certification and Evidence B remain deferred. This does not erase Functional GO and does not create an accepted address book. |
| Mystery / Holder holding window | Mainnet target: 604,800s | Functional Testnet used the manifest's accelerated 900s window; this is not a Mainnet promise. |
| Robinhood Chain Mainnet | Not deployed / NO-GO | All production replacements and security gates remain blocking. |
Readiness layers
- operationalReady
- Manual paths plus release identity, external health, settlement signer, Reserve, Bond, JIT, and service gates.
- mysteryReady
- operationalReady plus a genuine seven-day holding window and Mystery budget/access gates.
- fullAcceptanceReady
- mysteryReady plus the full acceptance matrix and zero unexplained terminal exposure.
A liveness response is not a readiness response. A 503 readiness result means the evidence is insufficient; it must not be interpreted as permission to proceed.
What remains after Functional GO
- Preserve the Functional Testnet manifest and acceptance report as a bounded, historical GO artifact.
- Complete Formal H3–H11 certification, the 100/50 Provider replay gate, Evidence B and disaster-recovery certification before calling the Testnet release formally accepted.
- Generate the accepted-release projection from the final immutable Evidence B instead of copying Functional addresses by hand.
- For Mainnet, create a separate 4663 release with real seven-day TWAP/TWAB history, official assets, production venues, governance and external security evidence.
- No testnet acceptance can change Mainnet from NO-GO; Mainnet requires a separate 4663 release and evidence set.