tron.price Table: ez_asset_metadata Type: Base Table
What
This table provides metadata for all assets (tokens and native TRX) tracked in the price schema. It includes verification status, provider information, and token properties. Use this to discover which assets have price data available.Key Use Cases
- Discovering which tokens have price data available
- Looking up token addresses by symbol or name
- Checking verification and deprecation status of assets
- Finding asset identifiers for cross-referencing with price providers
Commonly-used Fields
token_address: Contract address (NULL for native TRX)symbol: Token ticker symbolname: Full asset namedecimals: Token decimal placesis_verified: Whether the Flipside team has verified this asset
Columns
| Column Name | Data Type | Description |
|---|---|---|
| TOKEN_ADDRESS | TEXT | Contract address of the token on the blockchain, in 0x-prefixed hex format. NULL for native TRX. Example: ‘0xa614f803b6fd780986a42c78ec9c7f77e6ded13c’ |
| ASSET_ID | TEXT | Unique identifier for the asset from the upstream price provider. Example: ‘tron’ |
| SYMBOL | TEXT | Token ticker symbol as commonly recognized. Example: ‘USDT’ |
| NAME | TEXT | Full name of the asset or token. Example: ‘Tether USD’ |
| DECIMALS | NUMBER | Number of decimal places for the token. TRX uses 6 decimals; most TRC-20 tokens use 18. Example: 6 |
| BLOCKCHAIN | TEXT | The blockchain network where the asset exists. Example: ‘tron’ |
| IS_NATIVE | BOOLEAN | Boolean indicating if the asset is the blockchain’s native currency (TRX). |
| IS_DEPRECATED | BOOLEAN | Flag indicating if the asset is no longer actively supported or tracked. |
| IS_VERIFIED | BOOLEAN | Boolean indicating Flipside team verification of the asset. |
| 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: VARCHAR containing composite key generated using MD5 hash of the relevant columns. Usage: Deduplication in incremental loads Join operations for data quality checks Troubleshooting specific records |
| 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 |
| MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp of the most recent update to this record. Format: TIMESTAMP_NTZ Use Cases: Tracking data corrections and reprocessing Monitoring incremental model updates Data quality audits |