Skip to main content
FlipsideAI is fully transparent. Every query, every calculation, every data point is accessible for validation, download, and further analysis.

Understanding Flipside Data boxes

When FlipsideAI runs a query, results appear in Flipside Data boxes—expandable containers that show:
1

Query preview

Summary of the query that was run
2

Results table

Data returned by the query
3

Full SQL

Complete, executable SQL query
4

Download option

Export results as CSV

Expanding data boxes

Click the data box to expand and see:
  • Full SQL code
  • Tables queried
  • Filters applied
  • Joins and aggregations
Use this to verify FlipsideAI’s approach.
See the raw data:
  • All columns returned
  • Row-by-row detail
  • Data types and formatting
Cross-check against your expectations.
See metadata:
  • Execution time
  • Rows returned
  • Data freshness (when the underlying tables were last updated)

Validating results

Always validate before trusting the numbers, especially for high-stakes decisions.

Sanity checks

  • Compare to known benchmarks
  • Inspect the SQL
  • Ask for validation
  • Test with known cases
Cross-reference with external sources:
  • TVL: Check against DeFiLlama, DefiPulse
  • Prices: Verify with CoinGecko, CoinMarketCap
  • Volumes: Compare to protocol dashboards or Dune Analytics
If numbers diverge significantly, investigate why.

Common data quality issues

Watch out for: - Incomplete data: Some chains or protocols may have data gaps - Token vs USD amounts: Verify whether values are in token units or USD - Duplicate counting: In complex joins, rows might be double-counted - Stale data: Check when tables were last updated (especially for “current” metrics)
If you spot an issue, point it out:
"This TVL seems too low. Can you check if LP tokens are being counted correctly?"

Downloading data

CSV export

Every Flipside Data box has a download button:
1

Expand the data box

Click to open the query results
2

Click the download icon

Usually in the top-right of the data box
3

Save the CSV

File downloads with query results

What you get

  • All columns from the query
  • All rows (up to query limits)
  • Column headers
  • Raw data (no visualizations, just the numbers)

Use cases for CSV export

  • Further analysis: Import into Excel, Python, R, or your tool of choice
  • Archiving: Save snapshots for historical comparison
  • Sharing with non-technical stakeholders: Send raw data alongside visualizations
  • Custom visualizations: Build your own charts with the data

Running queries directly

Already know SQL? Skip the chat and run queries directly.

Paste SQL into chat

SELECT
  DATE_TRUNC('day', block_timestamp) AS date,
  COUNT(DISTINCT from_address) AS unique_users,
  SUM(amount_usd) AS volume_usd
FROM ethereum.defi.ez_dex_swaps
WHERE platform = 'uniswap-v3'
  AND block_timestamp >= '2024-01-01'
GROUP BY 1
ORDER BY 1
Paste this into chat, and FlipsideAI will:
  1. Execute the query
  2. Return results
  3. Offer to summarize, visualize, or analyze further

Why run queries directly?

  • Precision: You control exactly what data is retrieved
  • Speed: Skip the “figure out what I want” step
  • Reproducibility: Same query → same results every time
  • Learning: See how FlipsideAI would structure a query, then tweak it

Uploading your own data

Upload CSVs to combine external data with Flipside’s blockchain data.

How to upload

1

Click the upload icon

In the chat interface, look for the file upload option
2

Select your CSV

Upload a well-formatted CSV file
3

Describe the data

Tell FlipsideAI what the CSV contains: - “This is a list of addresses I want to analyze” - “These are token balances from an external source”
4

Ask your question

“Analyze these addresses for airdrop farmer behavior” “Join this with Flipside data to track user activity”

Privacy

  • Uploads are private: Your CSV data stays private to you
  • Not shared: Other users cannot see your uploaded data
  • Temporary: Files are not stored permanently (only for the session)

Use cases

Upload a list of addresses to:
  • Analyze their onchain behavior
  • Track token holdings over time
  • Identify patterns or anomalies
Define your own user segments: - Upload a CSV of “power users” based on off-chain criteria - Compare their behavior to the broader population
Upload data from other sources: - Compare Flipside data to your internal metrics - Validate consistency across data providers
Upload recipient lists:
  • Analyze their wallet activity
  • Check for sybil behavior or wash trading
  • Score addresses based on quality metrics

Handling errors or odd results

Sometimes queries fail or return unexpected data. Here’s how to handle it.

FlipsideAI auto-retries

When a query fails, FlipsideAI automatically:
  1. Identifies the error
  2. Adjusts the query
  3. Retries
You’ll see: “Retrying with updated query…”

Persistent errors

If retries don’t work, try:
"This query failed. Can you try using a different table?"
Sometimes alternative tables have the same data with different schema.
"These numbers seem off. Are you using token amounts or USD amounts?"
Token/USD confusion is a common issue—clarify the units.
"This query is too complex and timing out. Can you break it into steps?"
Large queries can be split into smaller, faster queries.
"Let's do this in steps:
1. First, show me total volume
2. Then, break it down by protocol
3. Finally, add the time series"
Sequential queries are more reliable than one big query.

Pro tips

Don’t wait until the end of a long analysis to export data. Download intermediate results as you go—especially if the chat is getting long and might hit context limits.
Download data from FlipsideAI, then build your own charts/reports in tools you control. This is useful for: - Client deliverables - Recurring reports (monthly, quarterly) - Custom dashboards
If you’re unfamiliar with a table:
"What columns are in the ethereum.defi.ez_dex_swaps table?"
FlipsideAI can explain table schemas.
Upload a list of addresses, then:
"Use live query to get the current USDC balance for each address in my CSV"
This blends external data with real-time blockchain state.

Next steps