Documentation · Architecture
How BOLT is put together
BOLT is built as five contract layers, three applications, and one router-of-routers — designed so each surface is audit-isolated and the failure of one layer cannot compromise another.
Contract layers
Core AMM
UniswapV2-style pair + router with native BOT wrapping and 1/6 protocol-fee accrual to BoltFeeTreasury.
- contracts/src/core/BoltFactory.sol
- contracts/src/core/BoltRouter02.sol
- contracts/src/core/BoltPair.sol
- contracts/src/core/WBOT.sol
- contracts/src/core/BoltFeeTreasury.sol
Launch infrastructure
Launch registry, no-admin-key LP locker, cliff + linear vesting factory.
- contracts/src/launch/BoltLaunchFactory.sol
- contracts/src/launch/BoltLiquidityLocker.sol
- contracts/src/launch/BoltVestingFactory.sol
Registry layer
Project metadata for grants and AI-agent identity. No custody.
- contracts/src/registry/BoltGrantRegistry.sol
- contracts/src/registry/BoltAgentRegistry.sol
Grant payouts
Merkle-tree epoch claims funded by anyone; recovery only after the epoch closes.
- contracts/src/grants/BoltGrantPayouts.sol
Vault + router aggregation
Conservative LP vault with no admin withdrawal; registry-based router aggregator.
- contracts/src/vaults/BoltVault.sol
- contracts/src/router/BoltRouterAggregator.sol
Route adapters
Gated adapters that revert with explicit errors until BOT Chain publishes the relevant ABI.
- contracts/src/adapters/BDEXAdapter.sol
- contracts/src/adapters/BridgeAdapter.sol
Compute registry
Non-custodial registry for AI / DePIN compute assets, paired against BOT Chain liquidity.
- contracts/src/compute/ComputeAssetPool.sol
Spark · permissionless launches (Phase 4)
Permissionless ERC20 + bonding-curve launches with two-step graduation into BOLT pools and locked LP.
- contracts/src/spark/BoltSparkToken.sol
- contracts/src/spark/BoltSparkFactory.sol
- contracts/src/spark/BoltBondingCurve.sol
- contracts/src/spark/BoltSparkGraduator.sol
Applications
Next.js 14 App Router static export deployed to Cloudflare Pages.
REST + WebSocket surface over indexed BOT Chain data (operator-hosted).
Postgres event indexer for BoltPair / BoltLaunchFactory / Grant events.
Trust boundaries
- No contract holds upgrade authority over another. Every layer is owned by the same multisig, but ownership cannot move funds out of layers that don't expose that path.
- Adapters are isolated:
BDEXAdapterandBridgeAdaptercannot custody funds and revert until two-step activation by the multisig. - Grant payouts use Merkle roots committed once per epoch; the contract has no path to mint or seize.
- The aggregator is a thin dispatcher — every routed transaction's failure mode is the adapter's, not the aggregator's.