BOLT Protocol · Documentation

Deployment gates

Ordered gates between the Mainnet Beta RC and any on-chain broadcast. Every gate is fail-closed.

Gate sequence

  1. Read-only validation. Intelligence surfaces confirmed live against BOT Chain mainnet (chainId 677) with sourced, fresh data.
  2. Safe creation. The dedicated 2-of-2 Safe (Ledger + BO Wallet) is created, validated and tested on BOT Chain through Safe Global. See Safe gates.
  3. Contract package review. The BOLT contract set is compiled, verified and packaged for release — not yet broadcast.
  4. Broadcast authorization. Broadcast stays blocked until explicit, out-of-band final authorization is issued.
  5. Ownership handoff. Deployed contracts hand ownership to the Safe; no single key holds admin.
  6. Execution enablement. Only after the above, execution is enabled per-surface, still behind Safe approval.

Deploy tooling posture

The deployment scripts default to dry-run. A live broadcast requires exact confirmation tokens and a valid Safe target; absent either, the tooling refuses to broadcast. This is a safety rail, not a switch to flip casually.

Current gate status

  • Read-only validation — active.
  • Safe creation — prepared, not executed.
  • Contract broadcast — blocked (not broadcast).
  • Ownership handoff — pending Safe.
  • Execution — disabled / fail-closed.