Build with CoinStats’ all-in-one API. Learn more

Deutsch한국어日本語中文EspañolFrançaisՀայերենNederlandsРусскийItalianoPortuguêsTürkçePortfolio TrackerCryptocurrenciesPricingCrypto APIMCPIntegrationsNewsRWA MarketEarnBlogNFTWidgetsDeFi Portfolio TrackerDerivativesETF FlowsCrypto GamingPrediction Markets24h ReportPress KitAPI Docs

Ethereum Exchange-Flow History Was Rewritten — Here’s Why Backtests Can Be Wrong

18m ago•
bullish:

0

bearish:

0

A chart showing Ethereum leaving exchanges can look like hard historical fact. In reality, the chart itself can change years later.

Coin Metrics has recomputed its Ethereum Standard Flow Metrics from genesis using its latest wallet-attribution data. The update affects all ETH exchange-flow metrics at both daily and hourly frequencies.

The reason is simple but important: data providers do not know every exchange wallet in real time. When a previously unknown address is later identified as belonging to Coinbase, Binance or another exchange, standard historical flow data can be recalculated to include that wallet’s earlier activity.

The same date can show a different exchange outflow later

Coin Metrics explicitly distinguishes between standard flow metrics and its new Point-in-Time, or PIT, series.

Standard metrics use all addresses currently known to belong to an exchange. If an address is identified today but was active in 2022, its historical transactions can appear in a rebuilt 2022 exchange-flow chart.

Point-in-Time data works differently. An address only counts as belonging to an exchange from the date it was actually identified. That makes PIT data more appropriate for backtests designed to answer a specific question: what information could a trader realistically have known at the time?

This distinction matters because exchange outflows are one of the most heavily used signals in crypto market analysis. Large withdrawals are often interpreted as accumulation, reduced sell-side liquidity or coins moving into long-term custody.

But a strategy tested on a modern reconstructed dataset can accidentally use information that did not exist when the original trade would have been made. That is a classic form of look-ahead bias.

On-chain data is measurable, but attribution is still a model

The blockchain itself is immutable. The attribution layer is not.

An Ethereum transaction from wallet A to wallet B cannot be rewritten. What can change is the label attached to wallet B. If analysts later determine that B belongs to an exchange, the economic interpretation of that historical transfer changes.

Coin Metrics says its recomputation covers ETH flow metrics from genesis to the present. The provider’s documentation also notes that standard historical values may change when new entity addresses are discovered, while PIT values remain fixed based on what was known at each historical interval.

That does not make exchange-flow data unreliable. It means researchers need to distinguish between blockchain facts and entity-attribution estimates. For live monitoring, the fullest modern wallet coverage can be useful. For historical trading simulations, a point-in-time dataset is safer.

This is especially relevant for strategies built around “exchange reserves falling” or “whales withdrawing from exchanges.” Without data-version controls, a backtest may look cleaner than the signal that traders actually had available at the time.

Sources: Coin Metrics recalculation notice and Coin Metrics Point-in-Time methodology.

The post Ethereum Exchange-Flow History Was Rewritten — Here’s Why Backtests Can Be Wrong appeared first on TechGaged.com.

18m ago•
bullish:

0

bearish:

0

Manage all your crypto, NFT and DeFi from one place

Securely connect the portfolio you’re using to start.