EDITORIAL POLICY
Evidence and limits come before conclusions
Every guide answers one specific ledger question and states its calculation basis, its limits, and its sources.
Source rules
Fee schedules, funding mechanics, and export paths cite the exchanges' own help centres or developer documentation. Aggregator sites, community posts, and other analysis sites are never used as factual sources. A repository check enforces that every listed source resolves to binance.com or okx.com.
Automated pre-publication checks
There is no second person doing manual review here, so every check that can be automated lives in the repository: each guide must carry a formula, a worked numeric example, a field-level table, stated limits, and at least two sources, and every source must resolve to binance.com or okx.com. Missing any of these fails the build and the guide cannot ship. The constraints are in scripts/validate-content.mjs.
What this does not replace
Automated checks enforce structure and source compliance. They cannot replace a second pair of eyes on the arithmetic. If you find an error in a formula, a field name, or a worked example, please report it — that is currently the most reliable way errors get caught. Affected data is marked unavailable before anything is rewritten.
Update rules
Guides carry a last-verified date. When a public fee schedule goes unverified for more than 30 days, report confidence drops automatically and affiliate links stop appearing. This is enforced in code, not by policy alone.
Corrections
When a field or rule changes, the affected data is marked unavailable and recommendations stop first; sources, wording, and the verification date are updated after. We do not mass-produce near-synonym pages without new evidence.
Figures and examples
All amounts and rates in the guides are anonymized examples that demonstrate a method. They represent neither a real account nor current fees. Actual rates depend on the exchange's published schedule and your own fee tier.