> For the complete documentation index, see [llms.txt](https://docs.mooncake.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mooncake.fi/concepts/leveraged-tokens-lt/concept-of-leveraged-token.md).

# Concept of Leveraged Token

## Concept of Leveraged Position

The Leveraged Position represents the USD price exposure of the underlying token. In other words, the entire value change of the underlying token is fully reflected in the value of the Leveraged Position.

<figure><img src="/files/lsMhJIkDOtA0o5dSZTnR" alt=""><figcaption></figcaption></figure>

#### Example

Continuing from the earlier example:

Suppose 1 SOL = $200, split into Funding Position ($100) + Leveraged Position ($100). If the SOL price instantly increases from $200 to $220 (+10%),

* The Leveraged Position value increases from $100 to $120 (+20%).
* This shows the 2x leverage effect in action.<br>

The value of the Leveraged Position in USD terms is:

$$
Leveraged\ Position\ Value = Underlying\ Token\ Value\ –\ Funding\ Position\ Value
$$

## Mooncake's Leveraged Token

All leveraged positions from leverage users are pooled together inside a single Leveraged Vault, and the receipt of this vault is the Leveraged Token (LT).

Whenever the price of the underlying token moves enough to hit the rebalance threshold, all leveraged positions inside the vault are replaced with a new set of positions of the same value.<br>

This ensures that the effective leverage ratio of the LT remains constant.<br>

For example, in a 3× LT market, if the price of the underlying token increases and causes the effective leverage of the LT to fall below 3×, then during the rebalance the Leverage Vault needs to obtain additional risk exposure from the LP in order to restore the target leverage.


---

# 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.mooncake.fi/concepts/leveraged-tokens-lt/concept-of-leveraged-token.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.
