> 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/nfts/about.md).

# About

The collection of NFTs consists of a fixed number of **3.500 characters**, each character containing the following statistics: level, attack power (damage), and health points (HP).

### Traits:

**Level**

This trait represents the experience level of each NFT and can be increased by gaining experience.

**Attack power & health points:**

Attack Power and Health Points are two essential features in the battles of the game. They give players the opportunity to develop complex tactical strategies, helping them achieve victory in numerous encounters in the game. These traits can be upgraded with each level up in the game, thus giving players the opportunity to optimize their characters as they progress.

*These traits will be stored on the blockchain, ensuring transparency and visibility for all holders. This will give them the opportunity to sell or buy them on the secondary market.*

**Holders of NFTs will receive monthly 15% of the revenue from royalties.**


---

# 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/nfts/about.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.