**Proponent:** 14Pn8sUxdEMgFRDgZ5J2VfcUVMLaMQhst9XuvCj9

**Date:** 26.01.2024

**Requested DOT:** $250,000 (39,100 DOT - rate 1 DOT=$6.39)

**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](https://docs.google.com/document/d/1j-Nb7FYgSJpChgbvkbkHCM_dsjENhrh4Vqc4rNsmNGY/edit), 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 !

Polkadot Kusama Bridges Security Bug Bounty

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](https://docs.google.com/document/d/1j-Nb7FYgSJpChgbvkbkHCM_dsjENhrh4Vqc4rNsmNGY/edit#heading=h.v6is2ta0txr1), 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!

POLKADOT <> KUSAMA BRIDGE SECURITY BOUNTY

This referendum proposes the Curators for [bounty 44](https://polkadot.polkassembly.io/bounty/44) – Bounty Proposal for Polkadot <> Kusama Bridge Security Bug Bounty. Please review the bounty and previous referendum which funded this [bounty](https://docs.google.com/document/d/1j-Nb7FYgSJpChgbvkbkHCM_dsjENhrh4Vqc4rNsmNGY/edit#heading=h.v6is2ta0txr1) for more info.
The curators are responsible for evaluating the effectiveness of the different phases and for the attribution of the reward to the bug bounty reporter. To ensure the successful implementation of this bounty, the curators are bringing diverse forms of expertise.
More details about the curators and key activities [attached](https://docs.google.com/document/d/1MrmlOmyjKcDbvGv8OyxcFXBnYnZWjJBUQrX6sFdHqdg/edit)

CURATORS PROPOSAL FOR BOUNTY 44 - POLKADOT <> KUSAMA BRIDGE SECURITY BUGBOUNTY

<div class="flex flex-col relative">
<div class="osn-previewer">
<div class="markdown-body ">
Proponent:&nbsp;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&rsquo;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 <a href="https://docs.google.com/document/d/1j-Nb7FYgSJpChgbvkbkHCM_dsjENhrh4Vqc4rNsmNGY/edit">attached</a>, 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!
</div>
</div>
</div>