> 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/roadmap.md). # Roadmap Sets out the planned milestones for GPUFi development. ## Roadmap GPUFi's roadmap is an intended progression, not a promise of fixed delivery dates. Each phase builds on the economic infrastructure established before it. ``` Trading-funded mining ↓ First physical GPUs ↓ External GPU operators ↓ Developer compute ``` Progress depends on actual ecosystem activity and treasury accumulation. The roadmap describes what changes when each phase is reached. ### Current state {% hint style="info" %} **Current status: Phase 1. GPU infrastructure has not been deployed yet.** {% endhint %} GPUFi begins with trading-funded mining. There are no physical GPUs yet, and mining is initially funded by trading activity. The treasury accumulates through its creator-tax allocation. Physical GPU infrastructure is planned for later phases. | Current | Planned for later phases | | --------------------- | ----------------------------------- | | Trading-funded mining | Physical GPU infrastructure | | Treasury accumulation | GPU rental activity | | GPU-powered ecosystem | Inference API and developer compute | ### Phase 1: Trading-Funded Mining **Objective:** Establish GPUFi's economic foundation before physical GPU infrastructure exists. Phase 1 connects trading activity to mining rewards and treasury accumulation. The 3% creator tax supplies the initial mechanism: 25% of that tax enters the mining pool, equivalent to 0.75% of every trade, and 30% accumulates in the treasury. Users can commit GPUF into the mining contract. Mining power increases toward 100% over 21 days. Rewards are distributed hourly and depend on trading activity and the amount entering the mining pool. This phase is designed to establish the mechanism that can fund later infrastructure. It does not promise a fixed APY. #### What Phase 1 does not have * No physical GPUs. * No GPU rental revenue. * No external GPU operators. * No inference API. GPUFi is a GPU-powered ecosystem in this phase. It is not currently GPU-backed. ### Phase 2: First GPU Infrastructure **Objective:** Convert accumulated treasury into the first physical GPU infrastructure. The roadmap target is approximately one to two months after launch. It targets two NVIDIA RTX 3090 units at approximately $1,500 per unit. These are roadmap targets, not guaranteed purchases. Phase 2 marks the intended transition from a trading-funded mining mechanism toward physical GPU infrastructure. #### Verification after purchase After GPUs are actually purchased, GPUFi intends to publish: * Serial numbers and photos. * Hosting location and monthly uptime reports. * Utilization information. This disclosure is intended to make the physical infrastructure publicly verifiable. {% hint style="success" %} **Phase 2 milestone:** GPUFi intends to use GPU-backed language only once physical GPUs are live and generating rental revenue. Until then, it remains a GPU-powered ecosystem. {% endhint %} ### Phase 3: GPU Operator Ecosystem **Objective:** Expand the physical infrastructure layer beyond GPUs purchased directly through the treasury. External contributors can provide physical GPUs as GPU operators. ``` External GPU operators ↓ Provide GPUs ↓ GPUs participate in rental activity ↓ Operators are intended to receive 70% of rental fees ``` The roadmap does not assign the remaining rental fees to a destination. #### Admin-control transition Phase 3 includes the planned permanent and irreversible renouncement of admin control. Before this phase, admin control exists. Phase 3 is intended to remove that control permanently. This is a deliberate design commitment. It also means future administrative changes cannot simply be made by the team. It is not a guarantee that the system is risk-free. ### Phase 4: Inference API **Objective:** Add a developer-facing compute layer to GPU infrastructure. GPUFi intends to introduce an inference API. Developers would pay per token of compute. ``` GPU Infrastructure ↓ Inference API ↓ Developer Compute Usage ↓ Compute Revenue ↓ Mining Pool ``` Actual compute usage is intended to create another ecosystem revenue source. Future GPU rental revenue and future inference API revenue are intended to contribute to the mining pool. Phase 4 is intended to move GPUFi toward a more self-sustaining ecosystem through actual compute usage. #### Revenue sources by phase | Phase 1 | Later phases | | ----------------------------------------------- | ---------------------------------------------------------------------------------------- | | Trading activity is the initial revenue source. | Trading activity, GPU rental, and inference API revenue can contribute to the ecosystem. | Trading tax remains part of the intended ecosystem flow. GPU rental and inference API revenue do not currently exist. ### Roadmap at a glance ``` PHASE 1 Trading-Funded Mining No GPUs ↓ PHASE 2 First Treasury-Funded GPUs ↓ PHASE 3 External GPU Operators + Permanent Admin Renouncement ↓ PHASE 4 Inference API + Developer Compute ``` The roadmap depends on actual ecosystem activity and treasury accumulation. Low trading activity can slow the transition toward physical 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://docs.gpu-fi.uk/roadmap.md?ask=&goal= ``` `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.