Corrections — What We Got Wrong and When We Fixed It

Site informationUpdated 2026-09-12By Ivo Renner

This site assembles a roster of seventy-odd 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

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.

Dates identify the revision recorded here. A check of one mechanism does not re-verify every contract in the launch archive.

Correction log
Date	Page	Was / is	Caught by
2026-09-12	Index and mark price; three editions	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; three editions	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; three editions	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 roster 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 editions	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 field as a pair with the launch date instead of as a trend, and says plainly that we have no evidence for why August reverted.	Recomputing the leverage distribution from `data/contracts.json` while expanding the page, rather than re-reading the sentence
2026-09-04	Binance TradFi perp fees, all three editions	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.	An SEO 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 editions	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 edition	Was: a full Vietnamese edition, 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 edition was withdrawn rather than stripped down. A Spanish edition for readers in the Americas replaces it. Entries below that mention Vietnamese pages describe that retired edition.	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 editions	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 editions
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: every string the script writes is keyed by language and selected off `<html lang>`; the apology notes are gone.	A check that now executes the real script in both languages against a DOM shim
2026-08-30	Ten pages carrying screenshots and diagrams	Was: ten `<img>` tags whose declared width and height did not match the file — one portrait screenshot declared as landscape, which stretched it. Is: declared dimensions are compared against the bytes of each image file before publishing.	A dimension check added after the first one was spotted by eye
2026-08-29	Every Vietnamese guide	Was: structured data on each Vietnamese article pointing its author URL at `/vi/about/`, a page that did not exist at the time. Is: the page exists, and every URL asserted in structured data is now resolved against the file it claims.	A link check extended to cover JSON-LD, not just visible anchors
2026-08-29	Regional availability (Vietnamese)	Was: a finished guide that had never been added to `sitemap.xml`, so nothing told a search engine it existed. Is: in the sitemap, and no page can now be published whose canonical is missing from it.	A sitemap coverage check run before publishing
2026-08-29	One home page	Was: a home page that silently lost its entire block of language alternates during an edit, leaving the two editions unlinked for search engines. Is: restored, reciprocal, and refused publication if either side of the pair stops pointing back.	A reciprocity check added because every other check had stayed green

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 editions. 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.

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.