Skip to main content
Upload CSV files to combine your external data with Flipside’s blockchain data catalog. Analyze address lists, compare custom cohorts, or validate internal metrics against on-chain activity.

​
How to Upload

1

Click the upload icon

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

Select your CSV

Upload a well-formatted CSV file with clear column headers.
3

Describe the data

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

Ask your question

  • “Analyze these addresses for on-chain behavior” - “Join this with Flipside data to track user activity” - “Screen these addresses against our anti-sybil scores”

​
Privacy and Security

  • Uploads are private: Your CSV data stays private to you and your team
  • Not shared: Other users cannot see your uploaded data
  • Session-scoped: Files are processed for your session only

​
Common Use Cases

​
Address Analysis

Upload a list of addresses to analyze their on-chain behavior: 
"I've uploaded a CSV of wallet addresses. For each address, show me:
- Total transaction count across Ethereum, Arbitrum, and Polygon
- DeFi protocol interactions
- Estimated wallet value"

​
Cohort Comparison

Compare your user segments against on-chain metrics: 
"This CSV contains our 'power users' based on off-chain criteria.
Compare their on-chain behavior to the general Uniswap user base."

​
Anti-Sybil Screening

Screen address lists for potential farmers or bots: 
"Screen these addresses against Flipside's wallet scores.
Flag any with score below 3 or suspicious patterns."

​
Data Validation

Validate your internal metrics against on-chain data: 
"This CSV has our internal DEX volume numbers.
Cross-check against Flipside's ethereum.defi.ez_dex_swaps for the same period."

​
Airdrop Targeting

Refine distribution lists: 
"These are candidate airdrop addresses.
Filter to only addresses that:
- Have used DeFi in the last 90 days
- Have wallet score > 5
- Are not flagged as potential sybils"

​
CSV Format Best Practices

Use descriptive column names:
address,label,category
0xA0b8...,whale_1,high_value
0xB1c9...,whale_2,high_value
Include full addresses (checksummed or lowercase):
address
0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48
0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984
If addresses are chain-specific, include a chain column:
address,chain
0xA0b8...,ethereum
0xB1c9...,arbitrum
For optimal performance:
  • Under 10,000 rows is ideal
  • Under 100,000 rows is manageable
  • Larger files may require batching

​
Combining with Live Query

For real-time analysis of uploaded addresses: 
"Use live query to get the current ETH balance for each address in my CSV"
This fetches current on-chain state rather than historical table data.

​
Next Steps

Agents

Use specialized agents for address targeting

SQL Editor

Write custom queries against your data

Artifacts

Create shareable reports from your analysis

Teams

Share analyses with colleagues