> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tplus.cx/llms.txt
> Use this file to discover all available pages before exploring further.

# Asset parameters

> Token-specific parameters: addresses, decimals, deposit caps, vaults, and target weight.

Token-specific parameters are published onchain in the registry and mirrored by the OMS. They are separate from per-asset [risk parameters](/trading/margin) (collateral and liability factors, IM factors, open-interest caps), which are served by `GET /registry/risk-parameters`.

`GET /registry/assets` returns one entry per listed (asset, chain), corresponding to the onchain `IRegistry.AssetData`:

| Parameter                 | Meaning                                                                                       |
| ------------------------- | --------------------------------------------------------------------------------------------- |
| `index`                   | The Tplus asset index a pooled token credits to. See [Asset fungibility](/funds/fungibility). |
| `assetAddress`, `chainId` | The token's onchain address and the chain it lives on.                                        |
| `maxDeposits`             | Total deposit cap for the (asset, chain). A deposit past it credits an isolated balance.      |
| `max1hrDeposits`          | Rolling 1-hour deposit cap for the (asset, chain).                                            |
| `minWeight`               | The vault's minimum target weight, used by [rebalancing](/funds/rebalancing).                 |

Two parameters are read from separate endpoints:

* **Decimals** — each token's onchain decimals, used to normalize amounts to Tplus's 18-decimal internal units. `POST /registry/decimals`.
* **Vault address** — the deposit-vault contract per chain. `GET /registry/vaults`; never hardcode it.

Per-chain confirmation policy — how many confirmations before a deposit, withdrawal, or settlement is ingested — is listed under [Deposits](/funds/deposits#chains-and-confirmation-times).

Read these from the registry endpoints rather than hardcoding them; values change by governance.