somnia.defi Table: ez_protocol_tvl Type: View
What
This table provides daily Total Value Locked (TVL) metrics for DeFi protocols across EVM-compatible blockchains. It aggregates values by platform to track liquidity and value deposited in various DeFi applications. Methods may vary by protocol and blockchain.Methodology Note
For certain protocols (e.g., Uniswap v2/v3/v4 and forks), TVL is calculated only for pools where both tokens are verified. This filtering removes low-quality or spam pools, providing a more accurate representation of “real” TVL rather than values inflated by low-liquidity tokens.Key Use Cases
- Tracking protocol TVL growth and trends over time
- Comparing TVL across different protocols and platforms
- Analyzing protocol adoption and liquidity depth
- Building TVL-based dashboards and metrics
Commonly-used Fields
block_date: Date of the TVL snapshottvl_usd: Total Value Locked in USDprotocol: Name of the DeFi protocol (e.g., Uniswap, Aave)version: Protocol version (e.g., v2, v3)platform: Specific deployment or platform identifier
Sample queries
Columns
| Column Name | Data Type | Description |
|---|---|---|
| BLOCK_DATE | DATE | The date of the daily TVL snapshot. Example: ‘2025-06-10’ |
| TVL_USD | FLOAT | The total value locked in USD for the protocol on the given date. Values exceeding $1 trillion (1e12) are excluded to filter out erroneous pricing data. Example: 1500000000 |
| PROTOCOL | TEXT | The name of the DeFi protocol. Example: ‘Uniswap’ |
| VERSION | TEXT | The version of the protocol deployment. Example: ‘v3’ |
| PLATFORM | TEXT | The specific platform or deployment identifier for the protocol. Example: ‘uniswap-v3-ethereum’ |
| 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: |
| 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: |
| EZ_PROTOCOL_TVL_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. |