> For the complete documentation index, see [llms.txt](https://shiro.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shiro.gitbook.io/docs/smart-contracts-and-interactions/the-token-contract.md).

# The Token Contract

### Functionality

The Token Contract is the backbone of the economic interactions within Shiro. It is responsible for:

* **Minting and Burning:** Creating new $SHIRO tokens as rewards and removing tokens from circulation if necessary to control supply.
* **Transfers:** Enabling players to send and receive $SHIRO tokens within the game and on external exchanges.
* **Staking:** Allowing players to stake their tokens to earn rewards, contributing to the security and robustness of the platform.

### Technologies Used

This contract is written in Rust due to its performance and safety features, which are critical for maintaining the integrity and security of blockchain operations on Solana.


---

# 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://shiro.gitbook.io/docs/smart-contracts-and-interactions/the-token-contract.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.
