# Lucky Greenbies Lucky Greenbies is an in-game feature that sells numbered tickets based on Green Hero's ID number and gives prizes to the Green Hero's holders of numbers drawn at random. ## How does it work? Ticket sales opening time: From 0:00 to 23:00 (UTC) everyday The ticket code is the Green Hero's ID number. Price: XXXX/ticket. Players now can purchase a number of tickets that is less or equal to the amount of Green Heroes that you own. $GFRUIT collected from ticket-selling is divided as follows: * Daily prizes: 50% * Jackpot prize: 20% * For ‘’Burned’’ and ‘’Starting Jackpot’’ purpose: 30% ## Rewards: ### **Daily prizes** * 50 random ticket codes (Green Heroes’ ID number) will be drawn at random by the system through and announced at midnight (UTC) * Total prizes: 50 lucky Greenbies * Reward: $GFRUIT 🍀 Reward distribution: * 1st prize: 25% * 2nd prize: 13% * 3rd prize: 8% * 4th - 10th: 2% * 11th - 50th: 1% ### Jackpot prize: * 01 ticket codes (Green Heroes’ ID number) will be drawn at random by the system through and announced at midnight (UTC) * The winning rate of the Jackpot is 3% but no daily winner is guaranteed * Starting Jackpot (15,000,000 $GFRUIT) is an amount to which a Jackpot prize is reset after it’s been won. * A Jackpot price has a starting jackpot that can keep growing with each rollover until it’s won. Particularly, total Jackpot prize = 15,000,000 $GFRUIT + $GFRUIT from daily accumulation. 🍀 Reward will be distributed to Locked Rewards --- # 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://greenbeli.gitbook.io/green-beli/gameplay/lucky-greenbies.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.