> For the complete documentation index, see [llms.txt](https://docs.gpu-fi.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpu-fi.uk/mining/emergency-exit.md).

# Emergency Exit

Explains the emergency exit mechanism for mining positions.

### Normal path

Normally, a miner:

1. Commits $RIG.
2. Builds mining power toward 100% over 21 days.
3. Unlocks tokens at 10% per day after day 21.
4. Can fully withdraw by day 31.

### Emergency path

If a miner exits before completing the normal mining period:

```
Early Exit
    ↓
90% Returned
    +
10% → Mining Pool
```

The miner receives 90%. The remaining 10% goes directly to the mining pool. It does not go to the treasury or operator reserve.

The penalty compensates the mining pool when a miner exits early.

### Illustrative example

If a miner exits with 1,000,000 $RIG before the normal period completes:

| Outcome                 | Amount       |
| ----------------------- | ------------ |
| Returned to the miner   | 900,000 $RIG |
| Sent to the mining pool | 100,000 $RIG |

This example illustrates the 90/10 rule.


---

# 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.gpu-fi.uk/mining/emergency-exit.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.