Zano Trade is a non-custodial web UI where you post or accept swap proposals for ZANO and confidential assets.
For more information about Zano, please visit https://zano.org/ and Zano Trade https://trade.zano.org/dex
Status
This Audit Competition Is Over
Thank You to All Participating Security Researchers!
Your valuable contributions played a crucial role in identifying and resolving critical vulnerabilities, helping to strengthen and secure the Zano Trade platform for all users.
Immunefi vault program
Rewards
Rewards by Threat Level
Rewards Terms
Rewards are distributed among SRs according to Immunefi’s Standardized Competition Reward Terms.
Rewards are denominated in USD and distributed in USDC on Ethereum.
The reward pool is $14,000 USD if any bug is found.
If not a single bug is found (Insights do not count as bugs) the reward pool is $1,260 USD
On top of this, each participating SR will receive a guaranteed reward of $2,000 USD.
Proof of Concept (PoC) Requirements
For this program, runnable PoC code is not required. Whitehats are instead required to write a step-by-step explanation of the PoC and impact.
Insight Rewards Payment Terms
Insight Rewards: Portion of the Rewards Pool
*The "Insight" severity was introduced on Boost (Audit Competitions) & Attackathon programs to recognize contributions that extend beyond identifying immediate vulnerabilities. Currently, it's not an option to select the Insight severity when submitting a report. However, our team or program will designate it accordingly if applicable. "Insights" underscores our commitment to valuing all types of contributions that contribute to a more secure environment and will always be rewarded. View more information about Insights
Duplicates of Insight reports are not eligible for a reward.
Program Overview
Zano Trade is a non-custodial web UI where you post or accept swap proposals for ZANO and confidential assets.
For more information about Zano, please visit https://zano.org/ and Zano Trade https://trade.zano.org/dex
Zano rewards are denominated in USD and distributed in USDC on Ethereum.
KYC is not required.
KYC not required
No KYC information is required for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
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 our 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
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.
Therefore, 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.