With airdrops, the rules change often, and whoever's writing is bound to slip up now and then. Our approach is simple: when we find something wrong or out of date, we log it here in the open and then fix it, rather than quietly changing it and pretending it never happened. Below are also a few important corrections we made to early drafts during our pre-launch self-check — we're writing them down so you can see how we treat accuracy.
Spotted a problem? We'd like to hear it: here's how to reach us.
Problem: a few places in the early drafts wrote out specific event thresholds (a minimum stake, a points threshold, a minimum lock amount).
Fix: Binance adjusts these numbers every round, so printing them as fixed values would mislead readers. We changed all such hard numbers across the site to explaining the mechanism plus "per the official announcement for the current round (checked 2026-06)", and wherever a specific value is needed we point readers to Binance's official page for the current figure.
Problem: the draft on "should you sell if a new token lists below price" had a sentence that read like operational advice (close to an absolute "selling at open is safest").
Fix: that's investment advice and beyond what we should be doing. We changed it to "selling at open is just one common approach, not a hard rule," handed the decision back to the reader, and stressed that nothing here is investment advice. See that article for details.
Problem: the first versions of several calculators didn't make clear where the data came from, so it was easy to assume the results were "live and accurate."
Fix: all tools now have you enter the inputs yourself, and the math runs locally in your browser, with every result labelled "an estimate, for reference only — go by Binance's official page for the real figures." We don't plug in any data source that would show fake live numbers, so the wording and the behavior match.
Problem: the sign-up walkthrough in from sign-up to your first airdrop said the registration page should prefill the invite code, as if it were a field on the sign-up form, and the FAQ answer left the same impression.
Fix: we opened the live page at accounts.binance.com on 2026-09-08 and read Binance's help-center registration guide: the first screen asks only for an email or phone number, and the referral code step appears after the account is created — prefilled from an invite link, changeable if wrong, skippable if empty, locked once bound. The step, the FAQ answer and its structured-data copy now say so; numbers and links are unchanged.
Problem: the opening of the full Launchpool guide said Launchpool has "no lock-up". Binance's Launchpool guide (the Chinese-language page) calls putting coins in "locking" them, while also saying they can be redeemed at any time.
Fix: the line now says there is no fixed lock-up period and notes Binance's wording and the redeem-anytime rule. Being able to take your principal back at any time has not changed.
Any future corrections to already-published content will keep being logged here by date. Related: About us · Disclaimer