Coin Metrics recomputed Ethereum's Standard Flow Metrics from the network's inception using its most current information, announced on October 1 as part of its Ethereum Point-in-Time release. The revision affects all ETH Flow Metrics at daily and hourly frequencies, with corrected history available for backfilling.
The rebuild highlights a practical challenge for investment research and backtesting. Historical data downloaded today reflects exchange wallet identifications made since those dates occurred. Backtests that replay trading rules through historical data require the information available when each decision would have occurred, creating different information sets even when observations carry the same dates.
Two Methods, Different Results
Coin Metrics uses two approaches to handle wallet identification. Standard metrics apply all addresses currently known to belong to an exchange, with history rewritten when new addresses are identified. Point-in-Time series instead uses only addresses known to belong to the entity during each historical interval, with later discoveries not affecting earlier data.
The distinction matters because a transfer can be assigned to an exchange retrospectively once the provider identifies the wallet. That fuller reconstruction may be useful for analyzing past supply movements with today's address coverage, but establishing what a trader could have recognized requires only the address information available at that earlier moment.
Data Versioning and Publication Timing
Coin Metrics announced the recomputation on September 28, expecting completion by September 30. The completion notice posted October 1 at 17:04 UTC does not establish when each affected value became available.
CryptoQuant's ETH Exchange Flows documentation explicitly warns that historical values may change as exchange wallets are discovered and validated through periodic clustering updates. CryptoQuant schedules automatic updates weekly on Tuesday at 00:00 UTC, with values potentially changing slightly, especially for recent observations.
Retaining an old query date is insufficient if historical values are fetched again from a mutable endpoint. The dates of observations may remain the same while the information used to construct them changes.
Measuring Trading Impact Requires Careful Comparison
Measuring whether the rebuild affects trading outcomes requires paired observations from the same provider and metric with matching exchange coverage, intervals and dates. The comparison must use retained pre-rebuild values alongside post-rebuild history for the same Standard metric.
Testing a trading signal also requires demonstrably available information at each decision time and must keep the rule fixed: the same entry and exit conditions, parameters and evaluation window. Availability cutoffs and execution timing belong in the test alongside trading costs.
A revised outflow metric measures movement relative to attributed exchange wallets. Claims about buying or profitable trading require additional evidence beyond outflow data alone. Any revised history can describe supply patterns with current address knowledge, but demonstrating a usable trading edge requires reproducible inputs, documented publication timing and fixed trading decisions.
