Protocol summary
Pre-registered · A count over the whole market- Question
- Did liquidated positions break Guard’s leverage or liquidation-buffer default more often than positions that were not liquidated?
- Sample
- All of Hyperliquid over 30 days, 4 Sep – 3 October 2026: 95,095 liquidated positions and 7,942,674 position-days that were not; 62% of liquidations covered.
- Measure
- The share of positions with leverage above 5× or liquidation within 10% of entry at that morning’s snapshot; the relative risk of liquidation that day.
- Trials counted
- 18 comparisons reported, listed in the method.
- Result
- 91% of liquidated positions against 38% of the others; relative risk 15.7 (95% interval 15.0–16.4). An association, not a claim that Guard prevents liquidations.
- Principal limitation
- Daily snapshots cannot observe every change before liquidation. This is an association with rule violations, not a claim that Guard would prevent those liquidations.
On this page
91% of 95,095 liquidated positions broke Guard’s leverage or liquidation-buffer default at that morning’s snapshot, against 38% of positions not liquidated; about 16 times as likely to be liquidated that day. All the studies.
How it was done
- Data, archived only. Our bucket’s copy of Hydromancer’s public archive:
- the daily position snapshot (
snapshots/perp, about 00:08 UTC, every open main-dex perp position with entry price, liquidation price, notional, account value and leverage setting); - all perp fills of the previous day (
fills/perp/all, for “opened in the 24 h before”). - No request was sent to Hyperliquid.
- the daily position snapshot (
- Unit: every snapshot position with notional ≥ $10 and account value > 0, outside the system addresses. Liquidated: a liquidation fill of the same account and market, on the snapshot’s side, between the snapshot and the end of the day.
- Rules: Guard’s defaults (rules schema v1), each judged from the snapshot as the protocol’s table says. Not one of them is run through the engine: the engine needs a trade and a stop, and the snapshot holds neither.
- Why not the recorder. The recorder’s trades carry no liquidation flag, and its
userFillscover the HLP liquidator vaults only (backstop liquidations; on 3 Oct every liquidation fill was methodmarket). ItsclearinghouseStatesweeps cover about 15,000 large accounts. The Hydromancer snapshot is the cheapest honest source of every position’s leverage and liquidation price.
Limits
- Not at entry. The rules are read at the daily snapshot. Leverage and liquidation price drift with the price and, in cross margin, with the account’s other positions. A position that was within the rules when opened may break them by the next morning because it lost money. The 24-hour subset narrows the gap, and its result is the same.
- Mechanical link. A liquidation price close to the entry makes a liquidation likelier by definition, and R2 alone separates the groups most (76.8% against 12.8%).
- The relative risk says how strongly the rules separate positions that were liquidated from those that were not.
- It says nothing about what Guard would have prevented. A refused trade might have been replaced by another, and the replay of real accounts (
survival-study.md,compliance-study.md) is the place for what-ifs.
- Coverage: 62.5% of liquidations, by count, are seen (above).
- Equity. The snapshot’s account value can include assets outside the perp account (unified and portfolio-margin accounts), which lowers measured leverage. A third of positions report no liquidation price and pass R2 by construction. Both bias the shares down.
- Stops are not in the data. R3 assumes Guard’s attached 2% stop. A trader’s own tighter stop would allow a larger position, so R3 overstates breaches for traders with stops; the compliance study found that few use them.
- Daily intervals. The per-day files use Wilson intervals on positions. These ignore that one account holds several positions, so they are too narrow. The pooled intervals are clustered by account.
- One month, a volatile one. The share of open positions breaking the rules (the base) moved only between 36% and 40%.
Trial count
| Item | Measurements |
|---|---|
| Pre-registered headline: pooled primary composite, all positions: shares and difference, relative risk | 2 |
| Pre-registered secondary: 2 composites × 2 subsets, shares and relative risks (headline cells included) | 6 more |
| Per-rule shares (4 rules + leverage setting) × 2 subsets | descriptive, 10 |
| Total comparisons reported | 18 |
Nothing else was tried. No definition, threshold or subset was changed after the first share was computed.
Deviations
None in method.
- The pooled per-rule table sums the day files’ counts. It is descriptive, as the protocol lists it.