Corrections · Public diffs
Every published correction here is shown with old / new / date / reason. Recording the full cycle — missed, found, fixed — is part of what transparency means. Entries #001–#005 below are pre-publication edits caught during editorial review; reader-submitted corrections start at #100.
Total entries: 5 pre-publish + 0 post-publishLast update: 2026-05-18
Transparency commitment
When errors are found post-publish, we fix the article body within 24 hours and log the diff here. Significant changes (conclusions affected) also get a callout at the top of the article. We don't delete old versions — keeping the diff is the point.
📬 Site just launched · waiting on the first reader correction
The site went live on 2026-05-18. Post-publish reader-submitted corrections are still at 0. Stale data, conceptual errors, dead links, sloppy terminology — all of it counts as a valid correction. Submit via privacy@okexcex.com; accepted submissions enter the list starting at #100 with submission date, anonymized submitter ID, and reason.
old: OKX Wallet currently supports over 100 chains
new: OKX Wallet currently supports 120+ chains
Reason: cross-checked against OKX Web3 documentation (2026-05-15 version) during final pre-publish review; actual count is 120+, draft cited stale 2025-year-end figure.
old: first-3-months phishing rate for self-custody beginners is ~20%
new: first-6-months phishing rate for self-custody beginners is ~12% (multi-source editorial estimate)
Reason: the "20% in 3 months" figure couldn't be traced to a precise primary source in SlowMist or Chainalysis public reports. Revised to a multi-source editorial estimate "~12% in 6 months" with the source nature explicitly labeled.
old: X Layer has ~30+ DeFi protocols and ~$90M TVL (2026-05-01 DefiLlama)
new: X Layer has ~30+ DeFi protocols and ~$1-1.5B TVL (2026-05-13 DefiLlama)
Reason: draft based on 2026-05-01 data. The article publishes 2026-05-17. TVL changed meaningfully. Aligned to 2026-05-13 snapshot and used a range to reduce daily-fluctuation re-correction frequency.
old: ranked by "2025-2026 growth rate" (Permit #1, SetApprovalForAll #2)
new: ranked by "2024 cumulative losses" (SetApprovalForAll #1, Permit #2)
Reason: second editorial review (2026-05-15) concluded reader-relevant "danger" is better captured by "maximum loss already caused" than by "rate of growth". Cumulative loss reflects scale of damage; growth rate matters less to a beginner audience. Also reduces monthly re-ranking churn.
old: under any circumstance, never approve "unlimited" — strict allowance every swap
new: official mainstream contracts (Uniswap, Curve, 1inch etc.) can approve unlimited but monthly revoke.cash sweep; unknown / new contracts strict allowance always
Reason: first editorial review (2026-05-15). Draft used "strict always" stance — theoretically safest. But: strict adds cognitive load on every swap, leading to fatigue-induced click-throughs. Mainstream official contracts (Uniswap V3 SwapRouter etc.) are well-audited; accepting unlimited there is a reasonable trade. Monthly revoke as "rear defense" is more sustainable than "per-swap defense". Revised to tiered stance for real-world usability.
The editorial team is grateful to every reader who files a correction — you do something we can't do for ourselves.