> For the complete documentation index, see [llms.txt](https://fxprotocol.gitbook.io/fx-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fxprotocol.gitbook.io/fx-docs/faq/what-could-go-wrong.md).

# What could go wrong?

xTokens (v1): In the worst-case scenario, all xTokens could potentially lose their value. Before this happens however, the stability mechanism is designed to trigger and rebalance them. However, if the mechanism becomes exhausted, xTokens could drop to zero. In such extreme cases, the protocol's total collateralization ratio remains at 100% and the stablecoin is always backed and pegged to the dollar. If the market continues to decline, the stablecoin may temporarily de-peg, with a strong likelihood of recovery if the underlying market (e.g., ETH) rebounds. For more details about the stability mechanism, please refer to the V1 [Stability Mechanism](https://fxprotocol.gitbook.io/fx-docs/more/f-x-protocol-1.0/stability-mechanism.md).

xPOSITION (v2): Rebalancing and liquidation thresholds are carefully calibrated to prevent such scenarios. In an unlikely worst-case scenario where both rebalancing and liquidation mechanisms fail, the protocol may incur a bad debt. To safeguard users from this, f(x) Protocol allocates a significant portion of its revenue to a reserve fund specifically for such extreme cases. If the reserve fund is insufficient, the bad debt would be distributed among all xPOSITIONs.\
\
Learn more:

{% content-ref url="/pages/bCCcalc50nQbBcNyHMb2" %}
[Risk framework](https://fxprotocol.gitbook.io/fx-docs/risk-management/risk-framework.md)
{% endcontent-ref %}

{% content-ref url="/pages/PtqNJUHJq0xwbkTkxgWY" %}
[Advanced Peg Protection Mechanisms](https://fxprotocol.gitbook.io/fx-docs/risk-management/advanced-peg-protection-mechanisms.md)
{% endcontent-ref %}


---

# 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://fxprotocol.gitbook.io/fx-docs/faq/what-could-go-wrong.md?ask=<question>&goal=<user_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.
