Phase Overview
Each phase is a definition gate, not a timeline or promise. The gate states what must be true before the network invites new dependency, and it demands reproducible outputs and clear boundaries. Optional adoption requirements live in the adoption tracks, but no phase advances without its technical and governance conditions met.
DevCo (Build Phase)
Private build work happens in DevCo, where the kernel, reference interfaces, and security model are developed before public dependence. Work here focuses on core protocol engineering, reproducible tooling, and internal validation. It excludes public governance, token distribution, and any claims of decentralization or production readiness.
What lives here
Core work that can be built and shared without implying public readiness.
- Kernel modules and chain parameters
- Reference interfaces and SDK foundations
- Internal testnets and reproducible tooling
- Security design and threat modeling
Out of scope
Items that must remain outside the phase boundary until later gates.
- Public governance or token distribution
- Claims of decentralization or production readiness
- Value-bearing activity or public dependency
- Marketing-led protocol commitments
Mental model
Private engineering effort with internal validation, not a live network.
Testnet (Reality Phase)
CurrentPublic validation happens on testnet, where the Hub is exercised under controlled risk. It focuses on measurable performance, bug discovery, and real integration feedback. It excludes value-bearing activity, production assurances, and any timelines tied to token pricing or hype.
What lives here
Public testing and validation that pressure the system without market risk.
- Public or semi-public testnet
- Operators under test rules and monitoring
- Stress testing, bug bounties, and parity checks
- Developer onboarding and integration pilots
Out of scope
Items that must wait until readiness is proven and audited.
- Value-bearing assets
- Production assurances or uptime promises
- Mainnet timelines tied to price or hype
- Dependency from real-world operations
Mental model
Public lab where outputs can reset and scope can evolve.
Foundation (Governance Transition)
Stewardship moves from DevCo to an independent body in the foundation phase. It sets policy baselines, clarifies legal separation, and designs decentralization paths. It excludes exclusive DevCo control, commercial service delivery, and any single-operator control of protocol changes.
What lives here
Governance setup and legal separation that enable independent stewardship.
- IP transfer to the foundation before mainnet (or licensing with disclosed scope)
- Governance framework and policy baselines
- Operator decentralization strategy and grants
- Disclosure standards and stewardship roles
Out of scope
Items that conflict with independent stewardship or neutral posture.
- Exclusive control by DevCo
- Commercial service delivery
- Single-operator protocol control
- Unbounded governance discretion
Mental model
Constitutional layer that separates builders from stewardship.
Audit (Readiness Phase)
Independent review happens in the audit phase, where reviewers validate security and operations before any mainnet commitment. It focuses on audits, remediation, and rehearsals. It excludes unreviewed protocol changes, ad-hoc governance overrides, and any mainnet launch before audits conclude.
What lives here
Independent review and operational rehearsal that prove readiness.
- Security audits and remediation cycles
- Operational readiness reviews
- Incident response drills
- Release and upgrade checklists
Out of scope
Items that undermine audit integrity or readiness discipline.
- Mainnet launch before audits conclude
- Unreviewed protocol changes
- Ad-hoc governance overrides
- Claims without evidence
Mental model
The gate before mainnet, enforced by evidence and review.
Mainnet (Protocol Phase)
Live protocol operation begins at mainnet, where real economic activity and governance operate on-chain. It focuses on operator performance, upgrades, and stable network operations. It limits emergency actions through timelocks and public procedures, and avoids opaque administrative changes outside governance.
What lives here
Live operations, governance, and transparent network reporting.
- Live operators, budgets, and upgrades
- Operational monitoring and incident response
- Public transparency on network status
- Real economic activity and fee flow
Out of scope
Items that compromise neutrality or governance discipline.
- Centralized kill switches
- Emergency rule-change powers
- Opaque administrative control
- Unbounded privileged access
Mental model
Infrastructure layer with public accountability and predictable rules.
Adoption (Ecosystem Phase)
Dependency grows in the adoption phase as integrations mature and real-world usage expands. It focuses on apps, wallets, reporting, and partner programs that rely on the Hub. It excludes protocol changes driven by marketing and governance shortcuts that bypass formal processes.
What lives here
Ecosystem expansion and integration with real usage signals.
- Applications, wallets, and SDK integrations
- Explorers, indexer services, and reporting tools
- Partner programs and ecosystem support
- Institutional observation in read-only mode
Out of scope
Items that compromise neutrality or governance integrity.
- Protocol changes driven by marketing
- Governance shortcuts that bypass process
- Promises that compromise neutrality
- Dependency claims without evidence
Mental model
Ecosystem growth that follows stable protocol foundations.
Manifesto
"My goal is simple: make it possible for anyone, anywhere, to form an entity that can operate with credibility, continuity, and real financial rails, built for stablecoin-native operations."
Read the ManifestoNicolas Turcotte
Founder and Lead Engineer
Contribute now
Testnet is for builders, operators, and stewards who want to validate the Hub in public.
Protocol engineers
Working on kernel definitions, message scope, and invariants.
Indexer and data engineers
Defining event schemas and reproducible view inputs.
Early operators
Testing sequencer, batch posting, and operational scope under testnet rules.
Infrastructure-aligned investors
Tracking scope, risks, and progress (no return claims implied).
Legal counsel
Reviewing boundary posture, non-custodial scope, and document stack order.
Governance stewards
Shaping kernel/adapters separation and upgrade posture.
Testnet
Testnet access
If you're building or validating the Hub, request testnet access to evaluate it.
Newsletter
Stay in the loop
Concise updates on testnet readiness, releases, and governance milestones.
Testnet
Testnet access
If you're building or validating the Hub, request testnet access to evaluate it.
Request testnet accessNewsletter
Stay in the loop
Concise updates on testnet readiness, releases, and governance milestones.