Zano is the development of a scalable and secure coin, designed for use in e-commerce. The technology behind our blockchain provides reliability, security, and flexibility—a perfect option for P2P transactions.

For more information about Zano, please visit [https://zano.org/](https://zano.org/).

Zano rewards are denominated in USD and distributed in USDC on Ethereum

Network not being able to confirm new transactions (total network shutdown)

Execute arbitrary system commands

Retrieve sensitive data/files from a running server, such as:
- /etc/shadow
- database passwords
- blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)

Taking down the application/website

Taking down the NFT URI

Taking and/modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as:
- Changing registration information
- Commenting
- Voting
- Making trades
- Withdrawals, etc.

Changing NFT metadata

Direct theft of user funds

Malicious interactions with an already-connected wallet, such as:
- Modifying transaction arguments or parameters
- Substituting contract addresses
- Submitting malicious transactions

Direct theft of user NFTs

Injection of malicious HTML or XSS through metadata

Injecting/modifying the static content on the target application without JavaScript (persistent), such as:
- HTML injection without JavaScript
- Replacing existing text with arbitrary text
- Arbitrary file uploads, etc.

Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as:
- Email
- Password of the victim etc.

Improperly disclosing confidential user information, such as:
- Email address
- Phone number
- Physical address, etc.

Changing non-sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as:
- Changing the first/last name of user
- Enabling/disabling notifications

Redirecting users to malicious websites (open redirect)

Injecting/modifying the static content on the target application without JavaScript (reflected), such as:
- Reflected HTML Injection
- Loading external site data

Changing details of other users (including modifying browser local storage) without already-connected wallet interaction and with significant user interaction, such as:
- Iframing leading to modifying the backend/browser state (must demonstrate impact with PoC)

Taking over broken or expired outgoing links, such as:
- Social media handles, etc.

Temporarily disabling user to access target site, such as:
- Locking up the victim from login
- Cookie bombing, etc.

Direct loss of funds

Unintended permanent chain split requiring hard fork (network partition requiring hard fork)

Permanent freezing of funds (fix requires hardfork)

Unintended chain split (network partition)

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

Causing network processing nodes to process transactions from the mempool beyond set parameters

RPC API crash affecting programs with greater than or equal to 25% of the market capitalization on top of the respective layer

Shutdown of greater than or equal to 30% of network processing nodes without brute force actions, but does not shut down the network

Increasing network processing node resource consumption by at least 30% without brute force actions, compared to the preceding 24 hours

A bug in the respective layer 0/1/2 network code that results in unintended smart contract behavior with no concrete funds at direct risk

Shutdown of greater than 10% or equal to but less than 30% of network processing nodes without brute force actions, but does not shut down the network

Modification of transaction fees outside of design parameters

**Where do you suspect there may be bugs and/or what attack vectors are you most concerned about?**

We are concerned the most about implementation of cryptography and core rules (Bulletproofs, CLSAG etc). 

Most concerning attack vectors are:
- Emission bugs (printing coins out of air)
- Consensus bugs (double spend attack vectors, PoS grinding attacks)

**What external dependencies are there?**

Boost and OpenSSL

**What are the most valuable educational resources already available? (Ie. Documentation, Explainer videos or articles, etc**

This repository contains papers that describe math behind the project:  [https://github.com/hyle-team/docs/tree/master/zano](https://github.com/hyle-team/docs/tree/master/zano)

Any attacks related to lock time in transaction are out of scope. We removed this parameter from API but it still possible to create transaction with locked outputs. we are aware of this situation and it’s known to exist. Also, the default wallet behaviour is ignoring such transactions.

Zano Codebase

This repository contains papers that describe math behind the project

Educational Resources

Rewards are distributed among SRs according to [Immunefi’s Standardized Competition Reward Terms](https://immunefisupport.zendesk.com/hc/en-us/articles/31657285001873-Standardized-Competition-Reward-Terms).

Total budget: $25,000 broken down as follows:

**Reward pool:**

If bugs are found → USD $15k (see [Immunefi’s Standardized Competition Reward Terms](https://immunefisupport.zendesk.com/hc/en-us/articles/31657285001873-Standardized-Competition-Reward-Terms))

If only Insights are found → USD $1,35k (9% of the Reward pool)

**Guaranteed rewards:**
$5k per SR → $10k total (for 2 SRs)

Duplicate submissions of bugs are valid. Duplicate submissions of Insights are invalid.

**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.

IOP | Zano

Live

Live

Codebase

Documentation