Polygon zkEVM
Polygon zkEVM is the leading zero-knowledge scaling solution that is fully equivalent to an EVM. All existing smart contracts, developer toolings and wallets work seamlessly. Polygon zkEVM harnesses the power of zero-knowledge proofs in order to help reduce transaction costs and massively increase throughput, all while inheriting the security of Ethereum.
PoC required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
(For Blockchain/DLTR and Smart Contracts Only) This program is considered to be governed by Primacy of Impact. For more information on what this means visit: Best Practice - Primacy of Impact vs Primacy of Rules.
For fflonkVerififer Assets
- To check latest verifier in scope used by each rollup, use https://etherscan.io/address/0x5132A183E9F3CB7C848b0AAC5Ae0c4f0491B7aB2#readProxyContract then get the verifier used by each rollup using
rollupIDToRollupDatafor IDs ranging from 1 onwards. Then, the verifier contract will be part of the returning data.
Impacts to other assets
Hackers are encouraged to submit issues outside of those outlined Impacts and Assets in Scope.
If Whitehats can demonstrate a critical impact of code in production for an asset not in scope, Polygon Labs encourages you to submit your bug report using the “primacy of impact exception” asset as outlined below.
The final classification however takes into consideration the likelihood of the impact being achieved based on the table below. When submitting a bug report, select the original assigned impact level, but please be aware that its severity level may be reassigned based on the likelihood according to this table.
| Impact \ Likelihood | Critical | High | Medium | Low | None |
|---|---|---|---|---|---|
| Critical | Critical | Critical | High | Medium | Informational |
| High | High | High | High | Medium | Informational |
| Medium | Medium | Medium | Medium | Low | Informational |
| Low | Medium/Low | Medium | Low | Low | Informational |
| None | Informational | Informational | Informational | Informational | Informational |
In addition to Immunefi’s Vulnerability Severity Classification System, Polygon classifies vulnerabilities using the Common Vulnerability Scoring System (CVSS). In case of discrepancy, final determination is done by Polygon.
Network not being able to confirm new transactions (Total network shutdown requiring hard fork)
Unintended permanent chain split requiring hard fork (network partition requiring hard fork)
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
Permanent freezing of funds
Protocol insolvency
Unintended chain split (network partition)
Transient consensus failures
Temporary freezing of funds for at least 1 week
Theft of user fees
DoS and does not shut down the network
Out of scope
- Broken link hijacking is out of scope
- Loss of funds held by third parties
- Best practice critiques
- Attacks using vulnerable, old or deprecated libraries, that are not exploitable
The following activities are prohibited by this bug bounty program. Violation of these rules can result in a temporary suspension or permanent ban from the Immunefi platform at the sole discretion of the Immunefi team, which may also result in: 1) the forfeiture and loss of access to all bug submissions, and 2) zero payout.
Please note that Immunefi has no tolerance for spam/low-quality/incomplete bug reports, “beg bounty” behavior, and misrepresentation of assets and severity. Immunefi exists to protect the global crypto community, not facilitate grift.
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
756.8k from 53 paid reports