Optimism
Optimism is a project dedicated to scaling Ethereum's technology and expanding its ability to coordinate people from across the world to build effective decentralized economies and governance systems.
PoC required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Loss of user funds by direct theft, other than unclaimed yield
Permanent freezing of funds
Protocol insolvency
Direct loss of funds
Issues in the dispute-mon service causing a failure to detect a resolved dispute game leading to permanent loss of user funds
Network not being able to confirm new transactions (Total network shutdown)
Transient consensus failures
Freezing of funds (fix requires L2 hardfork)
Temporary freezing of funds (e.g. recoverable via an upgrade)
Incorrectly resolved dispute game (mitigated by a delay)
Incorrectly proven withdrawal (mitigated by a delay)
Incorrectly initiated bond withdrawal (mitigated by a delay)
Out of scope
-
Vulnerabilities in the implementation of ‘custom token bridges’ which are written by third parties for bridging tokens to their network
-
Best practice critiques
-
Since Optimism uses a fork of Geth, issues which are responsibly disclosed to upstream cannot be "replayed" against Optimism’s bug bounty program if the vulnerability has already been made public. If the vulnerability is disclosed to Optimism at the same time as upstream Geth, the vulnerability is eligible for the bug bounty program.
The following known issues are considered to be out of scope of this bug bounty program:
- All currently known issues with devp2p here: https://github.com/ethereum/devp2p/blob/master/rlpx.md#known-issues-in-the-current-version
Smart Contract 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