> For the complete documentation index, see [llms.txt](https://docs.polypump.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.polypump.app/documentation/polypump-process/images-and-media.md).

# Outcome Resolution

### At the predetermined expiration time (or trigger moment), the market closes and no further bets are allowed. Polypump’s resolution mechanism now kicks in. The system checks the condition attached to the token’s address:

* If the condition is **met**, the outcome is determined to be “Yes.”
* If the condition is **not met**, the outcome is “No.”

### For instance, if the market question was about a token’s market cap and the target was surpassed by the deadline, that yields a “Yes” outcome. If not, “No” wins. This check is done automatically via on-chain queries or an oracle, ensuring fairness and accuracy. In our example screenshot question “Will more than 500 shitcoins migrate today?”, at the end of the day the system would count the actual number of token migrations that occurred on pump.fun that day by reading the platform’s contract state. Based on that count, it would resolve the market to Yes or No accordingly.


---

# 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://docs.polypump.app/documentation/polypump-process/images-and-media.md?ask=<question>&goal=<endgoal>
```

`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.