Track Definition
Adoption tracks are optional paths that describe how different audiences may engage with the Hub after specific phase gates are met. They do not imply timelines or commitments. Track activation depends on the gate definitions in dev phases, and any track can remain inactive until its gate conditions are proven in practice.
Optional paths
Tracks describe possible adoption patterns without implying the Hub will reach them.
Phase-gated
Each track activates only after its phase gate is satisfied and verified.
Non-promissory
Tracks avoid growth claims or market outcomes and remain descriptive only.
Track Map
Use the track map to see each audience, its minimum phase gate, and the evidence signal required to treat the track as active. Testnet tracks are technical readiness only and use non-value-bearing tokens; real payment activity remains mainnet and audit gated. When adapters are mentioned, the kernel remains required; adapters are optional and cannot redefine kernel semantics. The map is a planning view, not a schedule.
| Track | Primary audience | Minimum phase gate | Activation signal |
|---|---|---|---|
| Builder readiness | Builders and integrators | Testnet (Reality Phase) | SDKs and tools reproduce schemas, tags, and views using testnet tokens only; no real payment flows. |
| Operational adoption | Founders and operators | Mainnet (Protocol Phase) | Entities run end-to-end operations on-chain with stablecoin flows and tagged outputs. |
| Nonprofit transparency | Nonprofits and NGOs | Mainnet (Protocol Phase) | Donation and program flows use tags and evidence anchors for public transparency views. |
| Institutional observation | Institutions (read-only) | Testnet (Reality Phase) | Read-only observation of registry and explorer views without operational dependence. |
| Adapter adoption | Jurisdictions and service providers | Adoption (Ecosystem Phase) | At least one opt-in adapter pilot runs with explicit boundaries and disclosures. |
Phase-Gated Dependence
Track activation depends on phase gates, not interest or demand. Phase status is visible in the topbar; no promises beyond current capability. If a phase gate is not met, the related track remains inactive, even if interest exists.
Gate discipline
Adoption tracks become eligible only after the phase gate is satisfied and verified through reproducible outputs.
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.