> For the complete documentation index, see [llms.txt](https://docs.sturdy.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sturdy.finance/overview/liquidations.md). # Liquidations **Maximum LTV**\ Each silo has a maximum LTV, or loan-to-value ratio. LTV is calculated by dividing the user's borrowed amount by the user's collateral amount. LTVs are calculated independently for each silo, meaning a borrower's position in one silo will not impact the LTV in another silo. When a user's LTV exceeds the maximum LTV, their position will be eligible for liquidation. **Liquidations** During liquidations, any user can repay the borrower's debt and receive a portion of their collateral equal to the debt plus a liquidation fee. Each silo has its own liquidation fee set when it is deployed. The liquidation fee and max LTV can be viewed by calling the `liquidationFee()` and `maxLTV()` functions on the silo respectively. They can also be viewed on the UI by clicking on a given silo's overview page. Users can track their LTV on the Dashboard page of the UI, or alternatively check their Health Factor. The Health Factor represents distance from liquidation, which occurs when the Health Factor drops below 1.0. For example, a Health Factor of 1.05 would represent a position that is 5% away from liquidation. --- # 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://docs.sturdy.finance/overview/liquidations.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.