> 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/protocol-mechanics/fees_distro.md).

# Fees Distribution

In the world of derivatives trading, commissions are the primary source of protocol revenue. On blockchain derivative exchanges, democratization takes center stage as these platforms allow anyone to provide liquidity and participate in revenue sharing. In this section, we will explore how **Storm** enables both liquidity providers and token stakers to actively participate in the evolving protocol economy.

***

## 🔥 Revenue Distribution

The protocol charges the following trading fees:

* 💰 **Trading Fees** (fees for opening/closing positions)
* 🔁 **Funding**
* ⚠️ **Liquidation Penalties**

All fees contribute to the commission distribution between STORM token stakers and liquidity providers. Specifically:

* **30% of the commission** is allocated to **STORM token stakers**.
* **The remaining 70%** of the commission goes to **liquidity providers**, who help increase market depth.

***

For more details about protocol and network fees, see the [Fees](/trading-mechanics/fees.md) section.


---

# 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.storm.tg/protocol-mechanics/fees_distro.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.