> 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/mining-overview.md).

# Mining Overview

Understand the architecture, lifecycle, and economic purpose of USE-GPU's token-based mining mechanism.

USE-GPU mining is a token-commitment mechanism. It is not proof-of-work mining and does not require GPU hash power. Participants commit USEGPU tokens and time. Those inputs determine Mining Power.

Mining Power determines a miner's proportional claim on the Mining Pool for each Epoch.

### Lifecycle

```
Commit
  ↓
Mining Power accrues according to commitment duration
  ↓
Mining Power reaches 100% at day 14
  ↓
Epochs calculate proportional reward allocation
  ↓
Post-day-14 token unlock begins
  ↓
15% unlocks per day
  ↓
Full lockup becomes unlocked by day 21
```

The normal commitment path is detailed in [Unlock Schedule](/mining/unlock-schedule.md). The separate early-exit path is detailed in [Emergency Exit](/mining/emergency-exit.md).

### Mining Pool revenue

In Phase 1, 35% of the Creator Fee allocation funds the Mining Pool. The Creator Fee is generated through pump.fun trading activity.

In later phases, GPU rental and inference service revenue can become additional Mining Pool sources. These future sources are not current Mining Pool revenue.

```
Trading volume
  ↓
0.30% Creator Fee
  ↓
35% Creator-Fee allocation
  ↓
Mining Pool
  ↓
Epoch-level distribution
  ↓
Miner share based on Mining Power
```

### Reward-share invariant

For each Epoch, a miner's share is determined by:

$$
\frac{\text{Miner Mining Power}}{\text{Total Mining Power}}
$$

The calculation of an Epoch payout is specified in [Epochs & Rewards](/mining/epochs-and-rewards.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 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/mining-overview.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.