# Announcement on destruction of MDEX team lock-up rewards and the schedule of DAO launching The boardroom lock-up function has been recognized and supported by communities since the first date it launched. Thank you so much for your trust and company! In order to reduce the circulation of MDX in market, the MDEX teams decided to destroy all the rewards locked in the boardroom with an interval of 365 days on a regular basis for MDEX teams themselves. In the future, new products will focus on creating added value and reduction the circulation of MDX. The first destruction time is scheduled on 4th Aug 2021 and 2363991 MDX will be destroyed with a value of about 2.75 million USDT. The destruction hash address is as follows: The subsequence destructions of rewards for the previous month are scheduled on the first day of coming month. HECO: 0xF9852C6588b70ad3c26daE47120f174527e03a25. BSC: 0x000000000000000000000000000000000000dEaD. In order to more effectively implement the plans on the Q3 roadmap, MDEX team intends to implement the DAO governance within 3 months to give MDX holders the governance authority of the platform. By then, issues such as the destruction of team rewards after unlocking, the proportion and usage of income distribution, the form of buyback & destruction and the adjustment of tokenomics will be decided by DAO. MDEX Team August 4, 2021 --- # 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://mdexdoc.gitbook.io/doc/announcement/announcement-on-destruction-of-mdex-team-lock-up-rewards-and-the-schedule-of-dao-launching.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.