Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.boltliquidity.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Liquidity should be a utility, not a liability.

​
The Traditional Problem

Traditional AMMs require pools to be deeply capitalized at all times, even when no trades are happening. Capital sits idle. Liquidity providers pay the cost of impermanent loss. Ecosystems pay the cost of incentive programs. The system assumes that execution quality is a function of capital depth, so more capital must always be locked to ensure good execution. This assumption breaks economics at scale.

​
How Bolt Works Differently

In Bolt’s model, pools are settlement infrastructure, not pricing engines. Liquidity is deployed on demand: capital enters the system when a trade occurs, gets hedged externally, and returns to the pool. The pool does not need to hold enough capital to set prices. It just needs enough to settle the next trade. This is the core insight. If pricing is deterministic and oracle-referenced, then liquidity depth no longer determines execution quality. The capital requirement becomes a function of settlement size, not volume throughput.

​
The On-Demand Cycle

1

Trade arrives at Outpost

A trader submits an order. The Outpost receives the trade request with full details: asset pair, size, and oracle-referenced pricing.
2

Market maker settles and hedges

The Bolt market maker settles the trade immediately at the oracle price already posted on-chain, using deposited pool liquidity. The settlement price is derived from the AVO oracle, independent of pool depth. Once settled on-chain, the market maker hedges all directional exposure on external venues in real time.
3

Hedged assets return to pool

Once hedged, the settlement capital cycle completes. The assets used to settle the trade are refreshed, and the pool is ready for the next trade. The LP’s capital is never exposed to directional risk.

​
The Capital Efficiency Proof Point

29.7x daily inventory turnover — 23x the Sui DEX peer average. Across 16 SUI/USDC pools spanning 8 protocols and 4 AMM architectures, the volume-weighted peer turnover is 1.28x. Bolt’s turnover rate is a direct consequence of on-demand liquidity deployment.
In a traditional AMM model, the pool must hold enough capital to set the price. The deeper the pool, the tighter the spread. Capital sits idle waiting for trades. In Bolt, the capital requirement is the amount needed to settle the next trade. This is not a feature. It is a consequence of the architecture. When pricing comes from an oracle, capital only needs to settle, not to set the price.

​
What This Means

For traders, zero slippage regardless of trade size. For liquidity providers, fees without impermanent loss. For ecosystems, execution quality that does not require massive liquidity incentives. The on-demand model eliminates the capital liability that haunts traditional AMMs.

Bolt vs. Traditional Models

Head-to-head architectural comparison across AMMs, RFQs, intents, and CLOBs.

Earn Fees with Bolt

How liquidity providers earn fees with no impermanent loss.