> 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/announcement/mdex.com-heco-will-soon-start-joint-mining-activity-with-o3.md).

# MDEX.COM (HECO) will soon start joint mining activity with O3

MDEX.COM (HECO) will start joint mining activity with O3 at 12:00 PM (UTC) on June 29, 2021, and adjust the liquidity mining weight.

The details of the joint mining activity are as follows:

1. New list of liquidity mining:

   Stake O3/HUSD to mine MDX. The activity lasts for 30 days, and the mining reward is 150,000 USDT worth of MDX. 
2. Boardroom newly added list:

   Stake MDX to mine O3. The activity lasts for 30 days, and the mining reward is 150,000 USDT worth of O3.

At the same time, MDEX will adjust the liquidity mining weights. The specific number of outputs per block is subject to the official announcement on its website. If there is any change, MDEX will announce the news.

After the DAO Governance is implemented, the MDX token holders will take over the right to decide the weight.

MDEX Team

June 29 2021


---

# 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/announcement/mdex.com-heco-will-soon-start-joint-mining-activity-with-o3.md?ask=<question>&goal=<endgoal>
```

`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.