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

# 🧰 Technology Stack

**🛠️ Technology Stack**

**Pixel Toy** combines traditional game development tools with modern Web3 infrastructure to deliver a seamless retro-pixel MMORPG experience.

***

**🎮 Game Development**

**Engine** Developed on Unity with custom pixel-art rendering.

**Art and Design** Created in 8–16 bit retro style, optimized for performance on both PC and mobile.

**Cross-Platform Support** Available for Windows and macOS, with mobile versions (iOS and Android) in development.

***

**⛓️ Blockchain Integration**

**Network** Built on Monad, a high-performance Layer 1 blockchain with low fees, high throughput, and Ethereum compatibility.

**NFTs** Heroes, skins, and rare items can be minted as NFTs, providing true ownership and tradability.

**Smart Contracts** Written in Solidity, ensuring security and compatibility with the Ethereum ecosystem.

***

**🧠 Backend and Infrastructure**

**Servers** Scalable cloud-based architecture supporting large numbers of concurrent players.

**Databases** Hybrid approach:

* Off-chain storage for gameplay and progression
* On-chain storage for assets and transactions

**Security** Anti-cheat systems, encrypted connections, and audited smart contracts.

***

**⚙️ Development Tools**

**Version Control** Git-based repositories for collaborative development.

**Project Management** Agile workflows supported by tools like Jira and Notion.

**Design Tools** Figma for UI/UX design and Aseprite for pixel-art asset creation.

***

**🚀 Summary**

Pixel Toy is built using a combination of proven game development technologies and modern blockchain infrastructure, ensuring both stability and scalability for long-term growth.


---

# 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://pixeltoy.gitbook.io/pixeltoy-docs/technology-stack.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.