Skip to main content
Important: The schemas listed below are deprecated and will be removed by December 18, 2025. Please migrate to the recommended alternatives as soon as possible.
Looking for crosschain.stablecoin.* or crosschain.metrics.stablecoin_volume? See the separate Stablecoin Schema Deprecation page — it’s on a different timeline than the schemas below.

Overview

Allium is deprecating legacy asset schemas across all major chains to simplify and standardize asset data tables. The new schema family introduces consistent naming conventions across blockchains. Starting December 18, 2025, the legacy schemas listed below will be deprecated and removed from allium catalog and respective shares. Please migrate to the new standardized schemas before this date.
Key clarification: The fungible_* tables (e.g., fungible_token_transfers, fungible_balances) contain both native token (e.g., ETH, MATIC, AVAX) and ERC20 token data. This was also the case with the legacy tables they replace. Use the token_type column to filter: NATIVE for native transfers, ERC20 for ERC20 transfers.

Summary

Table Mappings

Schema Changes & Column Mappings

Fungible Token Transfers

Important: The ASSETS.FUNGIBLE_TOKEN_TRANSFERS table contains both native and ERC20 token transfers, same as the legacy tables it replaces. Use the token_type column to filter: NATIVE for native transfers, ERC20 for ERC20 transfers.
When migrating from legacy ERC20 token transfer tables (e.g., ASSETS.ETH_ERC20_TOKEN_TRANSFERS) to the new ASSETS.FUNGIBLE_TOKEN_TRANSFERS schema, the following changes apply:

Column Renames

Value Changes

All other columns maintain the same names and types between the legacy and new schemas.

Token Prices

The token_prices_hourly_easy table is being deprecated in favor of common.prices.hourly.
The new hourly table does not provide the same abstraction of token prices across chains. This cross-chain abstraction feature is no longer supported. All other column names and types remain the same.

Migration Checklist

  • Review the new schema structure - Review available columns
  • Update your queries - Replace all references to legacy tables using the mappings above
  • Test your applications - Run existing queries against new schemas to ensure compatibility
  • Deploy changes - Update your workflows to use the new schema
  • Validate results - Verify data accuracy and performance
  • Complete migration by December 18, 2025 - Legacy schemas will be removed after this date

Key Benefits

The new schemas maintain full coverage with:
  • Unified fungible tables - native and ERC20 token data combined into single fungible_* tables, reducing query complexity
  • Standardized naming across all chains
  • Consistent chain logic and data structure
  • Maintenance and support of the new schemas

Support

If you need help with migration or have questions about deprecated schemas:
  • Review the recommended alternative schema documentation.
  • Reach out to our support team for migration assistance.