Bug bounty
Triaged by Hackenproof

Polkadot Bridge: Program info

Polkadot Bridge

Company: Polkadot
KYC required
This program will start in 1 day
Program infoReports

We're a core blockchain infrastructure company. We're creating an open-source creative commons that will enable people to create better institutions through technology.

In scope
TargetTypeSeverityReward
https://github.com/paritytech/parity-bridges-common
copy
Copy
success Copied

Parity Bridges Common

Code
Critical
Bounty
https://github.com/paritytech/polkadot-sdk/tree/master/bridges
copy
Copy
success Copied

Polkadot SDK: Bridges

Code
Critical
Bounty
https://github.com/paritytech/polkadot-sdk/tree/master/cumulus/parachains/runtimes/bridge-hubs
copy
Copy
success Copied

Polkadot SDK: Bridge hub parachains

Code
Critical
Bounty
https://github.com/polkadot-fellows/runtimes/tree/main/system-parachains/bridge-hubs
copy
Copy
success Copied

Runtimes: Bridge hub

Code
Critical
Bounty
Target
https://github.com/paritytech/parity-bridges-common
copy
Copy
success Copied

Parity Bridges Common

TypeCode
Severity
Critical
RewardBounty
Target
https://github.com/paritytech/polkadot-sdk/tree/master/bridges
copy
Copy
success Copied

Polkadot SDK: Bridges

TypeCode
Severity
Critical
RewardBounty
Target
https://github.com/paritytech/polkadot-sdk/tree/master/cumulus/parachains/runtimes/bridge-hubs
copy
Copy
success Copied

Polkadot SDK: Bridge hub parachains

TypeCode
Severity
Critical
RewardBounty
Target
https://github.com/polkadot-fellows/runtimes/tree/main/system-parachains/bridge-hubs
copy
Copy
success Copied

Runtimes: Bridge hub

TypeCode
Severity
Critical
RewardBounty

Focus Area

Parity Bridges Common is a collection of components for building bridges. These include Substrate pallets for syncing headers and passing arbitrary messages, as well as libraries for building relayers to provide cross-chain communication capabilities.

Familiarize yourself with the bug bounty program requirements.

In case that your finding is valid you might be asked for extra KYC verification to proceed with payments

Program Rules

Rules of the road

Submission timing

Only submissions received by the official start date are considered. If you suspect that the flaw you found may be fatal for the items in the scope, please do not take further action. Instead, describe your assumptions as detailed as possible in the report.

Report critical flaws

If you identify a significant vulnerability, please stop at the point of recognition, gather the minimum amount of evidence necessary to demonstrate the issue, and report the vulnerability.

Duplicate submissions

Duplicate submissions within 72 hours of each will split the bounty. If duplicate submissions are of unequal quality, the split will be at the level of the lesser report, and the greater report will receive a prorated additional bounty on top of the split. Despite striving to be transparent as much as possible, we do not disclose other participant’s names in such cases.

Accidental access

Notify us immediately at [email protected] if you inadvertently access, modify, delete, or store user data by accident, and delete any stored data after notification.

Respect our infrastructure

Our security team will investigate and potentially increase the bounty if the impact is greater than initially assessed. Please refrain from attempts that could break the systems, as many participants share the bounty program resources.

Rules of conduct

Zero tolerance

Threats or extortion towards members of the Polkadot/Kusama ecosystem, including withholding security issues, releasing vulnerabilities or data to the public or third parties, or engaging in disruptive behavior, will lead to immediate disqualification.

Safe and supportive environment

We reserve the right to disqualify individuals acting in a malicious, disrespectful, or disruptive manner. Such actions undermine the shared goal of creating a safe and supportive space for all.

Disclosure Guidelines

  • Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization
  • No vulnerability disclosure, including partial is allowed for the moment.
  • Please do NOT publish/discuss bugs

Eligibility and Coordinated Disclosure

We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward:

  • You must be the first reporter of a vulnerability.
  • The vulnerability must be a qualifying vulnerability
  • Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
  • You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary.
  • You must not be a former or current employee of us or one of its contractor.
  • ONLY USE YOUR HackenProof ADDRESS (in case of violation, no bounty can be awarded)
  • Provide detailed but to-the point reproduction steps

What makes a good submission?

Ultimately, we’re after findings that have a real impact. Purely theoretical findings are sometimes entertaining to investigate, so feel free to send us any. However, it will only be eligible if there is a way to break our systems in practice. Here’s what we’re looking for:

Proof-of-concept

Provide a working proof-of-concept (or equivalent evidence) — assuming that your research didn’t produce unrecoverable changes. This helps us to evaluate whether your submission is within the program’s scope and usable in possible attacks.

Impact vision

Describe the potential impact and attack scenario, including necessary conditions.

Originality

Ensure the bug is original and previously unreported (with no traces of reporting in public issues or internal audits).Where applicable, include links to any issues or PR that lead to your discovery or introduction of the vulnerability.

Legal and privacy

The Bug Bounty Program is a discretionary rewards program designed to encourage and reward those helping to improve the systems we build. It is not a competition, and we can cancel the program at any time. Awards are at our sole discretion.

All Bug Bounty awards are subject to compliance with local laws, rules, and regulations. We will not issue awards to individuals who are on sanctions lists or who are in countries on sanctions lists. We may conduct background checks via our screening tool in order to verify eligibility. You are responsible for all taxes payable on received rewards. All rewards are subject to the laws of England and Wales.Your testing must not violate any law or compromise any IP rights, data, or funds that are not yours.

To participate in the Bug Bounty Program, you will need to share personal data, including your name, email address, ID information and photos, and a blockchain address. The Polkadot and Kusama community are committed to protecting and respecting your privacy. For details on how your personal data is used, please see our Privacy Policy.

Any obligations arising out of or in connection with the Polkadot/Kusama Bridges Bug Bounty Program or its subject matter, will be governed by and construed in accordance with the law of England and Wales. The courts of England and Wales have exclusive jurisdiction to settle any disputes or claims (including non-contractual disputes or claims) arising out of or in connection with the program.

This program strongly supports and encourages security research into Polkadot/Kusama Bridge. If you conduct genuine, in-scope, bug-hunting research in good faith and in accordance with this policy, we will consider your actions to be legitimate and not seek prosecution. But for the avoidance of doubt, this does not give you permission to act in any manner that is inconsistent with the law or might cause us to be in breach of any of our legal obligations.

Rewards
Range of bounty$1,000 - $100,000
Severity
Critical
$100,000
High
$25,000
Medium
$10,000
Low
$1,000
Stats
Scope Review71
Submissions0
Total rewards0
Types
other
Languages
Rust
SLA (Service Level Agreement)
Time within which the program's triage team must respond
Response TypeBusiness days
First Response3d
Triage Time3d
Reward Time3d
Resolution Time14d