> For the complete documentation index, see [llms.txt](https://docs.hop.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hop.exchange/governance/liquidity-mining.md).

# Liquidity mining

As one of its first actions, the Hop DAO enacted a liquidity mining campaing to attract liquidity in the bridge AMM's.\
\
Maintaining a high level of AMM liquidity is important for keeping bridging costs low and rates competitive. Higher AMM liquidity allows users to bridge large amounts with less slippage.

This is especially important for arbitrageurs. Bridge arbitrageurs make tight margins and need to offset their gas costs. Being able to transact in larger volumes with less slippage allows arbitrageurs to keep price differences across networks closer. Smaller price differences mean better rates for all users.

The campaign is issuing 2,200,000 HOP every month (around 2.6% annualized) split across the ETH, USDC, DAI, and USDT bridges.\
\
The split is based on the % of total volume a given bridge AMM receives and can be adjusted by the Hop governance.

<figure><img src="/files/mpqoFYiZw84Y4JOywsys" alt=""><figcaption></figcaption></figure>

<br>


---

# 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:

```
GET https://docs.hop.exchange/governance/liquidity-mining.md?ask=<question>
```

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.