> 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/help/glossary.md).

# Glossary

| Term                 | Plain meaning                                                                                                        |
| -------------------- | -------------------------------------------------------------------------------------------------------------------- |
| **WIN POWER / WP**   | A wallet's lottery weight. Normally 1 WP per whole 10,000 `$MEGA`, minus any remaining winner deduction.             |
| **Eligible wallet**  | A non-system wallet with at least 1 live WP.                                                                         |
| **Treasury / pot**   | ETH available for the next lottery draw, excluding already owed prizes or marketing payments.                        |
| **Snapshot**         | The fixed participant weights used for one specific draw. Later trades do not change it.                             |
| **Merkle-sum root**  | A compact on-chain commitment to every eligible wallet, its WP and the total WP.                                     |
| **Proof**            | Data allowing the contract to verify that a wallet and WP belong to the committed root.                              |
| **Commit**           | The moment the contract saves the pot, participant root and future reveal block.                                     |
| **Reveal block**     | A future Robinhood L2 block whose hash becomes the random seed.                                                      |
| **Blockhash**        | A cryptographic identifier of a mined block, used here as on-chain randomness.                                       |
| **Settlement**       | Verification of the three winners followed by payouts and buyback handling.                                          |
| **Keeper**           | An off-chain bot that watches contract state and pays gas to advance ready draw steps. It does not choose winners.   |
| **Claim**            | Fallback withdrawal used only when a wallet could not receive its automatic ETH prize.                               |
| **Buyback and burn** | Swapping 5% of a completed pot for `$MEGA` and sending the tokens to the permanent burn address.                     |
| **Burn address**     | An address with no usable private key; tokens sent there are treated as permanently removed from circulation.        |
| **Uniswap pair**     | The registered MEGA/WETH liquidity pool used for buys, sells, fee swaps and buybacks.                                |
| **BPS**              | Basis points. 100 BPS = 1%; 500 BPS = 5%.                                                                            |
| **MEV**              | Value that block builders or searchers may extract by changing transaction ordering, often affecting swap execution. |


---

# 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/help/glossary.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.