diff --git a/docs/zkapps/o1js/index.mdx b/docs/zkapps/o1js/index.mdx index 573a20a25..1b712b8ed 100644 --- a/docs/zkapps/o1js/index.mdx +++ b/docs/zkapps/o1js/index.mdx @@ -60,7 +60,7 @@ Start your o1js journey by learning about [basic zk programming concepts](/zkapp ## Audits of o1js -* **Third-party audit (Q1/Q2 2024)**. An audit by an external security firm is ongoing and on track to complete in Q2 2024. Results will be shared when available. +* **Third-party audit (Q1/Q2 2024)**. An audit by an external security firm is ongoing and on track to complete in Q2 2024. Results will be shared when available. x * [**Internal audit (Q1 2024)**](https://github.com/o1-labs/o1js/files/15192821/Internal.o1js.audit.Q1.2024.pdf). In March 2024, the o1js team spent roughly two person-weeks to conduct an internal audit of parts of the o1js code base. The audit focused on reviewing core provable code. A number of issues were found and fixed. diff --git a/docs/zkapps/writing-a-zkapp/introduction-to-zkapps/secure-zkapps.mdx b/docs/zkapps/writing-a-zkapp/introduction-to-zkapps/secure-zkapps.mdx index 8619d915e..7170386e0 100644 --- a/docs/zkapps/writing-a-zkapp/introduction-to-zkapps/secure-zkapps.mdx +++ b/docs/zkapps/writing-a-zkapp/introduction-to-zkapps/secure-zkapps.mdx @@ -19,13 +19,7 @@ On this page, you will find guidance for how to think about security when buildi Apart from acquiring a solid understanding of security aspects of zkApps, we recommend that critical applications also get audited by independent security experts. -There has been an internal audit of the o1js code base already, [the results of which you can find here](/zkapps/o1js#audits-of-o1js). An audit by a third-party security firm is ongoing. - -:::caution - -Until the third-party audit of o1js is completed, audits of zkApps should also include the relevant parts of o1js in their scope. - -::: +There has been an internal audit of the o1js code base already, [the results of which you can find here](/zkapps/o1js#audits-of-o1js). ## Attack model