Research preview · No live network or real fundsProject status ↗
Roadmap / Acceptance gates

Build what matters.
Prove what ships.

A sequence of engineering and operating milestones, not a promise that a public network launches on a chosen date.

01 / Native application research

Status: local prototypes and tests. Develop the native monetary rules, durable account history, key transitions, bounded agent grants and shared allowances. Exercise rejection, replay and recovery rather than only successful transfers.

Separate production claims from constructed test environments. Preserve explicit protocol versions and reproducible development evidence.

02 / Actual network verification

Status: not yet verified. Build and execute the pinned upstream engine. Run communicating validators against the native application, then verify transfers, grant changes, key rotation and shared-budget enforcement.

Acceptance requires observed quorum loss and recovery, restart behavior and independently checked receipts. More unit tests or synthetic certificates cannot satisfy this gate.

03 / Public-testnet readiness

Status: future gate. Address bounded resource use, authenticated storage, monitoring, operator documentation, release verification, backups and upgrade procedures. Run independent technical review and adversarial exercises.

A public testnet must identify its operators, limits and reset policy. Test assets must remain clearly separate from real funds and public issuance.

04 / Bounded user experience

Status: product prototype. Connect the human-readable permission experience to verified account state and protected signing. Validate recovery with people and at least one agent runtime outside the original implementation.

Success is understandable authorization and dependable task completion—not a decorative balance or manufactured network activity.

05 / Everyday access

Status: proposed and partner-dependent. Evaluate dollar instruments, eligible external assets and card integrations. Each route needs explicit custody, funding, consent, disclosures and reconciliation.

A failed conversion must be visible. The software must not silently switch assets, borrow or imply a protected bank deposit where none exists.

06 / Native network launch

Status: no date announced. Public launch requires reviewed monetary policy, sustainable security incentives, independent operation, incident readiness and appropriate legal work.

There is no sale, yield promise or mainnet access through this website. Each stage depends on evidence from the preceding gates.