> 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/resolution/how-to-participate/verify/tips.md).

# Tips

Here are some tips for verifying proposals. 

### Check the Polymarket odds

Check the **Polymarket odds** to see if traders believe the market is ready to be resolved.

*Example*: If a Yes proposal has been submitted but the market is still trading at 50¢, it may suggest the outcome needs further review.

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

### Consider the timing of evidence

Only consider information that was **publicly available** at the time the proposal was submitted.

*Example*: In *Will Trump endorse Andrew Cuomo for NYC Mayor?*, a Yes proposal was submitted after *The New York Times* reported that President Trump endorsed Andrew Cuomo. It was later disputed for not meeting the consensus of credible reporting requirement.

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

### Ask if you're unsure

When you're unsure whether a proposal is accurate, **gather as many details as possible** before verifying.

*Example*: In *South Park: Trump x Satan baby boy or girl?*, the rules referenced *Season 27*, which was expected to have ten episodes. After the season was cut in half, verifiers discussed how to handle the unexpected change before confirming accuracy.

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