Polkassembly Logo

Head 1
Head 3
Head 4
Create Pencil IconCreate
TRACKS
ORIGINS
Report an issueNeed help with something?
Foot 1
Foot 2
Foot 3
Foot 4
OpenGov
View All Medium Spender

ink! 5.0 Codebase Security Audit

inMedium Spender
a year ago
security
ink
polkadot
Executed

Proposal Overview

The ink! smart contract programming language is becoming increasingly popular among developers within the Polkadot community for its simplified syntax and efficient deployment, utilizing the contracts pallet. Previous audits in 2022 and 2023 commissioned by Parity Technologies and executed by SRLabs have focused on auditing ink! 4.0 and the contracts pallet. Important to note that at the time of this previous audit, there was a limited number of real-life contracts with complex logic utilizing ink!

This proposal enables a comprehensive audit of the ink! 5.0 smart contract language and implementation to identify new vulnerabilities and point out potential areas of improvement in its codebase. On top of the codebase changes since the latest review, the auditors will conduct a deep dive on the ink! storage layer and XCM integration. By joining forces with the Parity Security team to ensure that relevant real-life contracts and all major stakeholder expectations are considered, we will enhance the security and reliability of ink! smart contracts and ultimately contribute to the growth and adoption of this innovative programming language within the Polkadot ecosystem.

Deliverables

  • Comprehensive audit report. The project report deliverable will be made available to the public, after the main findings have been fixed, to document the results of the ink! 5.0 audit. This enables the ink! developer community to benefit from the audit findings and recommendations.
  • Ecosystem blogpost. From the audit findings, a dedicated blogpost will be compiled and shared on the Polkadot forum help ink! developers to incorporate security considerations into their codebase, ultimately improving the overall security and reliability of smart contracts developed using the ink! programming language. By making this information accessible to the community, we aim to foster collaboration and contribute to the continued development and enhancement of the ink! ecosystem.
  • Responsible disclosures. Additionally, the open-source ink! contracts that were selected as examples to aid the audit process will further benefit from responsible vulnerability disclosures from the auditors in case any bugs are discovered in their codebase during the audit.

Engage with Us

  • Read the Full Proposal: For a detailed understanding of the context of this proposal, the audit workstreams and division of responsibilities, read our full proposal
  • Learn About Parity Security: Fostering security awareness, prioritisation of mitigation efforts and vulnerability disclosures, Parity Security is pivotal in keeping the polkadot-sdk codebase and the ecosystem as a whole secure. Discover more of their work on the Polkadot forum
  • Learn About SRLabs: Security Research Labs is a cybersecurity consultancy committed to making the world more secure. Discover more about them on their website

We Appreciate Your Feedback

How can we improve our proposal? Which ink! contracts do you believe are most used in the ink! ecosystem that could benefit from our audit? Your input will help us refine our approach to better serve the Polkadot community. Thank you.

Comments (7)

a year ago

contracts pallet is really important, but is undergoing a PVM transformation, which will be used about 10^N times more than any thing "ink!" with this transformation + Solidity-to-PVM compiler for increasing N as time goes on. Very clear, correct?

The efficient thing to do is to audit it LATER. An audit now would only cover ink! 5.0, which is your scope. An audit LATER would get this real usage.

This is a gauge of how much ink! is used in the ecosystem.
https://astar.subscan.io/wasm_contract_dashboard?tab=verified

image

There will be some other entity who will make great claims about how ink! is alive and well and how much it will be used in the future -- please present this data and how many active users are actually using those contracts -- we want to know!

Please explain why an ink! 5.0 centric audit is justified NOW instead of later when contracts pallet has PVM powers? Even more importantly, what is your role in auditing the Solidity-to-PVM compiler?

a year ago

Please note the beneficiary address is an ink! address. As setting identities for Pure Proxies on the People Chain is still awaiting a solution, the address does not have an identity. Please see the official ink! repository description to verify the address: https://github.com/use-ink

Load more comments
PleaseLogin to comment

Requested

DOT
43.14K DOT

Proposal Passed

3

of 3

Summary

0%

Aye

AyeNay

0%

Nay

Aye (52)0.0 DOT

Support0.0 DOT

Nay (12)0.0 DOT

Help Center

Report an Issue
Feedback
Terms and Conditions
Github

Our Services

Docs
Terms of Website
Privacy Policy

A House of Commons Initiative.

Polka Labs Private Limited 2025

All rights reserved.

Terms and ConditionsTerms of Website
Privacy Policy