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

# Stablecoins List

> Table of main stablecoins (inclusive of other currencies) and their respective contract addresses across various chains.

The stablecoin list includes a list of curated stablecoins with various denominations. This list is used to identify the list of stablecoins to be included in the `crosschain.stablecoin.transfers` table.

**Unique Key**: `chain`, `address`

### Sample Query

### Table Columns

| Column Name | Description                                                                                                     |
| ----------- | --------------------------------------------------------------------------------------------------------------- |
| currency    | The ISO currency code (e.g. usd, eur, jpy, xau (gold)) of the stablecoin, in lower case.                        |
| base\_asset | The underlying stablecoin for stablecoins that are issued by third parties, such as bridges, or defi-protocols. |
| address     | The contract address of the stablecoin. The contract address for a stablecoin is unique on the blockchain.      |
| symbol      | Symbol of the token, in lower case by default.                                                                  |
| name        | Name of the token.                                                                                              |
| decimals    | Decimals of the token, used for normalization. This field is optional and may be null.                          |
| chain       | Blockchain of the where the stablecoin is based, in lower case.                                                 |
| is\_bridge  | When TRUE, this means that the stablecoin is bridged.                                                           |

<Tabs>
  <Tab title="Stablecoin Base Assets">
    Stablecoins can be broadly classified into their underlying **peg mechanism.**

    They can be fiat-backed, commodity-backed, algorithmic, crypto-backed (DAI), or a hybrid of many.

    For **fiat-backed stablecoins**, there is often a regulated entity involved in the issuance and management of the stablecoin ensuring its stability and value. These entity-issued stablecoins are said to be "native".

    Using USDC as an example, there are multiple variants of USDC:

    * A **native stablecoin** refers to a stablecoin issued directly from a regulated entity such as Circle, which is redeemable for the underlying asset (be it US Dollars, Euros, etc). Circle maintains a list of their native stablecoins [here](https://www.circle.com/en/multi-chain-usdc).

    * A **bridged stablecoin** refers to a stablecoin that is issued by a third-party application (e.g. Wormhole, Axelar, etc.) issued by locking a native stablecoin in a smart contract on one blockchain to mint a bridged stablecoin on another blockchain.

    * A **defi variant stablecoin** refers to a stablecoin issued by a decentralized application (e.g. Compound, Aave, etc.) and is backed by the underlying collateral assets in the protocol. One example is Aave interest-bearing USDC [(aUSDC)](https://etherscan.io/address/0xbcca60bb61934080951369a648fb03df4f96263c).

    The `base_asset` field in the stablecoin list aims to capture the underlying stablecoin of a token. For example, Axelar USDC, Aave USDC, and Bridged USDC.e on Avalanche will all be labelled as `usdc` its `base_asset`.
  </Tab>
</Tabs>