> For the complete documentation index, see [llms.txt](https://docs.reloadsol.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reloadsol.app/understand-risk/risk-basics.md).

# Risk basics for spot traders

Essential risk management for spot traders: drawdown recovery math, payoff ratios, break-even win rate, and fixed-fee drag on small stakes.

**TL;DR:** On-chain micro-cap tokens move fast in both directions. Controlling position size, understanding drawdown recovery math, and avoiding tiny-stake fee drag matter more than predicting every winner.

[Open reloadSol P\&L →](https://reloadsol.app/pnl)

***

## What reloadSol does (and does not) do

{% hint style="warning" %}
reloadSol public trading surfaces are **spot, fully-collateralised, non-custodial** market execution. There is **no margin, no leverage, no liquidation, no resting limit order, and no exchange-side stop-loss or take-profit order**. Your position is a token in your own wallet and you exit by selling it.
{% endhint %}

***

## Drawdown recovery math

Losses and gains are asymmetric. The deeper a [drawdown](https://docs.reloadsol.app/start-here/trading-terms.md#risk-metrics) gets, the harder it is to recover:

| Drawdown from entry | Gain required to break even |
| ------------------- | --------------------------- |
| **−10%**            | **+11.1%**                  |
| **−25%**            | **+33.3%**                  |
| **−50%**            | **+100.0%**                 |
| **−80%**            | **+400.0%**                 |

Cutting losing trades early keeps your capital intact for the next setup.

***

## Payoff ratio and break-even win rate

You do not need to win more than 50% of your trades to be profitable—what matters is your **Payoff Ratio (`R = Avg Win ÷ |Avg Loss|`)** and **Break-Even Win Rate (`1 ÷ (1 + R)`)**:

| Avg Win  | Avg Loss | Payoff Ratio (R) | Break-Even Win Rate |
| -------- | -------- | ---------------- | ------------------- |
| **+20%** | **−20%** | `1.00×`          | **50.0%**           |
| **+45%** | **−15%** | `3.00×`          | **25.0%**           |
| **+60%** | **−10%** | `6.00×`          | **14.3%**           |

A trader winning only **40%** of trades with a `3.00×` payoff ratio is solidly profitable; a trader winning **60%** of trades with small wins and one **−80%** rug loses money.

***

## Fixed-cost drag on tiny positions

Network and priority fees are **flat per transaction**, not a percentage of your trade. On very small stakes (for example, `0.002 SOL`), flat round-trip fees can eat **10%+** of your position before price even moves. Size positions high enough that fixed fees stay a small fraction of your trade.

*Try the math interactively:* [Open the Fee-Drag & Payoff Calculator →](https://studentofcoding.github.io/reloadsol-docs/widgets/index.html?view=calculator)

***

## Related

* [Stop-Loss, Take-Profit & Exit Mechanics](https://docs.reloadsol.app/understand-risk/sl-tp-and-exit-protection.md)
* [Rug Detection & Knowledge Graph](https://docs.reloadsol.app/understand-risk/rug-detection-and-knowledge-graph.md)
* [Risk disclosure](https://docs.reloadsol.app/help/risk-disclosure.md)


---

# 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.reloadsol.app/understand-risk/risk-basics.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.
