Theoretical papers explaining the math behind codebase:

- Original CryptoNote protocol description (basic concepts of ring signatures and ephemeral keys): https://github.com/hyle-team/docs/blob/master/arch/cryptonote_wp_v2.0.pdf
- Zano original whitepaper: https://github.com/hyle-team/docs/blob/master/zano/Zano_WP_latest.pdf
- Extension of CLSAG that used in Zano signatures: https://github.com/hyle-team/docs/blob/master/zano/dv-CLSAG-extension/dv-CLSAG-extension.pdf
- RingCT and Confidential Assets: https://github.com/hyle-team/docs/blob/master/zano/CA_paper/Zano_CA_for_RingCT_and_Zarcanum_v1.1.pdf
- Confidential PoS: https://github.com/hyle-team/docs/blob/master/zano/PoS_with_Hiden_amounts_Zarcanum/Zarcanum-PoS-with-hidden-amounts.pdf

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.


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

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

Direct loss of funds

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

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

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

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

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

Subdomain takeover with already-connected wallet interaction

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

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

Redirecting users to malicious websites (open redirect)

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.

Codebase

Documentation

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

__Reward Calculation for Critical Level Reports__

For critical Blockchain/DLT bugs, the reward amount is 10% of the funds directly affected, capped at the maximum critical reward USD 20 000. However, a minimum reward of USD 5 000 is to be rewarded in order to incentivize security researchers against withholding on a bug report.

For critical Blockchain/DLT bugs with a non-funds-at risk impact, the reward will be paid out as follows: 

- Network not being able to confirm new transactions (total network shutdown) - USD 5 000
- Unintended permanent chain split requiring hard fork (network partition requiring hard fork) - USD 5 000
- Permanent freezing of funds (fix requires hardfork) - USD 5 000

For critical web/apps bugs, reports will be rewarded with USD 10 000, only if the impact leads to:

- A loss of funds involving an attack that does not require any user action
- Private key or private key generation leakage leading to unauthorized access to user funds 

All other impacts that would be classified as Critical would be rewarded a flat amount of USD 4 000. The rest of the severity levels are paid out according to the Impact in Scope table.  

__Reward Calculation for High Level Reports__

For high Blockchain/DLT non-funds-at risk impacts, the reward will be paid out as follows: 

- Unintended chain split (network partition) - USD 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 - USD 4 000
- Causing network processing nodes to process transactions from the mempool beyond set parameters - USD 4 000
- RPC API crash affecting projects with greater than or equal to 25% of the market capitalization on top of the respective layer - USD 4 000

__Reward Payment Terms__

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

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.