![Polygon zkEVM-logo](/_next/image/?url=https%3A%2F%2Fimages.ctfassets.net%2Ft3wqy70tc3bv%2F4HtvkOERB7FEW5uUNz22lB%2F2ba376a451814502754906d247e472e5%2FPolygon_zkEVM_logo_dark_copy.png&w=128&q=75)
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
Resources & Documentation
Impacts only apply to assets in active use by the project like contracts on mainnet or web/app assets used in production.
For GitHub repositories please ensure you are reviewing the latest published releases and not the default branch
Any impact that applies to assets not in active use, like test or mock files, are out-of-scope of the bug bounty program unless explicitly mentioned as in-scope.
Blockchain/DLT
- Blockchain/DLT - PoC, Blockchain/DLT bug reports are to include a runnable Proof of Concept (PoC) in order to prove impact.
- For more information on PoCs please visit: Proof of Concept (PoC) Guidelines and Rules
Smart Contracts
- Smart Contracts - PoC, Smart Contract bug reports are to include a runnable Proof of Concept (PoC) in order to prove impact.
- For more information on PoCs please visit: Proof of Concept (PoC) Guidelines and Rules
Dev Environment and Documentation Polygon Labs has included dev documentation and/or instructions to help in reviewing code and looking for bugs:
Dev or Staging Environment Links |
---|
https://wiki.polygon.technology/docs/zkEVM/develop/ |
Impacts to other assets Hackers are encouraged to submit issues outside of the outlined Impacts and Assets in Scope.
If Whitehats can demonstrate a critical impact on 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.