> For the complete documentation index, see [llms.txt](https://risk.infinity.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://risk.infinity.exchange/liquidations/overview.md). # Overview Infinity runs a competing dual-channel External/Internal liquidation process for Tokens, Floating Rate Positions, and Fixed Rate Positions in an attempt to achieve the best execution. In this process, it simultaneously: * Externally: seeks bids from counterparties for such positions, and * Internally: queries other exchanges in the background (e.g. Uniswap) for prices Within five (5) seconds, Infinity will then automatically liquidate positions at the best price via the respective channels accordingly. When an account is liquidated, a **\[ 5 ]%** charge on assets is taken as a penalty fee and split 50/50 between the Infinity Treasury and the Liquidator. ## Which Assets Do We Liquidate? In determining which assets to liquidate, we take into account: * the biggest contributors to risk * the liquidity of the underlying markets both on Infinity, and externally * the correlation of such assets --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://risk.infinity.exchange/liquidations/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.