**Proponent**: Fy6erZmPp78ZY2cN945FU9KnKdATmxvG2eB9a1kh2VX33xz

**Date**: 01.03.2024

**Requested KSM**: $250,000 (5102 KSM - 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](https://docs.google.com/document/d/1rzvoJxMVIG1MJfHCkHDLmXYBTlkJZvUgwsP4IV4oHKw/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 !


- **Problem Statement:** Enhancing security for bridges due to vulnerabilities leading to financial losses.
- **Significance:** Bridges are crucial for transferring data between chains but are prone to malicious activities.
- **Proposed Solution:** Implementing a Security Bug Bounty Program to engage the community in identifying vulnerabilities.
- **Expected Outcomes:** Increased security for bridges through community involvement and bug identification.

#353 POLKADOT <> KUSAMA BRIDGE SECURITY BOUNTY