DOM Protocol coin
DOM Protocol
Roadmap

The path to block zero.

DOM launches when the work is done, not on a date. The chain is validated before the first block — by the project’s own audit software and a private burn-in — so that everyone who joins, joins at block zero, on equal terms.

Done In progress Ahead
01
Consensus & immutability
Deterministic replay, reorg equivalence, and cross-platform agreement — the chain reaches the same state everywhere, every time.
Done
02
Cryptographic core
Confidential amounts on Bulletproof range proofs, with the underlying equivalence proven rather than sampled.
Done
03
Storage durability
The ledger survives crashes and partial writes, and rebuilds itself to the exact same state on reopen.
Done
04
Recoverability
Bit-for-bit recovery after interruption, with corruption detected and refused rather than silently carried forward.
Done
05
Spec ↔ code locking
The written rules and the running code are held together, so any drift between them becomes visible.
Ongoing
06
Security audit framework
The project’s own audit software: fuzzing of consensus-critical paths, invariant checks against inflation and double-spend, and a catalog of Mimblewimble attacks run against the chain.
In progress
07
Adversarial hardening
Network, economic, and resource-exhaustion attacks exercised at scale — eclipse and sybil resistance, mempool and difficulty behaviour under pressure.
Ahead
08
Private burn-in
A real, continuous chain run before launch to surface what only time reveals — stability under sustained load. No public participants, no insiders.
Ahead
09
Mainnet from block zero
Deterministic genesis, no premine, no private round, no public testnet. The chain opens for everyone at the same first block.
Ahead

Milestone-based, not calendar-based. Each gate opens only when its work is actually done.