All smart contracts of zkSync Lite can be found at [https://github.com/matter-labs/zksync/tree/breaking/contracts](https://github.com/matter-labs/zksync/tree/breaking/contracts). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program. 

__Note__ that the bug bounty program includes contracts from the currently active version o zkSync target/governance target/additional zkSync.

zkSync Lite is a scaling engine for Ethereum. Its current functionality scope includes low gas transfers of ETH and ERC20 tokens, atomic swaps & limit orders as well as native L2 NFT support. 

Loss of user funds by permanent burning, freezing or direct theft

Network shutdown

Double spending

Inability to generate a block for a priority operation that is added through a smart contract

Minting fungible tokens not through a deposit

Ability to steal/burn/freeze other people's tokens

Leak of user data

Redirected funds by address modification

Site goes down

Temporary freezing of funds for at least 24 hours

Forceful activation of exodus mode

Blocking of upgrade system

Ability to execute a transaction with changed signed parameters (e.g. sender/recipient/amount/tokenId/feeToken/...)

Ability to create a block with public input information that is not enough to restore state transition

Smart contract gas drainage

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Smart contract fails to deliver promised returns, but doesn’t lose value

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2). This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.  For the ZK-SNARK Circuits, the classification will be based on the impacts listed on the Impacts in Scope section below

All critical and high severity bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.

Rewards for critical smart contract vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum reward of __USD 50 000__ for Critical bug reports. 

The rewards for the Blockchain/DLT section is only for the ZK-SNARK Circuits assets and not any other blockchain/DLT section.

__KYC__

zkSync has a Know Your Customer (KYC) requirement for bug bounty payouts. Government identification is required for the KYC process.

Payouts are handled by the __zkSync__ Lite team directly and are denominated in USD. However, payouts are done in __USDC__ via zkSync Lite.

zkSync

Resources & Documentation