> For the complete documentation index, see [llms.txt](https://mdexdoc.gitbook.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mdexdoc.gitbook.io/doc/activity/win-double-gifts-for-everyone-usd20-000-in-usdsheesha-as-rewards.md). # Win double gifts for everyone $20,000 in $SHEESHA as rewards ### The 1st Activity: Predict SHEESHA\[BEP20] price to win $500 per person **Activity duration:** 12:00 PM UTC, Dec. 28th, 2021 -- 12:00 PM UTC, Dec. 31th, 2021 Activity tasks: a.Follow [MDEX Twitter](https://twitter.com/Mdexswap) and join the[ MDEX Telegram group.](https://t.me/MdexEN) b.Follow [SHEESHA Twitter](https://twitter.com/SheeshaFinance_) and join the [SHEESHA Telegram group](https://t.me/Sheesha_Finance). c.Quote this twitter and predict: the SHEESHA\[BEP20] at 12:00 PM UTC, Dec. 31th. d.[Fill out the form](https://forms.gle/tUEeyoCmiPFgyx9v8) to participate (the form is accessible within 48 hours after the event starts). **Rewards:** 8 users with the closest prediction will each receive $500 in $SHEESHA. **Notification:** 1.The actual price of SHEESHA\[BEP20] at 12:00 PM UTC, Dec. 31th will be taken from the price displayed on coinmarketcap.com. 2.The activity lasts for 72 hours. Users can fill out the form to predict the price within the first 48 hours. 3.The final actual token price will subtract the prediction result submitted by users in the[ form,](#the-1st-activity-predict-sheesha-bep20-price-to-win-usd500-per-person) and the 8 users with the smallest absolute value will become the final winners. 4.The rewards will be distributed in 7 days after the event ends. ### The 2nd Activity: Trade SHEESHA to win $16,000 rewards pool **Activity duration:** 12:00 PM UTC, Dec. 28th, 2021 -- 12:00 PM UTC, Jan. 4th, 2022 **Activity tasks and rewards:** a. During the event, users who haven't traded SHEESHA on MDEX yet can get an equal share of the $6,000 SHEESHA token prize pool by reaching minimum trading volumes of $100 SHEESHA. b.During the event, users with the cumulative trading volume of SHEESHA over $500, can evenly share the $6,000 SHEESHA token prize pool. c.The TOP 10 users whose cumulative trading volume of SHEESHA over $10,000 during the activity will receive the following rewards: | Rank | Rewards | | :--: | :--------------------------------------------------------------------------------: | | 1 | $1000 in $SHEESHA | | 2-3 | Divide the $1000 in $SHEESHA based on the proportion of each user's trading volume | | 4-6 | Divide the $1000 in $SHEESHA based on the proportion of each user's trading volume | | 7-10 | Divide the $1000 in $SHEESHA based on the proportion of each user's trading volume | d.[Fill out the form](https://forms.gle/tUEeyoCmiPFgyx9v8). **Notification:** 1.The same user will have the opportunity to get all rewards. 2.The rewards will be distributed in 14 days after the event ends. 3.To obtain the reward, you need to [fill in the form ](https://forms.gle/tUEeyoCmiPFgyx9v8)(not filling in is regarded as automatic abandonment). 4.The final interpretation right of this event belongs to MDEX. --- # 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://mdexdoc.gitbook.io/doc/activity/win-double-gifts-for-everyone-usd20-000-in-usdsheesha-as-rewards.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.