Documentation · Deployment
Deployment playbook
Stages, scripts, and safety rails for putting BOLT on BOT Chain — testnet and mainnet.
Fail-closed scriptsTestnet env required
Stage 0 · Pre-flight
- BOT Chain mainnet RPC reachable; chain id returns 677.
- Deployer wallet funded with native BOT for the Phase 1–2 rollout and early grant epochs.
- Explorer API key supplied for source verification on scan.botchain.ai.
- RPC and mainnet pre-flight checks pass.
Stage 1 · Phase 1
- Deploy WBOT, BoltFactory, BoltRouter02, and BoltFeeTreasury.
- Submit contract sources to the explorer for verification.
- Hand the factory fee-setter role to the BOLT multisig.
Stage 2 · Phase 2
- Deploy the launch factory, locker, vesting factory, and registries.
- Verify each contract on scan.botchain.ai.
- Transfer ownable roles to the multisig.
Stage 3 · Grants
- Deploy the grant-payouts contract to mainnet.
- Publish the first weekly epoch under the BOLT operator key.
- Open the claim window for eligible recipients.
Stage 4 · Phase 3
- Select the first BoltPair LP as the vault underlying.
- Deploy BoltVault, the router aggregator, adapters, and the compute-asset pool.
- Register BoltRouter02 as the internal adapter on the aggregator.
- Leave the BDEX and Bridge adapters gated until BOT Chain publishes their ABIs.
Stage 5 · Testnet
- Configure testnet RPC, chain id, and explorer endpoints.
- Run the fail-closed RPC check before any deployment.
- Deploy each phase in sequence against the testnet environment.
- Verify contract sources, then confirm deployed bytecode on every recorded address.
Safety rails
- Every script refuses to deploy unless the chain id matches and the deployer balance is non-zero.
- Mainnet deploys require an explicit confirmation flag.
- No secret is committed to source control. Keys live exclusively in environment configuration.
- Two-step adapter activation: configure the router, then confirm. One transaction is never enough.