Launch Gates & Readiness
Relevant source files
The following files were used as context for generating this wiki page:
Launch Gates and Readiness constitute a systematic, evidence-based audit and verification framework designed to ensure the X3 mainnet is operationally prepared for deployment. The system replaces subjective assessments with AI-driven auditing and rigorous checklists to verify module connectivity, bridge safety, system invariants, and governance integrity.
The primary objective of this system is to achieve 100% coverage across critical domains, including cross-VM attack vector mitigation, total supply enforcement, and node stability. This process ensures that no "guesswork" is involved in the transition from development to a live production environment.
Sources: launch-gates/README.md:3-14, launch-gates/MAINNET_AUDIT_WORKFLOW.md:7-13
Audit Infrastructure and Workflow
The Launch Gates system utilizes Repomix to generate targeted "audit packs" from the codebase, which are then analyzed against specialized prompts to identify blockers and calculate readiness scores.
Audit Pack Generation
The system categorizes the repository into five distinct packs to allow for focused auditing:
- Full Repo: A complete codebase snapshot for wiring and general readiness.
- Runtime & Consensus: Specifically targets the core blockchain logic.
- Bridge & Atomic: Focuses on cross-VM communication and atomic swap logic.
- Tests: Aggregates all test suites to identify coverage gaps.
- Git Drift: Analyzes recent changes and logs to identify potential regressions.
Sources: launch-gates/README.md:33-41, launch-gates/MAINNET_AUDIT_WORKFLOW.md:15-23
The Five Core Audits
The following table describes the specialized audits performed on the generated packs:
| Audit Type | Purpose | Primary Pack | Success Criteria |
|---|---|---|---|
| Wiring Audit | Proves all modules are connected with no dead code. | Full Repo | 100/100 score |
| Launch Gate | Provides a 0-100 readiness score by category. | Full Repo | $\ge$ 95/100 overall |
| Bridge Safety | Identifies cross-VM attack vectors (replay, atomicity). | Bridge/Atomic | 95+/100 score |
| Invariant Hunter | Verifies all critical properties are tested/monitored. | Full Repo | All properties enforced |
| Test Gap | Identifies untested edge cases and scenarios. | Tests | All scenarios covered |
Sources: launch-gates/README.md:46-54, launch-gates/MAINNET_AUDIT_WORKFLOW.md:25-96
Operational Workflow Diagram
The diagram below illustrates the iterative cycle of pack generation, auditing, and remediation.
The audit cycle ensures that every fix is re-verified through a fresh repository snapshot.
Sources: launch-gates/README.md:88-109, launch-gates/MAINNET_AUDIT_WORKFLOW.md:105-119
Readiness Criteria and Gates
The project defines specific thresholds and "Hard Gates" that must be passed before the Genesis ceremony.
Quantitative Readiness Scores
Mainnet readiness is tracked via a MAINNET_READINESS.json file. Successful launch requires meeting the following minimum metrics:
- Overall Audit Score: $\ge$ 95/100.
- Category Scores (Wiring, Consensus, Tests): $\ge$ 90/100.
- P0 Blockers: Exactly 0 remaining.
- Testnet Stability: 72+ hours of stable operation without intervention.
Sources: launch-gates/README.md:69-82, launch-gates/MAINNET_AUDIT_WORKFLOW.md:144-160
Hard Gates (CI and Security)
The system enforces "Hard Gates" within the Continuous Integration (CI) pipeline to prevent regression:
- Zero Unwrapped Options: Production code must not contain
.unwrap()calls to prevent panics. - Invariant Checks:
check_invariant()must be called in every supply-changing operation. - Build Reproducibility: The WASM blob must be built with
srtooland match the hash in the genesis chain spec. - External Audit: A full external security audit must be signed off, with all critical findings resolved.
Sources: MAINNET_LAUNCH_CHECKLIST.md:58-65, MAINNET_LAUNCH_CHECKLIST.md:79-88, MAINNET_LAUNCH_CHECKLIST.md:139-145
Genesis Ceremony Checklist
The Genesis Ceremony is the final, irreversible gate. It is divided into several verification phases.
Configuration and Economics
The Chain Launch Committee must verify the finality of the network identity and economics:
- Chain ID: A unique numeric value locked in
chain-spec.json. - Total Supply: Finalized breakdown across native genesis, EVM wrapped, and SVM wrapped supplies.
- Genesis Accounts: Audit confirms all balances sum to the canonical supply.
Sources: launch-gates/GENESIS_CEREMONY_CHECKLIST.md:15-45
Validator and Network Readiness
Before cutting the genesis block, the following infrastructure must be verified:
- Bootnodes: At least 3 resolution-verified nodes must be online.
- Session Keys: All validator keys collected and verified unique.
- Monitoring: Prometheus metrics and alerting rules (e.g., block production stalls) must be active.
Sources: launch-gates/GENESIS_CEREMONY_CHECKLIST.md:103-125, launch-gates/GENESIS_CEREMONY_CHECKLIST.md:179-195
Phase 13f Operational Documentation
Phase 13f represents the final documentation suite required for launch operations. It ensures that the operations team has a manual for every scenario.
Documentation Suite Components
| Document | Purpose |
|---|---|
| Mainnet Launch Runbook | Hour-by-hour execution (T-48h to T+7d). |
| Incident Response | 8 detailed playbooks for service crashes or network partitions. |
| RPC Failover | Procedures for switching between providers (Alchemy, Infura, etc.). |
| Validator Operations | Lifecycle management including key rotation and slashing recovery. |
Sources: crates/x3-relayer/PHASE_13F_MASTER_INDEX.md:15-22, crates/x3-relayer/PHASE_13F_COMPLETION_DECLARATION.md:15-21
Escalation and Decision Support
The system provides a clear decision tree for incident management to minimize MTTR (Mean Time To Recovery).
Conclusion
Launch Gates & Readiness provide a rigorous framework for transitioning the X3 project to mainnet. By combining AI-assisted auditing (Wiring, Bridge, Invariants) with prescriptive manual checklists (Genesis, CI, Phase 13f), the project minimizes the risk of catastrophic failure during the initial launch phase. Success is defined by high audit scores ($\ge$ 95) and the total absence of P0 blockers.
Sources: launch-gates/README.md:153-166, launch-gates/MAINNET_AUDIT_WORKFLOW.md:170-178