> For the complete documentation index, see [llms.txt](https://docs.hubbleprotocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hubbleprotocol.io/faq/liquidations/liquidation-example.md).

# Liquidation Example

First, a user takes a loan:

* SOL/USD is $100.0
* User Position (debt=100, collateral=2 SOL)
* User LTV is: (100 / 200)\*100 = 50% LTV 
* User is safe. Liquidation point is 80% LTV.

Then, SOL price drops:

* SOL/USD is $80.0
* User Position (debt=100, collateral=2 SOL)
* User LTV is: (100 / 160)\*100 = 62.5% LTV 
* User is safe. Liquidation point is 80% LTV.

Then, SOL price drops again:

* SOL/USD is $62.0
* UserPosition (debt=100, collateral=2 SOL)
* User LTV is: (100 / 124)\*100 = >80% LTV 
* User is liquidated (loses 90% of collateral), because liquidation point is below the user's LTV. In this case, **the user loses 90% of their collateral**, receives 10% of their assets back, and their debt is fully paid by the USDH Vault. 
* After liquidation: User Position (debt=0, collateral=0 SOL) 
  * If the user has kept their 100 USDH, they incur a net loss of \~10% (Collateral $124 - Debt $100 - $12.4 assets returned = $11.6 loss).


---

# 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.hubbleprotocol.io/faq/liquidations/liquidation-example.md?ask=<question>&goal=<endgoal>
```

`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.