> For the complete documentation index, see [llms.txt](https://moonmakerprotocol.gitbook.io/moon-maker-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://moonmakerprotocol.gitbook.io/moon-maker-protocol/transaction-fees.md).

# Transaction Fees

**A transaction fee of 10% applies to every transaction on MMP. This fee helps to solidify the ecosystem and is broken down thus:**

**▶ 5%** - goes towards MMP-BNB liquidity pools via PancakeSwap

**▶ 3%** - is granted to the holders under the “Automatic divided distribution system”

**▶ 2%** - is collected for platform development and goes towards creating awareness and expanding the community

     ➡ 1% to goes towards marketing and management plans. This is further broken down  \
                into\
     ➡ 0.7%  towards operation expenses and marketing campaigns\
     ➡ 0.3%  towards strengthening the MMP blockchain infrastructure.


---

# 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://moonmakerprotocol.gitbook.io/moon-maker-protocol/transaction-fees.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.