> For the complete documentation index, see [llms.txt](https://crus.gitbook.io/crus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crus.gitbook.io/crus/governance/understanding-governance.md). # Understanding Governance Governance is crucial to the protocol, which is given to the decentralized community DAO. the community DAO determines the protocol development direction and incentive matters, including product upgrades, token economic model upgrades, issuance volume, interest rates, stable coin liquidity allocation, etc. DAO weights are unique - and mutually exclusive, so you can only choose to give either trading governance or liquidity governance, for acceleration or voting, for the same period.Community members can participate in DAO governance using veCrus with voting rights. ### **Voting on the** Crus **DAO** To vote on the Crus DAO, users need to lock vote lock their Crus. By doing so, participants can earn a boost on their provided liquidity and vote on all DAO proposals. Users who reach a voting power of 2000 veCrus can also create new proposals. There is no minimum voting power required to vote. ### **Voting Power** veCrus stands for vote escrowed Crus, it's a locker where users can lock their Crus for different lengths of time to gain voting power. Users can lock their Crus for a minimum of week and a maximum of four years. As users with long voting escrow have more stake, they receive more voting power. ### **Submitting proposals** If you wish to create a new official proposal, you should draft a proposal and post it on the governance forum. You must also research that it's possible and gauge interest of the community via the Crus Discord or Governance forum. If you're not sure about the technical details of submitting your proposal to the Zksync blockchain, you can ask a member of the team to help. --- # 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://crus.gitbook.io/crus/governance/understanding-governance.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.