> For the complete documentation index, see [llms.txt](https://docs.hashed.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hashed.tech/core-concepts/extraction-and-cooldowns.md).

# Extraction & Cooldowns

**Claiming your mined tokens is done through the Extraction process.**

When you extract, all accumulated $HASH tokens move from the datacenter pool directly to your wallet.

<figure><img src="/files/G3sxzXQlgGAHg9A7YngS" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
To extract - **you need to have a few $HASH tokens in your wallet** (to open a Solana token account).
{% endhint %}

Extracting withdraws your node from the datacenter and triggers **a random 15–30 minute cooldown.**&#x20;

### Node Cooldown

Your node cannot be redeployed until this period ends, though this can be shortened if your node has a Cooldown Reduction passive skill.

If you fail to maintain your node and its power drops **below 25%**, the system will automatically extract it for you (with a 10% penalty fee) and send it to your wallet.

<br>


---

# 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.hashed.tech/core-concepts/extraction-and-cooldowns.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.
