> For the complete documentation index, see [llms.txt](https://userguide.cryptoquant.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.cryptoquant.com/zh/market-indicators/yu-gu-gang-gan-lv.md).

# 预估杠杆率

预估杠杆率（ELR）是指未平仓量与交易所储备的比值。

## Definition

Estimated Leverage Ratio (ELR) is defined as the ratio of open interest divided by the reserve of an exchange.

$$
\text{Estimated Leverage Ratio} = \frac{\text{Open Interest}}{\text{Amount of Reserve}}
$$

## Interpretation

ELR for a derivative exchange tells us how much leverage is used by users on average. This information measures traders' sentiment whether they take a high risk or low risk. If ELR value is high compared to the last couple of days, it indicates traders are quite confident in their positions. Funding data such as funding rates may help traders to build a robust trading strategy with this information.

In addition, ELR can estimate the exchange's transparency indicating exchange risk itself.

## Link to Our Data

* [Estimated Leverage Ratio in CryptoQuant Live Chart](https://cryptoquant.com/overview?search=estimated+leverage+ratio)
* [Estimated Leverage Ratio in CryptoQuant Data API docs](https://cryptoquant.com/docs/#operation/getEstimatedLeverageRatio)


---

# 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://userguide.cryptoquant.com/zh/market-indicators/yu-gu-gang-gan-lv.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.