Roadmap

The implementation considerations in Section 13 directly inform the sequencing below: each phase is structured to validate a specific open question before the next phase depends on the answer.

Phase 1

Specification & Core Protocol Development

Finalise the consensus, monetary, and virtual-machine specifications described in Sections 5–7. Begin reference implementation of the Shared Host API, the consensus engine, and the EQCF/ADTMS monetary logic.

Foundational

Phase 2

Hardware Calibration & Edge-Tier Validation

Empirical testing of physically unclonable function stability on target hardware under target-region environmental conditions, per Section 13.1. Validation of the Sovereign Edge Layer's sovereignty guarantee on real ESP32 and nRF52840 hardware.

Hardware-dependent

Phase 3

Public Testnet

A live, multi-tier network bringing together all five hardware classes simultaneously, used to calibrate the stress-index and persistence-gate parameters described in Section 13.3 under genuine network conditions, and to validate throughput and finality figures at meaningful scale per Section 13.2.

Network-scale validation

Phase 4

Developer Tooling & Ecosystem Onboarding

Maturing the dual-target compiler path described in Section 11.4, expanding documentation and tooling for the Pim Cell Type Standard, and onboarding early application developers building on the native object types described in Section 7.4.

Parallel workstream

Phase 5

Regulatory Engagement

Direct engagement with regulatory bodies in target jurisdictions, beginning with Nigeria, addressing the considerations described in Section 13.5 — conducted in parallel with, not after, technical development.

Parallel workstream

Phase 6

Mainnet Launch

Genesis block deployment with the full post-quantum cryptographic suite active from block one, as described in Section 8.1, following successful validation of the preceding phases.

Launch

Phase 7

Cross-Chain Bridge & Continued Extension

Development of the cross-chain bridge described in Section 11.3, alongside continued expansion of the Pim Cell Type Standard registry as new use cases, described in Section 12, mature into formal native object types.

Post-launch

This roadmap is presented as a sequence of dependencies, not a fixed calendar. Each phase's completion criteria are tied to the specific open questions identified in Section 13, and a phase is not considered complete — regardless of elapsed time — until its corresponding validation has actually been performed.