> 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/gpu-infrastructure/from-treasury-to-gpus.md).

# From Treasury to GPUs

Understand how creator-fee revenue is intended to move from treasury accumulation toward physical GPU infrastructure.

USE-GPU begins with a fee-funded mining system, not physical hardware. The treasury is the intended bridge between current trading activity and future GPU infrastructure.

```
TRADING ACTIVITY
        ↓
0.30% CREATOR FEE
        ↓
USE-GPU TREASURY
        ↓
┌───────────────────────────┐
│ Mining Pool               │
│ GPU Treasury              │
│ Holder Sharing            │
│ Buyback and Burn          │
│ Operations                │
└───────────────────────────┘
```

The GPU Treasury receives **30% of creator-fee revenue**. It is designated for GPU purchases, development, and growth. This is not 30% of the entire treasury, and the GPU Treasury is only one destination for creator-fee revenue.

### Yield before hardware

Phase 1 establishes trading activity, creator-fee revenue, mining participation, and treasury accumulation. There are no GPUs in this phase. Creator fees are the current revenue source.

The intended sequence puts economic activity before hardware acquisition. A GPU purchased before sufficient activity exists creates a cost base. USE-GPU instead plans to accumulate the GPU Treasury first, then introduce hardware progressively.

```
GPU TREASURY
        ↓
FIRST GPU ACQUISITION
        ↓
GPU DEPLOYMENT
        ↓
GPU RENTAL
        ↓
COMPUTE SERVICES
```

Trading activity affects creator-fee revenue. Creator-fee revenue affects treasury accumulation. More activity can increase accumulation, while lower activity can slow the path toward the first GPUs.

The treasury therefore connects the current mining system to planned physical compute infrastructure.


---

# 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/gpu-infrastructure/from-treasury-to-gpus.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.