> 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/trading/collateral-and-settlement-network.md).

# Collateral and Settlement Network

Carbon accepts USDC as its only collateral, deposited on Arbitrum. All trades settle on-chain on Arbitrum (chain ID 42161). How to verify it.

Carbon accepts USDC as collateral, deposited on Arbitrum, and settles every trade on-chain on Arbitrum (chain ID `42161`). USDC is currently the only collateral asset. One USDC balance funds crypto perpetuals, 24/7 RWAs and Carbon TradFi markets, with no transfers between them.

### Supported collateral

* **Asset:** USDC only. See the [Trading FAQ](https://docs.carbon.inc/trading/trading-faq.md).
* **Deposit network:** Arbitrum. Deposit from a connected wallet, or send USDC to your deposit address if you log in with Telegram, Google or Apple. See [Getting Started](https://docs.carbon.inc/trading/getting-started.md).
* **How the balance is used as margin:** crypto positions are cross-margined by default and can be isolated one by one; each TradFi market has its own isolated margin pool. See [Trading Basics](https://docs.carbon.inc/trading/trading-basics.md).

### Settlement network

* Trades settle on Arbitrum, chain ID `42161`. Every account and market API request carries a `chainId`. See [What is Carbon](https://docs.carbon.inc/developers/introduction/what-is-carbon.md).
* Each position is a bilateral contract between you and the solver that quoted it, with collateral locked on-chain by both sides. See [Counterparty Risk](https://docs.carbon.inc/how-carbon-works/counterparty-risk.md).
* The CLP vault that funds the Carbon Solver is deployed on Arbitrum at `0xAdBb55b3d7f93A6c213754e8B7a89996Cd009179`. See [Carbon Solver (CLP)](https://docs.carbon.inc/how-carbon-works/carbon-solver-clp.md).

### How to verify before integrating

1. Read balances from `/v1/accounts/...` and the market catalog from `/v1/markets/...`. See [Developers](https://docs.carbon.inc/developers/developers.md).
2. Check that API responses carry `chainId` `42161`. See [Conventions](https://docs.carbon.inc/developers/http-api/conventions.md).
3. Note the amount encoding: `Wei` fields are base-unit integers with 18 decimals, sent as strings.
4. Read the audit reports on [Security & Audits](https://docs.carbon.inc/additional-information/security-and-audits.md).

### Withdrawals

Withdrawals go through a 12-hour fraud-proof window. A new request during the window restarts it, and a request can be cancelled during the window. Instant withdrawal is available for up to $1,000. See [Security & Withdrawals](https://docs.carbon.inc/trading/security-and-withdrawals.md).

***

*Carbon's TradFi markets are not available to US persons. Please review the* [Terms & Conditions](https://docs.carbon.inc/additional-information/terms-and-conditions.md) *before trading.*


---

# 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/trading/collateral-and-settlement-network.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.
