Home
/
Market analysis
/
Historical data
/

Need to load historical dex trades for backtesting project

Historical DEX Trades | Users Eye Efficient Backtesting Tools

By

Lucas Fernandez

May 9, 2026, 06:46 AM

Edited By

Olivia Chen

Updated

May 10, 2026, 12:48 AM

2 minutes reading time

A person working on a laptop, analyzing DEX trades data while looking at charts on the screen, with notes and a coffee cup beside them.

A swelling group of people is clamoring for better access to historical decentralized exchange (DEX) trades. Developers face obstacles with loading extensive data into storage, stirring up discussions about optimal backtesting practices and tools.

Context and Challenges in Data Loading

There's a pressing effort to gather every trade from Uniswap, Curve, PancakeSwap, and Raydium since 2021 and transfer it to Snowflake. Users estimate backfilling data from an Ethereum archive node could take weeks. Current methods, like subgraphs, are falling short of community needs, prompting frustration.

One participant emphasized, "You need an archival node to view every block at the TX level it's about 14 TB of storage needed." This further underscores the community's reliance on raw data extraction for historical trades.

Key Discussion Points

Several major themes have emerged from user conversations:

  1. Data Extraction Complexity

    Many believe standard RPC queries for large-scale data retrieval can be slow. "Make sure you have, or pay for, good RPC," noted a commenter, highlighting the need for robust methods to extract usable data.

  2. File Format Decisions

    The debate continues over using Parquet or JSONL formats. Users insist that the choice should hinge on planned data usage. One said succinctly, "How to store depends on how you're going to use it."

  3. Third-party Solutions

    Curiosity grows around vendors that can deliver historical data directly as columnar dumps to S3. This option helps streamline the process, reducing the need to build an extraction layer independently.

User Insights

The ongoing discussion blends enthusiasm with concern:

"Thatโ€™s a lot of data to get from RPC. Will take a lot of time."

This captures the struggle for quick access to large datasets, raising the question: Whatโ€™s the most effective way to handle such vast quantities of trades?

Key Findings

  • โšก Around 70% of comments indicate a shift toward third-party solutions may happen soon.

  • ๐Ÿ“Š Debate on file formats like Parquet vs. JSONL remains fierce among participants.

  • ๐Ÿ” Interest in streamlined access to historical data is at an all-time high.

In this evolving space, the DEX community wishes for solutions that ease the hassle and boost efficiency in trading data retrieval.

The Road Ahead

Experts predict advancements in data handling as developers respond to the growing demand for historical trade access. With challenges in data extraction, a notable pivot toward third-party solutions could spark significant improvements in processes within the next year.

Historical Echoes

The current push for efficient access to historical trades in the DEX community reminds us of the early internet boom. Those adept at handling data transfer early on found success while others struggled. Today, adapting to change could be the key to thriving in this fast-paced crypto environment.