> 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-token.md). # BRIDGE token The BRIDGE token serves a multifaceted role within the Octus Bridge ecosystem, acting as a cornerstone of the platform's governance and economic model. 1. **Voting Rights and Liquidity Management**: BRIDGE tokens empower holders with voting rights, enabling active participation in platform governance, including liquidity pool management. 2. **Dividend Distribution**: BRIDGE token holders are entitled to receive dividends in proportion to their staked amount. Staking BRIDGE tokens presents an opportunity to earn a share of generated income. 3. **Relayer Participation**: BRIDGE tokens grant the ability to become a relayer, contributing to the network's operation and earning additional income through this role. Furthermore, users can participate in farming by adding liquidity to various pairs on FlatQube, subsequently receiving BRIDGE tokens as rewards. --- # 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-token.md?ask=&goal= ``` `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.