> 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/interactive-blocks.md).

# Payout and Settlement

### Once the outcome is finalized, Polypump’s smart contract immediately settles the market:

* All stakes on the **losing side** are collected. A predetermined fraction of that total is taken out for fees (burn + dev reward).
* The remaining portion of the losing side’s stake becomes the reward pool for the winners.
* Participants who bet on the **winning side** receive their payout automatically. Each winner receives their initial stake back *plus* a share of the losers’ stakes proportional to their contribution to the winning side. This is handled in a single transaction per winner or can be claimed by the user through the platform UI.
* The **burn mechanism** is executed: the fee portion reserved for burning is used to reduce supply. If the market was in $POLYPUMP, those tokens are directly burned. If it was in SOL, the equivalent value could be converted to $POLYPUMP (via a swap on a DEX) and then burned, or in some cases SOL could be sent to an unrecoverable address. This deflationary action increases scarcity of $POLYPUMP, benefiting all token holders.
* The **developer reward** portion is transferred to the designated developer/treasury address. This could be in the form of SOL or $POLYPUMP depending on the market currency and how the fee policy is set. These funds support the platform’s development and maintenance. (In future, this fund might also be partially redistributed as community incentives or used to bootstrap new markets.)

### Finally, the market is marked as **resolved**. The outcome (Yes/No) is recorded and visible. Users can see the final statistics — for example, “Yes won with 1500 $POLYPUMP vs 500 $POLYPUMP staked on No.” The platform might also display the factual outcome (e.g., “600 tokens migrated today, so the result is YES”). All of this happens seamlessly through the Polypump program on Solana, ensuring trustless execution. Users can withdraw their winnings, and the market is closed to further activity. The entire lifecycle from creation to payout is managed on-chain, with the Polypump UI and API providing a user-friendly way to interact with the contracts.


---

# 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/interactive-blocks.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.