Skip to main content

​
The price your protocol depends on is wrong

Protocols don’t fail because their logic is wrong. They fail because the prices they trusted were. Lending protocols, perpetuals, vaults, and liquidation engines depend on price feeds. Most feeds report the past: the last DEX trade, a delayed oracle update, or a single-source reference that may already be stale. The consequences are real. Moonwell took $1.78M in bad debt after a cbETH oracle misconfiguration. Aave saw $27M of erroneous wstETH liquidations from a stale oracle parameter. Different protocols. Different root causes. The same underlying problem: protocols inherited prices that no longer reflected the market.
Stale price feeds do not just produce inaccurate quotes. They cause bad debt, failed liquidations, and cascading losses across every protocol that trusts them.

​
What Bolt provides

Bolt provides an executable convergence price built from real-time market data across venues. Unlike a traditional oracle that reports the market, Bolt publishes the price its own Execution Rail settles against. Protocols build on execution-grade pricing rather than advisory pricing. Bolt’s executable convergence price is verifiable onchain and updated continuously.

Executable, not advisory

The convergence price is not a reference for others to interpret. It is the price Bolt’s own pools settle against. Protocols inherit executable pricing rather than interpreting a reference feed.
The price is derived from a depth-weighted composite across multiple venues, with staleness filtering and outlier rejection. No single venue failure can corrupt the feed.
Every published price is clamped to a bounded deviation from the composite and verifiable onchain. The execution quality of the feed is auditable, not opaque.

​
Use cases

Liquidation cascades often start with a stale price feed mispricing collateral. A continuously updated, executable convergence price narrows the gap where cascading failures originate.

​
How integration works

The convergence price is public and readable onchain without permission. The Bolt team works directly with protocol teams on integration architecture and deployment support. Book a call to scope your integration.
1

Read the convergence price onchain

Bolt publishes an executable convergence price for every supported pair. The price is derived from a depth-weighted composite across multiple venues, clamped to bounded deviations, and verifiable onchain. Your contracts read it the same way they read any onchain state.
2

Anchor your protocol logic

Replace your existing price dependency with the convergence price wherever your protocol relies on external pricing: collateral valuation, liquidation triggers, mark-to-market for perpetuals, funding-rate computation, or vault rebalancing thresholds. One price source covers all of them.
3

Scope the integration with Bolt

The Bolt team configures pair coverage, update parameters, and deviation bounds to match your protocol’s risk model. Every integration is scoped to the protocol’s specific requirements.
4

Verify independently

Every published price is auditable onchain. After deployment, your team can verify execution quality, freshness, and deviation history against the composite independently.

​
Co-marketing

Launching a Bolt integration? The marketing team provides brand assets, announcement support, and amplification through Bolt’s channels.

Book a Marketing Call

Co-marketing, integration announcements, and partner materials.

Brand Kit

Logos, colors, and brand assets.

How Bolt Works

The four-step pipeline from market data to onchain settlement.

Talk to the Team

Integration architecture, deployment support, and partnership.