Timeline
Table Mappings
Breaking Column Changes
These columns are removed in the new schema. Update queries before October 31, 2026.crosschain.stablecoin.transfers → stablecoins.core.transfers
crosschain.stablecoin.transfers → stablecoins.core.transfers
Column map (all other columns keep their names):
token_type→token_typeonstablecoins.registry.deployments(join onchainandaddress = token_address)base_asset→ No single column. See Grouping by base assetis_bridge→ Closest isstablecoin_type = 'bridged'(values differ)_fact_created_at→_created_at_fact_updated_at→_updated_at_dim_updated_at→_metadata_updated_attransaction_hash,unique_id(TON) → Same names (values differ)token_address(Stellar) → Same name (format differs)token_symbol(Hyperliquid) → Same name (values differ)transaction_from_address,transaction_to_address,block_number,block_hash,transfer_type→ Not on this table. Use<chain>.stablecoins.transferstoken_acc_from,token_acc_to→ Not on this table. Usesolana.stablecoins.transfers
stablecoins.core.transfers):PRODUCT_ID— links tostablecoins.registry.catalogIS_NATIVE— true for native-chain stablecoinsSTABLECOIN_TYPE— fiat-backed, crypto-backed, algorithmic, etc.USD_EXCHANGE_RATE— rate at transfer timeISSUER_ID— links to issuer registryPEG_MECHANISM
crosschain.stablecoin.list → stablecoins.registry.catalog + stablecoins.registry.deployments
crosschain.stablecoin.list → stablecoins.registry.catalog + stablecoins.registry.deployments
crosschain.stablecoin.list combined product-level and deployment-level data in one table. The new schema splits them:stablecoins.registry.catalog— one row per stablecoin product (USDC, USDT, etc.)stablecoins.registry.deployments— one row per chain/address deployment
list by chain, use stablecoins.registry.deployments WHERE chain = '<chain>'. For product metadata, join on product_id.Column map on stablecoins.registry.deployments (all other columns keep their names):base_asset→ No single column. See Grouping by base assetis_bridge→ Closest isstablecoin_type = 'bridged'(values differ)stablecoin_id→ Removed.product_iduses different IDssymbol→ Same name (values differ)id,source,content_hash→ Removed
crosschain.stablecoin.supply_beta → stablecoins.core.supply_daily
crosschain.stablecoin.supply_beta → stablecoins.core.supply_daily
Column map (all other columns keep their names):
symbol→ Removed. Closest islower(token_symbol)(values differ)name→ Removed. Closest istoken_name(values differ)stablecoin_id→ Removed.product_iduses different IDssupply→ Removed. Closest istotal_supply(values differ)supply_usd→ Removed. Closest istotal_supply_usd(values differ)supply_delta→ Daily change intotal_supplysupply_delta_usd→ Daily change intotal_supply_usdnon_circulating_supply→total_supply - circulating_supply(values differ)non_circulating_supply_usd→total_supply_usd - circulating_supply_usd(values differ)base_asset→ No single column. See Grouping by base assetis_bridge→ Closest isstablecoin_type = 'bridged'(values differ)_changed_since_full_refresh→ Removed
ADJUSTED_CIRCULATING_SUPPLY— nets out bridge escrows, protocol collateral, and savings-vault depositsPRICE_USD— daily close price
<chain>.assets.stablecoin_list → stablecoins.registry.deployments
<chain>.assets.stablecoin_list → stablecoins.registry.deployments
Per-chain
assets.stablecoin_list tables are discontinued on all 28 chains that have one. Use stablecoins.registry.deployments filtered by chain instead. The crosschain table has the same data with additional registry metadata.crosschain.metrics.stablecoin_volume → stablecoins.metrics.volume_daily
crosschain.metrics.stablecoin_volume → stablecoins.metrics.volume_daily
Column map (all other columns keep their names):
base_asset→ No single column. See Grouping by base assettransfer_count,transfer_tx_count,transfer_volume,transfer_volume_usd→ Same names (values differ)token_symbol→ Same name (values differ)avg_transfer_count→transfer_count / transfer_tx_countavg_transfer_volume→transfer_volume / transfer_tx_countavg_transfer_volume_usd→transfer_volume_usd / transfer_tx_countentity_adjusted_single_direction_max_transfer_tx_count→adjusted_transfer_tx_count(different methodology)entity_adjusted_single_direction_max_transfer_volume_usd→adjusted_volume_usd(different methodology)entity_adjusted_single_direction_max_transfer_volume→ Removedsingle_direction_max_transfer_volume,single_direction_max_transfer_volume_usd→ Removedsingle_direction_net_transfer_volume,single_direction_net_transfer_volume_usd→ Removedtransfer_volume_is_anomaly→ Removed
PRODUCT_ID,ISSUER_ID,PEG_MECHANISM,TOKEN_NAME,IS_NATIVE,STABLECOIN_TYPE— registry metadata joined in directlySENDER_COUNT,RECIPIENT_COUNTADJUSTED_TRANSFER_COUNT— adjusted transfer-level count, alongside the renamedADJUSTED_TRANSFER_TX_COUNT(formerlyENTITY_ADJUSTED_SINGLE_DIRECTION_MAX_TRANSFER_TX_COUNT)HAS_ADJUSTED_VOLUME— check before relying onADJUSTED_VOLUME_USD; it isnull(not zero) on chains wherehas_adjusted_volume = false
Chain-level tables (assets.stablecoin_*)
The per-chain assets.stablecoin_* tables also reach end of lifecycle on October 31, 2026 and are deleted on December 1, 2026, on every chain listed below, EVM and non-EVM. Each chain already has a <chain>.stablecoins.transfers replacement.
EVM chains (30)
EVM chains (30)
arbitrum, avalanche, base, berachain, blast, bob, bsc, celo, codex,
ethereum, hyperevm, ink, linea, mode, monad, optimism, plasma, plume,
polygon, polygon_zkevm, scroll, sei, soneium, sonic, stable, tempo,
unichain, worldchain, x_layer, zksync
bob, tempo, and x_layer only have stablecoin_transfers, with no stablecoin_list.Non-EVM chains (9)
Non-EVM chains (9)
aptos, hyperliquid, near, solana, starknet, stellar, sui, ton, tronOnly
solana has assets.stablecoin_list. The other non-EVM chains only have stablecoin_transfers.<chain>.assets.stablecoin_transfers → <chain>.stablecoins.transfers
<chain>.assets.stablecoin_transfers → <chain>.stablecoins.transfers
Column map (all other columns keep their names):
base_asset→ No single column. See Grouping by base assetis_bridge→ Closest isstablecoin_type = 'bridged'(values differ)_metadata_created_at(Aptos, NEAR, Solana, Stellar, Sui, TON) → Removedbatch_instruction_index(Solana) → Removedtransaction_hash,unique_id(TON) → Same names (values differ)
PRODUCT_ID: links tostablecoins.registry.catalogIS_NATIVE: true for native-chain stablecoinsSTABLECOIN_TYPE: fiat-backed, crypto-backed, algorithmic, etc.USD_EXCHANGE_RATE: rate at transfer time (EVM chains and hyperliquid only)
Why we’re migrating
Thestablecoins.* schema replaces the crosschain.stablecoin.* family with:
- Registry metadata joined in —
product_id,issuer_id,is_native, andstablecoin_typeare available directly onstablecoins.core.transfers,stablecoins.core.supply_daily, andstablecoins.metrics.volume_daily, without a separate join. - A cleaner registry split —
stablecoins.registry.deployments(per chain/address) andstablecoins.registry.catalog(per product) replace the overlappingcrosschain.stablecoin.list,.catalog, and.deploymentstables. - New tables with no legacy equivalent —
stablecoins.core.supply_change(mint/burn events) andstablecoins.core.balances_daily(daily forward-filled holder balances). - A more conservative supply methodology —
stablecoins.core.supply_dailyaddsadjusted_circulating_supply, which nets out bridge escrows, protocol collateral, and savings-vault deposits on top of the issuer-basis exclusions already incirculating_supply.
Migration Checklist
- Review the new schema — See the Stablecoins docs for full column-level detail.
- Update your queries — Replace legacy references using the table mapping above. Pay attention to removed columns.
- Test your applications — Run existing queries against the new schema to confirm parity.
- Deploy changes — Update your workflows to use
stablecoins.*before October 31, 2026.