Getting something wrong happens. Hiding it is the real problem. This page lays out what we've changed: each entry dated, with what changed and why. It's how you can see how we treat accuracy, and decide for yourself how much to trust us.
How to report an error
Found something wrong, out of date, or out of sync with Binance's current page? Write in:
Here's what happens once we get it:
- We verify. We check Binance's current help pages, or confirm what you saw against a block explorer.
- We correct. If it's wrong, we fix the article and record what changed in the log below.
- We leave a trail. Every correction is dated, and for meaningful changes we bump the "Updated" date on the article itself.
Include the specific page and line and we can turn it around faster.
On-chain fees, minimum withdrawal amounts, and confirmation counts shift anytime with congestion and Binance's policy. Any exact number written in stone can already be wrong by the time you read it. So in the corrections below, you'll see us swap "fixed value" wording for "ballpark, and go by what the official page shows at the time" again and again. That's not us being vague — it's us not misleading you.
Change log
What changed: Step 1 of the sign-up-to-first-deposit guide opened with "Nine times out of ten, beginners don't lose money on-chain". It now says a common way beginners lose money has nothing to do with the chain: they open a fake Binance.
Why: we have no statistic behind "nine out of ten", so it should not have been written as a figure. The advice itself is unchanged: trust only binance.com.
What changed: In “Binance, start to finish: from sign-up to your first deposit landing”, the Step 2 checklist said that if the sign-up form had a referral / invite code field, you should check whether our referral parameter appeared in it. It now says the form has no such field: the code appears in a step after the account is created, already filled in from the link with a green tick and “Bound”; it can be skipped or corrected if invalid, and can't be changed once bound. A short answer box under Step 2 now says the same.
Why: On 2026-09-08 we opened the registration page at accounts.binance.com again and read Binance's own help-center article on registering. The first screen has a single email/phone field and no referral box; the code is only handled after the account exists. Telling readers to look for a field on the form sends them hunting for something that isn't there, so we moved the step to where it actually happens.
What changed: We pulled BEP2 / Beacon Chain out of the tools entirely — the network picker no longer lists it under BNB, the memo lookup dropped its "BNB · Beacon Chain / BEP2" entry, the network table lost that row, and the fee estimator and deposit troubleshooter had their wording brought in line. In the articles, warnings like "don't mix up BEP20 and BEP2" that treated it as a live network are now historical notes, with one consistent rule: go by the networks Binance currently lists and the receiving side supports.
Why: BNB Beacon Chain is retired. The Final Sunset hardfork took effect at block 384,544,850 on 2024-11-19, 06:00 UTC, and what it cut was the cross-chain link between Beacon Chain and BSC; the chain's last block is recorded as 385,251,927 on 2024-12-03, after which the Post-Fusion phase shut the validator nodes down, published the balance dump, and opened token recovery. Binance had already halted BEP2 withdrawals on 2024-11-01 and deposits on 2024-11-08. So BEP2 simply isn't selectable on the withdrawal page today — our old "both are there, be careful not to confuse them" framing was teaching a chain that was already on its way out, which is stale and can send people the wrong way. The one place BEP2 still matters: moving old assets stranded on the dead chain over to BSC through the official recovery tool. One clarification: BEP20 is the common network for BNB, but not the only one — Binance also supports BNB deposits and withdrawals on opBNB. Go by the networks Binance currently lists. The 2026-06-25 entry below is a true record of what we did at the time and stays as written.
What changed: Across the network-picking content, we replaced the loose "BSC network" with a clear split between "BEP20 (BNB Smart Chain)" and "BEP2 (Beacon Chain)," and added a line noting the two have different addresses and use cases — don't mix them up.
Why: Our text only said "BSC" and never separated BEP20 from BEP2, even though both show up in the withdrawal dropdown. These really are different networks, and blurring them makes it easy to pick the wrong one and lose coins, so we got the names right and added the distinction.
What changed: In a spot describing the TRC20 withdrawal fee, we swapped "the fee is fixed at X" for "the fee is very low; go by what Binance's page shows the moment you withdraw," and removed a leftover specific amount in the body.
Why: Withdrawal fees move with Binance's policy and on-chain conditions. Calling one "fixed" is both inaccurate and liable to mislead readers after a policy change. Describing it qualitatively plus "go by the official page" is what our no-hard-numbers rule calls for.
What changed: In the arrival content, we changed "network X needs Y confirmations to land" into a qualitative "needs a few / a fair number of confirmations," and added "the exact count goes by what the block explorer and Binance's page show at the time."
Why: The confirmations needed aren't a constant — they vary by coin and by moment, and the exchange can adjust its crediting requirements. A number that looks precise actually makes it easier to misjudge arrival time. Qualitative wording plus a pointer to verify is the safer call.
Note: the above are the corrections from the site's early days. New corrections will keep getting added here in date order.
For how we write and check our work, see About us; for where the risk lines are, see the disclaimer.