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

# Prizes, claims & win deductions

Prize percentages, automatic ETH delivery, claim fallback and WIN POWER deductions.

## Prize distribution

Every completed draw uses the pot saved at snapshot time.

| Result           | Share | What the winner receives                                |
| ---------------- | ----: | ------------------------------------------------------- |
| 1st place        |   50% | ETH                                                     |
| 2nd place        |   30% | ETH                                                     |
| 3rd place        |   15% | ETH                                                     |
| Buyback and burn |    5% | Buys `$LOTRIO` on Pons and sends it to the dead address |

## How a winner receives ETH

Normally the contract pushes ETH directly to the winning address during settlement. The holder does not approve, sign or claim anything.

{% hint style="success" %}
**Normal case:** the draw settles and ETH appears automatically in the winning wallet.
{% endhint %}

## When `claim()` is needed

Some smart-contract wallets reject a direct ETH transfer. In that case:

1. the draw still completes;
2. the failed amount is recorded in `unclaimedPrizes` for that winner;
3. the ETH remains reserved inside the lottery contract;
4. the winning wallet can later call `claim()`.

Reserved prizes are excluded from the available pot, so they cannot be paid to somebody else in a later draw.

## What winning changes

Winning reduces the winner's live WP, not the token balance.

| Place | Prize | WP deduction |
| ----- | ----: | -----------: |
| 1st   |   50% |          30% |
| 2nd   |   30% |          20% |
| 3rd   |   15% |          10% |

The deduction is calculated from the wallet's WP in the committed snapshot.

### Example

A wallet had 50 WP when the snapshot was created and later wins first place:

```
snapshot WP:       50
first-place cut:   15 WP
new live WP:       35
$LOTRIO removed:     0
```

Buying more can raise raw WP again. Selling releases the deduction proportionally; selling the entire balance clears the remaining deduction attached to that balance. Each deduction recovers 25% after 24, 48, 72 and 96 completed draws — see [WIN POWER](/start-here/win-power.md#recovery).

## Where does the other 5% go?

5% of every committed pot goes to buyback and burn. The lottery sends it to the separate buyback burner contract, which buys `$LOTRIO` on Pons and sends every token to the dead address. The burner has no owner and no withdraw function, so its ETH can leave only as a `$LOTRIO` purchase.

The buyback cannot block winner payments. If the lottery cannot send the 5% to the burner, the draw still settles and that ETH rolls into the next pot.

There is no house cut at draw time. The team's 20% share of creator fees stays in the treasury wallet before the ETH ever reaches the lottery; everything inside the lottery is paid out as prizes and the 5% burn.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lotrio.app/the-lottery/payouts-and-claims.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.