> 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/why-gpufi.md). # Why GPUFi Explains the need for GPUFi and its yield-before-hardware approach. ### The model GPUFi is approaching GPUFi's view is that many DePIN models begin with hardware before enough demand or participation exists to fully use it. GPUFi reverses that sequence. It intends to establish an economic mechanism first, accumulate treasury through activity, then build hardware infrastructure later. This is GPUFi's model and thesis. It is not a universal statement about every DePIN project. ### Why Robinhood Chain GPUFi positions Robinhood Chain as an environment built around RWA activity. * The project sees access to retail users and stock-token activity as relevant. * It references Robinhood Chain's stock-token environment and users holding assets such as stock tokens. * GPUFi chose Robinhood Chain over Ethereum or Solana for this combination of RWA infrastructure and retail accessibility. Robinhood Markets is not a GPUFi partner. ### Why NVIDIA and NVDA NVIDIA is the reference point for GPUFi's GPU infrastructure narrative. The NVDA stock token is the RWA anchor in the project's design. **NVDA and GPU narrative** → **GPUFi token** → **mining license** → **trading activity** → **treasury** → **GPU acquisition** → **GPU infrastructure** {% hint style="info" %} GPUFi has no partnership with NVIDIA. NVIDIA does not endorse GPUFi. The project states that NVIDIA does not know GPUFi exists. {% endhint %} ### The GPUFi thesis The token creates economic activity. Trading activity creates tax revenue. Tax revenue funds the mining pool and treasury. Treasury accumulation is intended to acquire physical GPUs. Those GPUs are intended to generate additional ecosystem revenue through rental. Later phases are intended to introduce GPU operators that contribute hardware. An inference API is also planned so developers can pay for compute. {% hint style="warning" %} GPU infrastructure, GPU operators, and the inference API are future phases. They are not current capabilities. {% endhint %} Next, continue to [How It Works](/how-it-works.md) for the system mechanics. --- # 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/why-gpufi.md?ask=&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.