Correction & update log
This is the public record of material corrections and how we handle developing-story updates. We do not silently rewrite old Latest News URLs when a thread moves. New facts get new posts. Wrong facts get fixed—and logged here.
Policy
For developing stories, we publish a new Latest News update that links the prior piece. The original chapter stays at its address. We do not quietly overwrite history on that URL.
A correction is different: a material fact in a published piece was wrong. We correct the article, note the change when readers would otherwise be misled, and add a row to the log below. Developing-story chapters are not corrections—they are new reporting.
Full desk rules for multi-chapter threads: How we cover developing stories. Active sagas live on the Watchlist.
Log
None logged yet. No formal corrections have been filed since this log went live. Developing-story updates appear on the Watchlist, not as correction rows.
Update practice (not corrections)
These are examples of how the desk files updates—new Latest News posts that link priors—rather than silent edits. They are labeled updates, not corrections.
- UPDATE · Bitget withdrawals — Attacker test transfers / risk controls linked prior reopen chapters (AMA, BTC reopen, phased plan) instead of rewriting them. Tracker: Bitget hack / withdrawals.
- UPDATE · Solana Alpenglow — No AlpenRush / mainnet null filed as a new chapter after the activation-schedule post, with the prior URL left intact. Tracker: Solana Alpenglow.
Related
- How we cover developing stories — new posts, trackers, Receipts, what we refuse
- Watchlist — open developing-story hub
- Editorial Policy — originality, sourcing, desks, AI cover disclosure
To report a material error: email info@8bitcrypto.com with CORRECTION in the subject—include a link to the story and the evidence—or use the Contact page.