16 / AMUNCHAIN
Development status
Clarity is part of the architecture.
What exists, what is being tested and what remains a vision. Statuses reflect the supplied September 2026 blueprint, not live network monitoring.
Project status matrix
| Component | Status | Meaning | Source |
|---|---|---|---|
| Constitutional & protocol foundation | Established · project reported | Established according to the project blueprint; independent production verification is not claimed. | p. 4, 24 |
| AmunCore & local validation | In development | Rust core, specifications, authorization and recovery are within the local development and validation scope. | p. 11–12 |
| Company formation | Under formation | Final legal entity and jurisdiction remain to be confirmed. | p. 4, 32 |
| Consensus, VRF & threshold/MPC | Implementation evidence pending | Exact implementation and test evidence must be published before production capability claims. | p. 12, 32 |
| Public testnet | Planned | Follows local validation, controlled multi-node testing and devnet. | p. 24 |
| AmunChain mainnet | Planned | Target after independent security review and readiness gates; no public launch date is set here. | p. 24 |
| NTR / Nefertari | Not launched | Proposed native network asset. No official contract address or distribution is provided. | p. 14–17 |
| Governance institutions | Strategic vision | Future institutions with constitutional limits; not operating government bodies. | p. 13 |
| National projects & APTS | Governance approval required | Activation requires decentralization, legal and feasibility review, and governance approval. | p. 17–21 |
| AQRI research institute | Strategic vision | Strategic research objective; no operating institute or deployed quantum capability is claimed. | p. 22–23 |
Data version 1.3.0 · Editorial review 2026-09-28
What makes a claim verifiable?
A status claim should link to a specific specification, code release, test report or audit. This edition is based on the project blueprint; an independent implementation-evidence or benchmark package was not supplied.
A public description or design does not establish activation. Statuses should be revised as evidence and official updates become available.
Limitations and open questionsSource: Master Blueprint v1.0, pages 4–5, 24, 32 · View source PDF