Roadmap / evidence-based delivery

Measure first.
Scale responsibly.

A staged 2026–2030 development programme, shaped by open developer access, constrained pilots, institutional mandates and independent assurance.

01 / White-paper roadmap

Milestones and release gates.

Targets below are proposed and conditional. No delivery milestone is a guarantee or assertion of present deployment.

Q4 2026–Q1 2027

Foundation & charters

Confirm chain configuration, documentation, contract inventory, use-case charter and technical benchmarks.

Release gate / Chain evidence and signed specifications.
2027 / H1

Constrained product pilots

Credential/signature MVP, audited contract templates, private B2B marketplace, asset-passport sandbox and PQC gateway.

Release gate / Privacy tests, agreements and reviewed source.
2027 / H2

Institutional experiments

Enterprise subchain, restricted issuance prototypes, marketplace reconciliation and PQC wallet testnet.

Release gate / Issuer rights, governance, contract audit, throughput data.
2028

Controlled production candidates

Expand commerce, servicing, verified oracle/custody integrations and limited authorised financial sandboxes.

Release gate / Production approvals and recovery tests.
2029

Ecosystem interoperability

Managed nodes, sector integrations, institutional RWA servicing and sustainable enterprise programmes.

Release gate / Independent assurance and viable unit economics.
2030

Selective cross-jurisdiction pilots

Evaluate mature crypto-agility, quantum-classical results and approved institutional interoperability.

Release gate / Lawful partner mandates and published outcomes.
02 / Capability status

Clarity is part of the product.

Product pages use these evidence-based distinctions.

DOCUMENTED

Published foundation

Network identity, Chain ID, RPC, explorer and described EVM development.

PROJECT-REPORTED

Requires corroboration

Supply or activity figures that need independently reviewable on-chain evidence.

PROPOSED

Product roadmap

AI, marketplace, Volrex One, RWA, PQC and subchains until verified.

AUTHORISED ONLY

Institutional mandate

CBDC, regulated issuance and public/legal powers cannot be self-declared.

03 / Release acceptance

Evidence before production claims.

Every high-impact module should have a named legal operator, controlled deployment, audit scope and human-accountability mechanisms.

01

Technical evidence

Versioned source, signed releases, network health, contracts and reproducible tests.

02

Security assurance

Independent review, clear key custody, incident runbook and tested recovery.

03

Legal authority

Document actual issuer, regulator, custodian, rights holder and jurisdiction.

04

Governance

Named directors/operators, role separation, dispute handling and upgrade authority.

05

Measurable outcomes

Report defined metrics, deployment date, scope and limitations.

The next chapter

Engineer what comes next.

Explore the network, evaluate a focused pilot or collaborate on responsible digital infrastructure.