> For the complete documentation index, see [llms.txt](https://neiroinu.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://neiroinu.gitbook.io/whitepaper/audited-by-blocksafu.md). # Audited By BlockSafu At Neiro Inu, transparency and security are paramount. To ensure the integrity of our project, we have successfully completed a comprehensive smart contract audit conducted by BlockSafu, a leading blockchain security auditor. This pre-launch audit rigorously examined our codebase, identifying and mitigating potential vulnerabilities to provide our community with a secure and trustworthy project. We are proud to have achieved a perfect score of 100 Trust Cores from BlockSafu, demonstrating our commitment to the highest standards of security. You can view the full audit report here:
Looking ahead, we plan to further strengthen community trust by undergoing additional audits with other reputable blockchain security firms. This commitment to ongoing security assessments will provide our investors with peace of mind and reinforce our dedication to building a sustainable and transparent project. --- # 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://neiroinu.gitbook.io/whitepaper/audited-by-blocksafu.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.