Why we publish corrections openly
When something we write is wrong, the cost of that mistake isn't borne by us — it's borne by the reader who follows the instructions. In a domain where on-chain transactions are irreversible, that matters more than usual. So we've committed to a rule: any change that affects understanding or procedure gets logged here publicly, with the date, the original text, what it was changed to, and why. No silent edits. No pretending the original didn't exist.
Typo fixes and formatting tweaks don't make the log. Substantive changes — anything that could lead a reader to make a different or riskier decision — get a numbered entry, in chronological order, which only ever grows. The corrected pages themselves also get their "updated" date bumped, so the two records stay in sync. The first three entries below are from the site's build phase, recorded accurately as they happened.
All corrections
Page: DZ-01 Network selection guide (other guides used range language from the first draft)
Original → revised: The first draft quoted fixed withdrawal fee figures → replaced throughout with fee ranges and a note reading "check the live withdrawal page for the current rate."
Reason: Withdrawal fees fluctuate with network congestion and platform policy. Fixed figures go stale and mislead; ranges with a live-check reminder are more reliable.
Page: DZ-01 USDT network selection guide
Original → revised: "Ethereum produces a block roughly every 12 seconds" → "Ethereum advances roughly every 12 seconds per slot."
Reason: Post-Merge Ethereum operates on slots, not mined blocks. The original phrasing was technically imprecise.
Page: All article cover images (site-wide)
Original → revised: Some cover images had title text that wrapped mid-word, breaking "ERC20" and similar terms across two lines → line-break positions adjusted to keep technical terms intact.
Reason: A broken network name on a cover is exactly the kind of thing someone might misread. In this context, misreading a single character costs real money.
Spotted an error? Tell us
If anything is wrong — a step that doesn't match what you see on-screen, a number that's out of date, a phrase that would cause someone to make a bad transfer — please email [email protected] with the page URL and the specific location of the problem. A source or reference is even better. Accepted corrections make it into this log with the reason noted. If you want a credit in the entry, just say so. Readers who catch errors are the most important editors this site has.