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

# Overview

Introduces GPUFi, its purpose, and the mechanism connecting trading, mining, treasury growth, and GPU infrastructure.

GPUFi is building a mining ecosystem around GPU infrastructure, but it does not begin with physical GPUs.

**Yield first**\
→ **Community second**\
→ **Hardware third**

The intended economic path is:

**Trading activity** → **trading tax** → **treasury accumulation** → **mining rewards** → **GPU acquisition** → **future GPU infrastructure**

### The three building blocks

#### GPUFi Token

The token is the economic entry point into the ecosystem. Every trade carries a **3% creator tax**.

That tax supports burn, the mining pool, holder sharing, the treasury, and the operator reserve. The detailed allocation appears in Tokenomics.

#### Mining Contract

GPUFi calls this mechanism **mining**, not staking. Users commit tokens and time to obtain mining power.

Mining power increases over a 21-day period. The mining pool distributes rewards hourly. The detailed formula and parameters appear later.

#### GPU Infrastructure

Physical GPU infrastructure is not available in Phase 1. Phase 1 yield comes from the trading tax.

Phase 2 is intended to use treasury accumulation to acquire the first GPUs. Later phases introduce GPU operators and, eventually, an inference API.

{% hint style="warning" %}
GPUFi is not currently an established GPU-backed infrastructure network. The initial system is funded by trading activity, so it does not promise fixed yield. Physical GPU infrastructure is planned as the ecosystem develops.
{% endhint %}

The next page sets out the principles behind this sequence.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gpu-fi.uk/introduction/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.