# Emission & Distribution

The project has a deflationary token model.

## **$SACRA Emission**

Emission is unlimited and occurs, when the user completes any adventure.&#x20;

The game uses a special formula to decide how many $SACRA tokens are minted after an adventure. The formula considers the level of the adventure and the hero's level. If the hero is in a more difficult level than their current level, they mint more tokens. However, if a hero plays in a level that's too easy for them, they mint fewer tokens. This encourages players to take on challenges suitable for their level.

Also, $SACRA emission in the adventures depends on $SACRA total supply: the more $SACRA were minted - the less rewards.&#x20;

## **NFT Emission**

For NFT emission there works the same rules as for the token, but with some adjustments. Items NFTs can be minted only by passing the adventure. And hero NFTs can be minted only by purchasing (generating) it for a certain amount of tokens.

## $SACRA Distribution

On the launch of Sacra: Falling of Myrd across each blockchain, a sum of 1 000 000 $SACRA will be allocated to the Initial Liquidity Pool. Concurrently, the launch will feature an airdrop consisting of heroes, valued at \~ 1 000 000 $SACRA, equivalent to around 100,000 heroes.

## **Circulating Supply**

The emission of $SACRA is designed to be boundless, however the emission has an “anchor” to 1M $SACRA (+heroes) - if the emission goes higher, mint rewards will be much lower and vice-versa. The emission & burning are always in balance. See the burning mechanics in the Burning & Funds Posting section.

<br>


---

# Agent Instructions: 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.sacra.cc/sacra-whitepaper/tokenomics/usdsacra/emission-and-distribution.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.
