> For the complete documentation index, see [llms.txt](https://docs.carbon.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carbon.inc/how-carbon-works/solver-network-explained.md).

# Solver Network Explained

How third-party solvers on Carbon's crypto perpetual track deposit collateral, stream quotes, hedge filled trades and keep margin on and off chain.

Solvers are the backbone of Carbon. They source liquidity, stream live quotes, hedge filled trades, and provide the on-chain margin that makes the bilateral agreement model work.

This page covers the **third-party solver network** that powers Carbon's crypto perpetual track. The Carbon Solver, which powers the TradFi track, follows similar mechanics but operates as a single proprietary solver funded by the CLP vault.

The lifecycle below shows one possible operating profile. The system is designed for flexibility: solvers can hedge, quote, and manage risk in many ways.

***

### <mark style="color:$info;">1. The Solver Deposits Collateral On- and Off-Chain</mark>

To participate, a solver begins by depositing collateral both on-chain and off-chain:

* **On-Chain:** A portion of the solver’s collateral is held in Carbon’s on-chain contracts as a guarantee for execution.
* **Off-Chain:** The remaining collateral is deployed at the solver’s hedging venues of choice, which may include centralized exchanges, OTC desks, TradFi brokers, or other venues.

This structure gives solvers the ability to execute trades on behalf of Carbon users while keeping on-chain settlement secure and transparent.

<figure><img src="https://3351097766-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbpemdioXs8P0YBsLx7uh%2Fuploads%2FHnU5zucmEIbiow5V1JIy%2Fimage.png?alt=media&#x26;token=cd55d6b8-a077-49a9-81ce-3d102db5b3b3" alt=""><figcaption></figcaption></figure>

***

### <mark style="color:$info;">2. The Solver Configures Their Market Making Infrastructure</mark>

Once collateral is placed, the solver sets up their market-making software. This infrastructure must be able to:

* Query and execute trades at off-chain hedging venues
* Interact with Carbon’s on-chain execution engine contracts
* Stream quotes to Carbon’s front-end via APIs and WebSockets

<figure><img src="https://3351097766-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbpemdioXs8P0YBsLx7uh%2Fuploads%2F5Pjm427CYLnMqFV7hVHV%2Fimage.png?alt=media&#x26;token=9402cf2f-c365-458c-abed-5cdcb0016c39" alt=""><figcaption></figcaption></figure>

***

### <mark style="color:$info;">3. Solvers Stream Pricing Data to Carbon</mark>

Solvers continuously source pricing data from their chosen hedging venues. They then stream live quotes to the Carbon front-end with their desired spread (for example, +/– X bps vs. the off-chain order book). This constant loop of sensing and quoting ensures Carbon users always see real-time, competitive pricing.

<figure><img src="https://3351097766-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbpemdioXs8P0YBsLx7uh%2Fuploads%2FrQS4nJcftC8SZHQjk9mH%2Fimage.png?alt=media&#x26;token=45c137a0-7b8f-4d1b-9f1e-ed72fb62a5ee" alt=""><figcaption></figcaption></figure>

***

### <mark style="color:$info;">4. A Trader Inputs Intent and Accepts a Quote</mark>

From the Carbon WebApp, a trader inputs their trade intent — size, order type, leverage, and asset. Solvers compete to quote the best price.

Carbon’s proprietary matching system ensures the best available quote per the trader’s intent. If the trader accepts, they sign a “request for trade” and deposit their required margin into Carbon’s on-chain execution engine.

<figure><img src="https://3351097766-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbpemdioXs8P0YBsLx7uh%2Fuploads%2F8XujAseuZhBVtdtg1Wkp%2Fimage.png?alt=media&#x26;token=1a746457-6d68-4429-a897-c2d4bee7118b" alt=""><figcaption></figcaption></figure>

***

### <mark style="color:$info;">5. The Solver Executes and Opens the Trade</mark>

Once the request for trade is submitted, the solver receives it and executes the hedge off-chain (if they choose to remain delta-neutral) before filling the on-chain position.

The solver then deposits their own required margin into the on-chain perpetual contract. The position is now open.

Note: Solvers are not required to hedge. They may choose to take directional risk or hedge using other methods such as spot positions. This example simply illustrates one possible approach.

<figure><img src="https://3351097766-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbpemdioXs8P0YBsLx7uh%2Fuploads%2FawlXdxfEbOJR3j0xPuYZ%2Fimage.png?alt=media&#x26;token=2ce742bd-a907-45a2-8fb2-4e97a7a7018c" alt=""><figcaption></figcaption></figure>

***

### <mark style="color:$info;">6. Both Parties Monitor Margin, Rebalance, or Close</mark>

Both trader and solver are responsible for maintaining their margin:

* **Traders:** Must monitor and maintain the margin behind their positions or risk liquidation.
* **Solvers:** Must maintain margin both on- and off-chain. If the trader requests to close, the solver can preemptively close their off-chain hedge, then accept the on-chain close request.

Third-party liquidators monitor all open positions using oracle price feeds. If margin falls below requirements, either party can be liquidated.

<figure><img src="https://3351097766-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbpemdioXs8P0YBsLx7uh%2Fuploads%2Fi7tA335lifq8NW7GlRks%2Fimage.png?alt=media&#x26;token=55937a9d-6799-4e16-8b7e-ac8887b6bd22" alt=""><figcaption></figcaption></figure>

***

### <mark style="color:$info;">On-Chain and Off-Chain Orchestration</mark>

Carbon’s solver architecture brings true hybrid execution to DeFi. The intent-based system allows:

**For Traders:**

* Optimal price execution by accessing off-chain liquidity on-chain
* A streamlined RFQ process with fill times under five seconds
* Exposure to crypto and TradFi derivatives products that may not exist natively on-chain
* Permissionless, self-custodial, and trustless on-chain settlement
* Large orders filled by multiple solvers acting as liquidity aggregators

**For Solvers:**

* Ability to maintain delta-neutral positions with proactive hedging
* Freedom to source liquidity from any venue - CEX, DEX, OTC, TradFi brokers, CME options, etc.
* Advanced infrastructure such as netting (future product) to offset exposures between solvers at low or zero cost

***

### <mark style="color:$info;">Solver-Based RFQ Compared with an Order Book</mark>

On an order book, your order matches against another anonymous order. On Carbon there is no shared book: a solver quotes your intent, takes the other side, and the trade settles on-chain on Arbitrum.

|                  | Solver-based RFQ on Carbon                                                            |
| ---------------- | ------------------------------------------------------------------------------------- |
| **Counterparty** | The solver that quoted your trade (`PartyB`)                                          |
| **Price**        | Quotes streamed by solvers from their hedging venues, plus their spread               |
| **Collateral**   | Locked on-chain by both you and the solver for each position                          |
| **Capacity**     | Set by each solver's open-interest cap; large orders can be filled by several solvers |
| **Rejections**   | A solver can reject a trade if the price moved since the quote                        |
| **API**          | A `solver` parameter and `/v1/solvers/...` endpoints, because there is no shared book |

To compare execution, look at the quote's price, spread, fees and funding before you sign, the `slippage` bound on market orders, and the final status of each order. See [Counterparty Risk](https://docs.carbon.inc/how-carbon-works/counterparty-risk.md) and [How trading works](https://docs.carbon.inc/developers/architecture/how-trading-works.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.carbon.inc/how-carbon-works/solver-network-explained.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
