> For the complete documentation index, see [llms.txt](https://docs.bounce.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bounce.tech/basics/how-leveraged-tokens-work/standby-mode.md).

# Standby mode

Due to minimum size thresholds enforced by Hyperliquid, when the TVL of a specific leveraged token is below $250 it enters `Standby mode`. In standby mode users can still buy and sell leveraged tokens. However all funds will be held idly in the HyperEVM smart contract and have no exposure to the underlying asset. Meaning, the value of minted tokens will remain static until the enforced TVL requirements are met. As soon as the TVL of a leveraged token goes above $300, it will be activated again with no additional action required by the user.

{% hint style="info" %}
Standby mode is very uncommon and will most likely (if ever) only impact low volume long tail assets.
{% endhint %}


---

# 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.bounce.tech/basics/how-leveraged-tokens-work/standby-mode.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.