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.
Our anti-phishing code article said, in its section on choosing a code, that the code is "effectively public" because it shows up in your emails, and compared it to the design on a personal seal that "others can see." That runs against the Binance Help Center article the page itself cites ("What Is an Anti-Phishing Code and How to Set It up on Binance?"), whose current Chinese, English and Spanish versions all say to update the code as soon as possible if you suspect it has leaked; Binance's blog post of 2022-06-14, which predates our article, also says never to share it with anyone, including Binance staff. The article now says the code appears in every genuine email, so anyone who can see your inbox or screen can see it, but you shouldn't share it, and should change it if you suspect a leak. We also added the current format rules, examples that pass and fail, and a comparison with the 2022 blog rules. It has been retitled "What Is an Anti-Phishing Code? Meaning, Format, Examples", and links to it elsewhere on the site use the new title. Sources: the Binance Help Center article in English and Spanish (marked updated 2026-08-28) and Chinese (marked updated 2026-06-10), and the Binance blog post "Today’s Catch: Anti-Phishing Codes and How to Protect Yourself" (dated 2022-06-14, edited 2022-06-22), all checked 2026-11-14.
Our Binance API key article said in its FAQ that funds could be withdrawn through an API key "only if you gave that key withdrawal permission, left it without an IP whitelist, and the secret then leaked", and the body said sensitive permissions such as withdrawal "typically" require an IP whitelist. Binance's Help Center article on creating API keys (360002502072) states that an IPv4 IP access restriction is mandatory to enable withdrawal permission, and that since 2023-01-30 00:00 (UTC) a system-generated key with unrestricted IP can only be set to reading. Both rules were public before our article first appeared, so under the current rules a key with withdrawals on and no IP binding can't be created. The article has been rewritten to match (body, FAQ and structured data) and retitled "Binance API Key Permissions & IP Whitelist: What Each Setting Allows"; links to it elsewhere on the site now use the new title. Source: Binance Help Center, English version (marked updated 2026-11-06) and the Chinese and Spanish versions (marked last updated 2025-03-20), checked 2026-11-13.
Our article on the Binance fund password described it as a second lock on withdrawals, separate from the login password, said someone who broke into an account would be stopped at the withdrawal step, and told readers to stack it with 2FA; our account-security checklist, sign-up guide and exchange-versus-wallet piece, plus the security check-up and the glossary, repeated the idea. Binance's own material says otherwise. The fund password is a P2P feature: switched on in Advertisement Mode, it lets you release orders worth 500 USD or less instead of using 2FA, and Binance recommends turning it on only during peak hours. Withdrawals end with “Verify the transaction with your passkey or 2FA devices” and never ask for a fund password. We have rewritten the fund password article (body, FAQ and structured data) and fixed the related sentences in the other articles, the home page, the check-up and the glossary. Sources: the Binance blog post “Fund Passport: A New Security Feature For Faster and Safer Transactions on Binance P2P”, the help-centre notice “Registration and Use of Funding Password for P2P Trading” and “How to Withdraw Crypto from Binance?” (updated 2026-09-18 per Binance), all checked on 2026-10-03. The help-centre article “How to Enable Fund Password on Binance P2P” showed “This article does not exist” that day.
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.