> 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/how-it-works/what-we-are-building.md).

# What We Are Building

Defines the system GPUFi is designed to build over time.

GPUFi has three primary components: the GPUF token, the mining contract, and planned GPU infrastructure. The token is the economic entry point into the ecosystem.

### GPUFi token

| Parameter    | Value              |
| ------------ | ------------------ |
| Name         | GPUFi              |
| Symbol       | GPUF               |
| Chain        | Robinhood Chain    |
| Total supply | 1,000,000,000 GPUF |
| Decimals     | 18                 |
| Quote asset  | ETH                |
| Creator tax  | 3% on every trade  |

The creator tax funds several destinations. Its exact split is defined in [Tax Architecture](/how-it-works/tax-architecture.md).

### Mining contract

GPUFi calls this mechanism *mining*, not staking. Users commit GPUF tokens and time. Mining power grows linearly from roughly 5% on day one to 100% on day 21.

* The mining pool pays rewards every hour.
* Users can claim multiple hours at once to reduce gas overhead.
* After day 21, mining power remains at 100%.
* Tokens then unlock gradually at 10% per day.
* The full lockup becomes withdrawable by day 31.

An emergency exit before the full period returns 90% of committed tokens. The remaining 10% goes to the mining pool.

One wallet can hold mining power from at most 2% of total supply. With a 1,000,000,000 GPUF supply, this equals 20,000,000 GPUF.

Mining rewards come from the mining pool. The pool is funded initially by the mining portion of trading tax. Future GPU rental and inference API activity are intended to add revenue to the pool.

### GPU infrastructure

{% hint style="info" %}
Phase 1 has no physical GPUs. Revenue and mining-pool funding come from trading tax.
{% endhint %}

| Phase   | Planned development                                                                                                                                                                                                                                    |
| ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Phase 2 | Treasury is intended to purchase the first GPUs, targeting two NVIDIA RTX 3090 units at around $1,500 each. After purchase, the project intends to publish serial numbers, photos, hosting location, uptime logs, and monthly utilization information. |
| Phase 3 | External GPU operators can contribute hardware. Operators are intended to receive 70% of rental fees. Admin is planned to be permanently renounced.                                                                                                    |
| Phase 4 | GPUFi intends to introduce an inference API. Developers would pay for compute based on token usage, creating another intended ecosystem revenue source.                                                                                                |

The next step is [Token Launch](/how-it-works/token-launch.md), which explains how GPUF enters the market.


---

# 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.gpu-fi.uk/how-it-works/what-we-are-building.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.