Documentation · Integrations

External integration status

Every external surface BOLT touches, in plain language. What we have verified independently, what is gated, and what is pending an external party.

Read-only intelligence liveB DEX read-only validatedAdapters gated

What it does

BOLT is built so integration points can land without a redeploy. Each adapter and wiring listed below is either verified against on-chain data or explicitly gated until a clear precondition is met.

How BOLT extends BOT Chain

A protocol's integration claims should be testable from the outside. Every verified row links to an address or endpoint anyone can independently check; every gated row names the precondition.

BOLT contracts are packaged for Mainnet Beta RC and are not broadcast until final authorization. Testnet proof is archived at demo.boltterminal.xyz.

Integration status

BOT Chain RPC + chain config
Verified
BOT Chain · chainId 677 confirmed by eth_chainId against rpc.botchain.ai. Read-only intelligence live against the mainnet RPC.
Owner: BOLT Protocol
RPC
https://rpc.botchain.ai · chainId 677
Explorer
https://scan.botchain.ai
Native token
BOT (18 decimals)
Explorer + verification API
Verified
BOT Explorer is Blockscout with an Etherscan-compatible /api endpoint (Solidity 0.8.24, optimizer 800, Shanghai). BOLT contracts are packaged for the Mainnet Beta RC and are not broadcast until final authorization; source verification runs at broadcast time.
Owner: BOLT Protocol
Explorer
https://scan.botchain.ai
Verification API
Blockscout Etherscan-compatible /api
Mainnet verify
https://scan.botchain.ai/contract-verification
B DEX integration
Testnet addresses confirmed · gated
BDEX addresses taken from the official BOT Chain dev docs (dev-docs.botchain.ai/docs/DEX/contract-addresses). BDEX V2 (UniV2-compatible) and V3 (UniV3 fork) routers/factories are callable on BOT Chain · chainId 677 — verified read-only. No WBOT/USDT pool is seeded at the documented token pair yet, so routed-swap validation is pending a seeded BDEX pool (open question to the BDEX technical contact). BDEXAdapter stays gated — execution disabled until Safe validation and until that routed swap succeeds.
Owner: BOLT Protocol
Source
dev-docs.botchain.ai/docs/DEX/contract-addresses
V2 Factory
0x65b8e98ceA190d8c28B3e4716402027f634d15a3
V2 Router02
0xD6425a02f0845B8D99e349C34D2E7A576E177345
V3 Factory
0x1C51c173323ec11BB4e3C4fD2314c225Dc4b5419
V3 SwapRouter
0x07032d47A1b9f8460cBeE9dC17c1d3E438693929
V3 QuoterV2
0x034A705b36067cff99ABf5C662Be881cBd8d0176
Read-only check
V2/V3 routers + factories reachable on 677 ✓ · pool seeding pending
BOT Bridge integration
Gated
BOT Bridge contracts exist behind OZ TransparentUpgradeableProxies; the bridge API (api-bridge.botchain.ai/config) exposes the cross-chain map. BridgeAdapter stays gated until BOLT has read each implementation address and validated the public surface.
Owner: BOLT Protocol
Bridge API
https://api-bridge.botchain.ai/config
Mainnet proxy
0xB230BDA1D8971eCB2E59ceD8f8F73aC5F128AEf0
Wrapped BOT + tokens
Verified
WBOT is the canonical wrapped native, deployed at the same address on mainnet and testnet. Mainnet USDT / USDC are not yet deployed; testnet TUSDT exists for faucet flows.
Owner: BOLT Protocol
WBOT (both nets)
0xD5452816194a3784dBa983426cCe7c122F4abd30
TUSDT (testnet)
0x75edC9335175Fc0552D51D48439F229c10420fe3
USDT / USDC mainnet
not deployed yet
BO Wallet dApp listing
Pending
BOLT works in MetaMask / WalletConnect today via standard EIP-3085. BO Wallet dApp-browser inclusion requires a partner submission against the BO Wallet team.
Owner: BO Wallet team
Indexer + Nexus API
Pending host
apps/api + apps/indexer ship in this repo. Mainnet eth_getLogs is disabled, so production indexing uses WSS subscriptions or a self-hosted node. Production API is live at api.boltterminal.xyz; indexer activation remains tied to verified contract sources.
Owner: BOLT operations