# Discord Channels

You can follow the full resolution process through several Discord channels on both **Polymarket** and **UMA**.

Each stage of the proposal and resolution cycle is announced through specific channels, allowing you to track updates in real time.

### Proposal Requested

If you find a market that is ready to be proposed, you can submit it with supporting evidence in **#proposal-requests** on the UMA Discord.

<figure><img src="/files/9kNPJLIwPlfMUyCnsQxU" alt=""><figcaption></figcaption></figure>

### Proposal Submitted

When a proposal is submitted, updates appear in two places:

#### Polymarket Discord

In the **#proposals** channel, the **Proposals Alerts bot** sends a message for every new market proposal.

<figure><img src="/files/4uT6E0NMi0T7v6Wawt0B" alt=""><figcaption></figcaption></figure>

#### UMA Discord

In the **#oo-live-feed** channel, the **UMA Infrastructure bot** posts whenever a proposal is submitted to the Oracle.

<figure><img src="/files/BARAIDSPXXsj4bfh3fB8" alt=""><figcaption></figcaption></figure>

### Verification

After a proposal has been submitted, the **Ticket Tool** on UMA Discord automatically creates a new channel for each proposal.

<figure><img src="/files/qlLfTyEm8HzsQafQUlsR" alt=""><figcaption></figcaption></figure>

#### Verification Channel

Each channel is named **#proposal-######**. In these channels, verifiers review the submitted proposal and discuss whether it is correct.

<figure><img src="/files/KkVKjJ3jyXOlZ61jkAIe" alt=""><figcaption></figcaption></figure>

#### Correct Proposal

If the proposal is considered correct, a verifier will mark it as reviewed and accurate.

<figure><img src="/files/mkSvSG006nj1LPbj8J0t" alt=""><figcaption></figcaption></figure>

#### Incorrect Proposal

If a proposal is incorrect or unclear, verifiers post a notice in **#dispute-alerts** to notify the community.

<figure><img src="/files/uLxH4EBZ3zByBeYrsPEl" alt=""><figcaption></figcaption></figure>

### Market Resolved

When the Oracle confirms the final result, the **PolyResolutions bot** posts the outcome in the **#resolutions** channel on the Polymarket Discord.

<figure><img src="/files/bsKQmst31q1SBKLTWCAz" alt=""><figcaption></figcaption></figure>

### Review

Timeline of channels:

1. **#proposal-requests** — Market suggested for proposal (UMA Discord)
2. **#oo-live-feed** — Proposal submitted to the Oracle (UMA Discord)
3. **#proposals** — New proposal posted (Polymarket Discord)
4. **#proposal-######** — Verification discussion created (UMA Discord)
5. **#dispute-alerts** — Dispute notice if proposal is incorrect (UMA Discord)
6. **#resolutions** — Final outcome posted (Polymarket Discord)


---

# Agent Instructions: 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:

```
GET https://polymarketguide.gitbook.io/polymarketguide/resolution/the-resolution-process/discord-channels.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.