Zano Bug Bounty Program

Zano is the development of a privacy focused, scalable and secure L1, designed as platform for privacy focused projects. The technology behind our blockchain provides reliability, security, and flexibility—a perfect option for P2P transactions.

Program Type: Blockchain/L1 (C/C++)

Maximum Bounty: $10,000

Live Since: 14 July 2025

Rewards by Threat Level

Blockchain/DLT

Critical

• Maximum: $10,000
• Minimum: $2,000
• Primacy of Impact applies

High

• Up to: $3,000
• Primacy of Rules applies

Medium

• Up to: $1,000
• Primacy of Rules applies

Websites and Applications

Critical

• Maximum: $5,000
• Minimum: $2,000
• Primacy of Impact applies

High

• Up to: $3,000
• Primacy of Rules applies

Medium

• Up to: $2,000
• Primacy of Rules applies

Reward Calculation

Critical Level - Blockchain/DLT:

For critical Blockchain/DLT bugs, the reward amount is 5% of the funds directly affected, capped at the maximum critical reward of $10,000. A minimum reward of $2,000 is guaranteed to incentivize security researchers against withholding bug reports.

For critical Blockchain/DLT bugs with non-funds-at-risk impact:

• Network not being able to confirm new transactions (total network shutdown) — $3,000
• Unintended permanent chain split requiring hard fork (network partition requiring hard fork) — $3,000
• Permanent freezing of funds (fix requires hardfork) — $3,000

High Level - Blockchain/DLT:

For high Blockchain/DLT non-funds-at-risk impacts:

• Unintended chain split (network partition) — $4,000
• Temporary freezing of network transactions by delaying one block by 500% or more of the average block time of the preceding 24 hours beyond standard difficulty adjustments — $4,000
• Causing network processing nodes to process transactions from the mempool beyond set parameters — $3,000

Reward Calculation Details:

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.

The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.

Reward Payment Terms:

Payouts are handled by the Zano team directly and are denominated in USD. However, payments are made in USDC on Ethereum.

Responsible Disclosure

Zano adheres to Category 3: Approval Required. This policy determines what information researchers are allowed to make public from their submitted bug reports.

Primacy of Impact vs Primacy of Rules

Zano adheres to the Primacy of Impact for the following impacts:

• Blockchain/DLT — Critical
• Website & Application — Critical

Primacy of Impact means that the impact is prioritized rather than a specific asset. This encourages security researchers to report on all bugs with an in-scope impact, even if the affected assets are not in scope.

When submitting a report on Immunefi's dashboard, the security researcher should select the Primacy of Impact asset placeholder. If the team behind this project has multiple programs, those other programs are not covered under Primacy of Impact for this program. Instead, check if those other projects have a bug bounty program on Immunefi.

If the project has any testnet and/or mock files, those will not be covered under Primacy of Impact.

All other impacts are considered under the Primacy of Rules, which means that they are bound by the terms and conditions set within this program.

Proof of Concept (PoC) Requirements

A PoC, demonstrating the bug's impact, is required for this program and must comply with the Immunefi PoC Guidelines and Rules. Proof of concept is required for all severities.

Previous Audits

Zano has completed an Invite-only Program with Immunefi. The audit reports can be found at https://drive.google.com/file/d/1R8jcc5_vFfCdR4jAmtfEGvmCoa2j0dJe/view. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.

Feasibility Limitations

The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity.

Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report, including:

• Chain Rollbacks
• Pre-Impact Bug Monitoring
• Attack Investment Amount
• Attacks With A Financial Risk To The Attacker
• When Is An Impactful Attack Downgraded To Griefing?

KYC Requirements

No KYC information is required for payout processing.

Prohibited Activities

• Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
• Any testing with pricing oracles or third-party smart contracts
• Attempting phishing or other social engineering attacks against employees and/or customers
• Any testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
• Any denial of service attacks that are executed against project assets
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty
• Any other actions prohibited by the Immunefi Rules

Program Information

For more information about Zano, please visit https://zano.org/

Zano provides rewards in USDC on Ethereum, denominated in USD.