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.
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 hard-code a 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.