Treasury Proposal: ink! v6 and cargo-contracts Security Audit by Oak Security

Hey community!

This is Stefan from Oak Security. Oak Security has performed over 600 audits since 2017. Over the last year, we have performed numerous security audits of various projects in the Polkadot ecosystem, for teams such as Hydration, KILT, Zeitgeist, Mythical Games, Bifrost, Snowbridge, and of several ink! smart contracts. We also have deep experience auditing various virtual machines and low-level technologies, e.g., Filecoin’s EVM, CosmWasm, the Gno language and virtual machine, and Stellar’s Soroban language and virtual machine.

We are now proposing an 8-week security audit of ink! v6 for a total fee of 244,800 USD.

We truly value the thoughts and perspectives of the community, as they help guide the direction of the entire ecosystem. Before moving this proposal forward to the referendum stage, we wanted to share it openly here. Your feedback and insights are essential in ensuring we align with the broader needs of the ecosystem!

As we finalize our treasury proposal for the ink! v6 security audit, we wanted to share more about the direction this initiative is taking. ink! v6 will introduce a shift to RISC‑V execution, migration from pallet‑contracts to pallet‑revive, and integration of PolkaVM compatibility and Solidity ABI support. These changes expand the attack surface and could introduce vulnerabilities not seen in earlier releases, so an independent security review is critical.

Over the past 6 months, we’ve had several iterations with members of the ink! Alliance and R0GUE teams - including Michi Müller and David Semakula. What we present here reflects the outcome of these discussions and the alignment between our teams.

We believe a focused 8-week audit, executed by two teams in parallel, is the best way to ensure depth and coverage. The audit will be executed by two teams of three senior security researchers each, using Oak Security’s signature blinded review process.

Here is how the audit is structured:

  • 4 two‑week sprints, executed by two teams in parallel.

  • Each sprint is staffed with 3 senior security researchers.

  • Sprint planning to prioritize items from a backlog provided by the ink! Alliance.

  • Blinded code review: auditors independently review the codebase, ensuring each line is covered by multiple researchers.

  • Interim report at the end of each sprint detailing findings and recommendations.

  • Remediation review: Auditors are available for five weeks to discuss and verify fixes.

  • Final report published under a Creative Commons licence in Oak Security’s public audit repository, with findings presented to the community.

We believe this audit will strengthen trust in ink! v6, mitigate ecosystem‑wide risks and provide actionable security improvements for developers. Please read our full proposal for details on budget and scope, and share your feedback and questions so we can prioritize the areas that matter most to you.

Many thanks!

Stefan

5 Likes

As a long-time contributor to the ink! ecosystem, I thoroughly support this treasury proposal. Having facilitated the ink!ubator for the past 2.5 years and been involved with ink! since the early days of OpenBrush, I have witnessed its evolution and growth firsthand.

The upcoming ink! v6 is a significant milestone, introducing powerful features like the shift to RISC-V, PolkaVM compatibility, and Solidity ABI support. These advancements will undoubtedly attract more developers and projects to the Polkadot ecosystem.

However, with great power comes great responsibility. The expanded capabilities of ink! v6 also introduce a larger attack surface, making a comprehensive security audit not just a “nice-to-have,” but an absolute necessity.
Oak Security’s recommended 8-week, two-team audit is a considered and sound approach to affirming the security and stability of this critical infrastructure Investing in ink!'s security is investing in the future of the Polkadot ecosystem in general. With a secure and reliable ink!, we will win developer confidence, attract high-value projects, and ultimately bring about adoption of Polkadot as a premier platform for smart contracts

Thank you for posting here, Stefan!

As one of the core developers of ink! I want to emphasize that we had a number of meetings with Oak Security about how to best approach this audit. Oak brought a number of options to the table and after discussing them, we believe the approach from the proposal is best suited for this audit and the changes entailed from v5 to v6.

The proposal was reviewed by a number of people working on ink! v6, we are aligned with it and fully support it :slightly_smiling_face: .