About this website
Corrections and updates
Point us to the claim. We will check the evidence before changing the explanation.
Updated on 2026-09-16
A wrong number or an unclear instruction can matter when you are reading an order screen. Tracepu distinguishes mistakes in published content from later changes to an exchange's rules and from edits that simply make a sentence easier to read.
Report a specific issue
Email [email protected] with the page address, section heading and the exact passage or number you want checked. If possible, include a public official source, the date you viewed it and a short explanation of the difference.
Sending a report does not mean it has been read or that a reply is guaranteed. Do not use this email address for an account emergency. See the contact page for those limits.
What we check
- Locate the claim and the context around it.
- Check the original source, relevant date, calculation or actual tool behavior.
- Determine whether the content was wrong when published or whether an external rule changed later.
- If a change is needed, update the explanation and any related structured information so they do not contradict one another.
We do not promise a fixed handling time or decide a factual question by counting emails. If the evidence is incomplete, we should say what remains uncertain.
Different changes need different treatment
A correction fixes something already wrong or materially misleading when published: an arithmetic error, a guarantee that should have been conditional, or a claim about the tool that does not match its requests. A correction that substantially affects understanding or an action will receive a short explanation on the relevant page.
An update reflects a later external change, such as a renamed field or revised order requirement. It should include the new checking date. It does not automatically mean the earlier explanation was wrong at the time.
Spelling, punctuation and wording changes that leave the meaning intact normally do not need a separate public entry.
Public correction record
Each entry identifies the page, the date, what the page originally said and what it says now.
- 2026-09-16 · How to open a Binance account and prepare for a first spot trade: adding a referral code later. The registration steps told readers to check the referral field because the page “may only allow it during registration”, and the referral section said not to assume a code would be added later. That overstated the limit. The page now says the safest time is before submitting, and that Binance allows a referrer to be added from the referral page within 30 days of signup when all of its conditions are met, including no deposits or trades and no existing referral relationship. It also now explains that referral cashback is paid afterwards in USDC rather than as a lower fee rate.
- 2026-09-16 · The same article and the referral code box on the home page: where readers live. Both said only that the offer depends on your location, and the article added that a copied country list could not establish eligibility, without naming any region. Based on Binance’s list of prohibited countries and its Referral Program Additional Notes (checked September 2026), they now state that people in the United States, Canada and the Netherlands cannot use binance.com, and that users registered in the EEA, UK retail users, residents of Singapore, Israel-based users, Nigerian residents or nationals, Japan residents joining as referred users and Hong Kong residents joining as referred users receive no referral rewards, and that the retail referral program in Turkey has closed.
Responsibility stays with Tracepu
The Tracepu editorial team is responsible for publication and correction decisions. Read the editorial policy and affiliate disclosure for the wider approach.