> For the complete documentation index, see [llms.txt](https://dao-docs.everclear.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dao-docs.everclear.org/dao-documents/processes/how-to-vote.md).

# How to Vote

{% hint style="warning" %}
This document is currently subject to public review before being finalized. If you notice a revision that needs to be made or have feedback, please [request a revision](https://github.com/connext/gitbook-docs/issues/new) or start a conversation with us on Discord at <https://discord.com/invite/everclear>
{% endhint %}

As a member of the Connext DAO, you can actively participate in the DAO's decision-making process by voting on governance proposals that other DAO members submit.

As a CLEAR token holder (or delegate), you can participate in these Snapshot polls and "temperature check" discussions:

1. Go to the Connext DAO governance forum.
2. Locate the proposal you'd like to vote on and read through the proposal and the discussion thread.
3. Provide feedback and participate in the discussion to help shape the proposal.
4. The forum submission for any given proposal will usually include a link to a Snapshot poll that allows you to vote on the proposal:
   * Navigate to **Snapshot**.
   * Connect your wallet.
   * Open the **Connext DAO Snapshot space** and locate the proposal you'd like to vote on (or click the Snapshot link in the forum submission).
   * Cast your vote by following the prompts within Snapshot's UI. Voting options are “For,” “Abstain,” and “Against.”


---

# 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://dao-docs.everclear.org/dao-documents/processes/how-to-vote.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.