> 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/costs-and-practice/fees.md).

# Fees

**Storm Trade users pay two types of fees:**

* 🔗 **Network fee** — for executing a transaction on the TON blockchain;
* ⚙️ **Storm Trade protocol fee** — for using the platform and performing trading operations.

***

## 🔗 TON blockchain network fee

The network fee consists of several components and is calculated based on many factors: the size and content of the transaction, network conditions, processing time, and so on.

> 💡 **Important:** The exact fee cannot be predicted in advance. This is why most services reserve an amount with a buffer and return the remainder to the user once the transaction is complete.

On Storm Trade, opening a position charges around **\~0.25 TON**, of which **\~0.17 TON is returned** to the user's wallet.

### 📐 Network fee formula:

$$
Transaction Fee = Storage Fees + In Fwd Fees + Computation Fees + Action Fees + Out Fwd Fees
$$

| Component          | Description                                                                                   |
| ------------------ | --------------------------------------------------------------------------------------------- |
| `storage_fees`     | Payment for storing the smart contract on the blockchain when sending/receiving a transaction |
| `in_fwd_fees`      | Fee for delivering incoming external messages                                                 |
| `computation_fees` | Payment for executing code in the TVM virtual machine                                         |
| `action_fees`      | Payment for performing actions in the smart contract body                                     |
| `out_fwd_fees`     | Payment for sending outgoing internal messages                                                |

***

## ⚙️ Storm Trade protocol fee

The platform fee is charged when **opening and closing a position** and is deducted automatically from your collateral.

### 📊 The fee depends on the trading pair:

* 💰 For **USDT pairs** — from **0.06%** to **0.12%**
* 💎 For **TON/NOT pairs** — from **0.12%** to **0.2%**
* 💵 For **Forex pairs** — **0.06%**
* 🪙 For **Gold** — **0.08%**

> 💡 **Example:**\
> Opening a **100 USDT position with 10x leverage** on a USDT pair:\
> `100 * 10 * 0.0012 = 1.2 USDT` will be charged as a fee.

***

## 🕒 Funding

**Funding Fee** is a recurring (hourly) payment between traders holding opposite positions, used in perpetual futures trading.

### 🔁 How funding works:

* If most traders go long and funding turns positive:
  * 💸 Long traders pay, short traders receive.
* If shorts dominate the market and funding turns negative:
  * 💸 Short traders pay, long traders receive.

> 📌 Funding helps balance supply and demand in the perpetual futures market.

***

🏄 *Understanding the fee structure helps you manage your positions and costs on Storm Trade more effectively.*


---

# 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/costs-and-practice/fees.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.