BOLT Protocol · Documentation

Safe gates

Admin custody for the BOLT Mainnet Beta RC — Safe-gated deployment, prepared but not executed.

Custody model

  • Operator interface: the official Safe Global app, which supports BOT Chain mainnet (chainId 677).
  • Threshold: a dedicated 2-of-2 Safe.
  • Signers (planned): a hardware Ledger key and the BO Wallet key.
  • Status: Safe creation is pending creation, validation and testing. No Safe transaction has been broadcast.

The retired BOT Chain-branded Safe host is not part of the operating path. Operators must use the official Safe Global interface and independently verify chainId 677 before any future action.

Why every write is Safe-gated

BOLT is fail-closed by design. Ownership of protocol contracts and every privileged action — enabling fees, transferring ownership, funding grant epochs, activating execution — routes through the 2-of-2 Safe. Until the Safe is created and validated on mainnet, all of these paths stay disabled and no artifact can move.

Hard gates

The following are blocked and are not performed by any automated surface:

  • Creating the Safe on-chain.
  • Broadcasting Safe transactions.
  • Broadcasting BOLT contracts.
  • Transferring ownership.
  • Enabling fees.

Contract broadcast remains blocked pending explicit, out-of-band final authorization. See deployment gates for the full checklist.