> 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.md).

# Risks

Explains the dependencies and uncertainties that affect GPUFi.

GPUFi's design depends on trading activity, treasury accumulation, future physical infrastructure, smart contracts, and regulatory conditions. Each dependency introduces a different type of uncertainty.

This section explains those dependencies clearly.

### Risk areas

| Area                        | What it covers                                                                          |
| --------------------------- | --------------------------------------------------------------------------------------- |
| Economic Risk               | How trading activity affects mining-pool funding and reward variability.                |
| Hardware Risk               | How physical GPU infrastructure depends on treasury accumulation and future deployment. |
| Regulatory Risk             | The unresolved legal treatment of mining rewards and jurisdictional uncertainty.        |
| Smart Contract Risk         | The implementation and audit risks associated with the mining contract.                 |
| Centralization & Admin Risk | The trade-off between early administrative control and permanent future renouncement.   |

> Understanding the mechanism also means understanding what the mechanism depends on.

Start with [Economic Risk](/risks/economic-risk.md), which explains how trading activity funds the mining pool.


---

# 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.md?ask=<question>&goal=<endgoal>
```

`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.