Immunefi
ZKsync Era-logo

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.

ETH
zkSync
Blockchain
L2
Solidity
Yul
Maximum Bounty
$300,000
Live Since
10 March 2023
Last Updated
12 November 2026
  • PoC Required

  • KYC required

Codebase

Title
ZKsync Smart Contracts
Description
Smart Contract Submodule For ZKsync Era
Link
Go to Audits & Known Issues
Assets Body
  • 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.

  • Web/App - Bug reports are to include a runnable Proof of Concept (PoC) in order to prove impact. All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. All PoC content must adhere to the PoC guidelines and rules of Immunefi. In the event that a PoC requires an attack on a web/app asset provided, they must still adhere to the rules provided, otherwise eligibility for a reward may be revoked.

  • For more information on PoCs please visit: Proof of Concept (PoC) Guidelines and Rules

Whitehats we highly encourage you to review any potential subdomains and what specific port(s) are in scope. Even though the domain may be the same, different ports may point to different assets.

Dev Environment and Documentation:

ZKsync has included dev documentation and/or instructions to help in reviewing code and exploring for bugs:

Pinned code:

GitHub assets are pinned to a commit. Reports on them are judged against the pinned code.

EraVM Airbender verifier and vm2:

From protocol version v34, Era batches are proven with both Boojum and Airbender. The EraVM Airbender verifier is the Airbender guest program: it re-executes the batch with vm2, the out-of-circuit EraVM, and checks the result against the batch commitment.

The verifier and vm2 assets point into the zksync-protocol repository at commit 2a2ecb3bfcccc46758826d3b0d11933b95e511be on main.

Reports on zksync-protocol assets must reproduce the issue in a local test against the pinned code.

Reports that the EraVM Airbender verifier accepts an invalid batch are assessed as if Airbender were the only proof system required to finalize a batch. Reports that it rejects a valid batch are assessed under the High impact "Difference between implementation outside of the circuit and within the circuit".

Denial of service through proving limits:

In production, the EraVM Airbender verifier must prove each batch within Airbender's limit of 2^36 cycles and a peak guest memory of 4 GiB. This section covers only reports that a batch can't be proven because it exceeds one of these limits; other denial-of-service reports are assessed as usual.

Such a report is in scope only if a single L1→L2 transaction that the L1 contracts accept from a user exceeds a limit, even alone in a batch. On EraVM chains, the contracts cap a user's L1→L2 transaction at 15M gas for its body (USER_PRIORITY_TX_MAX_GAS_LIMIT). Reports that need several transactions to exceed a limit are out of scope. In-scope reports are assessed under the High impact named above.

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 and high impact for an asset not in scope, ZKsync encourages you to submit your bug report using the “primacy of impact exception” asset.