> For the complete documentation index, see [llms.txt](https://docs.zircuit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zircuit.com/info/security/audit-reports.md). # Audit Reports **Security is the foundation of Zircuit's innovation.** We prioritize safeguarding our users and the integrity of our platform. In addition to conducting **rigorous internal audits** by our experts, we collaborate with **trusted, industry-leading external partners** to ensure our systems are secure against vulnerabilities. These external audits provide an additional layer of assurance, ensuring that Zircuit meets the highest standards of security and reliability in the Web3 ecosystem. Here is the link to our audits:
AuditorDescriptionAudit DateReport
QuantstampL2 Upgradeable Contract28 September 2024Link
QuantstampLido's wstETH23 September 2024Link
Secure3USDCAdapter19 September 2024Link
Secure3Token and Migration18 September 2024Link
Salus SecurityLiquidity Hub14 September 2024Link
HalbornToken and Migration2 August 2024Link
DecurityToken and Migration31 July 2024Link
DedaubBridge24 July 2024Link
DedaubStaking Pool11 March 2024Link
OtterSecStaking Pool15 February 2024Link
### Acknowledged Issues * `eth_call` , `eth_estimateGas` and similar rpc calls do not include the L1 fee in their estimation. This can lead to transactions succeeding on the rpc call that later fail due to insufficient funds. We recommend [manually computing the l1 fee](/info/architecture/gas-pricing-and-transaction-fees/l1-data-fee-calculation.md) when operating with low-balance accounts. Last updated on 14 August, 2025 --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.zircuit.com/info/security/audit-reports.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 `build a script that syncs our docs to a CMS` 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.