Scroll
Scroll is an EVM-compatible zk-Rollup built to scale the Ethereum network. Our goal is to provide users with near instant and cost efficient transactions while also upholding the high security properties offered by the Ethereum network.
PoC required
Vault program
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Direct loss of funds
Permanent freezing of funds (fix requires hard fork)
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Protocol insolvency
Permanent freezing of funds (that cannot be fixed by upgrade)
Causing network processing nodes to process transactions from the mempool beyond set parameters
Temporary freezing of funds for at least 24h
Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
Theft of gas
Unbounded gas consumption
Out of scope
- Best practice recommendations
- Problems caused by L1 Gas Pricing
- Logic errors with rebase tokens and interest-bearing tokens
- Attacks related to deposit and withdraw limits
- Issues that affect geth (upstream) and are not caused by changes made in the scroll implementation
- Freezing of own funds due to mistaken operation
- Throttling or suppression of operations without loss of user funds
Blockchain/DLT specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
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 (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- 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
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers