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 walk through Binance's own flow again, 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: 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: A reader wrote in saying the withdrawal dropdown showed both BEP20 and BEP2, and our text — which only said "BSC" — left them confused. 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.