> For the complete documentation index, see [llms.txt](https://docs.suno.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.suno.finance/resources/security-audit.md). # Security audit Nethermind's independent review of Suno's smart contracts, its findings, and the final report. Nethermind Security completed an independent review of Suno's smart contracts on September 14, 2026. The final report, NM-1010, covers [protocol code at commit e1555fb](https://gitlab.com/suno-finance/suno-protocol/-/tree/e1555fb6f571b53030a251232975a168a8f8c331). {% file src="/files/LRLM1hF9RQYrPk6embFD" %} Nethermind Security — final audit report, September 14, 2026 {% endfile %} ## Scope The review covered 28 Solidity files, including the desk, uWatt, the Reserve, project contracts, staking, yield distribution, price oracles, the sUSDS adapter, and LayerZero cross-chain contracts. The admission registry, disabled Axelar adapter, valuation engine, off-chain monitoring, custody practices, and legal agreements were outside its scope. The [contract directory](/resources/documents-and-contracts.md) includes both audited and out-of-scope components. ## Findings and follow-up The review identified 12 findings: 1 High, 3 Medium, 5 Low, and 3 Informational. Eleven were fixed and one was mitigated. The mitigated finding concerns the daily redemption limit. The fix prevents desk redemptions from reducing their own daily allowance, but privileged burns outside the desk still require operational coordination. The audit assesses the specified code; it does not verify the underlying assets or guarantee against losses. Ongoing security also depends on accurate reporting, authorized operators, and external protocols. See [Risks and protections](/overview/risk-management.md). --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.suno.finance/resources/security-audit.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.