> For the complete documentation index, see [llms.txt](https://docs.nomic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nomic.io/governance.md).

# Governance

Nomic is governed by holders of the NOM token.

Whilst the project undergoes a security audit, the bridge currently implements a capacity limit of **21 BTC**, and fixed deposit and IBC transfer fees. BTC deposits are disabled by the protocol when the bridge reaches this capacity limit.

After the successful completion of the audits, the network’s next upgrade will put control of the capacity limit and fee parameters under control of NOM holders using simple coin voting via the Nomic app. The right to vote may also be delegated to validators.

A beta governance system is currently in place. A future upgrade will be released which will introduce a novel futarchy-based governance mechanism for lifting the NOM transfer restriction and selecting other chain parameters.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nomic.io/governance.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.