Table Freshness Targets
The following can be tuned/adjusted.
Flipside's tables target the following latency schedule from Chain Head. The following can be tuned based on use cases/needs. Please reach out if you have a specific use case that requires a latency closer to the chain head and our team would be happy to discuss solutions with you.
Flipside refreshes data across three dimensions fact tables, dim tables, and ez tables.
Blockchain | Category (Fact, Dim, Ez) | Target Latency from Chain Head |
|---|---|---|
Arbitrum | Fact + Dim + EZ | 30 minutes |
Avalanche | Fact + Dim + EZ | 30 minutes |
Avalanche | decoded_event_logs | 2.5 hours |
Axelar | Fact + Dim | 1.5 hours |
Axelar | EZ | 2 hours |
BSC | Fact + Dim + EZ | 2 hours |
Cosmos | Fact + Dim + Ez | 15 hours |
Ethereum | Fact + Dim | 20 minutes |
Ethereum | Ez | 1 hour |
Ethereum | Balances | 4 hours |
Flow | Fact + Dim + Ez | 45 Minutes |
Gnosis | Fact + Dim + Ez | 2 hours |
NEAR | Fact + Dim | 2 hours |
NEAR | Ez | 3 hours |
Optimism | Fact + Dim + Ez | 35 minutes |
Osmosis | Fact + Dim + Ez | 11 hours |
Osmosis | ez_pools | 24 hours |
Polygon | Fact + Dim + Ez | 40 minutes |
Polygon | decoded_event_logs | 2.5 hours |
Solana | Fact + Dim | 40 Minutes |
Solana | Ez | 1 hour |
Terra | Fact + Dim + Ez | 24 hours |
Thorchain | Fact + Dim + Ez | 2 hours |
Last modified 5mo ago