POLKADOT <> KUSAMA BRIDGE SECURITY BOUNTY
Proponent: 14Pn8sUxdEMgFRDgZ5J2VfcUVMLaMQhst9XuvCj9mKJYUAN2
Date: 01.03.2024
Requested DOT: $250,000 (30,581 DOT - based on EMA7 March 1st 2024)
Short description:
Bridges enable transferring data, assets, and more between multiple chains. Due to their pivotal role and high transaction volumes, they have simultaneously become a hotspot for malicious activities. When exploited, these breaches can lead to significant impact including financial losses.
This proposal aims to ensure the utmost security of the bridges and promote community involvement by implementing a Security Bug Bounty Program. While all developers involved work hard to ensure the software and protocols built are bug-free, secure by design, and third-party code audits have been already performed, it is recognised security best practices to complement this. That’s why Polkadot and Kusama need community and bug bounty hunters to help to identify security vulnerabilities that could cause impact from all the severity levels before it is widely used and adopted.
To support this, the Bug Bounty participants are provided with many context details in the full proposal attached, including a threat model of the scope.
As a security vulnerability in the bridge can impact both the source and destination blockchains, a mirror bounty is raised on Kusama and Polkadot
Thanks for your time and support to make Polkadot more secure!
Comments (10)
Proposal Passed
3
of 3Summary
0%
Aye
0%
Nay
Aye (142)0.0 DOT
Support0.0 DOT
Nay (10)0.0 DOT
Voting Data
Approval%
Support%
Threshold0.00%
Threshold0.00%
The bounty could probably be bigger, given it's an allocation it may not even all get spent....
This is a critical part of ensuring security of bridge infrastructure, as well as the best practices of such. It serves two purposes: 1) to ensure users that security is taken seriously, and, 2) to provide an economic incentive for third parties to reveal disclosures.