Draft. Pre-launch, spec stage. Phases are ordered, not dated. Scope can move between phases.
Hash Chain is at phase 0. The work moves from spec, to a devnet, to a public testnet, to audits, to mainnet, and then to the later connections and modules. No dates are given because dates would be guesses.
flowchart LR
P0["0 Spec, website, community"] --> P1["1 Devnet"]
P1 --> P2["2 Public testnet"]
P2 --> P3["3 Audits and validators"]
P3 --> P4["4 Mainnet"]
P4 --> P5["5 Later connections and modules"]
| Phase | Contents |
|---|---|
| 0. Spec, website, community | This specification, the website and open discussion. Now. |
| 1. Devnet | Private accounts and payments, validator client. |
| 2. Public testnet | Private swaps, Base and Ethereum connections, SDK preview. |
| 3. Audits and validator onboarding | Independent audits. Onboarding of the first validator set. |
| 4. Mainnet | Accounts, payments, swaps, Base and Ethereum connections. |
| 5. Later | Robinhood Chain, Monero swaps, private assets and apps. |
Phases do not start until the previous one is in good shape. Audits come before mainnet. Early mainnet will have limits, and the anonymity set will be small at first (09).
Each phase maps to documents in this spec: accounts and payments (03, 04), swaps (05), connections (10, 11), assets and apps (06, 07).
- Exact scope of the devnet and what makes a phase complete.
- Validator onboarding process and early set composition.
- Whether any module moves earlier or later based on audit findings.