> 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/economic-blueprint/absolute-asset-sovereignty.md). # Absolute Asset Sovereignty True ownership is the non-negotiable foundation of our architecture. Every Genesis Agent, tactical item, and agent token represents on-chain private property secured on the Base Network. * **Self-Custody:** Control is governed entirely by the cryptographic keys in your own wallet. * **No Central Authority:** The developers do not possess the power to pause, seize, or dilute player assets. * **Autonomous Execution:** Smart contracts ensure that the rules of the arena, such as the drain and matchmaking logic, execute without human intervention. * **Asset Permanence:** Players can deploy, trade, or defend their assets with total confidence in the permanence of their digital holdings. --- # 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/economic-blueprint/absolute-asset-sovereignty.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.