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

# Supported Blockchain Assets and Networks — Finrock

> Retrieve the full list of assets supported by Finrock. Use asset tickers in API requests for wallets, addresses, and transactions across 7 chain families.

Finrock supports a broad range of blockchain assets across UTXO chains, EVM-compatible networks, Tron, Solana, and several additional Layer-1 protocols. Every asset is identified by a string ticker that you pass in the `asset` field when creating wallets, generating addresses, or submitting transactions. Before going to production, fetch the live asset list from the API to confirm current support and exact ticker values.

## Fetching the Supported Assets List

Call the `/assets` endpoint to retrieve the authoritative, up-to-date list of every asset Finrock supports. This endpoint requires no authentication.

```bash theme={null}
curl --request GET \
     --url https://api.finrock.io/assets \
     --header 'accept: application/json'
```

The response is a JSON array of asset objects. Each entry includes the ticker, full name, blockchain network, and precision metadata you need to construct accurate transaction payloads.

<Tip>
  Always query the `/assets` endpoint programmatically rather than hardcoding a list of tickers. Finrock regularly adds new assets, and the live endpoint reflects any additions or deprecations immediately.
</Tip>

## Asset Ticker Conventions

Asset tickers follow a predictable naming convention:

* **Native coins** use their standard symbol directly — for example, `BTC`, `ETH`, `TRX`, `SOL`, `XRP`.
* **Tokens on a specific network** use the format `TOKEN_NETWORK` — for example:
  * `USDT_ETH` — Tether on Ethereum
  * `USDT_TRX` — Tether on Tron
  * `USDT_BSC` — Tether on BNB Smart Chain
  * `USDC_ETH` — USD Coin on Ethereum
  * `USDC_SOL` — USD Coin on Solana

This convention means the same token (e.g., USDT) can exist on multiple networks, each with its own distinct ticker. When your user wants to receive USDT, confirm which network they expect so you use the correct ticker.

## Using Tickers in the API

The `asset` field is required in the following core endpoints:

| Endpoint                                | Usage                                              |
| --------------------------------------- | -------------------------------------------------- |
| `POST /dac/v1/wallet`                   | Specify which asset the wallet will hold           |
| `POST /dac/v1/address`                  | Generate a deposit address for the specified asset |
| `POST /dac/v1/transaction`              | Denote the asset being transferred                 |
| `GET /dac/v1/network-fee-rates/{asset}` | Retrieve current fee rates for the asset           |
| `POST /dac/v1/estimate-fee`             | Estimate fees for a transaction in a given asset   |

Always pass the exact ticker string returned by the `/assets` endpoint. Ticker values are case-sensitive.

## Supported Chain Categories

The following sections outline the blockchain families Finrock currently supports. For the definitive list of supported tokens within each family, always refer to the live `/assets` endpoint.

<AccordionGroup>
  <Accordion title="UTXO Chains">
    UTXO-based chains use a Satoshi-per-byte fee model. The following networks are supported:

    | Ticker | Asset        |
    | ------ | ------------ |
    | `BTC`  | Bitcoin      |
    | `LTC`  | Litecoin     |
    | `DASH` | Dash         |
    | `DOGE` | Dogecoin     |
    | `BCH`  | Bitcoin Cash |

    Fee rates for UTXO chains are expressed in **Sat/Byte**. Use the fee rate endpoint to get current mempool fee rates before submitting a transaction.
  </Accordion>

  <Accordion title="EVM-Compatible Chains">
    Finrock supports all major EVM networks along with their ERC-20 and equivalent token standards:

    | Ticker   | Network           |
    | -------- | ----------------- |
    | `ETH`    | Ethereum          |
    | `BSC`    | BNB Smart Chain   |
    | `POL`    | Polygon           |
    | `BASE`   | Base              |
    | `ARB`    | Arbitrum          |
    | `AVAX`   | Avalanche C-Chain |
    | `OP_ETH` | Optimism          |
    | `FTM`    | Fantom            |
    | `CRO`    | Cronos            |
    | `ONE`    | Harmony           |
    | `KLAY`   | Klaytn            |

    Fee rates on EVM chains are expressed in **GWei**.
  </Accordion>

  <Accordion title="Tron">
    Tron and all TRC-20 tokens are fully supported. Common examples:

    | Ticker     | Asset            |
    | ---------- | ---------------- |
    | `TRX`      | Tron (native)    |
    | `USDT_TRX` | Tether on Tron   |
    | `USDC_TRX` | USD Coin on Tron |

    Fee rates on Tron are expressed in **Sun**. Finrock also supports Tron staking and unstaking — see the [Tron Staking reference](/api-reference/utilities/tron-stake) for details.
  </Accordion>

  <Accordion title="Solana">
    Solana's native coin and SPL tokens are supported:

    | Ticker     | Asset              |
    | ---------- | ------------------ |
    | `SOL`      | Solana (native)    |
    | `USDT_SOL` | Tether on Solana   |
    | `USDC_SOL` | USD Coin on Solana |

    Fee rates on Solana are expressed in **Lamport**.
  </Accordion>

  <Accordion title="Ripple (XRP)">
    | Ticker | Asset  |
    | ------ | ------ |
    | `XRP`  | Ripple |

    Fee rates on Ripple are expressed in **Drop**. Note that XRP transfers to exchanges or wallets that require a destination tag will fail if the tag is omitted. See the [XRP destination tag memo reference](/api-reference/utilities/xrp-dt-memo) for how to enforce memo requirements on your workspace.
  </Accordion>

  <Accordion title="Stellar (XLM)">
    | Ticker | Asset          |
    | ------ | -------------- |
    | `XLM`  | Stellar Lumens |

    Fee rates on Stellar are expressed in **Stroop**.
  </Accordion>

  <Accordion title="Cardano (ADA)">
    | Ticker | Asset   |
    | ------ | ------- |
    | `ADA`  | Cardano |

    Fee rates on Cardano are expressed in **Lovelace**.
  </Accordion>
</AccordionGroup>

<Note>
  The chain categories and example tickers listed above are illustrative. New assets are added on an ongoing basis. Always treat the `/assets` API response as the single source of truth for what your workspace can transact.
</Note>