> For the complete documentation index, see [llms.txt](https://wp.anomus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp.anomus.io/no-rug-pulls-anomus-security-audit.md). # No rug pulls: ANOMUS Security Audit Security has always been an integral part of blockchain technology. When done correctly, the advantage of a secure protocol significantly outperforms centralised custodial services whether financial custody or custody of ownership rights, given that the user properly stores and manages private keys. Smart contracts, on the other hand, are yet to become a universally perfected technology. Errors or bugs found in the code of smart contracts have proven disastrous over the years, resulting in millions in stolen funds and poses a significant threat for the well-being and long-term adoption of any protocol. Now, security is more important than ever before as the 2020-2021 period has seen its fair share of high profile smart contract and protocol exploits. Unfortunately, many decentralized and layer-two projects skip the smart contract and protocol auditing process entirely. ANOMUS however, makes it a top priority to perform rigorous audits of the ANOMUS token smart contract, and the content platform before deployment as well as any new feature or functionality implementation. ANOMUS dev team strongly believes that in order to pave a prosperous future, security must be a top priority. That is why ANOMUS is taking a robust stance in verifying its smart contracts and protocol’s safety. --- # 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://wp.anomus.io/no-rug-pulls-anomus-security-audit.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.