Skip to main content
Schema: somnia.price Table: dim_asset_metadata Type: Base Table

​
What

This table provides comprehensive metadata for all assets (tokens and native assets) tracked in the price schema across EVM blockchains. It includes provider, asset identifiers, names, symbols, contract addresses, blockchain, and verification status.

​
Key Use Cases

  • Join price data to asset metadata for enriched analysis
  • Cross-chain asset analysis and mapping
  • Asset discovery and verification status checking
  • Provider-specific data source analysis

​
Important Relationships

  • Join with ez_prices_hourly: For price time series data
  • Join with core.dim_contracts: For contract metadata

​
Commonly-used Fields

  • provider: Data source (coingecko, coinmarketcap, etc.)
  • asset_id: Provider-specific unique identifier
  • blockchain: Network identifier
  • token_address: Contract address (NULL for native assets)
  • symbol: Token ticker symbol
  • name: Full asset name

​
Sample Queries

Basic Asset Lookup 
SELECT *
FROM <blockchain_name>.price.dim_asset_metadata
WHERE blockchain = 'ethereum'
ORDER BY symbol;

​
Columns

Column NameData TypeDescription
TOKEN_ADDRESSTEXTContract address of the token on the blockchain. NULL for native assets (ETH, AVAX, etc.). Example: ‘0xa0b86a33e6776a1e7f9f0b8b8b8b8b8b8b8b8b8b’
ASSET_IDTEXTUnique identifier for the asset from the price provider. Provider-specific ID format. Example: ‘ethereum’
SYMBOLTEXTToken ticker symbol as commonly recognized. Usually 3-5 uppercase characters. Example: ‘WETH’
NAMETEXTFull name of the asset or token. More descriptive than symbol. Example: ‘Wrapped Ether’
BLOCKCHAINTEXTThe blockchain network where the asset exists. Lowercase by convention. Example: ‘ethereum’
BLOCKCHAIN_IDTEXTThe numeric or string identifier for the blockchain on which the asset exists. Used for cross-chain mapping. Example: ‘1’
PROVIDERTEXTData source that provided the price information. Values include ‘coingecko’, ‘coinmarketcap’, ‘dex_aggregated’. Example: ‘coingecko’
DIM_ASSET_METADATA_IDTEXTPrimary key - unique identifier for each row ensuring data integrity. Format: Usually VARCHAR containing composite key generated using MD5 hash of the relevant columns. Example: MD5(blocknumber, txhash, trace_index) Usage: Deduplication in incremental loads Join operations for data quality checks Troubleshooting specific records Important: Implementation varies by table - check table-specific documentation.
INSERTED_TIMESTAMPTIMESTAMP_NTZUTC timestamp when the record was first added to the Flipside database. Format: TIMESTAMP_NTZ Use Cases: Data freshness monitoring Incremental processing markers Debugging data pipeline issues SLA tracking Query Example:
MODIFIED_TIMESTAMPTIMESTAMP_NTZUTC timestamp of the most recent update to this record. Format: TIMESTAMP_NTZ Triggers for Updates: Data corrections Enrichment additions Reprocessing for accuracy Schema migrations Monitoring Usage: