> 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/risks/regulatory-risk.md). # Regulatory Risk Explains unresolved legal treatment of mining rewards and jurisdictional uncertainty. The regulatory treatment of GPUFi mining rewards is not settled. ### Current legal position * No legal opinion has been obtained determining whether mining rewards could be considered a security. * The project references the Howey framework as a relevant consideration. * The project frames mining rewards as community rewards rather than an investment product. This framing does not determine how a regulator or court would classify the mechanism. ### Why the question matters Regulatory classification could affect who can access the mechanism, how it operates, and whether changes are required. The project identifies possible consequences that include restricting access, changing the mechanism, or shutting down mining. These are possible consequences identified by the project. They are not predictions. ### Jurisdiction Regulatory treatment can differ by jurisdiction. A treatment applicable in one jurisdiction may not apply in another. ### Planned legal review Legal counsel is planned before launch. {% hint style="warning" %} GPUFi is not claiming that its community reward framing guarantees a particular legal classification. {% endhint %} Next, [Smart Contract Risk](/risks/smart-contract-risk.md) covers the mining contract's current implementation status. --- # 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/risks/regulatory-risk.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.