somnia.price Table: ez_asset_metadata Type: Base Table
What
This curated dimensional table provides comprehensive metadata for tokens and native assets across EVM blockchains. It serves as the authoritative source for asset information, with quality checks and verification status to ensure reliability.Key Use Cases
- Asset discovery and verification checking
- Cross-chain asset mapping and analysis
- Token metadata lookup for display purposes
- Filtering for verified or native assets only
Important Relationships
- Join with ez_prices_hourly: For price data enrichment
- Join with ez_token_transfers: For transfer metadata
Commonly-used Fields
token_address: Contract address (NULL for native assets)symbol: Token ticker symbolname: Full asset namedecimals: Token decimal placesis_verified: Flipside verification statusis_native: Native asset flagblockchain: Network identifier
Sample Queries
Verified Asset DiscoveryColumns
| Column Name | Data Type | Description |
|---|---|---|
| TOKEN_ADDRESS | TEXT | Contract address of the token on the blockchain. NULL for native assets (ETH, AVAX, etc.). Example: ‘0xa0b86a33e6776a1e7f9f0b8b8b8b8b8b8b8b8b8b’ |
| ASSET_ID | TEXT | Unique identifier for the asset from the price provider. Provider-specific ID format. Example: ‘ethereum’ |
| SYMBOL | TEXT | Token ticker symbol as commonly recognized. Usually 3-5 uppercase characters. Example: ‘WETH’ |
| NAME | TEXT | Full name of the asset or token. More descriptive than symbol. Example: ‘Wrapped Ether’ |
| DECIMALS | NUMBER | Number of decimal places for the token. Most ERC-20 tokens use 18 decimals, USDC/USDT use 6, WBTC uses 8. Example: 18 |
| BLOCKCHAIN | TEXT | The blockchain network where the asset exists. Lowercase by convention. Example: ‘ethereum’ |
| IS_NATIVE | BOOLEAN | Boolean indicating if the asset is the blockchain’s native currency. TRUE for ETH on Ethereum, AVAX on Avalanche, etc. Example: true |
| IS_DEPRECATED | BOOLEAN | Flag indicating if the asset is no longer actively supported. TRUE for deprecated assets that may have stale prices. Example: false |
| IS_VERIFIED | BOOLEAN | Boolean indicating Flipside team verification of the asset. TRUE for manually verified assets with validated metadata. Example: true |
| IS_VERIFIED_MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | IS_VERIFIED_MODIFIED_TIMESTAMP column |
| EZ_ASSET_METADATA_ID | TEXT | Primary 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_TIMESTAMP | TIMESTAMP_NTZ | UTC 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_TIMESTAMP | TIMESTAMP_NTZ | UTC 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: |