All smart contracts of LayerZero can be found at [https://github.com/LayerZero-Labs.](https://github.com/LayerZero-Labs) However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Impacts found in contracts which are deployed to multiple chains will be treated as one singular issue.

Documentation and instruction for PoC can be found here:
- GitHub README:[ https://github.com/LayerZero-Labs/LayerZero](https://github.com/LayerZero-Labs/LayerZero)
- Gitbook: [https://layerzero.gitbook.io/docs/](https://layerzero.gitbook.io/docs/)
- V2 Docs: [https://docs.layerzero.network](https://docs.layerzero.network)

If an impact can be caused to any other asset managed by LayerZero that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project. The vulnerability will then be evaluated by LayerZero Labs in good faith to determine where it would lie on the vulnerability scale.

LayerZero is an omnichain interoperability protocol that allows developers to seamlessly interact with contracts across dozens of blockchains. 

All above impacts for OApp, OFT & ONFT related contracts

Any governance voting result manipulation

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

Exploits resulting in the permanent locking or theft of user funds

Permanent DoS attacks (excluding volumetric attacks)

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, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported. 

V1 Smart Contract rewards are classified by Group 1 and Group 2. Group 1 consists of: Ethereum, BNB Chain, Avalanche, Polygon, Arbitrum, Optimism, Fantom. Group 2 consists of all other chains. Group 1 rewards are notated in the rewards table by the higher ranges listed by severity level, while Group 2 rewards are notated by the lower ranges listed by severity level. 

All 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. Bug reports are required to include a runnable PoC in order to prove impact. Exceptions may be made in cases where the vulnerability is objectively evident from simply mentioning the vulnerability and where it exists. However, the bug reporter may be required to provide a PoC at any point in time.

All vulnerabilities marked in the [https://github.com/LayerZero-Labs/Audits ](https://github.com/LayerZero-Labs/Audits) are not eligible for a reward.

All Impacts for OFT and [ONFT](https://github.com/LayerZero-Labs/solidity-examples/tree/main/contracts/token/onft) related contracts will be treated as low severity classifications and respective rewards. 

Critical V1 smart contract vulnerability payouts for Group 1 are a minimum of __USD $250,000__, or 10% of the value at risk at the time of report submission, with a hard cap of __USD $15,000,000__, whichever is larger. Value at risk should be calculated primarily (though not exclusively) based on concrete and demonstrable funds at risk. Any supplementary reward beyond the minimum USD $250,000 or 10% of value at risk is at the discretion of the team.

Critical V1 smart contract vulnerability payouts for Group 2 are a minimum of __USD $25,000__, or 10% of the value at risk at the time of report submission, with a hard cap of __USD $1,500,000__, whichever is larger. Value at risk should be calculated primarily (though not exclusively) based on concrete and demonstrable funds at risk. Any supplementary reward beyond the minimum USD $25,000 or 10% of value at risk is at the discretion of the team.

Critical V2 smart contract vulnerability payouts are a minimum of __USD $100,000__, or __10%__ of the value at risk at the time of report submission, with a hard cap of __$2,000,000__, whichever is larger. Value at risk should be calculated primarily (though not exclusively) based on concrete and demonstrable funds at risk. Any supplementary reward beyond the minimum __USD $100,000__ or __10%__ of value at risk is at the discretion of the team.

All non-critical rewards for the project bug bounty program are scaled based on an internally established team criteria, taking into account the exploitability of the bug, the impact it causes, and the likelihood of the vulnerability presenting itself, which is especially factored in with bug reports requiring multiple conditions to be met that are currently not in-place. Rewards will be provided at the determined fair value by the team depending on these conditions, assuming that the bug report is in-scope of the bug bounty program.

LayerZero requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed are: 
- Invoice is required with Name, Address, and Payment Instructions
- Proof of address (either a redacted bank statement with your address or a recent utility bill with your name, address, and issuer of the bill)
- Copy of your passport or other Government ID will be required
- Bounty hunters must pass OFAC Screening. Rewards cannot be paid out if hunters are on the OFAC SDN list 

The collection of this information will be done by the project team.

Payouts are handled by __LayerZero Labs__  directly and are denominated in USD. However, payouts are done in __Fiat USD via wire transfer, or USDC, USDT and BUSD__, with the choice of ratio at the discretion of the team.