Phase 3 · BoltRouterAggregator
One router, many adapters
A registry-based aggregator that routes through whichever liquidity sources BOT Chain exposes. The internal BOLT route is deployed to Bohr testnet. External adapters (BDEX, BOT Bridge) are deployed in a gated state.
What it does
- Owner registers each adapter as
(adapterId, address, type, name). quote(adapterId, data)— read-only, callable even on disabled adapters.execute(adapterId, swapData)— only on enabled adapters; forwards to the adapter's own logic.- Aggregator never custodies funds — each adapter is responsible for its own token movement.
- Disabled adapters stay registered (preserves historical addressability) but cannot execute.
How BOLT extends BOT Chain
BOT Chain has multiple liquidity sources today (BOLT, B DEX, BOT Bridge). Without an aggregator, every integration is a one-off. BoltRouterAggregator makes adding a new source a single transaction (registerAdapter) — and the BDEX + Bridge adapters are already deployed in a gated state, so activation is a single transaction once each precondition is met.
Readiness evidence
BoltRouterAggregatorlive on Bohr at0xd8875d5941d6d2a07485c3c3fe25bd2f010db196.- 10 / 10 Foundry tests covering register / quote / execute / disable.
BDEXAdapter+BridgeAdapterreverts with explicit errors (BDEXAbiNotConfirmed/BridgeAbiNotConfirmed) until activation.- Activation requires a two-step
setRouter+setConfirmed(true)by the multisig.
Once mainnet deployment completes
The internal Bolt adapter is registered first so /swap/ routes through the aggregator end-to-end. BDEX activates after BOLT exercises a routed swap on Bohr; Bridge activates after EIP-1967 implementation verification. See /integrations/.
Commercial value
- Standard 0.30% LP fee on internal routes.
- Future external-route surcharge for desk-grade execution.
- Routing data sold via the Nexus API.