> For the complete documentation index, see [llms.txt](https://a51-finance.gitbook.io/a51-finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://a51-finance.gitbook.io/a51-finance/tokenomics/revenue-model-and-lps.md).

# Revenue Model & LPs

Liquidity Providers play a crucial role in sustaining the liquidity of the $A51 token ecosystem. In recognition of their contributions, they are compensated through a well-designed revenue distribution model.

## LP Revenue Distribution

A51 charges a fee to the LPs who use A51 to provide liquidity.

### **Protocol Revenue**

Half of the collected fees (50%) are used by the protocol to acquire wETH (Wrapped Ether). This wETH is subsequently distributed to those who have staked their A51 tokens, serving as a reward mechanism.

### **Protocol Net Revenue**

The remaining 50% of the fees make up the Protocol Net Revenue. This portion is used by the protocol to buy back A51 tokens from the open market. This action creates buying pressure and serves as a countermeasure against inflation.


---

# 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://a51-finance.gitbook.io/a51-finance/tokenomics/revenue-model-and-lps.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.