Corrections
What this site got wrong, what it says now, and how each error was caught. Kept as a running list rather than edited away, because a reference you cannot audit is not a reference.
This site puts together a list of two hundred contracts by hand, from separate announcements, about a product Binance is still actively re-specifying. Errors are not a possibility to be hedged against. They are a certainty to be managed, and the way you manage them in public is a page like this one.
The log of every correction, with dates
Newest first. Every entry states what the page said, what it says now, and what caught it — because “how was this found” tells you more about whether the process works than the fix does.
Each date is when that correction was made. Checking one mechanism again does not re-check every contract in the launch archive.
| Date | Page | Was / is | Caught by |
|---|---|---|---|
| 2026-10-12 | Contract archive, contract board, home page and every page quoting the contract counts; all three languages | Was: 205 contracts from 54 launch notices, 5 January to 29 September 2026, verified on 5 October; the 6 and 12 October launches were mentioned as outside the archive. Is: 213 contracts from 56 notices, to 12 October: USDEXUSDT, VKTXUSDT, MCDUSDT and AKAMUSDT (6 October) and ZCSHUSDT, MSTUUSDT, SNPSUSDT and RDWUSDT (12 October), all at 20×. Category counts are now 143 single stocks, 18 ETFs and 21 leveraged ETFs; 126 contracts launched at 20×. | The two launch notices, cross-checked against Binance’s public contract list on 12 October. |
| 2026-10-12 | Funding guide, calculators, contract list pages and every page that described the funding schedule; all three languages | Was: a single 10 September notice moving nine Hong Kong contracts was presented as the only departure from eight-hour funding with a ±2% cap. Is: on 12 October every US-listed stock and ETF contract was on eight hours and ±2%, while every commodity, Korean, Hong Kong and Shanghai contract was on four hours, with caps of ±0.5% (commodities, SK Hynix, Samsung, Hyundai), ±1% (most Asian listings) or ±2% (Unitree). Notices of 30 January, 14 July, 19 August and 4 September had been missed; Tesla returned to eight hours on 30 January. | Binance’s public funding-rate data, read in full for every TradFi symbol, then the notices behind each group. |
| 2026-10-12 | Korean, Chinese and Hong Kong equity perpetuals; all three languages | Was: the currency treatment of the Korean contracts was an open question, and the mode over the mainland lunch break unverified. Is: Binance’s TradFi FAQ applies a USDT/KRW conversion to Korean contracts from 7 August 2026 and USDT/HKD to Hong Kong ones from 22 July, and lists the mainland lunch break as Orderbook EWMA. | A full re-read of the TradFi FAQ (updated 24 September 2026). |
| 2026-10-12 | Index and mark price, and pages citing the deviation limits; all three languages | Was: the Academy page’s different equity deviation figure was described as an old conflict that had been resolved. Is: the Academy page still shows ±8% for daytime equity sessions against the FAQ’s ±5%; both are now printed side by side. The FAQ’s update date is 24 September 2026, not 18 August. | Opening both Binance pages again on 12 October. |
| 2026-10-12 | Dividends and corporate actions, ETF perpetuals, disclaimer; all three languages | Was: the dividend treatment was summarised as an index or price adjustment in places, and the methodology summary omitted its exclusions. Is: a special funding settlement from shorts to longs, with a reduce-only window around it, no cap, estimated ETF payouts without true-up, and no adjustment at all for leveraged ETFs and BITO. Splits close and reinstate the position and cancel open orders. | Re-reading the dividend methodology (updated 1 October) and the contract-size FAQ. |
| 2026-10-12 | About, editorial policy, disclosure, disclaimer, home page and board; all three languages | Was: four symbols described as unverified and one batch as resting on secondary reporting, after the 5 October re-check had resolved both; new batches said to arrive every two weeks. Is: no unverified symbol or batch resting on secondary reporting remains; batches have come every few days since May. | Reading every site-information page against the 5 October correction. |
| 2026-10-12 | Trading walkthrough and pre-trade checklist; all three languages | Was: the “which contract first” table still counted 2 commodities, 12 index ETFs, 4 non-US and 7 leveraged contracts, and said the weekend gap barely applies to commodities; the question-and-answer summary shown to search engines repeated older text than the visible answers. Is: 8, 17, 23 and 20 (8, 18, 23 and 21 after the contract-list update above); commodities close from Friday 17:00 to Sunday 18:00 New York time; the summary shown to search engines now matches the visible answers. | A full read of both pages against the 5 October contract list. |
| 2026-10-05 | Contract archive, board and every page that cites the contract list; all three languages | Was: 72 contracts from 17 announcements, presented as the TradFi list, with four symbols marked unverified and the statements that no Microsoft, Amazon, Coinbase, Strategy or Hong Kong contract had been found. Is: 205 contracts from 54 launch notices, 5 January to 29 September 2026. All 72 earlier entries matched their notices; 133 were missing, among them those four names and thirteen Hong Kong listings. The unverified symbols turned out to be two listed stocks and two crypto tokens. Category counts, leverage ranges (5× to 50× on stocks and funds, 100× on commodities), the listing-tempo figures, the claim that every contract shared one set of funding terms (Tesla launched with four-hour funding) and the date of the first leveraged-ETF contract (SOXL on 15 May, not the 9 July batch) were corrected wherever they appeared. | Reading every listing notice in Binance’s announcement centre from January onward, instead of looking for notices one at a time. |
| 2026-10-05 | Korean, Chinese and Hong Kong equity perpetuals; all three languages | Was: the currency treatment of the Korean and Shanghai contracts was an open question. Is: the Shanghai notices state that a live USDT/CNH rate is applied, and four Hong Kong contracts are labelled quanto; the Korean case is still open and says so. | The CXMT and Unitree launch notices, read in full during the contract-list re-check. |
| 2026-09-12 | Index and mark price; all three languages | The closed equity index was described as fixed, and Price 2 still used a 30-second window. The explanations now distinguish the Orderbook EWMA index from the standard median mark-price formula and use the one-minute Price 2 window effective 31 August. | Binance’s TradFi FAQ and the 31 August mark-price announcement. |
| 2026-09-12 | Funding guides and calculators; all three languages | Eight-hour funding and a ±2% cap were treated as universal. Parameters now depend on the contract; nine contracts changed to four hours and ±1% on 10 September. The calculator accepts an interval or an exact settlement count and clears results for invalid inputs. | The 10 September parameter announcement; independent numerical examples and browser checks. |
| 2026-09-12 | Fees, preparation and archive scope; all three languages | Live practice-trade prescriptions were replaced by reading the fee panel, existing records and paper calculations. Execution-cost examples no longer automatically charge a maker entry a full spread. The 72-contract list is labelled an archive checked on 29 August, not today’s complete list. | Review of the risk wording, cost arithmetic and subsequent official listing notices. |
| 2026-09-04 | Leverage tiers and liquidation, all three languages | Was: “From July onward, 25× is routine” — a tidy trend line drawn through five July batches. Is: July was 25× throughout, and then all three August batches (06, 17 and 25) launched at 20×. The claim was true of July and wrong about everything after it. The page now reads the leverage figure as a pair with the launch date instead of as a trend, and says plainly that we have no evidence for why August reverted. | Recounting launch leverage across our downloadable contract list while expanding the page, rather than re-reading the sentence |
| 2026-09-04 | Binance TradFi perp fees, all three languages | Was: a pledge to print no maker or taker percentage anywhere on the page, while the screenshot on that same page plainly showed one. Is: the published figure is quoted (Regular User at 0.0200% / 0.0500% in August 2026) with the scope stated, because the table it comes from is the USDⓈ-M Futures tab and not the TradFi Futures tab that governs these contracts. The pledge narrows to what it always meant: no number is presented as the reader’s own rate. | A review asked why a page about fees contains no fee; re-reading our own screenshot showed the number was public, and that the tab it sat on was the wrong one to quote it from |
| 2026-09-02 | Dividends, splits and corporate actions, both languages | Was: a clearly-labelled hypothesis that Binance’s dividend handling lived in the index and never touched a position’s cash flow, because the methodology document had not been read. Is: the methodology turned out to be a public FAQ article, and it says the opposite: a one-time special funding settlement on the ex-date in which shorts pay longs (cash dividend rate −D/M). The hypothesis paragraphs are replaced with the documented mechanism, and the “not read” rows in the verification table are filled in. | A screenshot taken for this page — the FAQ’s Related Articles sidebar listed the methodology, so we read it |
| 2026-09-02 | The whole Vietnamese-language version of the site | Was: a full Vietnamese-language version, built before launch on the understanding that affiliate activity was permitted in Vietnam. Is: retired before it was ever published. Vietnam’s Decree 284/2026, in force from 1 September 2026, fines individuals for trading crypto assets on platforms not licensed there — a guide steering Vietnamese readers toward registration stopped being defensible, so the Vietnamese version was withdrawn rather than stripped down. A Spanish version for readers in the Americas replaces it. Entries below that mention Vietnamese pages describe that retired version. | Reading the decree’s coverage the day after it took effect |
| 2026-08-31 | Both contract lists, the risk disclaimer and five guides, in both languages | Was: a sentence attributing to Binance’s education page the statement that holders receive “no ownership rights, dividends, or voting privileges” — wording we could not find at either source we had cited for it. One Vietnamese page also carried it twice in the same sentence after a botched edit. Is: the substance stated in our own words, with Binance quoted only on the wording that is actually on the page: contracts “allowing users to trade on the price movements of these assets without needing to own them directly”. The corporate-actions table no longer marks the retracted sentence “Verified”. | Re-opening the cited source to confirm a quotation, then searching the phrase across both languages |
| 2026-08-30 | Fees and the real cost of a trade | Was: that Binance’s fee schedule for TradFi futures sits behind a login. Is: the fee page is public and carries its own TradFi Futures tab; the guide links it and teaches you to find your own VIP row. | Re-reading the source while writing a different guide |
| 2026-08-30 | All five Vietnamese calculators | Was: Vietnamese pages whose calculator readouts came back in English, with a note on each page apologising for it. Is: the calculators’ results and messages now appear in the page’s own language; the apology notes are gone. | A test that now runs the real calculators in both languages |
| 2026-08-30 | Ten pages carrying screenshots and diagrams | Was: ten images whose stated width and height did not match the picture itself — one upright screenshot was set to display as a wide one, which stretched it. Is: every image’s stated size is checked against the actual picture before publishing. | An image-size check, added after the first mismatch was spotted by eye |
| 2026-08-29 | Every Vietnamese guide | Was: on each Vietnamese article, the author link in the page information that search engines read pointed to the Vietnamese About page, which did not exist at the time. Is: the page exists, and every link in that page information is now checked against a page that actually exists. | A link check extended to the page information search engines read, not just the links you can see |
| 2026-08-29 | Regional availability (Vietnamese) | Was: a finished guide that had never been added to the site’s list of pages for search engines, so nothing told a search engine it existed. Is: on that list, and no page can now be published without being on it. | A check, run before publishing, that every page is on that list |
| 2026-08-29 | One home page | Was: a home page that, during an edit, silently lost the links telling search engines about its other-language version, so search engines no longer saw the two language versions as a pair. Is: restored in both directions, and a page is not published if either language version stops pointing to the other. | A check that each language version points back to the other, added because every other check had passed |
What counts as a correction
Not every edit is one. Fixing a typo, rewording a clumsy sentence or adding a paragraph is ordinary editing, and logging it here would bury the entries that matter. An edit becomes a correction when it changes what a reader would have concluded:
- A wrong fact. A specification, a date, a leverage ceiling, a funding interval, a symbol, a venue.
- A wrong characterisation. Describing a mechanism in a way that would lead a reader to expect the wrong behaviour, even where every individual number is right.
- A source that does not say what we said it says. Including a source that has since been changed or withdrawn by Binance.
- A disclosure error. Anything inaccurate about the commercial arrangement on the disclosure page. These are treated exactly like factual errors, not as a lesser category.
- A divergence between language versions. If the English, Spanish or Arabic pages state different facts, at least one of them is wrong, and it is logged as a correction rather than quietly aligned.
Staleness is a separate thing and is handled differently. When Binance changes a leverage tier after we recorded it, the old figure was not wrong when it was written; the page is updated and its date changes, but nothing is logged here. The structural limits of that are set out on the methodology page.
How to report one
Email vozeso@vozeso.com. It helps enormously if you include the page URL, the sentence you are disputing, and a link to the Binance page or screen that contradicts it. A source link is worth more than a paragraph of argument; it lets the thing be settled in a minute rather than an exchange of opinions.
You do not need to be polite about it and you do not need to be certain. “This does not match what I see in my account” is a useful message. So is “this contradicts your own contract list”, which is the easiest kind of error for us to make and the hardest for us to notice.
What happens next
- It is checked against the source, not against us. The test is what Binance’s own announcement or specification page says today — not what this site said yesterday and not what we remember writing. If Binance and this site disagree, Binance is right and this site is stale.
- It is fixed in the text. Not appended as a footnote at the bottom while the wrong sentence stays where a skimming reader will still read it.
- It is logged here, and the page’s update date moves. Both, not either. A silent fix and a stale date are the two ways this page becomes decorative.
- You get an answer, including when the answer is that we have checked and think the page is right. In that case you get the source we checked against, so you can tell us why it is the wrong source.
What we will not do
- Delete the evidence. Pages are not removed to make an error disappear, and entries are not removed from this log once they are on it.
- Rewrite history in place. An error that changed what a reader would conclude is recorded, not quietly overwritten with the right answer and a fresh date.
- Argue with a source. Where Binance’s own pages contradict each other (which they do, on mark-price deviation limits) both versions are published and the reader is sent to the trading interface. That is not a correction; it is the honest state of the documentation.
- Treat a disclosure error as smaller than a factual one. It is larger.
Related
How pages get written and checked in the first place is on the editorial policy page. Where the contract data comes from, and what could not be verified, is on the methodology page. The commercial arrangement is on the disclosure page.