ZKsync OS-logo

ZKsync OS

Airbender is ZKsync’s next-generation proof system, purpose-built to enable efficient zero-knowledge proofs of RISC-V bytecode execution. Built on highly optimized STARK/FRI implementations, Airbender is designed to support ZKsync’s long-term scaling strategy by being fast, cost-efficient, and adaptable to a wide range of use cases — without compromising security.

zkSync
Maximum Bounty
$100,000
Live Since
24 November 2025
Last Updated
01 December 2025
  • PoC Required

  • KYC required

Select the category you'd like to explore

Assets in Scope

Target
Name
Basic bootloader
Added on
24 November 2025
Target
Name
Basic system
Added on
24 November 2025
Target
Name
Callable oracles
Added on
24 November 2025
Target
Name
Crypto
Added on
24 November 2025
Target
Name
EVM interpreter
Added on
24 November 2025
Target
Name
Oracle provider
Added on
24 November 2025
Target
Name
Proof running system
Added on
24 November 2025
Target
Name
Storage models
Added on
24 November 2025
Target
Name
Delegated U256
Added on
24 November 2025
Target
Name
Modexp
Added on
24 November 2025
Target
Name
U256
Added on
24 November 2025
Target
Name
System hooks
Added on
24 November 2025

Impacts in Scope

Severity
Critical
Title

Direct and publicly triggerable loss of funds

Severity
High
Title

Underconstraints in the circuit that make invalid ZKsync OS executions provable

Severity
High
Title

Circuit, node, or program mismatches that make valid ZKsync OS executions unprovable and require verification key regeneration

Severity
Medium
Title

Undocumented deviation from EVM behavior (not related to gas)

Out of scope

Default Out of Scope and rules

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