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

# asymmetric impact

A favorable price move is not paid out at the raw leveraged-PnL amount. GetRekt retains a small deadband and an asymmetric profit adjustment from the reference trading model. Losing PnL is not reduced by the same formula.

## Start with raw PnL

Let E be entry price, P the accepted settlement price, N the position notional and s the direction: +1 for long, −1 for short.

```
rawPnL = N × s × (P − E) / E
```

For an adverse move, the normal-close loss is capped at isolated margin. For a favorable move, calculate:

```
d = max(s × (P − E) − E / 50,000, 0)
move = d / E

scale = (1 − baseRate) /
        (1 + 1 / (move × rateMultiplier)
           + referenceNotional / (1,000,000 × move × positionMultiplier))

adjustedProfit = N × move × scale
netProfit = adjustedProfit × (1 − 0.02)
```

If `move` is zero, profit is zero; do not divide by zero. The deadband is 0.2 basis points. The 2% fee is charged on adjusted profit, not notional.

## BTC reference parameters

| Parameter          | Value   |
| ------------------ | ------- |
| baseRate           | 10%     |
| rateMultiplier     | 15,000  |
| referenceNotional  | 100,000 |
| positionMultiplier | 814.598 |

These are the BTC model parameters. Adding another market requires its own approved configuration and validation; changing a market label does not create a supported market. The scale depends on the favorable price move and these constants, rather than walking external orderbook liquidity.

“Zero slippage” and “no spread” describe execution-reference behavior. They must not be used to hide this adjustment. Integer math, rounding and extreme-value behavior must be reconciled with the exact deployed version before any UI quote can be treated as executable. [Trades and pricing](broken://pages/90e68d4ef1ac6d39a033ec4dca261cc52477c3ac).


---

# 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.getrekt.trade/docs/asymmetric-impact.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.