Corrections and change log
We get things wrong, so we keep a public record of what we changed. When it comes to security and money, we would rather be slow and accurate than fast and wrong. If you spot a mistake, please tell us — we verify it, fix it, and log it in the table below.
How to report a correction
Send the page link, the part you think is wrong, and your source (ideally a link to the relevant Binance official page) to the email on our contact page. For anything involving specific rules, we check it against Binance's own pages before acting. Remember: Binance's current page is the source of truth. Where anything on this site disagrees with the official page, go by the official page.
Change log
Below are our pre-launch internal edits and the corrections made since, most recent first.
The 2026-06 entry below says the anti-phishing code “appears only in the emails and in-app messages Binance sends you” and does not cover SMS. That no longer matches Binance's help center: “What Is an Anti-Phishing Code and How to Set It up on Binance?” (updated on 2026-08-28) says the code is included in all genuine emails and SMS from Binance, that it must be 6 to 8 characters using at least three of uppercase, lowercase, digits and underscores, and that updating it regularly is good practice. We have rewritten the anti-phishing code article to match (body, FAQ and structured data, including the setup steps, the advice on picking and rotating a code, and the example code, which used a hyphen and was too long), along with the matching sentences in our other articles that mention the code, the phishing message checker and the security glossary. The older entry stays in place as a record.
The English version of “Signed up for Binance? Don't rush to deposit” treated the invite code as a field on the registration form: it said the sign-up page “may show a referral / invite code field (sometimes under more options)” and told readers to “check that the page accepts the code before submitting”; the FAQ and the structured data likewise said codes are “usually entered during sign-up”. On checking, the first sign-up screen has only the email/phone box and no invite-code field; the code appears at the step after the account is created, is filled in automatically from a referral link and shown as “Bound”, can be changed if invalid, skipped if absent, and cannot be changed once bound. The body, checklist, FAQ and structured data have all been rewritten to say so. Basis: the Binance Help Center articles “How to Register on the Binance Website?” (updated on 2025-11-24) and “How to Register on the Binance App?” (updated on 2025-11-23), plus this site's own run through the sign-up page in a browser on 2026-09-08.
An early draft of the anti-phishing code article read as though the code could authenticate "every Binance notification." We tightened it to: the anti-phishing code appears only in the emails and in-app messages Binance sends you — it does not cover SMS, phone calls, or third-party messengers. This keeps readers from assuming the code alone makes them safe.
An early draft named a specific number of hours before a new address becomes active. Since Binance may adjust these timings, we changed it throughout to: a newly added address goes through a cooling-off period before it takes effect, and the exact length is whatever Binance's own page currently shows. We no longer state a fixed number.
In encouraging readers to act quickly, an early draft of the "hacked account" article leaned toward "try hard and there's a good chance you'll get it back." We rewrote it to state the truth plainly: coins moved on-chain are usually very hard to recover, and no one can guarantee getting them back. We also added a warning about "pay-to-recover" follow-on scams, so as not to set unrealistic expectations.