Mainnet Readiness Checklist

Tracking what's done, what's in progress, and what remains before Ladder Script is ready for mainnet activation.

5 of 8 complete
1. Formal Verification
Done
  • 9 TLA+ specifications model-checked across 3.3M states
  • Properties verified: evaluation semantics, anti-spam guarantees, wire format correctness, Merkle proof security, sighash binding, covenant termination, cross-input rules
  • Located in spec/ directory
2. Test Coverage
In Progress
  • 480 unit tests
  • 60 functional regtest tests
  • 41/61 active block types verified on live signet with fund+spend txids
  • 43 documentation accuracy tests
  • 15 proxy unit tests
  • 20 engine smoke checks
3. Fuzz Testing
Partial
  • rung_deserialize_fuzz.cpp — deserialization fuzzer
  • Needs: evaluator fuzzer
  • Needs: sighash fuzzer
  • Needs: MLSC proof fuzzer
4. Build & Deploy
Done
  • scripts/build.sh — single-command build (cmake -j2, strip)
  • scripts/deploy.sh — binary, proxy, web, smoke targets
  • Signet node operational at 85.9.213.194
  • 10-minute mining with real wall-clock timestamps
5. Tooling
Done
  • Descriptor notation: all 61 block types parseable via parseladder / signladder
  • Engine: browser-based visual builder with 43 templates
  • Block reference: 61 HTML block reference pages
6. Documentation
Done
  • BIP-XXXX submitted 2026-03-16
  • 22 markdown docs audited for accuracy
  • Comparison document: 7 patterns vs Bitcoin Script
7. Activation Mechanism
Not Started
  • BIP 9 version bits signaling (proposed)
  • All 61 block types activate simultaneously in single soft fork
  • Mainnet: only TX_MLSC (0xDF) outputs accepted (value-only, one conditions_root per tx)
  • RUNG_VERIFY_MLSC_ONLY flag (bit 28) enforced
8. External Review
Not Started
  • Needs review from Bitcoin Core developers
  • Needs security audit of evaluator + sighash
  • Needs adversarial testing by third parties