This page logs corrections made to this site. The rule is simple: if a change touches a fact, a number, a conclusion, or any wording that could shift a reader's judgement, it goes here. Typos and layout tweaks do not, or this page would drown in noise and the entries that matter would disappear.
Problems we caught ourselves before the site opened to readers are logged the same way. The idea that "mistakes before opening day do not count" is not an honest one.
September 2026
2026-09-30 · Google Analytics was added to this site while the privacy page still said "no analytics"
To find out which pages anyone actually reads, the Google Analytics tag was added to every page here. It stores measurement cookies in your browser, and what reaches us is the summary reports — visit counts, regions, page views — which we do not use to single out who is reading. The problem was that the privacy page still said "no cookies, no analytics of any kind", which stopped being true the moment the tag went live — on a page that also promises to be updated before anything about the site's technical make-up changes. That is now fixed: the privacy page lists what Google Analytics can see, what the cookies are called, and how to block it in your browser. Corrected in the Chinese and Hindi editions at the same time.
2026-09-17 · "Posting orders saves you fees" is not true at the entry tier
How Binance fees actually stack said that maker rates are lower "sometimes substantially", and called switching from market orders to limit orders the highest-value cost saving available to an ordinary account. Re-reading the platform's published spot fee schedule on 17 September 2026 showed that this does not hold at the entry tier at all: in that row the maker rate and the taker rate are the same number, and the maker column only drops below the taker column from the first VIP fee tier upward. We had written a conclusion that only applies higher up the table as though it applied to everyone — and nearly all of our readers sit in exactly the row where it does not. The text is corrected: limit orders are still worth using, but what an ordinary account saves is slippage and spread, not the fee rate. The same pass added the and/or distinction in the tier thresholds (the entry tier reads "or", every VIP tier above it reads "and") and replaced the illustration with a September 2026 screenshot. The Chinese and Hindi versions were corrected in the same pass.
August 2026
2026-08-24 · Why there is no Vietnamese edition: the risk of offshore exchange accounts in Vietnam
We had intended to publish a Vietnamese edition, reasoning that local peer-to-peer trading was still busy. Rechecking the Ministry of Finance's current position showed Vietnam moving toward licensing only domestic platforms and restricting citizens from trading on offshore exchanges — which is exactly what this site explains how to do. So there is no Vietnamese edition. The lesson generalises: peer-to-peer trading still being possible is not the same as it being permitted, and the two have to be checked separately.
2026-08-24 · On a phone, the referral code was hidden until you scrolled
On the earliest version of the home page, anyone opening it on a smaller phone had to scroll down before the referral code and the fee-discount note appeared, so the most important information was not visible at first glance. The page has been adjusted; on a phone the code and its explanation now show as soon as the page opens.
2026-08-24 · The asterisk after "up to 20% off trading fees" was easy to miss
On some phones, the asterisk after "up to 20% off trading fees" on the home page dropped onto a line of its own. It looked like a stray symbol, which made it easy to skip the sentence it points to: the one saying the actual percentage is whatever the exchange currently shows. Fixed; the asterisk now always stays attached to the text.
How to get something corrected
If you find something here that does not match how a platform currently behaves, or a conclusion that does not hold up, tell us through the contact page. Say which page and when you looked, and we will check it. Confirmed problems get the text corrected, the date on the page updated, and an entry added here.
If we check and conclude the original was right, you get a reply explaining why rather than silence. The full process is in the editorial policy.
What is logged and what is not
For this page to be useful it cannot become a dumping ground. The line sits here:
| Type of change | Logged | Why |
|---|---|---|
| A fact, number or rule stated wrongly | Yes | It feeds straight into what a reader decides and does |
| A conclusion that has to be withdrawn | Yes | This is the category most worth publishing |
| Wording that misleads or understates a risk | Yes | The consequences are as real as a factual error |
| Information gone stale against current platform behaviour | Yes | Correct information past its date works exactly like wrong information |
| Typos, punctuation, layout | No | Logging them buries the entries that matter |
| New sections or added coverage | No | That is an update, not a correction — different thing |
Why problems caught before the site opened are listed too
A corrections page that starts on opening day implies the site arrived finished, which is never true of anything. The three August entries were all caught before readers arrived, and including them costs us nothing except the pretence. It also gives you a sense of what kind of mistakes this site makes, which is more useful than an empty page.