CoinCrafty is written by people, and people get things wrong. When that happens we would rather fix it in the open than quietly hope nobody noticed. This page explains how to tell us about a mistake and what we do next.
How to report an error
Use the form on our contact page. Tell us which page you were reading, what looks wrong, and, if you have one, a source we can check against. A link or a screenshot makes the job much faster.
You do not need to be certain. “This paragraph reads oddly to me” is a perfectly good report, and we would rather field ten of those than miss one real error.
How reports are triaged
Every message is read by the CoinCrafty editorial desk. We go back to the original sourcing and re-check the claim. Where something cannot be verified, we say so on the page instead of guessing.
Anything touching reader safety jumps the queue. Wallet steps, key handling and scam warnings are treated as urgent, because a wrong instruction in a guide like backing up a seed phrase can cost somebody real money. If we are unsure mid-check, we would rather pull a section down for an hour than leave a risky step live.
What gets a visible correction
- A factual error: a wrong figure, a misdescribed protocol, a mistaken claim about how a product works.
- An edit that materially changes the meaning of what was published.
- A headline, standfirst or summary that misleads even if the body is right.
- Anything in a gear review that would change how you read the score, judged against our published scoring method.
Visible corrections are dated and appended to the foot of the article. The note says what was wrong and what it now says, in plain words. We do not silently rewrite history, and we do not delete an article to make an error disappear.
What we fix silently
Typos, broken links, a mislabelled image, a formatting glitch, a name spelled two ways in one piece. These get corrected without a note because nothing about the meaning changes. If a “typo” turns out to have altered a number or a step, it stops being a typo and gets a visible correction instead.
Updates are not corrections
Our explainers are living documents. When a guide is refreshed because circumstances moved on, we mark it as updated rather than corrected, because nothing was wrong when it was published. Corrections are for errors; updates are for time passing.
The public log
We keep a log of every visible correction so the record is one page rather than scattered footnotes. Right now that log is empty. The relaunched site has not yet issued a correction, and we are not going to invent entries to look diligent. When the first one happens, it will be listed here with its date.
The standards behind all of this are set out in our editorial guidelines, and there is more on who we are and how we work on our about page.