LEGAL · CORRECTIONS

Corrections record

Getting something wrong is normal; hiding the error is the problem. This page makes our corrections policy public, along with the things we've actually changed or added — all dated. An information site earns trust not by never erring, but by owning and fixing it when it does.

Corrections policy

The process is simple — three steps:

  1. You find a problem, you tell us. If something on the site is wrong or out of date, or you have more accurate official information, email [email protected]. Including the page URL and the problem you spotted helps us locate it faster.
  2. We check it. We cross-check against verifiable sources — official announcements, official documentation, block explorers — to confirm whether there really is an error.
  3. We correct it, and log it here. Fixing it isn't just quietly changing it; it's listing below "what changed, and on what date", so the correction itself is public and checkable.

Changes that affect content accuracy go on this page; for changes to features and page locations, we also rely on each article's "last checked" date to remind you to go by the official wording at the time.

A note: the entries below are clarifications and additions we made to existing content in the site's early days, not errors reported by readers. We won't invent past "error records" that never happened just to pad this out — this page only records things that actually happened.

Corrections and clarifications

2026-07-20 · Removed specific offer percentages, fixed fee-impact assurances and named regional eligibility claims whose evidence review was incomplete. Invite pages now tell readers to rely on the sign-up page, account status and the platform's current rules.
2026-06-15 · launch day: a specific offer percentage was given a platform-page caveat. Because its evidence review remained incomplete, the figure was removed on 2026-07-20.
2026-06-15 · launch day: the USDT network checker had a clarification added — ERC20 and BEP20 share the same address format, so the address alone can't tell you the chain; you must confirm separately which chain you intend to use, to avoid funds getting stuck in a cross-chain mix-up.
2026-06-15 · launch day: the look-alike domain checker had a note added — the tool only assists with character-by-character comparison and cannot guarantee a given URL is "safe"; we still recommend bookmark login as your main line of defence.

Can't find the correction you reported?

If you sent a correction and we did make the change but you don't see a matching entry above, it may still be in progress, or we may have judged that the report didn't affect content accuracy (for example, purely editorial style). If you're not sure, feel free to send another note to [email protected] to ask, or see the other channels on the contact page.