Skip to main content

30. Roadmap

The roadmap reflects repository maturity rather than marketing milestones. “Present in source” means code or an executable path exists; it does not mean that the subsystem is production-ready, deployed across a permissionless network, audited, or specified as a mainnet constant.

30.1 Present in Source​

  • Cryptography — ML-DSA-65 signing, ML-KEM-768-compatible Kyber P2P KEM, Rescue-Prime + STARK VRF, SPHINCS+, hashing, Merkle commitments and signature aggregation.
  • Consensus — DAG structure and ordering, validator/committee accounting, fast-path and pipelining modules, view-change, checkpoints and slashing paths.
  • Execution — Wasmer/WASM runtime, EVM and Solang compatibility paths, CU metering, state overlays, MVCC/speculative execution.
  • Token standards — QN4/QN8/QN12 implementation modules with tests and configurable limits.
  • STACC — quota, admission, compute-unit, activation, scheduling, mempool and reward-hook modules.
  • Sharding and state — shard mapping, load/rebalance helpers, cross-shard coordination, RocksDB storage, snapshots, compression and pruning-oriented code.
  • L0 and integrations — checkpoint proof construction, external adapters, relayers, bridge contracts, Rust/TypeScript SDKs and wallet components.
  • Application contracts — Solidity/WASM projects and deployment tooling with module-specific testnet/local status.

30.2 Required Before Mainnet​

  • Normative genesis and economics — supply, issuance, staking, delegation, quota, rent, slashing, treasury and upgrade authority.
  • Multi-validator validation — safety/liveness tests under faults, churn, delayed messages, partitions and reconfiguration.
  • Performance publication — reproducible throughput, latency, resource, conflict and cross-shard benchmarks.
  • Security assurance — independent cryptographic, consensus, VM, bridge and contract audits plus fuzzing and formal analysis where appropriate.
  • Interoperability hardening — per-chain verifier guarantees, relayer bonds, key management, replay protection and incident response.

30.3 Planned Research​

  • Formal verification of consensus invariants and state-transition properties.
  • Mature light clients and reduced-trust external-chain verification.
  • Production-grade resharding, data availability and cross-shard finality.
  • Complete permissionless staking, delegation and governance implementation.
  • Additional runtimes, tooling and application integrations.