> For the complete documentation index, see [llms.txt](https://docs.ouroboros.foundation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ouroboros.foundation/ouroboros-products/universal-staking-module/audit-contracts.md). # Audit/Contracts ### Audits Two separate audit rounds were conducted, by a total of 4 senior smart contract auditors. In round 1, a single auditor combed the entirety of the staking module codebase over a two week period, while in the second round, 3 senior auditors performed an in-depth review of the same, ultimately culminating in a report. Across both audits, no high or critical severity findings were observed from a security point of view, but the Ouroboros team opted to elevate one informational finding to H, in order to give the auditor who discovered the issue the deserved credit. This informational finding, resulted in the creation of the Share Weighted LP rewards distribution mechanism. {% file src="/files/vh52vdfeHcSk7OpHW5aq" %} --- # 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.ouroboros.foundation/ouroboros-products/universal-staking-module/audit-contracts.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.