> For the complete documentation index, see [llms.txt](https://docs.storm.tg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storm.tg/special-modes/degenmode.md).

# Degen Mode

**Degen Mode** is the ultimate trading mode for the boldest traders on Storm Trade!

### ⚡ Key Features

* **Leverage x500** — only the maximum leverage for maximum risk and reward.
* **Ultra-low fees** — just **0.02%** to open and close a position.
* **Zero spread** — your trade price always matches the oracle price.
* **No funding, only Rollover fee**.

💡 **Rollover fee** is a fee you pay for keeping your position open for a long time.

* Calculated every block.
* Rate: **0.005% of your position size per hour**.
* It directly shifts your liquidation price.

## **Note:** Rollover fee is charged for every open position and gradually shifts your liquidation price.

### 💎 Available Assets

| Asset | Collateral  |
| ----- | ----------- |
| BTC   | USDT        |
| ETH   | USDT        |
| SOL   | USDT        |
| TON   | USDT or TON |

***

### ⚠️ Limitations

* **Add/Remove margin is unavailable** — leverage is always fixed (x500).
* All other trading operations are available (open/close, TP/SL, etc.).

🏄 **Degen Mode** — *You’re either a legend or a meme in trader chats!*


---

# 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.storm.tg/special-modes/degenmode.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.