> For the complete documentation index, see [llms.txt](https://docs.ethena.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ethena.fi/protocol-overview/risks/margin-collateral-risks.md).

# Margin Collateral Risks

Ethena uses both linear and inverse margined perpetual futures, using linear perpetual futures that are  denominated in USDT. Denominating in Tether means that the margin and PNL calculations are quoted in Tether, and by extension, results in Ethena being positionally long USDT.

For example, if Ethena posts BTC as margin collateral, and takes a short position on a linear BTC/USDT perpetual future - Ethena has a delta of 0 on BTC due to being long spot (collateral) and short futures (perpetual), but it is directionally long USDT (quote currency) with no offsetting short exposure.&#x20;

The inherent risk this presents is exposure to a potential USDT idiosyncratic event.&#x20;

For context, 80% of perpetual futures open interest is stablecoin-margined, with the vast majority of those quoted in USDT.&#x20;

Ethena closely monitors USDT stablecoin price risk and solvency, and if a problem persists will take action accordingly. In this instance, Ethena would aim to move more of the perpetual futures positions into inverse contracts, margined with BTC or ETH, depending on liquidity.


---

# 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.ethena.fi/protocol-overview/risks/margin-collateral-risks.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.
