# Native Anti-ADL Shield
**ADL (Auto-Deleveraging)** is a venue-level mechanism on Hyperliquid that force-closes perpetual positions during extreme market stress, specifically when a counterparty's liquidation can't be filled at market. Any protocol running short perps can be hit by ADL. When that happens, the hedge breaks, and the synthetic dollar temporarily loses its delta-neutrality.
For a synthetic dollar protocol, this is the single scariest event. Monetrix's architecture is built specifically to make it survivable.
## How the shield works
Three subsystems work together to **prevent, detect, and recover from** ADL events.
### 1. ADL Rebalancer: prevention
Monitors the ADL queue in real time. If any of Monetrix's hedges move toward the high-risk zone of the queue, the rebalancer redistributes exposure across positions to push them back into the safe zone.
This is preventative. It reduces the probability of being ADL'd in the first place by keeping the protocol's positions structurally safer than the average short on Hyperliquid.
### 2. Auto-Reopen Engine: recovery
If a hedge is closed by ADL anyway, the engine automatically re-opens a matching short position as soon as market conditions allow. No governance vote, no manual call, no off-chain operator. The logic is hardcoded on-chain and triggers directly from the event.
### 3. Daily Queue Hygiene: ongoing maintenance
On a rolling schedule, the protocol rebalances positions to keep the aggregate ADL-queue ranking consistently in the safe zone. This amortizes ADL risk over time rather than letting it accumulate near the high-risk threshold.
## The ADL queue in plain terms
Hyperliquid ranks perpetual positions by "how much unrealized profit × how much leverage." Positions near the top of the queue are the ones that get ADL'd when a counterparty can't be liquidated at market. The shield keeps Monetrix's positions as close to the bottom of the queue as possible, so other positions get deleveraged first.
## Why on-chain matters here
On a CEX-dependent synthetic, ADL-equivalent events are invisible until after the fact: users see the depeg, not the mechanism. On Monetrix, the entire shield is:
* **Transparent.** Every rebalance and re-open is an on-chain transaction.
* **Real-time.** The queue ranking is a public Hyperliquid state; anyone can verify.
* **Fully automated.** No human operator, no CEX operator, no off-chain trigger.
## Extreme-stress recovery
Even under the worst-case scenario, a correlated liquidation cascade across all major pairs, the Auto-Reopen Engine is designed to restore delta-neutrality within minutes, not days.
This is the structural difference from the October 2025 Binance-driven USDe event: in that case, holders had to wait for a CEX to resolve an internal issue. In Monetrix, recovery is a deterministic on-chain process that runs on Hyperliquid's own state.
## What holders should expect
* **In normal conditions:** the shield is invisible. Rebalances happen regularly; positions stay safe; the sUSDM rate grows.
* **In high volatility:** rebalancing frequency increases. Gas costs tick up slightly; yield is unaffected in aggregate.
* **In an ADL event:** the affected hedge is re-opened automatically. Short-term volatility in the sUSDM rate is possible, but the protocol returns to delta-neutrality without user action.
Nothing in the shield requires USDM holders to do anything. It's protocol-side machinery.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://doc.monetrix.xyz/risk-and-security/anti-adl-shield.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.