# Collateral token

> Verify the collateral used for balances, orders, position operations, and payouts in this environment.

Production uses USD Coin (`USDC`) as its
collateral. Cash balances, BUY reservations, fees, withdrawals, splits,
merges, and resolution payouts are all denominated in this token.

| Environment | Production |
| --- | --- |
| Network | Base (`8453`) |
| Token | USD Coin (`USDC`) |
| Decimals | 6 |
| Contract | [`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`](https://basescan.org/address/0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) |

Only the configured contract funds your AGARA cash balance. A token with a
similar name or symbol is not interchangeable with it.

## Funding your wallet [#funding-your-wallet]

Use **Deposit** in the web app. You can send `USDC` on
Base directly to the AGARA deposit-wallet address shown in
Settings.

Always verify the network, destination wallet, and collateral contract before
sending. An unsupported token does not increase your trading balance and may
be unrecoverable.

## Withdrawing collateral [#withdrawing-collateral]

Use **Withdraw** in the web app for the standard flow. A same-chain withdrawal
sends `USDC` to an address on Base.

You can instead request a quote for a supported destination token and network.
The quote identifies the amount, route, and expected output to review before
confirming. A refund to the AGARA account appears as a `DEPOSIT` portfolio
activity.

The standard withdrawal endpoint requires a current browser session. A
personal access token alone cannot authorize it. If you hold your wallet's key,
you can submit a supported direct withdrawal in a wallet-signed
[account batch](/docs/api-traders/account-batches).

See [Portfolio → Withdrawals](/docs/portfolio#withdrawals) for limits and
asynchronous settlement.

## Amounts in the API [#amounts-in-the-api]

The collateral has six decimal places, so API amounts use millionths:

| Human amount      | API value     |
| ----------------- | ------------- |
| `0.01` collateral | `"10000"`     |
| `1` collateral    | `"1000000"`   |
| `100` collateral  | `"100000000"` |

Amount fields are normally decimal strings so large values cross JSON
boundaries without losing precision. See [Conventions](/docs/conventions).

## How collateral relates to outcome tokens [#how-collateral-relates-to-outcome-tokens]

Collateral backs every complete binary pair. Splitting one collateral unit
creates one unit of each outcome token; merging a complete pair returns one
collateral unit. After resolution, a winning share pays one collateral unit
and a losing share pays zero. A market can instead resolve to a
[split](/docs/automatic-redemption#split-resolutions), where each outcome pays
part of one collateral unit, such as 0.37 per YES share and 0.63 per NO share;
a complete pair still pays one unit.

Continue with [CTF tokens](/docs/tokens/ctf) for the outcome-token model.