Integritee Network
Integritee is a highly scalable, privacy-enabling network in the Polkadot ecosystem with parachains on Polkadot and Kusama. We seek to become the leading Web3 privacy solution - a blockchain network for developers and relevant to enterprises to build (decentralized) applications that benefit from unrivaled speed, verifiable confidentiality/privacy, and interoperability. At scale.
Polkadot
Blockchain
L2
Rust
C/C++
Python
Maximum Bounty
$10,000Live Since
10 June 2024Last Updated
10 June 2024PoC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Critical
Sidechain not being able to confirm new transactions (total network shutdown)
Critical
Unintended permanent chain split requiring hard fork (network partition requiring hard fork)
Critical
Direct loss of funds
Critical
Permanent freezing of funds (fix requires hardfork)
High
Unintended sidechain split (network partition)
High
Temporary freezing of network transactions by delaying one block by 500% or more of the average block time of the preceding 24 hours beyond standard difficulty adjustments
High
Causing network processing nodes to process transactions from the mempool beyond set parameters
High
RPC API crash affecting projects with greater than or equal to 25% of the market capitalization on top of the respective layer
Medium
Increasing network processing node resource consumption by at least 30% without brute force actions, compared to the preceding 24 hours
Medium
Shutdown of greater than or equal to 30% of network processing nodes without brute force actions, but does not shut down the network
Low
Shutdown of greater than 10% or equal to but less than 30% of network processing nodes without brute force actions, but does not shut down the network
Low
Modification of transaction fees outside of design parameters
Out of scope
Program's Out of Scope information
These impacts are out of scope for this bug bounty program.
All Categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (governance, strategist) except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
Blockchain/DLT Specific
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
Prohibited Activities
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- Any testing with pricing oracles or third-party smart contracts
- Attempting phishing or other social engineering attacks against our employees and/or customers
- Any testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
- Any denial of service attacks that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty