> For the complete documentation index, see [llms.txt](https://docs.trade.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trade.xyz/perpetuals/risk-and-margining/auto-deleveraging.md). # Auto-Deleveraging Auto-deleveraging mechanics for trade\[XYZ] perpetuals. #### Backstop Liquidator: The onchain backstop liquidator is live for XYZ markets where cross margin is enabled. This is a fully onchain strategy that takes over backstop liquidatable positions from assets where cross margin is enabled, making those assets less likely to experience ADL during high volatility events. The XYZ backstop liquidator helps manage undercollateralized positions in a way that is intended to reduce bad debt and minimize reliance on ADL. If market liquidations are insufficient, ADL serves as a final mechanism to help preserve system solvency. #### Auto-Deleveraging: Auto-deleveraging (ADL) is the final safeguard in the liquidation waterfall and exists to ensure system solvency under all conditions. It occurs only when both market and backstop liquidations (for cross margin assets) fail to close a position that has become under-collateralized. In a perpetual derivatives market, every long is matched by a short, and all positions are collateralized with margin from a shared collateral pool. When a trader’s account equity or an isolated position value becomes negative, the system must rebalance by closing positions on the profitable side. Otherwise, the system would accrue bad debt and violate the zero-sum constraint that total long notional equals total short notional. When ADL is triggered, users on the profitable side are ranked and selected for forced deleveraging based on a composite index that accounts for both profitability and leverage: `sorting_index = (mark_price / entry_price) * (notional_position / account_value)` Users with the highest ranking index (most profitable and most leveraged) are deleveraged first. Their positions are closed at the previous mark price against the insolvent side of the market. This transfer of position value ensures that aggregate system equity remains constant and that the platform has no bad debt. The system minimizes the frequency of ADL events through conservative maintenance margin settings and by routing most liquidations through market orders or, if necessary, the XYZ backstop liquidator (for cross margin assets). ADL is therefore a rare, last-resort settlement mechanism. In practical terms, ADL is similar to a system-wide rebalancing event that closes the loop when no external liquidity remains. It is mechanical, transparent, and non-discretionary. Every ADL event can be independently verified on-chain via Hypercore’s settlement records --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.trade.xyz/perpetuals/risk-and-margining/auto-deleveraging.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.