> For the complete documentation index, see [llms.txt](https://whitepaper.usegpu.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.usegpu.app/mining/unlock-schedule.md).

# Unlock Schedule

Trace the mining-power ramp, post-commitment unlock process, and complete token release timeline from day one through day 21.

The normal Commitment lifecycle progresses through these states:

```
LOCKED
  →
FULL MINING POWER
  →
GRADUAL UNLOCK
  →
FULLY UNLOCKED
```

### Timeline

| Time         |    Mining Power | Unlock State         |
| ------------ | --------------: | -------------------- |
| Day 1        |           \~10% | Locked               |
| Days 1 to 13 | Linear increase | Locked               |
| Day 14       |            100% | Full Mining Power    |
| After day 14 |            100% | 15% unlock per day   |
| Day 21       |            100% | Full lockup unlocked |

### Commitment and Mining-Power phase

On day 1, Mining Power is approximately 10%. From days 1 to 14, it progresses linearly. On day 14, it reaches 100%.

### Gradual Unlock phase

After day 14, Mining Power remains at 100%. Locked Tokens begin a Gradual Unlock of 15% per day. The full lockup is unlocked by day 21.

This is the normal lifecycle. [Emergency Exit](/mining/emergency-exit.md) is a separate early-exit path.


---

# 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://whitepaper.usegpu.app/mining/unlock-schedule.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.