> For the complete documentation index, see [llms.txt](https://plan-a-labs.gitbook.io/metawara/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://plan-a-labs.gitbook.io/metawara/tokenomics/staking-reward-structure.md).

# Staking Reward Structure

Staking rewards serve as a major incentive for player participation. Rather than passive yield, the system integrates with Political War, long-term loyalty, and faction-based governance.

The total staking reward pool is 150,000,000 MWAR, distributed over time based on gameplay dynamics.

| Period              | Block Reward | Features                                           |
| ------------------- | ------------ | -------------------------------------------------- |
| Presale \~ 6 months | 42.81        | High early rewards / No lock-up / Liquid support   |
| 7–10 months         | 29.97        | Gradual reduction / Encourages political voting    |
| 11–22 months        | 19.98        | Long-term loyalty focus / Linked to royalty system |
| After 22 months     | -            | Adaptive allocation based on ecosystem performance |

**Linked Reward Systems**

* Voting in Political War → Earn governance rewards
* Loyalty system boosts yield over time
* Staking status impacts eligibility in core game content like GATE transfers

***


---

# 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://plan-a-labs.gitbook.io/metawara/tokenomics/staking-reward-structure.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.