This log records changes that can affect a published figure or how a reader checks it. Editorial wording and visual-only changes are not listed.

22 August 2026

  • Correction — Tron send fee. Between 15 and 25 July 2026 the collector priced a simple Tron transfer at 2.8 TRX. A native transfer consumes about 267 bandwidth and the chain charges 1,000 sun per bandwidth byte, so an account with no free quota pays 0.267 TRX: the published figure was 10.5 times too high. The collector was corrected on 25 July 2026 at 13:07 UTC. Snapshot 475 (12:37 UTC) is the last reading with the wrong figure and snapshot 476 the first with the right one — 475 of the 1,799 readings collected up to 22 August 2026, or 26 per cent of the archive.
  • The Crypto Fees Index itself did not move. Tron's send cost sat above the cross-chain median at both the wrong and the right figure, so the median and the index are the same either way. Checked by recomputing all 1,799 readings, not assumed.
  • The affected pages were /api/data/fees/snapshots/1 to 475. Nothing on /fees, in an article or in an embed carried the wrong figure: those show the latest reading, which has been correct since 25 July, and the 30-day chart plots the index, which never moved.
  • Stored readings are not edited. A snapshot in that range now serves the corrected Tron figure with a corrections entry beside it, carrying the figure it published before, the date and the reason.
  • Snapshot URLs stay permanent but no longer send Cache-Control: immutable. They are cached for a day and carry an ETag, so a correction can reach anyone holding a cached copy. Every snapshot response now has a corrections array — empty when the reading is served exactly as recorded — and snapshotId is a number, as /openapi.json always said it was.
  • The two static estimates (TON and Tron) now carry reviewedOn in the data: the date they were last checked against the chain. The collector refuses to run if either drifts outside its documented range.

19 July 2026

  • Fees readings embedded in articles and statistics now render from the production database on each request. A database fallback is labelled sample; prose no longer describes a fallback as live.
  • The Fees API now supplies an immutable snapshot URL for every latest reading.
  • Government Holdings totals carry ~ whenever an included row is estimated.
  • Fee-source labels now link directly to the primary API or protocol documentation used by the collector.
  • Stable row links were added to every Dead Coins and Government Holdings record, and the public API returns each record's URL.

17 July 2026

  • Dead Coins expanded from 32 to 113 documented cases; every entry received an evidence URL.
  • Government Holdings stopped counting disputed claims and state-linked theft proceeds in its headline BTC total. Those rows remain visible and labelled.

16 July 2026

  • Government Crypto Holdings launched with 12 countries, per-record sources, confidence labels and as-of dates.

12 July 2026

  • Crypto Fees Index and the initial 32-case Dead Coins set launched.

Dataset-specific inclusion changes remain documented beside the method: Fees, Dead Coins, and Government Holdings.

Corrections that change a published fact are dated here with the corrected page. Contact details are on the press page.