Registry

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

select
    d.chain,
    d.address,
    d.symbol,
    d.stablecoin_type,
    d.is_native,
    c.issuer_name,
    c.peg_mechanism
from stablecoins.registry.deployments d
join stablecoins.registry.catalog c on d.product_id = c.product_id
where c.product_id = 'usdc' -- example product_id
order by d.chain

Table Columns

stablecoins.registry.deployments
stablecoins.registry.catalog

Column Name	Description
product_id	Internal Allium identifier for the stablecoin product. Join key to `stablecoins.registry.catalog`.
product_name	Display name of the stablecoin product (e.g. USD Coin).
product_symbol	Ticker symbol of the product (e.g. USDC), consistent across chains.
issuer_id	Entity that issues or backs the stablecoin (e.g. circle, tether).
is_native	True if this is the issuer’s canonical deployment on this chain, false if it’s a bridged/wrapped representation.
is_verified	True if this deployment has been manually verified by Allium.
stablecoin_type	Classification of the stablecoin mechanism (e.g. fiat_backed, crypto_backed, yield_bearing).
currency	Fiat or reference currency this stablecoin is pegged to, as a lowercase ISO code (e.g. usd, eur, jpy).
peg_mechanism	Mechanism used to maintain the peg (e.g. fiat_backed, crypto_overcollateralized, algorithmic).
chain	Blockchain of the deployment.
address	Contract address (or mint, for Solana) of the deployment. Unique per chain.
decimals	Decimals of the token, used for normalization.
symbol	On-chain symbol of the token, as reported by the deployment itself (may differ from `product_symbol` for wrapped/bridged variants).
name	On-chain name of the token.
token_type	Token standard of the deployment (e.g. erc20, trc20, spl).
status	Allium registry lifecycle status for the parent product (`active` or `deprecated`).
is_active	Boolean derived from `status`. True when the product is active in Allium’s registry.
status_reason	Human-readable explanation when `status` is not the default `active`. Null otherwise.
status_source_reference	Optional reference (PR, issue, ticket) supporting a non-default `status`.
_created_at	Timestamp this deployment row was first created.
_updated_at	Timestamp this deployment row was last updated.

Column Name	Description
product_id	Internal Allium identifier for the stablecoin product.
product_name	Display name of the stablecoin product (e.g. USD Coin).
product_symbol	Ticker symbol of the product (e.g. USDC).
issuer_id	Entity that issues or backs the stablecoin.
issuer_name	Display name of the issuer (e.g. Circle, Tether).
currency	Fiat or reference currency this product is pegged to, lowercase ISO code.
peg_mechanism	Mechanism used to maintain the peg.
is_native	True if the product has at least one native (issuer-canonical) deployment.
underlying_product_id	For wrapped/derivative products, the `product_id` of the underlying stablecoin this one is based on. Null for base products.
stablecoin_type	Classification of the stablecoin mechanism.
is_tokenized_deposit	True if this product is a tokenized bank deposit rather than a collateral-backed or algorithmic stablecoin.
deployment_count	Number of distinct on-chain deployments of this product across all chains.
_updated_at	Timestamp this catalog row was last updated.

Legacy Schema

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

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.

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

Overview

Data Verticals

Solana

Hyperliquid

Lighter

Bitcoin Ecosystem

EVM

Cosmos Ecosystem

Move Ecosystem

Other Ecosystems

Sample Query

Table Columns

Table Columns

​Sample Query

​Table Columns

​Table Columns

Sample Query

Table Columns

Table Columns