> For the complete documentation index, see [llms.txt](https://whitepaper.pethereum.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.pethereum.io/pethereum-ticket-generator/dao-ticket-benefits.md).

# DAO Ticket Benefits

### VIP Status&#x20;

The first benefit is VIP status, users will be able to buy VIP status in exchange for their tickets. This VIP status is integrated into Ticket Generator and affects in-game features like special discounts, better rarity levels for hatched eggs, and some other advantages.

### $PETH Rewards&#x20;

The second benefit is $PETH rewards. Users will be able to join staking pool rewards and earn $PETH with the tickets they have.

If a user has 100 tickets and the total ticket number in the staking pool is 10.000, he/she will receive 1% of the $PETH in the staking rewards pool created by Pethereum’s profit.

### DAO&#x20;

Users can join DAO and the tickets will represent the voting power of a user when the DAO is formed.


---

# 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://whitepaper.pethereum.io/pethereum-ticket-generator/dao-ticket-benefits.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.
