> For the complete documentation index, see [llms.txt](https://docs.yo.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yo.xyz/protocol/security-audits.md). # Security Audits The YO protocol prioritizes user security through robust and comprehensive practices. Developed following the ERC4626 standard, yoVault incorporates rigorous access control via an authorization mechanism, restricting sensitive operations exclusively to trusted operators. This ensures meticulous management of user funds, significantly reducing potential risks. Security audits from reputable firms, including Hunter Security and Offbeat Security, confirm the solidity of yoVault’s smart contract code. No critical or high-severity vulnerabilities were identified, demonstrating the protocol’s reliability and showing the team's proactive security approach. YO integrates mechanisms such as asynchronous redemption requests, clear fee structures, and strict controls over asset balance updates. Additionally, the protocol automatically pauses operations if asset valuations deviate significantly, providing an extra protective layer against market volatility or unexpected events. These carefully designed features collectively uphold the highest standards of user fund security. ### Existing audits **Core Protocol**
AuditorDateScopeReport
Offbeat Security15 January 2025yoVaultYo-Protocol-Offbeat-Security-Review.pdf
Hunter Security21 January 2025yoVaultYo-Protocol-Hunter-Security-Audit-Report.pdf
Spearbit29 May 2025yoVaultYO-Protocol-Spearbit.pdf
Aether Labs23 October 2025yoVaultSecondaryYo-Protocol-Aether-Security-Audit-2.pdf
Paladin21 November 2025yoVaultSecondary20251121_Paladin_YoProtocol_Final_Report.pdf
Aetheryc1 December 2025yoVaultV2Yo-Protocol-Aetheryc-Security-Review_V2.pdf
Zellic24 February 2026yoVault SolanayoSOL-Zellic Audit Report.pdf
Accretion13 April 2026yoVault Solana2026-accretion-yo-labs-yo-protocol-solana-audit-A26YOL1 (1).pdf
**YoGateway**
AuditorDateReport
Aether Labs20 August 2025Yo-Protocol-Aether-Security-Audit.pdf
Paladin21 November 202520251121_Paladin_YoProtocol_Final_Report.pdf
#### Onchain Adapters
AuditorDateReport
Cantina05 June 2026yo_contracts_v2_cantina.pdf
Cantina23 June 2026yo_contracts_v2_rereview_cantina.pdf
--- # 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.yo.xyz/protocol/security-audits.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.