> For the complete documentation index, see [llms.txt](https://mystic-reign.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mystic-reign.gitbook.io/whitepaper/token-information/token-features.md).

# Token Features

**Stable Coin Pairing with USDT :** Our decision to pair the ISV token with USDT , rather than the traditional native token (ETH), establishes a stable coin pairing immune to the volatility of market fluctuations. This ensures that the growth of the native token is contingent upon the success and utility of the project within the Isekaiverse ecosystem.

**True Burns:** Token burns are strategically managed by the team to reduce the total supply and contribute to raising the token price. These burns are triggered upon achieving specific milestones and are integrated into the rewards program, ensuring alignment with project objectives.

**Blacklist Functionality:** The contract empowers the owner to blacklist a wallet, preventing it from executing any transactions involving ISV tokens, including transfers, purchases, and sales. This capability serves to deter hackers and scammers, safeguarding the integrity of the ecosystem and ensuring the protection of investor funds.


---

# 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://mystic-reign.gitbook.io/whitepaper/token-information/token-features.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.