> For the complete documentation index, see [llms.txt](https://xdocs.ngd.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xdocs.ngd.network/bridge/general/roles-responsibilities.md).

# Roles and Responsibilities

The bridge involves several distinct roles that are managed in the BridgeManagement contract. Besides the already elaborated Validator and Relayer role, there exist the following additional roles:

* Owner
* Governor
* SecurityGuard

The owner is a multi-sig account consisting of keys stored in cold wallets. Its main responsibility is assigning roles as well as performing contract updates. On Neo X exclusively, the responsibility of updating the contracts lies with the Neo X committee, ultimately reducing the owner's responsibility on the bridge contracts on Neo X to role assigning only.

The governor is responsible for pausing/unpausing, updating parameters, and registering tokens.

Finally, the security guard is allowed to pause contracts with the intention of using this role for emergency intervention.

The table below provides an overview of the main functionalities of the smart contracts and who is allowed to use them.

<table><thead><tr><th width="220">Functionality</th><th width="230">Management</th><th width="150">TokenBridge</th><th width="150">MessageBridge</th></tr></thead><tbody><tr><td>Update Contract (N3/Neo X)</td><td>Owner/Committee</td><td>Owner/Committee</td><td>Owner/Committee</td></tr><tr><td>Assign Roles</td><td>Owner</td><td>-</td><td>-</td></tr><tr><td>Pause</td><td>-</td><td>Governor and SecurityGuard</td><td>Governor and SecurityGuard</td></tr><tr><td>Unpause</td><td>-</td><td>Governor</td><td>Governor</td></tr><tr><td>Update a Parameter (e.g., fee)</td><td>-</td><td>Governor</td><td>Governor</td></tr><tr><td>Register a Token</td><td>-</td><td>Governor</td><td>Governor</td></tr><tr><td>Request Bridging Tokens/Messages</td><td>-</td><td>Anyone</td><td>Anyone</td></tr><tr><td>Relaying Requests</td><td>-</td><td>Relayer (incl. enough Validator signatures)</td><td>Relayer (incl. enough Validator signatures)</td></tr></tbody></table>

> **IMPORTANT:**
>
> Although only the relayer is authorized to use the distribution/relaying functionality, it requires sufficiently enough signatures of validators. The required threshold of validator signatures is set in the BridgeManagement contract.


---

# 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://xdocs.ngd.network/bridge/general/roles-responsibilities.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.