gitbook/data/flipside-data/table-freshness-targets.md

Table Freshness Targets

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.

{% hint style="warning" %} Effective December 9th, 2024

Tables in non-core schemas like defi/nft/gov/stats/etc. that are not [db].core.[table] are subject to changes in their latency. See the updated latency by category below in yellow. {% endhint %}

Blockchain	CORE - Target Latency from Chain Head	NON-CORE - Target Latency from Chain Head	Category	Category
Aleo	30 Minutes	4 Hours		Core
Aptos	30 Minutes	1 Hour	Non-Core	Core
Arbitrum	1 Hour	6 hours		Core
Aurora	1 Hour	24 hours		Core
Avalanche	30 Minutes	1 Hour		Core
Axelar	1 Hour	1 Hour		Core
Base	1 Hour	4 Hours		Core
Bitcoin	1 Hour	6 Hours		Core
Blast	30 Minutes	4 Hours		Core
BSC	1 Hour	6 Hours		Core
CoreDao	30 Minutes	4 Hours
Cosmos	12 Hours	24 Hours		Core
Eclipse	30 Minutes	4 Hours
Ethereum	30 Minutes	4 Hours		Core
Flow	30 Minutes	1 Hour		Core
Gnosis	1 Hour	6 Hours		Core
Kaia	30 Minutes	4 Hours		Core
Mantle	30 Minutes	4 Hours
Movement	30 Minutes	4 Hours
NEAR	1 Hour	1.5 Hours		All Models
Optimism	1 Hour	6 Hours		Core
Osmosis	12 Hours	24 Hours		Core
Polygon	1 Hour	6 Hours		Core
Sei	30 Minutes	1 Hour		Core
Solana	30 Minutes	4 Hours		Core
Terra	12 hours	24 Hours		Core
Thorchain	2 hours	4 Hours		All Models