> For the complete documentation index, see [llms.txt](https://docs.megalottery.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.megalottery.fun/start-here/win-power.md).

# WIN POWER

WIN POWER, or **WP**, is the weight of a wallet in a draw. It is not a separate token and it is not something you buy directly.

```
raw WIN POWER  = floor($MEGA balance / 10,000)
live WIN POWER = max(raw WIN POWER - remaining winner deduction, 0)
```

## The simple rule

Every whole 10,000 `$MEGA` in a wallet creates 1 raw WP.

| `$MEGA` balance | Raw WP |
| --------------: | -----: |
|          10,000 |      1 |
|          50,000 |      5 |
|         500,000 |     50 |
|       5,000,000 |    500 |

More WP means more weight, but never guarantees a prize.

## How odds work

Before a draw, imagine all WIN POWER as numbered positions in one long list. A wallet with 50 WP owns 50 positions; a wallet with 5 WP owns 5 positions.

For the first winner, a useful approximation is:

```
your chance = your WP / total WP of all eligible wallets
```

The contract then removes the first winner's weight and selects the second, then removes both previous winners and selects the third. This guarantees **three different wallets**.

{% hint style="info" %}
The exact probability of winning any of the three places depends on the WP held by the wallets selected before yours. The contract performs the selection without replacement.
{% endhint %}

## What changes your WP

| Action                     | Effect                                                       |
| -------------------------- | ------------------------------------------------------------ |
| Buy more `$MEGA`           | Raw WP increases from the new net balance                    |
| Sell `$MEGA`               | Raw WP decreases with the balance                            |
| Transfer to another wallet | Tokens and their proportional winner deduction move together |
| Win a prize                | Live WP is reduced by place                                  |
| Sell the full balance      | The remaining deduction on that sold balance is released     |
| Buy again later            | New net balance earns fresh raw WP                           |

## Winner deductions

Winning does **not** burn or remove your `$MEGA` tokens. It reduces only the wallet's live WIN POWER.

| Place |       WP deduction |
| ----- | -----------------: |
| 1st   | 30% of snapshot WP |
| 2nd   | 20% of snapshot WP |
| 3rd   | 10% of snapshot WP |

Example: a wallet enters a draw with 50 WP and wins first place. A 15 WP deduction is recorded, so the wallet has 35 live WP while its token balance stays unchanged.

## Why moving tokens does not erase the deduction

A wallet-to-wallet transfer carries the same proportional share of the deduction with the tokens. Moving half of a winning balance moves half of its remaining deduction too.

Trading behaves differently by design: selling releases the deduction in proportion to the share sold. Selling the full balance releases it completely, and a later taxed buy earns new WP from the new net balance.

{% content-ref url="/pages/i6f9W0i0drmpWnPARCn6" %}
[Prizes, claims & win deductions](/the-lottery/payouts-and-claims.md)
{% endcontent-ref %}


---

# 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.megalottery.fun/start-here/win-power.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.