> For the complete documentation index, see [llms.txt](https://docs.unitas.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unitas.so/resources/audits.md). # Audits ### Overview Security and transparency are core priorities for Unitas. The protocol undergoes independent security reviews to assess contract correctness, risk exposure, and adherence to best practices across supported execution environments. Unitas does not treat audits as a one-time requirement. Reviews are part of an ongoing process to validate critical logic, minimize attack surfaces, and ensure that contract behavior aligns with documented design assumptions. ### Completed Audits Unitas contracts have undergone independent audits across both SVM and EVM environments. #### **SVM Contracts** 1. **Scalebit:** {% file src="/files/waAyqqWUfWf1ZUf2CmrK" %} 2. **Oaksecurity:** {% file src="/files/kXTnpPI9f3bUrsS0b1z6" %} #### **EVM Contracts** 1. **Scalebit:** {% file src="/files/ebfYZLySPjk6B4zwiiBC" %} 2. **Slowmist:** {% file src="/files/4rhAxNz9krFa7CR273xv" %} Each audit evaluated the relevant contract set deployed on its respective execution environment. ### Transparency and Review Process Audit reports are published to provide visibility into the review process and identified findings. Where applicable, remediation steps and design adjustments were implemented before mainnet deployment. Audits complement Unitas’ broader transparency framework, which includes real-time solvency verification, visible collateral flows, and third-party reserve attestations. Together, these measures support a protocol design that prioritizes verifiability, accountability, and operational security. --- # 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.unitas.so/resources/audits.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.