# Mechanics ## Bootstrap Phase A `24` hour period at the beginning of the game in which the minimum yeet size does not increase, and is fixed at `0.1` `$BERA`. This is for players to participate and purchase lottery tickets without the risk of being frontrun, and give fair entry to all. * Each lottery ticket costs `0.1` `$BERA` * Max amount of tickets that can be purchased in one transaction is `300` tickets (Only enforced via UI to prevent out of gas errors) * Players that participate in the bootstrap phase still earn $YEET participation rewards * This negates the advantage that bots have with sniping lottery tickets as soon as a new round begins When the Bootstrap Phase is concluded, the Game Phase begins. ## Game Phase **Timing** * With every new deposit, the timer is reset and extends the time remaining in the game * The amount of time the timer is reset by is `1 hour` * If `1 hour` passes since the last yeet with no new yeets, then the current game ends * Once a game concludes, anyone can permissionlessly call the appropriate function to start a new game * The amount of time that the timer is reset by is configurable, and can be changed by the admin multisig * This is to run shorter, faster games at times * Control over this variable will eventually be transferred to the community, or ossified at a specific value **Revenue** * `15`% of every yeet is taxed * `9`% of this is distributed to $YEET stakers via the Liquidity Trifecta Vault * `1`% is contributed to public goods funding on Berachain * `5`% is retained as protocol revenue **Lottery** * After a game concludes, `80`% of the prize pool is awarded to the last Yeeter, which they can claim at any time * `20`% of the prize pool is distributed via verifiably random lottery to `10` participating addresses * Pyth VRF will be the source of randomness (will document this more clearly once docs are done) * Each winning address will receive an equivalent amount * An address can win multiple times {% hint style="info" %} The % tax incurred on yeeting is subtracted before it goes to the prize pool. {% endhint %} --- # Agent Instructions: 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: ``` GET https://docs.yeetit.xyz/yeet/yeetarded-products/yeet-bonzi/mechanics.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.