Skip to main content
The stablecoin registry is Allium’s source of truth for stablecoin product and deployment metadata. It’s split into two grains:
  • stablecoins.registry.deployments — one row per (chain, address). Use this to resolve a specific on-chain contract/mint to its product, issuer, and peg metadata.
  • stablecoins.registry.catalog — one row per product (e.g. USDC), independent of chain. Use this for product-level rollups and issuer-level analysis.
Unique Key: stablecoins.registry.deployments — chain, address. stablecoins.registry.catalog — product_id.

Sample Query

Resolve a token address to its product and issuer, and check whether it’s a native or bridged deployment
Coming from crosschain.stablecoin.list or <chain>.assets.stablecoin_list? The old columns below map to these new columns. All other columns keep their names.crosschain.stablecoin.deployments and crosschain.stablecoin.catalog keep all their column names.

Table Columns

Grouping by base asset

The legacy base_asset grouped bridged and wrapped variants under one name. product_id gives each variant its own ID. To group them again:
crosschain.stablecoin.list is deprecated in favor of stablecoins.registry.deployments above (per-chain deployment grain, join to stablecoins.registry.catalog for product/issuer metadata). crosschain.stablecoin.catalog and crosschain.stablecoin.deployments are likewise deprecated in favor of stablecoins.registry.catalog and stablecoins.registry.deployments respectively.The legacy list includes a curated list of stablecoins with various denominations. This list is used to identify the list of stablecoins included in the crosschain.stablecoin.transfers table.Unique Key: chain, address

Table Columns

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.
  • 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).
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.