> For the complete documentation index, see [llms.txt](https://mole.gitbook.io/activation-lottery/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mole.gitbook.io/activation-lottery/activation-lottery.md). # Activation Lottery ## Summary **Win 50 usd in IOTX multiple times!** Activate Daibotuten or Benzaiboten or both using the IOTeX Network sending the equivalent of 15 usd (or more) in IOTX to `io148yvz30p2k3jr9shupm8tvp475fyc7936qpafy` to become eligible to win in the lottery. #### Example If the price of IOTX is 0.3 usdt, then send at least 50 IOTX, if the price of IOTX drops to 0.2 usdt, then send at least 75 IOTX, if the price of IOTX rises to 5 usdt, then send at least 30 IOTX and so on... ## How to activate? Follow the steps described in the github of Daibotuten (or Benzaiboten): The bot can be activated with multiple different cryptocurrencies, as shown in here: However, only the activations done in the IOTeX Network will be eligible for the lottery. ## When? Only from Nov-30-2021 08:00:00 AM UTC to Dec-10-2021 10:00:00 PM UTC Activations done outside from this interval won't be eligible. Also transactions that doesn't activate the bot won't be eligible. ## How the lottery works? Every 50 new users, one of the users that activated the bot using the address `io148yvz30p2k3jr9shupm8tvp475fyc7936qpafy` during the period of the lottery will receive 50 usd in IOTX. The rewards will be distributed once a day when 50 new users are reached and each user can win multiple times. ## Who will win? It will be used the **transaction hash** of the transaction of the activation of the bot to decide who is the winner. The transaction hash is an unpredictable number linked to the blockchain technology, so it's pretty fair to be used for this purpose. The following steps are used **every time 50 new users** activate the bot to elect the winner: 1. Get the transaction hash from the transaction of the last user 2. Calculate the reminder of the number formed by the last three cyphers of the transaction hash divided by the total number of new users (you can calculate it by yourself for example from ) 3. Starting from the last new user, go backward in the list of the valid transactions done to `io148yvz30p2k3jr9shupm8tvp475fyc7936qpafy` as the result calculated in step 2. The user that have done that transaction is the winner #### Example: Let's say that the transaction from the last user is this one: The last three cyphers are 083, so the number they compose is 83. Let's say that that user was the 100th of the list (without considering the ones in the list NOT eligible). So the reminder of 83/100 is 83. Then, starting from the last transaction done to activate the bot reported in the winner will be (if in total there was 100 users) the number 100-83=17 ## Early bird catches the worm Let's say that you are the 50th user to activate the bot. Then you are eligible to win in the lottery where the last transaction is yours, but if other 50 users arrives, you are eligible to win again one more time, even if you didn't win before and also if you did win before and so on... So... **More users will come during the lottery and more times you can win!!!** Spread the word and call all your friends to increase the chances of victory! --- # 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://mole.gitbook.io/activation-lottery/activation-lottery.md?ask=&goal= ``` `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.