> For the complete documentation index, see [llms.txt](https://docs.rsm.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rsm.network/introduction/design-principles.md). # Design Principles The RSM is designed based on three principles: security, extension, and consistency. The RSM Contracts must also conform to these three principles. ## 1. Security Security is the foundation of all RSM decentralized applications. RSM design needs to consider two aspects: user asset security and application security, including: * No custody of user assets * Trustless * Censorship-resistant * Permissionless * Token/Application's computing logic is open and transparent * Token/Application supports decentralized governance ## 2. Extension RSM should have great extension, and can support the logic of currently known decentralized applications and possible future innovations. RSM achieves extension and modularity through the support for token nesting. Applications deployed on RSM can create child applications to utilize the computing capabilities of the child applications, to implement the modularity of building application. ## 3. Consistency RSM must meet the consistency requirements, ensuring any indexer can compute a completely consistent state based on the on-chain data in OP\_RETURN and the computing logic of the Contract. The RSM Contract consists of two parts: state and state transition function. The state transition function must align with token UTXO operations, which are based on the UTXO model and cannot be extended, to ensure the compatibility and consistency of all Runes tokens. The state is expressed using the state machine model, that requires a rigorous and unambiguous description of the computing logic in the Contract to guarantee the consistency of all the indexers' computing. --- # 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.rsm.network/introduction/design-principles.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.