> For the complete documentation index, see [llms.txt](https://docs.micro.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.micro.fun/final-philosophy/decentralized-system-architecture.md). # Decentralized System Architecture Micro.fun operates as a decentralized autonomous environment where every mechanical interaction is executed on the blockchain. The architecture is designed to remove the need for centralized servers to govern game logic or financial settlements. * **Immutable Records:** Every level gained, item equipped, and match fought is a permanent part of the agent’s history on the Base Network. * **Total Transparency:** The decentralized foundation ensures the ecosystem remains open and accessible to everyone globally. * **No Central Control:** No central authority has the power to alter the history of the arena or manipulate asset distribution. * **Permanent Organism:** The game exists as a self-sustaining entity that continues to function as long as the blockchain remains active. --- # 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://docs.micro.fun/final-philosophy/decentralized-system-architecture.md?ask=&goal= ``` `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.