> For the complete documentation index, see [llms.txt](https://agp.aevo.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agp.aevo.xyz/approved-proposals/agp-3-aevonomics/proposal/new-reward-systems/staking-rewards/lottery-system.md).

# Lottery System

While exchange revenue sharing and LP fee distribution provide substantial long-term value, the lottery system creates ongoing daily engagement, keeping stakers active and connected to the protocol.

## Structure

* Lottery events run every 6 hours when both minimum thresholds are met:
  * 2 participants;
  * $50 pot;
* Every staker has access to the Lottery, all stakers participate equally;
* Tickets can be bought on Aevo, paid in USDC, 1 USDC = 1 ticket;
* Maximum 1,000 tickets per user per lottery event;
* One winner selected randomly per event.

## Prize Distribution

* 70% of ticket revenue (in USDC) goes to the winner;
* 20% of ticket revenue is distributed as staked $AEVO tokens to all participants, weighted by tickets purchased and added to their existing stake;
* 10% accrues to the DAO Treasury;

The staked $AEVO distributed to participants are staked with the same lock period as the main staking mechanism. All participants receive staked tokens proportional to their ticket purchases, ensuring everyone benefits while one lucky winner takes the main prize.

While the lottery may appear frivolous, it maintains daily user engagement, preventing stake-and-forget behavior while strengthening long-term alignment through the staked token distribution to all participants.


---

# 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://agp.aevo.xyz/approved-proposals/agp-3-aevonomics/proposal/new-reward-systems/staking-rewards/lottery-system.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.