Flipside Docs
Search
K

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
Target Latency from Chain Head
Aptos
Core/Non-Core
30 Minutes/1 hour
Arbitrum
Core/Non-Core
1 hour/2 hours
Aurora
Core
1 hour
Avalanche
Core/Non-Core
1 hour/2 hours
Axelar
Core/Non-Core
1 hour/2 hours
Base
Core/Non-Core
1 hour/2 hours
Bitcoin
Core/Non-Core
1 hour/2 hours
BSC
Core/Non-Core
1 hour/2 hours
Cosmos
Core/Non-Core
Ethereum
Core/Non-Core
30 minutes/1 hour
Flow
Core/Non-Core
1 hour/2 hours
Gnosis
Core/Non-Core
1 hour/2 hours
NEAR
All Models
2 hours
Optimism
Core/Non-Core
1 hour/2 hours
Osmosis
Core/Non-Core
Polygon
Core/Non-Core
1 hour/2 hours
Solana
Core/Non-Core
30 Minutes/1 hour
Terra
Core/Non-Core
Sei
Core/Non-Core
1 hour/2 hours
Thorchain
All Models
2 hours