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

# Security

The token and NFT assets on Matr1x platform mainly rely on the public chain (Polygon/Ethereum) for asset confirmation. The asset wallets on the MATR1X platform are classified as hot wallets and cold wallets. The hot wallet provides online asset access services for platform users, and the cold wallet provides offline storage of certain assets. When the assets proportion of hot wallets reaches a threshold ratio, the excess part will be transferred into cold wallets automatically. At the same time, the security of the wallet is based on Gnosis multi-signature wallet. In the future, hardware encryption machines will also be considered to further improve the security of assets.

In addition to the smart contracts on the chain, the MATR1X blockchain platform is also a distributed service based on AWS, which mainly handles asset logic and other business logic on the platform. All API interaction interfaces/sensitive data are cryptographically signed and stored to ensure the information and data security of the platform.

At the same time, the common functions of assets in the game, such as upgrades, casting, drops, rewards, etc., are abstracted to shape independent asset risk control servers. In the future, we will also consider publishing this part of the common logic on the chain to increase transparency and be available for other games.


---

# 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://matr1x.gitbook.io/matr1x-whitepaper/5.-technology/security.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.
