BlockWallet
BlockWallet is the most private, non-custodial Ethereum browser wallet.
PoC required
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.
All app bug reports must come with a PoC in order to be considered for a reward. All Medium and Low app bug reports require a suggestion for a fix to be eligible for a reward.
The following vulnerabilities are not eligible for a reward:
- Any vulnerability that can only be abused by a local attacker
- Local Attackers (with access to the user’s machine/browser) are not part of our threat model.
Bug reports involving the ability to correctly determine the seed phrase will be paid at USD 150 000. All other extension bugs that are critical and result in loss of funds are paid at USD 50 000. High, Medium, and Low Web/App bug reports have the final reward determined by the BlockWallet team depending on exploitability, final impact, and ease of attack
Payouts are handled by the BlockWallet team directly and are denominated in USD. However, payouts are done in USDC.
Program Overview
BlockWallet is the most private, non-custodial Ethereum browser wallet. BlockWallet uses smart contracts that allow users to hide the amounts and origins of cryptocurrency held, in a decentralized and frictionless manner. Each time you want to make a withdrawal, BlockWallet will create a new wallet address for you with the amount of crypto that you requested, which originates from the smart contract where everyone’s funds are pooled. For more information about BlockWallet, please visit https://www.blockwallet.io
This bug bounty program is focused on their app and is focused on preventing:
- Thefts of funds of any amount
- Leak of user data
- Deletion of user data
- Access to sensitive pages without authorization
KYC not required
No KYC information is required for payout processing.
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
- Any other actions prohibited by the Immunefi Rules
Feasibility Limitations
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.