As per the Optimism announcement “Funds Are Safu.” On February 2nd, the Optimism team was alerted by Jay Freeman of a critical bug in Optimism’s fork of the Ethereum Geth client software. browser extensions) as well as websites (e.g.Ethereum Layer-2 solution Optimism has fixed a critical software bug in one of its smart contracts on Ethereum. Any testing with third party systems and applications (e.g.Attempting phishing or other social engineering attacks against our employees and/or customers.Any testing with pricing oracles or third party smart contracts.Any testing with mainnet or public testnet contracts all testing should be done on private testnets.The following activities are prohibited by this bug bounty program: All currently known issues with devp2p here:.If the vulnerability is disclosed to Optimism at the same time as upstream Geth, the vulnerability is eligible for the bug bounty program. 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. Vulnerabilities in the implementation of ‘custom token bridges’ which are written by third parties for bridging tokens to their network.Basic economic governance attacks (e.g.Not to exclude oracle manipulation/flash loan attacks.Incorrect data supplied by third party oracles.Attacks requiring access to privileged addresses (governance, strategist).Attacks requiring access to leaked keys/credentials.Attacks that the reporter has already exploited themselves, leading to damage.The following vulnerabilities are excluded from the rewards for this bug bounty program: Payouts are handled by the Optimism team directly and are denominated in USD. The user cannot commit to a L1 gas price, the OVM_GasPriceOracle is owned by a key controlled by Optimism and is responsible for setting the L1 gas price.This bug is dependent on the layout of the implementation contract, and Optimism is not affected. A bug in Lib_ResolvedDelegateProxy.sol which could result in a storage slot key collision overwriting the address of the implementation.There is a workaround for this, by modifying the proof to add an extra element. A bug in Lib_MerkleTrie.sol which will prevent withdrawals from succeeding in some cases.The fact that fault proofs (FKA fraud proofs) are not yet running.The fact that their contracts are upgradable via a multisig.The following known issues are considered to be out of scope of this bug bounty program: Naturally if you do find a way to circumvent our protections, then we would reward you.įor testing any exploits involving cross-domain transactions, we recommend working with our dockerized services and modifying our integration tests There is no check in the L2StandardBridge, however the withdrawal is prevented from finalizing by a check in the L1StandardBridge. Note: that there appears to be an obvious bug which would allow an attacker to withdraw a fake ERC20 token from L2 in exchange for a real ERC20 (such as WBTC) token on L1. However, there is a minimum of USD 75 000 for Critical bug reports. 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.Īll smart contract bug reports must come with a PoC in order to be considered for a reward.įor KYC, OptimismPBC will request an invoice, with your name and address in order to payout the reward.Īny freezing of funds that is recoverable via an upgrade would be considered as High severity.Ĭritical vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System.
0 Comments
Leave a Reply. |