> ## 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.

# DeFi Protocols

> Build on one executable convergence price. Stop inheriting stale prices, bad debt, and failed liquidations.

## 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](https://www.theblock.co/post/390302/defi-lending-protocol-moonwell-hit-with-1-8-million-bad-debt-after-oracle-misconfiguration) after a cbETH oracle misconfiguration. Aave saw [\$27M of erroneous wstETH liquidations](https://www.coindesk.com/business/2026/03/10/defi-lending-platform-aave-sees-a-rare-usd27-million-liquidations-after-a-price-glitch) from a stale oracle parameter. Both are part of a pattern: unsynchronized prices create cascading failures in protocols that trust them.

<Warning>
  Stale price feeds do not just produce inaccurate quotes. They cause bad debt, failed liquidations, and cascading losses across every protocol that inherits them.
</Warning>

## What Bolt provides

Bolt's <Tooltip tip="Builds a fair price from a cross-venue composite, forecasts its near-term path, and posts one executable convergence price onchain.">Convergence Engine</Tooltip> builds a fair price from real-time data across venues and posts it onchain as an executable <Tooltip tip="The near-future fair price Bolt may lean toward when short-horizon signal is strong enough. Falls back to the composite when it is not.">convergence price</Tooltip>. This is not a reporting oracle. It is a price that real trades settle against, verifiable onchain, updated continuously.

<AccordionGroup>
  <Accordion title="Executable, not advisory" icon="gavel" defaultOpen={true}>
    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.
  </Accordion>

  <Accordion title="Cross-venue, not single-source" icon="layer-group">
    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.
  </Accordion>

  <Accordion title="Verifiable onchain" icon="shield-halved">
    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.
  </Accordion>
</AccordionGroup>

## Use cases

<Tabs>
  <Tab title="Lending & Borrowing">
    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.
  </Tab>

  <Tab title="Perpetuals">
    Mark-to-market against the convergence price. Funding rates and liquidation thresholds anchored to a synchronized price are more reliable than feeds derived from a single venue.
  </Tab>

  <Tab title="Vaults & Yield">
    Vault strategies that rebalance or settle based on price triggers benefit from a price that reflects real-time cross-venue conditions rather than lagging DEX state.
  </Tab>

  <Tab title="Liquidation Engines">
    Liquidation cascades often start with a stale price feed mispricing collateral. A continuously updated, executable convergence price narrows the gap where cascading failures originate.
  </Tab>
</Tabs>

## How integration works

<Info>
  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](https://calendar.google.com/calendar/u/0/appointments/schedules/AcZssZ0h8Dz0XD9uiYnrWu6PUHvRfnuoNjXyCJYnzFX8t548I1YO-qnJxJSOrvuWeenqacByagNyyB0E) to get started.
</Info>

<Steps>
  <Step title="Install the Bolt SDK">
    Get started with npm or yarn:

    ```bash theme={null}
    npm install @boltliquidity/sdk
    ```

    See the [5-Minute Integration](https://docs.boltliquidity.io/5-minute-integration) guide for full setup.
  </Step>

  <Step title="Query available pairs">
    Call `getAssets()` to see the pairs supported on Sui:

    ```typescript theme={null}
    const pairs = await bolt.getAssets();
    ```

    This gives you the complete list of tradeable pairs in the Bolt network.
  </Step>

  <Step title="Request a quote">
    Call `getQuote()` with the pair, amount, and direction:

    ```typescript theme={null}
    const quote = await bolt.getQuote({
      from: "SUI",
      to: "USDC",
      amount: "1000000",
      direction: "exact_in"
    });
    ```

    Bolt returns the exact output amount. No slippage estimate needed.
  </Step>

  <Step title="Execute the swap">
    Pass the quote to `executeSwap()` for atomic on-chain settlement:

    ```typescript theme={null}
    const txn = await bolt.executeSwap(quote);
    ```

    Settlement happens in a single transaction. Your user receives the quoted amount.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## Co-marketing

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

<CardGroup cols={2}>
  <Card title="Book a Marketing Call" icon="bullhorn" href="https://calendar.app.google/c2ZCSEdUTnrmseAF6">
    Co-marketing, integration announcements, and partner materials.
  </Card>

  <Card title="Brand Kit" icon="palette" href="https://drive.google.com/drive/folders/11KkpBjGBdMHQAG8RE8T4rqIhjcPeil59">
    Logos, colors, and brand assets.
  </Card>
</CardGroup>

***

<CardGroup cols={2}>
  <Card title="How Bolt Works" icon="cog" href="/how-bolt-works">
    The four-step pipeline from market data to onchain settlement.
  </Card>

  <Card title="Talk to the Team" icon="envelope" href="/contact">
    Integration architecture, deployment support, and partnership.
  </Card>
</CardGroup>