> For the complete documentation index, see [llms.txt](https://whitepaper.dexe.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.dexe.network/voting-logic/validators-voting.md). # Validator's voting Validator voting is the second round activated when configuring the Validators assigned during creating a DAO or when making further changes to the DAO's constitution. It is an additional security measure designed to protect the DAO from malicious proposals and manipulations, similar to double-factor authentication. After the main voting phase, the Validator voting begins. Validators use a separate token that cannot be transferred to another wallet. Validator voting takes effect after the main voting phase and also has its own quorum and voting duration settings. After the Validator voting ends, the proposal is either accepted and proceeds to the execution stage or rejected. Additionally, Validators have their own types of proposals that they can conduct without involving the entire DAO. These proposals are essential for managing the DAO's sustainability processes that do not require full DAO participation to avoid slowing down operations. --- # 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://whitepaper.dexe.network/voting-logic/validators-voting.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.