Skip to main content

The price your protocol depends on is wrong

Lending protocols, perpetuals, vaults, and liquidation engines depend on price feeds. Most feeds report past prices: the last trade on a DEX, a delayed oracle update, a single-source reference that can be stale, misconfigured, or manipulated. 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. Both are part of a pattern: unsynchronized prices create cascading failures in protocols that trust them.
Stale price feeds do not just produce inaccurate quotes. They cause bad debt, failed liquidations, and cascading losses across every protocol that inherits them.

What Bolt provides

Bolt’s builds a fair price from real-time data across venues and posts it onchain as an executable . This is not a reporting oracle. It is a price that real trades settle against, verifiable onchain, 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 that build on it inherit execution-grade pricing, not a lagging estimate.
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

Use the convergence price for collateral valuation and liquidation triggers. A fresh, cross-venue price reduces the window where stale pricing creates bad debt or erroneous liquidations.

How integration works

The convergence price is public and readable without permission, but the team works directly with protocol teams on integration architecture and deployment support. Book a call to get started.
1

Install the Bolt SDK

Get started with npm or yarn:
See the 5-Minute Integration guide for full setup.
2

Query available pairs

Call getAssets() to see the pairs supported on Sui:
This gives you the complete list of tradeable pairs in the Bolt network.
3

Request a quote

Call getQuote() with the pair, amount, and direction:
Bolt returns the exact output amount. No slippage estimate needed.
4

Execute the swap

Pass the quote to executeSwap() for atomic on-chain settlement:
Settlement happens in a single transaction. Your user receives the quoted amount.
5

Route comparison

Compare Bolt quotes against other liquidity sources in your routing engine. On large trades, Bolt’s zero-slippage execution will win more routes than traditional pools.

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.