> 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/how-it-works/market-resolution-logic.md).

# Market Resolution Logic:

## Each market has a predefined condition that must be checked at resolution. Polypump’s backend will automatically **verify the market condition** once the expiration time is reached (or immediately when a triggering event occurs, if it’s an event-driven market). This verification is done by retrieving on-chain data or via an oracle:

* For a market about **price or market cap**, Polypump queries the token’s on-chain trading data and supply. For example, it can multiply the token’s current price (from a DEX or oracle like Pyth) by its circulating supply to get market capitalization at the deadline, then compare it to the target value.
* For a market about **token events** (such as migrations, listings, or holder counts), the platform checks the relevant on-chain registry or smart contract. In pump.fun’s context, a “migration” might refer to tokens graduating from the pump.fun bonding curve to a public market or moving to another network. The system can count how many tokens have migrated on that day by reading event logs or a dedicated counter in the pump.fun program.
* Other conditions (e.g., “Did token X achieve Y number of holders?” or “Was a new contract deployed for token Y?”) are similarly verified through on-chain data or trusted oracle feeds that Polypump integrates with.

### If the condition is met, the outcome is **Yes**, otherwise **No**. Importantly, this check is trustless and automatic — once the smart contract or oracle confirms the data, the outcome is decided without manual intervention.


---

# 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/how-it-works/market-resolution-logic.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.