> For the complete documentation index, see [llms.txt](https://whitepaper.multi-fights.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.multi-fights.com/staking/systems.md).

# Systems

### Smart staking contracts are classified into the following categories:

**Smart contract for players:** This smart contract will play a key role in rewarding players by providing them with a significant APR in addition to regular in-game rewards. This additional reward mechanism is intended to stimulate the active participation of players and to reward them for their continued contribution to the success of the project.

**Classic Smart contract:** This smart contract is to allow any user to experience our game without having to buy an NFT. Instead, this system will temporarily provide them with an NFT. To provide an additional incentive to investors, the APR associated with this smart contract will be significantly higher than that offered under the player smart contract. The period for unbond the NFTs is 3 days!


---

# 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://whitepaper.multi-fights.com/staking/systems.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.