Corrections and Material Updates
Found a wrong fee, leverage limit, access claim or calculation? Send the page and what seems wrong. You do not need to prove the answer before reporting a problem.
Opens your email app. Nothing is sent automatically.
A useful report can be short
The email draft has space for the page URL, the disputed claim and your reason for questioning it. A provider link, the inputs used in a calculator or the time you saw a mismatch can help us reproduce the issue. These are useful clues, not requirements for being heard.
If the button does not work, write to hi@cryptoleveragehub.com. Do not include login credentials, identity documents, API secrets or wallet recovery phrases. Redact personal details from screenshots.
What happens after a report
- Find the discrepancyCompare the reported claim with its dated evidence or reproduce the calculator result using the same inputs.
- Identify what changedEstablish whether our statement was wrong, a provider changed its terms, or the available evidence remains inconclusive.
- Correct affected outputsTrace shared data into tools, rankings, dossiers and country pages so that fixing one sentence does not leave the same error elsewhere.
- Leave a visible recordFor a material correction, explain the old result, the replacement and the date in the relevant history. Keep published research editions intact.
A problem affecting liquidation, trade cost, position eligibility or resident access takes priority over a cosmetic edit. We do not promise a fixed response deadline or that every disagreement will result in a change. If a claim cannot be supported, the appropriate response may be to qualify or withdraw it rather than substitute another uncertain answer.
An actual correction: the $100 million BTC boundary
On 8 October 2026, we corrected how the BTC position-size study selected a Bybit margin tier at its upper boundary. The provider’s preserved schedule was unchanged; our interpretation of the boundary changed.
- Earlier result
- 9× at exactly $100 million, selecting the next tier at a shared boundary.
- Corrected result
- 10×, using the documented inclusive upper limit. The corrected model requires $10 million in initial margin for that total position.
- What it does not mean
- It does not show that one $100 million order can be submitted or filled. The saved order limit remains a separate constraint.
The new analysis is edition 2026-10-08.1. Its version date is not a new market observation: it recalculates retained September evidence. Publishing the correction did not overwrite the earlier archive.
Our error or a new exchange rule?
A misplaced decimal in a fee, a wrong contract multiplier or a source that never supported the claim is a correction. An accurately reported fee that an exchange subsequently changes is a material update. The distinction tells you whether the original conclusion was unsound or simply became outdated.
Typographic fixes that do not change meaning need no individual announcement. Changes to methods and shared datasets belong in the research changelog; exchange announcements and dated documentation checks appear in exchange updates.
Sources and research
The example above is reproduced in the corrected BTC dataset and its file manifest. The earlier edition’s manifest identifies the preserved inputs. This is evidence of our calculation correction, not a current Bybit account offer.