> For the complete documentation index, see [llms.txt](https://polymarketguide.gitbook.io/polymarketguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polymarketguide.gitbook.io/polymarketguide/case-studies/becoming-a-voter.md).

# Becoming a Voter

In collaboration with UMA.rocks

In the [How to Participate](/polymarketguide/resolution/how-to-participate.md) section, we covered three ways to participate in the UMA Oracle: proposing and disputing, participating in resolution discussions, and voting.

To review, here's how each works:

* **Proposals and disputes:** Participants submit an answer for how a market should resolve or challenge an existing proposal.
* **Discussion:** Anyone can share evidence and arguments about the correct resolution.
* **Voting:** UMA stakers vote on the outcome when a dispute reaches the oracle.

Proposals and disputes bring a resolution question to the oracle, while discussion helps surface the relevant evidence and arguments. Voting ultimately determines the oracle's answer.

This case study focuses on **voting**. When a disputed market reaches the voting stage, UMA stakers determine its final outcome.

<figure><img src="https://3511841878-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwmHFi7NV8gmAN3L4jVKb%2Fuploads%2Fgit-blob-f425dc548ff3f7c847c42802bb5a9025bae952f6%2Fimage%20(1194).png?alt=media" alt=""><figcaption><p>Source: UMAProtocol</p></figcaption></figure>

#### Coming Up

In this case study, we compare solo voting with voting pools, examine how UMA.rocks operates, and walk through what it takes to join a voting pool.