> For the complete documentation index, see [llms.txt](https://ton-ls-protocol.gitbook.io/ton-liquid-staking-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ton-ls-protocol.gitbook.io/ton-liquid-staking-protocol/protocol-components/governance-components/sudoer.md).

# Sudoer

### Overview

While initially empty, Sudoers gain the ability to send arbitrary messages from various parts of the system. 

Sudoers are generally empty by default and are used to send arbitrary messages from arbitrary portions of the system. They are used to significantly upgrade code within the protocol and to perform minor maintenance on the following components:

* Pool smart contracts
* Controller smart contracts

### Security Policy

Strict secure cold wallet, for example, Ledger.

### Deploy Policy

Sudoer smart contracts can be deployed only by Governors. Sudoer only becomes active if set more than *sudoer\_threshold* seconds ago (expected to be 24h). 

Sudoer could be deployed in the Basechain.


---

# 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://ton-ls-protocol.gitbook.io/ton-liquid-staking-protocol/protocol-components/governance-components/sudoer.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.