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

# Bridge DAO

Octus Bridge operates without a centralized decision-making mechanism. Instead, it embraces decentralization through its DAO (Decentralized Autonomous Organization) interface. The DAO facilitates the adoption of operational decisions directly by the Bridge's user community. Users actively participate using BRIDGE, the native utility token of the platform.

Every stakeholder holding BRIDGE tokens has the ability to cast their votes on platform proposals raised within the DAO. Moreover, the management of the liquidity locked in the Bridge's vault is orchestrated through the DAO protocol.

For stakeholders with a significant BRIDGE token share, the opportunity to propose initiatives for voting is also available. To engage in the voting process, navigate to the **Governance** tab on the Bridge site, where ongoing and completed proposal votes are listed. If you wish to submit your proposal, access the **Create Proposal** section within the Governance interface. Note that a minimum of 100,000 BRIDGE tokens is required to create a proposal.


---

# 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.octusbridge.io/use/governance/concepts/bridge-dao.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.