> For the complete documentation index, see [llms.txt](https://doc.metamarket.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.metamarket.tech/backing-pool.md).

# Backing pool

* 70% for base-level pricing - to place bids on the marketplace for Loyalty Badges 
* 20% for markup fund - to additionally appraise certain Loyalty Badges
* 5% for burning

Backing Pool are allocated into the following sub pools:

Additionally up to 20% of inApp monetization by selling game items are also used to be converted cash and subsequently provided into Backing Pool.

* advertising monetization - promoting external products and services 
* audience resale - services to get user base for game developers
* b2b integrations 

Backers  — the ecosystem partners who participate in the Loyalty protocol procedures by supplying their funds to the Backing Pool. Backers incentive is to get ecosystem benefits like up to 20% discounts (or depending on the financial structuring they can decide on their own which part of up to 20% of their payment is to be allocated into the pool) on the following services:

<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, and the optional `goal` query parameter:

```
GET https://doc.metamarket.tech/backing-pool.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.