> 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/centralization-and-admin-risk.md).

# Centralization & Admin Risk

Explains early administrative control and planned permanent renouncement.

{% hint style="info" %}
Admin control exists during Phase 1 and Phase 2.
{% endhint %}

### Early admin control

During the early phases, administrative control exists. The system has not yet reached the planned permanent renouncement stage.

The actual contract design determines which changes may be possible through the admin mechanism.

### Phase 3 renouncement

Phase 3 is planned to include admin renouncement. The renouncement is intended to be permanent and irreversible.

Its purpose is to remove ongoing team administrative control once the project reaches that stage. It does not provide an absolute decentralization guarantee.

### The trade-off

| Before renouncement                                                                               | After renouncement                                                                |
| ------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
| Administrative control remains.                                                                   | Team administrative control is removed.                                           |
| Changes may remain possible through the admin mechanism, depending on the actual contract design. | Future administrative intervention is no longer available.                        |
| Admin intervention remains part of the system's available control surface.                        | Bugs discovered after renouncement may not be fixable through admin intervention. |

The project accepts this as a design trade-off. Neither state eliminates risk.

### Irreversibility

Permanent renouncement means the team cannot simply restore administrative control later. This is intentional.

The same property that limits future administrative intervention can leave fewer possible remediation paths for future bugs.

### Current and future state

| Stage   | Admin state                    |
| ------- | ------------------------------ |
| Phase 1 | Admin exists                   |
| Phase 2 | Admin exists                   |
| Phase 3 | Planned permanent renouncement |

Phase 3 has not happened yet.

GPUFi treats administrative control and permanent renouncement as an explicit design trade-off, not as a claim that one state eliminates risk.


---

# 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/centralization-and-admin-risk.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.