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

# Markup protocol

The markup protocol procedure is aimed at defining the rarity of the Loyalty Badges by their additional appraisal by the community. The procedure takes place on Epoch basis. The whole markup fund (20% of Backing pool inflows) is to be distributed each Epoch.

Markup pricing procedure takes place in the following phases:

* Epoch N-1: Collecting submissions by the Loyalty Badges owners to apply the particular Loyalty Badges for the procedure. There is an additional requirement (which will be defined by the community closer to the procedure launch) to get access for the submission
* Epoch N: voting by community to allocate funds of the markup fund (as of the end of Epoch N-1 state) between the submitted Loyalty Badges. Each community member has the equivalent number of votes to his Loyalty points which can be allocated to several NFTs
* Epoch N+1: the protocol makes the bid offers on the internal marketplace which consolidate the base level pricing and the markup one. The markup value is calculated as a relative number of votings numbered the markup fund (as of the end of Epoch N-1 state). The bids are valid only for one Epoch and to be canceled the next one if not accepted
* Epoch N+2: not accepted bids are canceled, the allocated markup funds are returned back to the markup fund and the next Epoch bids are calculated and placed

Community memeber incentive to participate in the procedure is to get voting rewards from the dedicated fund.

Markup pricing procedure is applicable to all Loyalty Badges which have not been in the Repository after accepting the protocol bids.


---

# 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://sdk.metamarket.tech/markup-protocol.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.