← Back to Dashboard
Status as of 16 June 2026. This is a working checklist, not a marketing roadmap. Items are graded by what has actually been verified through testing, versus what is assumed or still pending. See also the development changelog for the testing sessions referenced below.
1. Consensus & protocol — critical path
ItemStatusNotes
Genesis block (official)✅ DoneHash 743c2849..., timestamp 1781545300, mined and live on testnet
PoUW enforced at consensus layer✅ VerifiedCheckPoUW() confirmed rejecting blocks without valid XMSS sig in regtest + testnet
End-to-end PoUW mining✅ Verified12 total blocks mined across regtest (6) and testnet (6), 100% success rate
Mainnet genesis at production difficulty❌ Not doneGenesis uses 0x1d00ffff (Bitcoin-equivalent) but has never been mined at that difficulty — only near-zero regtest/testnet difficulty tested
Key lifecycle reviewed✅ DoneOne-shot key model deliberately kept for this phase — see DEVDOCS.md design decision record
Difficulty retarget under load❌ Not doneNo multi-day testnet run exists to observe retargeting behavior
Chain reorg handling❌ Not doneNo test has forced a fork/reorg scenario with PoUW blocks
2. Wallet & RPC
ItemStatusNotes
getnewxmssaddress✅ VerifiedTested live, returns valid address + pubkey
exportxmsskey / importxmsskey✅ Fixed & verifiedWas broken (missing RPC registration + missing method) — fixed and tested 16/Jun
sendtoxmssaddress❌ Not testedImplemented per DEVDOCS but not exercised in this session
Wallet backup/restore with XMSS state❌ Not testedbackupwallet/restore documented but not run against an XMSS-holding wallet
Key exhaustion behavior (1024th sig)❌ Not testedCannot occur under current one-shot design; revisit if that design changes
3. Network & infrastructure
ItemStatusNotes
Single node running (testnet)✅ Donesystemd-managed, auto-restart configured
Multiple independent nodes✅ VerifiedTwo fully independent node processes reached identical chain state via direct submitblock and genuine automatic P2P relay — see Changelog Phase 6.9
DNS seeds❌ Not doneCommented out in chainparams.cpp, hardcoded single IP seed only
Public block explorer✅ LiveFlask-based explorer running, API verified
Dashboard / mining / whitepaper pages✅ LiveAll return HTTP 200
Stratum mining pool server⚠ ImplementedNot load-tested with multiple real miners
4. Documentation & legal
ItemStatusNotes
Whitepaper✅ DoneInternal consistency fixed (license, ports, magic bytes, halving)
BSL-1.1 license✅ AppliedConverts to GPL-2.0 on 15/Jun/2030
DEVDOCS.md✅ UpdatedCorrected against actual implementation, design decisions recorded
Changelog✅ MaintainedPhases 6.5 and 6.6 document the genesis launch and bug fixes
Security audit (external)❌ Not doneAUDIT.md is a self-audit; no external/independent review has occurred
5. Honest gaps
Items most likely to be glossed over under launch pressure — each is a real, unverified assumption
0
Resolved 17/Jun — was the most severe gap of all. Every SNTI block ever mined violated BIP141's coinbase witness rule, meaning no node other than the one that mined a block could ever accept it. This was undetectable with a single node and was only found once a second independent node was actually stood up. Fixed via a stable preimage signing design — see Changelog Phase 6.9. This is the strongest argument yet for never skipping the multi-node test, no matter how much single-node testing looks clean.
1
No external eyes have looked at this code. Every fix so far has been found by this team, in this session. A second reviewer — even an informal one — would likely find things missed here.
2
No adversarial testing. Nobody has tried to break the PoUW validation, attempt a key-reuse attack, or fuzz the XMSS bridge.
3
No multi-node network has ever existed. All consensus behavior observed so far is single-node. Network partition handling, peer banning, and propagation under real latency are unverified.
4
Mainnet difficulty has never actually been mined. The 0x1d00ffff target is copied from Bitcoin's genesis difficulty but untested against this codebase's actual hash rate plus PoUW overhead.
5
No incident has happened yet. There is no tested procedure for what happens if a bug is found in an already-mined block — no chain-split contingency, no communicated rollback plan.
6. Recommended order of operations
Dependency-driven, not date-driven
1
Get a second person (or fresh eyes after time away) to read through validation.cpp's CheckPoUW() and the XMSS bridge code — the two places where a bug has the highest blast radius.
2
Stand up a second node on a different machine/network and confirm both nodes sync and agree on the same chain.
3
Run testnet continuously for several days under real conditions to observe stale-tip warnings, retargeting, and stratum server behavior over time.
4
Only after 1–3 are satisfied, mine a real mainnet genesis block at production difficulty and treat that timestamp as final.
5
Domain registration, public release, and community announcement come after step 4 — not before.