> 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/manifesto.md). # Manifesto States the principles and long-term vision behind GPUFi. Most DePIN projects start with hardware they cannot fill and users who never come. GPUFi starts from the other direction. > **Yield first.**\ > **Community second.**\ > **Hardware third.** GPUFi is a mining license for an ecosystem that does not yet exist. The ecosystem is built progressively. Its initial yield mechanism does not depend on physical GPUs. Treasury accumulation is intended to move the project toward real GPU infrastructure. ### Yield before hardware Phase 1 does not have GPUs. Initial yield comes from trading activity. The trading tax funds the mining pool and treasury. The treasury is intended to eventually acquire physical GPUs. ### Transparency over promise Transparency is part of the system's design philosophy. * Every number should be onchain. * Every address should be public. * Every roadmap item should have a status. * The project should not claim to have something it does not have. If GPUFi does not have GPUs yet, it should say so. If a contract is not audited yet, it should say so. If yield depends on trading volume, it should say so. ### Renounce as commitment Admin control exists during the early phases. Phase 3 is planned to renounce that control. The renounce is intended to be permanent and irreversible. The stated goal is an ecosystem that continues without team control. This is a design commitment with trade-offs. Those trade-offs are discussed later in the Risks section. ### What GPUFi is not GPUFi is not NVIDIA.\ GPUFi is not Robinhood.\ GPUFi is not a dividend. GPUFi describes itself as: > “a tax-funded mining ecosystem that buys GPUs with treasury and pays miners with volume.” --- # 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/manifesto.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.