Skip to main content
The stablecoin registry has been split into two tables in the stablecoins.registry schema:

Registry: Catalog

Product-level stablecoin metadata — one row per stablecoin product (e.g. USDC, USDT, DAI) with peg currency, backing type, and issuer.

Registry: Deployments

Per-chain contract addresses — maps every (chain, address) to its canonical product_id, with native issuance flags.
These tables replace crosschain.stablecoin.list. The deployments table has a compatible schema with two additions: product_id and is_native.

​
Migration

Old query pattern (crosschain.stablecoin.list): 
select chain, address, symbol, currency
from crosschain.stablecoin.list
where currency = 'usd'
New query pattern (stablecoins.registry.deployments): 
select chain, address, symbol, currency, product_id, is_native
from stablecoins.registry.deployments
where currency = 'usd'
Key changes: base_asset and is_bridge are removed. Use product_id for stablecoin identity and is_native for chain-native vs. bridged/wrapped issuance. To replace base_asset = 'usdt', filter through the catalog: 
where product_id in (
    select product_id
    from stablecoins.registry.catalog
    where underlying_product_id = 'usdt'
        or product_id = 'usdt'
)
In stablecoins.core tables, registry address and symbol appear as token_address and token_symbol. See Filtering by stablecoin product for the full migration guide.