Skip to main content
Unlike the asset schema deprecations, no removal date has been set yet for crosschain.stablecoin.* or crosschain.metrics.stablecoin_volume. They remain queryable today, but all new stablecoin work should target the stablecoins.* schema — see the table mapping below and the Stablecoins docs for full column-level detail on each replacement table.

​
Table Mappings

​
EVM Chain-Level Tables Removed (assets.stablecoin_*)

An in-progress migration is removing <chain>.assets.stablecoin_transfers and <chain>.assets.stablecoin_list for all EVM chains listed below. Existing Snowflake tables are not dropped immediately, but they will soon stop receiving new data — queries against them will return increasingly stale results. Migrate to <chain>.stablecoins.transfers (transfers) and stablecoins.registry.deployments filtered by chain (list) now.
Affected chains (28): arbitrum, avalanche, base, berachain, blast, bsc, celo, codex, ethereum, hyperevm, ink, linea, mode, monad, optimism, plasma, plume, polygon, polygon_zkevm, scroll, sei, soneium, sonic, stable, tempo, unichain, worldchain, zksync. (tempo only ever had stablecoin_transfers, no stablecoin_list.) Not affected: Solana, Tron, Aptos, and other non-EVM chains — their assets.stablecoin_* tables are unchanged for now.

​
Why we’re migrating

The stablecoins.* schema replaces the crosschain.stablecoin.* family with:
  • Registry metadata joined in — product_id, issuer_id, is_native, and stablecoin_type are available directly on stablecoins.core.transfers, stablecoins.core.supply_daily, and stablecoins.metrics.volume_daily, without a separate join.
  • A cleaner registry split — stablecoins.registry.deployments (per chain/address) and stablecoins.registry.catalog (per product) replace the overlapping crosschain.stablecoin.list, .catalog, and .deployments tables.
  • New tables with no legacy equivalent — stablecoins.core.supply_change (mint/burn events) and stablecoins.core.balances_daily (daily forward-filled holder balances).
  • A more conservative supply methodology — stablecoins.core.supply_daily adds adjusted_circulating_supply, which nets out bridge escrows, protocol collateral, and savings-vault deposits on top of the issuer-basis exclusions already in circulating_supply.

​
Migration Checklist

  • Review the new schema — See the Stablecoins docs for full column-level detail on each stablecoins.* table.
  • Update your queries — Replace legacy crosschain.stablecoin.* / crosschain.metrics.stablecoin_volume references using the mapping above.
  • Test your applications — Run existing queries against the new schema to confirm parity.
  • Deploy changes — Update your workflows to use stablecoins.* going forward.

​
Support

If you need help with migration or have questions about this deprecation, reach out to our support team for assistance.