ZKsync Era
ZKsync Era is a layer 2 rollup that uses zero-knowledge proofs to scale Ethereum without compromising on security or decentralization. Since it's EVM compatible (Solidity/Vyper), 99% of Ethereum projects can redeploy without refactoring or re-auditing a single line of code.
PoC Required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Direct loss of funds
Direct theft of any user funds, whether at-rest or in-motion
Permanent freezing of funds (that cannot be fixed by upgrade)
Protocol insolvency
Permanent freezing of funds (that can be fixed by upgrade)
Permanent stopping the priority queue
Theft of user fees
Difference between implementation outside of the circuit and within the circuit, where the in-circuit implementation is accurate (e.g. overconstraint in the circuit)
Block stuffing for profit
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
- Any finding whose exploitation requires Gateway to be enabled and operating as a settlement layer is out of scope, since Gateway is not currently enabled and all chains settle directly to L1. This applies only to the Gateway precondition — the same code, when reachable by an L1-settling chain, stays in scope.
- Broken link hijacking is out of scope.
- Attacks requiring changing the verifier key.
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