A corrections page should not be decoration: a link in the footer, a one-line stub, never updated. This page is not that.
Every time I change something material in any article on this site, the change gets logged here with a date and a short note explaining what changed. Errors get fixed. Opinions get updated when new evidence arrives. None of it gets buried.
§1Why a corrections page even exists
Crypto moves fast, and writing about it sets every article up to age badly. Any piece published today can be partially or completely wrong three months from now:
- Projects referenced in an article may collapse (FTX, LUNA, Celsius, Three Arrows, Voyager)
- On-chain data referenced in passing may be overwritten by newer activity (address balances, network metrics, throughput numbers all drift daily)
- Exchange links may move domains, or affiliate-program rules may change
- My own view may change when new evidence shows up
- Regulatory ground shifts in major ways (new licensing regimes, exchanges leaving or entering a market, new tax-reporting rules) and an article that was accurate at publication can describe a legal landscape that no longer exists
This page is the public record of every change. It exists for two related reasons: accountability to you, and discipline for me. Because every edit ends up logged here in plain sight, I have to think harder about the edit before making it.
§2The three rules
The discipline is short enough to fit on a napkin:
- Wrong gets fixed — there is no version of this site where an article is treated as final-on-publication and stays uncorrected because changing it would be inconvenient
- Material errors get logged — if I wrote a wrong contract address or misstated a critical fact, it is corrected as soon as it has been verified and recorded on this page
- No silent opinion edits — when my view of something changes, the new view gets dated and added; the old view is not deleted, only marked as superseded. Opinions can be wrong, that is fine. Pretending they were never wrong is not fine
"Opinions are allowed to be wrong, and they are allowed to change. What they are not allowed to do is pretend they were never wrong and never changed."
§3Correction log
Reverse chronological. The oldest entry is at the bottom.
-
2026-09-29
Removed claims that could not be verified.
-
2026-09-25
Site-wide correction pass. On the English pages this covered a few things. Article titles were reworded to match how readers actually search; the URLs did not change. A batch of claims that could not be verified was removed. And the English pages are no longer written as if the reader were in the US or EU.
Later the same day a few factual errors were corrected. The wallet guide used to suggest testing a seed phrase by importing it on another computer, and described splitting an existing seed phrase by hand as a Shamir backup; both were wrong and now point to the device's own check and to Shamir shares created with a new wallet. The scams guide no longer says a platform that lets you withdraw a small amount must be genuine. On tokenized stocks, the bStocks issuer is now given as BTech Holdings, a Binance group affiliate, and the xStocks custodian, oracle and chains (including BNB Chain since 30 April 2026) follow the official docs and announcements. The liquidation-price article's maintenance-margin table was rebuilt from OKX and Bybit public API data. -
2026-05-28
Full English-language edition launched. Six core pages (disclaimer / privacy / corrections / resources / index / tools) plus 13 long-form articles translated and rewritten for the English-language reader. No content corrections to log on a new edition.
-
2026-05-24
Site relaunched in v11 magazine-style. Visual, structural and typographic redesign across the whole site. Article body text was not changed by the redesign. Three new policy pages were added at the same time: disclaimer, privacy policy and this corrections center.
-
2026-05-22
First eight introductory articles published (what is Bitcoin / what is Ethereum / what is a stablecoin / what is DeFi / what is a crypto wallet / how to read candle charts / what is leverage / how to call bull vs. bear). First publication, so there are no content corrections to log yet.
§4How to tell me something is wrong
There are four channels — X (Twitter) is the fastest. Email handles long-form or attachments better. Telegram for quick exchanges. Weibo for Chinese-language readers.
When you submit a factual correction please try to include: the article URL + the specific wrong passage (a screenshot helps) + the version you believe is correct (optional). With those three things in hand I can verify it faster, correct it as soon as it checks out and record it here.
§5What does not count as a correction
There is one category of "correction" requests I do not act on: disagreement with my opinion is not an error to be fixed.
A few examples:
- "You wrote that dollar-cost-averaging beats market-timing, but I market-timed and tripled my money, so you should change it" — not a correction, that is a different strategy and a small sample size
- "You said new traders should avoid futures, but I am new and I made money on futures, so you are wrong" — not a correction, your sample size is one
- "You should not have said project X has risks, that is FUD" — not a correction, factual risk analysis is not an attack
Disagreement is not error. If you disagree with something I wrote, X is open and I genuinely enjoy public debate. I will absolutely change my mind when shown new evidence — but the path is "here is data that contradicts your premise," not "I think you should change your conclusion to mine."
However: anything that is genuinely factual — a broken link, a wrong number, a misdated event, an incorrect contract address, a misattributed research-report author, a miscredited source quote — gets corrected as soon as it has been verified, and logged here.
§6How corrections work here, and why it matters
Why a corrections page matters to you as a reader
A maintained, dated, public corrections trail shows that the writer takes responsibility for mistakes and treats readers as adults rather than as a passive audience. When you are deciding how much weight to give a crypto site's claims, it is worth checking whether it has one, whether it is actually updated, and whether the original articles point back to it when something was fixed.
How to submit a correction
Three working channels, in order of how quickly I will respond:
- Email to [email protected] with subject "Correction: [article URL]" — works in any timezone, best for anything that needs attachments or a longer explanation
- X (Twitter) DM to @mor_xiaogan — fastest if you can fit the issue into the DM size limit
- Telegram to @txzx603 — best for a quick back-and-forth
There is no formal SLA and I do not pretend there is one; replies depend on time zones and on how much checking the correction needs.
The historical log stays public, always
Every correction entry on this page stays public forever. Old entries do not get cleaned up, paginated off, or memory-holed. This is the single biggest divergence between how a serious publisher handles corrections and how a "delete the tweet, pretend it never happened" influencer handles them. The discipline matters because the historical log is the only thing that lets a later reader verify that the corrections process is real and not theatre. Without a permanent log, anyone can claim "I always correct my errors" — the log is what makes that claim auditable.
Contrast with delete-the-tweet culture
Delete-the-tweet culture works the opposite way: a coin gets shilled, the call goes wrong, the original tweet gets deleted, and the same account starts shilling the next coin without ever having reckoned with the prior mistake. The result is a permanent fog where no one can audit who was right and who was wrong over a meaningful period of time. The corrections-page discipline is the opposite of that. It says: here is what I wrote, here is when I changed it, here is why I changed it, and here is the version that came before. If I am wrong about something, you will be able to find evidence of that here. That is the contract.
I am one person rather than an editorial desk, but the discipline does not depend on size: date everything, never silently edit, and log corrections in a permanent public place.
The major-correction process · how a real fix happens
What a substantive correction actually looks like, step by step, when something material has to change:
- Triage · I receive a credible report (email / DM / Telegram). I verify the underlying claim independently using primary sources — not just the reporter's framing of it
- Fix · once the claim checks out, the article is corrected in place as soon as possible
- Log here · a new entry is added to the timeline above with a short description of what changed and why
- Notify, where applicable · if the original error was egregious enough that I want to make sure readers see the correction, a short X post links to the corrections log entry. Quiet corrections for minor things, public corrections for the things that matter
Corrections that check out are fixed as soon as possible and recorded here. When the underlying claim itself is contested and needs deeper verification, it takes longer.
What "major" means · the taxonomy
Not every change is a "correction." The taxonomy I use:
- Data error · a number, date, address, hash or quantity is wrong. Always a logged correction
- Fact error · an asserted fact about a project, person, exchange or event is wrong. Always a logged correction
- Legal landscape change · a regulatory rule cited in the article has since been amended, repealed or superseded. Logged as an update, original text marked as "as of [date]"
- Opinion update · my view of something has changed in light of new evidence. Logged as a new opinion with a date, original view preserved with a "superseded on [date]" notation
- Typo / formatting · a misspelling, a broken link, an HTML rendering issue. Fixed silently without a log entry, because logging trivia would dilute the signal of the substantive entries
§7Contact
The four contact channels above all work. Email is the most reliable for anything requiring a paper trail, X is the fastest for short messages. For corrections specifically, please put "Correction: [article URL]" in the subject line or first line of the message so it gets routed correctly.
If your report is escalated to a logged correction in §3 above, you will see your contribution acknowledged in the log entry (anonymously by default, with attribution if you ask).