> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flipsidecrypto.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data Freshness

> Understanding Flipside's blockchain data update schedules and latency targets

Flipside continuously ingests and processes blockchain data across 30+ networks. This page explains
our update frequencies, latency expectations, and data quality standards.

## Data quality guarantee

Flipside runs **40,000+ automated tests** continuously to ensure data quality while maintaining
sub-24 hour latency. These tests validate:

* Block sequence completeness
* Transaction count accuracy
* Event log decoding correctness
* Label and metadata consistency
* Cross-table referential integrity

## How data flows through Flipside

<Steps>
  <Step title="Raw ingestion">
    Blocks, transactions, and logs are ingested as they're produced on-chain in real-time.
  </Step>

  <Step title="Core processing">
    Raw data is decoded, enriched with labels, and loaded into Core tables (blocks, transactions,
    logs, traces).
  </Step>

  <Step title="Curated processing">
    DeFi, NFT, Price, and Stats tables are derived from Core data with additional protocol-specific logic and curation.
  </Step>
</Steps>

**Result:** Different table types have different latency targets based on processing complexity.

## Latency targets by schema

### Core schema

Core tables are updated most frequently as they represent the foundation of all blockchain data.

| Table Type          | Latency Target  | Example Tables                |
| ------------------- | --------------- | ----------------------------- |
| **Blocks**          | 30 min - 1 hour | `fact_blocks`                 |
| **Transactions**    | 30 min - 1 hour | `fact_transactions`           |
| **Event logs**      | 30 min - 1 hour | `fact_event_logs`             |
| **Traces**          | 30 min - 1 hour | `fact_traces` (EVM chains)    |
| **Token transfers** | 1-2 hours       | `ez_token_transfers`          |
| **Decoded data**    | 1-2 hours       | `ez_decoded_event_logs`       |
| **Labels**          | 1-24 hours      | `dim_labels`, `dim_contracts` |

<Note>
  Latency can vary by blockchain. High-throughput chains like Solana may have slightly higher
  latency during peak activity.
</Note>

### DeFi schema

DeFi tables require additional processing to decode protocol-specific logic across multiple DeFi
protocols.

| Table Type           | Latency Target | Example Tables            |
| -------------------- | -------------- | ------------------------- |
| **DEX swaps**        | 1-4 hours      | `ez_dex_swaps`            |
| **Lending deposits** | 2-6 hours      | `ez_lending_deposits`     |
| **Lending borrows**  | 2-6 hours      | `ez_lending_borrows`      |
| **Liquidations**     | 2-6 hours      | `ez_lending_liquidations` |
| **Bridge activity**  | 2-8 hours      | `ez_bridge_activity`      |
| **Liquidity pools**  | 2-8 hours      | `ez_liquidity_pools`      |

### NFT schema

NFT tables are updated as marketplace activity is processed and decoded.

| Table Type              | Latency Target | Example Tables        |
| ----------------------- | -------------- | --------------------- |
| **NFT sales**           | 1-6 hours      | `ez_nft_sales`        |
| **NFT transfers**       | 1-4 hours      | `ez_nft_transfers`    |
| **NFT mints**           | 2-6 hours      | `ez_nft_mints`        |
| **Collection metadata** | 1-24 hours     | `dim_nft_collections` |

### Price schema

Price data is aggregated from multiple on-chain and off-chain sources.

| Table Type         | Latency Target | Example Tables       |
| ------------------ | -------------- | -------------------- |
| **Hourly prices**  | 1-2 hours      | `ez_prices_hourly`   |
| **Asset metadata** | 1-24 hours     | `dim_asset_metadata` |

### Stats schema

Stats tables contain pre-computed aggregates and metrics.

| Table Type       | Latency Target | Example Tables           |
| ---------------- | -------------- | ------------------------ |
| **Daily stats**  | 2-12 hours     | `ez_core_metrics_daily`  |
| **Hourly stats** | 1-4 hours      | `ez_core_metrics_hourly` |

## Blockchain-specific considerations

### EVM chains (Ethereum, Arbitrum, Optimism, etc.)

* **Block finality:** Most EVM chains have probabilistic finality
* **Reorgs:** Chain reorganizations can occur, especially near the chain head
* **Best practice:** Allow 10-15 minute buffer for finality before considering data complete

### Solana

* **High throughput:** Solana produces blocks every \~400ms
* **Skipped slots:** Some slots may be skipped due to validator issues (this is normal)
* **Latency:** May be slightly higher during network congestion or high activity periods

### Bitcoin

* **Block time:** \~10 minutes average between blocks
* **Confirmations:** Consider waiting for 6+ confirmations (60+ minutes) for transaction finality
* **Updates:** Bitcoin data updates less frequently than other chains due to slower block times

## Data access methods

Flipside blockchain data is available through multiple products:

<CardGroup cols={2}>
  <Card title="Snowflake Data Shares" icon="snowflake" href="/snowflake-data-shares/overview">
    Direct SQL access in your Snowflake account

    [See Snowflake-specific freshness guide →](/snowflake-data-shares/data-freshness)
  </Card>

  <Card title="FlipsideAI" icon="robot" href="/flipsideai">
    Conversational blockchain data analysis

    Always uses the latest available data
  </Card>
</CardGroup>

## When data might be delayed

Data updates may be delayed beyond normal latency targets due to:

<AccordionGroup>
  <Accordion title="Blockchain network issues" icon="triangle-exclamation">
    * Network congestion or outages
    * Validator or RPC node issues
    * Chain reorganizations or forks
    * Upgrade or maintenance periods
  </Accordion>

  <Accordion title="High activity periods" icon="chart-line">
    * Major protocol launches or events - Market volatility causing high transaction volumes - NFT
      drops or mints with extreme activity
  </Accordion>

  <Accordion title="Schema changes" icon="wrench">
    * New protocol integrations
    * Table structure updates
    * Decoder improvements or fixes
  </Accordion>
</AccordionGroup>

In these cases, data will catch up once the issue is resolved. Flipside monitors all pipelines
continuously.

## Support

If you notice data is significantly stale or missing:

**Contact:** [data-shares@flipsidecrypto.com](mailto:data-shares@flipsidecrypto.com)

**What to expect:**

* Core tables more than 6 hours behind → investigate
* DeFi/NFT tables more than 24 hours behind → investigate
* No updates in 48+ hours → likely requires attention

Include in your report:

* Which blockchain and schema
* Specific table(s) affected
* Last observed timestamp
* Your use case and urgency

## Next steps

<CardGroup cols={2}>
  <Card title="Schema overview" icon="sitemap" href="/blockchain-data/schema-overview">
    Understand how blockchain data is organized
  </Card>

  <Card title="Snowflake Data Shares" icon="snowflake" href="/snowflake-data-shares/data-freshness">
    Snowflake-specific freshness monitoring
  </Card>

  <Card title="Ethereum data" icon="ethereum" href="/blockchain-data/ethereum/overview">
    Explore Ethereum tables and schemas
  </Card>

  <Card title="Solana data" icon="coins" href="/blockchain-data/solana/overview">
    Explore Solana tables and schemas
  </Card>
</CardGroup>