Editorial policy
Which sources count, how a page is checked before it ships, what machines are and are not allowed to do here, and who is answerable when it goes wrong.
This site has no named author with a public CV, no institution behind it and no credential to lean on. What it has instead is a method you can inspect and an output you can check line by line against the same public pages it was built from. This page is the method. If the site ever stops following it, that is the thing to complain about.
What we publish, and what we refuse to
The subject is the instrument: what Binance has listed as a TradFi perpetual contract, what its published specification says, and what those mechanics do to a position that holds it. Inside that boundary the site tries to be exhaustive.
Outside it, four things are off the table permanently, and not because they are hard:
- No price views. No targets, no calls, no opinion on whether any underlying is cheap. Nothing here is a reason to open a position.
- No performance claims. No returns, no track record, no back-tests, no “traders using this made” anything. Neither ours nor anyone else’s.
- No individualised advice. We do not know your jurisdiction, your balance, your tax position or your tolerance for a gap open, and we will not answer email that asks us to pretend otherwise.
- No exchange comparison built to sell one. This site covers one exchange’s product because that product is undocumented, not because it won a review.
Which sources outrank which
Every factual claim on this site has to come from somewhere on this ladder, and a claim from a lower rung is never allowed to overrule a higher one.
| Rank | Source | Used for |
|---|---|---|
| 1 | Binance’s own launch announcement for a contract | Listing date, symbol, underlying, and the specification table as published on the day |
| 2 | Binance product documentation — the TradFi futures FAQ, the trading-parameters page, the fee schedule | Product mechanics and definitions: funding formula, index construction, margin behaviour; contract panels still govern symbol-specific parameters |
| 3 | The live Binance interface | Anything the reader must check for themselves, because it is account-, tier- or time-dependent. Cited as “go and look”, never transcribed as a fact |
| 4 | Primary non-exchange sources — regulators, listing venues, fund issuers | Facts about the underlying world rather than the contract: market hours, corporate actions, how a leveraged ETF resets |
| 5 | Secondary reporting | Last resort only, always flagged in the text as such. One launch batch rests on it today, and it says so on the page and in the dataset |
Two rules sit on top of that ladder. Where two Binance pages disagree, both are published (they do disagree, on mark-price deviation limits) and the reader is pointed at the interface rather than handed our guess. And where a specification could not be read at all, the symbol is listed as unverified rather than folded into the roster with a plausible number. Four symbols sit in that category. The full account is on the methodology page.
How a page is checked before it ships
The checking is deliberately split into two halves, because the two fail in different ways.
The judgement half is re-reading the claim against the source it cites, with the source open — not against a note about the source, and not against what the previous draft of the page said. Any figure that turns out to be VIP-tier dependent, promotional or account-specific is removed rather than qualified: this is why no maker or taker percentage appears anywhere on the site, and why the fee guide teaches you to read your own row instead.
The mechanical half is a checker that runs over every page and refuses publication on failure. It is not a style linter; each rule exists because something in that list already went wrong once. It enforces, among other things, that no internal link is dead, that every image file exists and matches its declared dimensions, that every URL asserted in structured data resolves, that both language editions point at each other reciprocally, that every published page reaches the sitemap, that the roster date stamped in the page header matches the dataset, and that spelled-out counts in prose have not drifted from the data. What it caught, and when, is in the correction log.
Where machines come into it
Stated plainly, because you cannot tell by looking
Pages on this site are drafted with the assistance of large language models, under editorial direction, and then checked as described above. We say so because a site that asks you to verify its claims has no business being coy about how it was produced, and because the alternative, letting you assume a newsroom, is the thing we would be criticising elsewhere.
The disclosure matters less than the boundary, so here is the boundary. Each of these is a rule with a consequence you can check on the site itself, not a reassurance.
- No fact is published because a model produced it. Every contract row traces to a launch announcement, and the whole dataset is published at /data/contracts.json so that you can re-derive the tables and the counts yourself. Where the source could not be read, the entry is flagged unverified rather than completed from inference. A plausible number with no source behind it is the specific failure this rule exists to prevent.
- No source is cited that was not opened. Every reference on this site is a link you can follow to a page that says what we said it says. If you ever find one that does not resolve, or that does not support the sentence citing it, that is a correction and we want the email.
- No experience is claimed. The byline is a disclosed pen name with no biography, no photograph and no credentials attached, precisely because a fabricated CV is the easiest thing in the world to generate and the hardest for a reader to disprove. Nothing on this site has been tested on a live trading account, and no page says otherwise.
- No evidence is synthesised. Every screenshot in these guides is a capture of a public Binance page, taken in a browser, with the month it was taken printed in the caption. No screenshot is a mock-up, a reconstruction or an image of an interface that does not look like that. Where a picture would be decorative rather than evidential, the page does without one.
- No quantity is estimated into existence. If we do not have a number, the page says what to go and look at instead of printing a figure with a hedge in front of it.
The assistance is used to draft and structure prose, adapt the English material into Spanish and Arabic, and check that the three editions state the same facts. Contract tables are generated from the shared dataset. That keeps the tables consistent with the archive, but does not establish that an archived parameter remains current.
The three editions
The Spanish edition includes local-time examples for readers in the Americas; Arabic includes examples for Dubai and Riyadh. Time-zone conversions and work schedules need their own checks. A funding schedule is always tied to a specified contract interval, rather than assumed to be the same across all TradFi contracts.
All three editions read the same dataset and must state the same facts. Differences in a contract parameter or calculation require correction, even when local examples differ. The calculators share one program with English, Spanish and Arabic display text; language changes must not change the arithmetic.
Independence, money and the pen name
One page per language edition carries one referral link. That is the entire commercial arrangement, it buys no influence over what is written or which contracts appear, and there are no paid placements, sponsored posts, ad slots or guest posts of any kind. The complete statement, including a table of every commercial link on the site, is on the disclosure page.
Links to Binance in the body of an article are plain citations of the page being discussed, carry no tracking of ours, and are marked so that search engines do not read them as endorsements. Links to non-Binance sources are there because the claim needs a source that is not the company being written about.
Who is answerable
The desk publishing this site is answerable for everything on it, including the parts a machine drafted. “The model wrote it” is not available as an explanation here and would not be worth much if it were: the decision to publish a sentence is the editorial act, and that decision is ours.
One address for all of it, including complaints about this policy: vozeso@vozeso.com. What we can and cannot help with is set out on the contact page; how errors are handled once reported is on the corrections page.
The short version
Machine-drafted, source-checked, publicly auditable, commercially disclosed, and answerable to the email address above. Read the methodology for where the data comes from, and the corrections log for what has already gone wrong.