Zano (ZANO)
Zano ranks #73 of 484 cryptocurrencies. On a list that also counts tokens, memecoins, wrapped coins, staked derivatives and stablecoins it appears at #402: 329 of the 401 assets ahead of it are not native coins but tokens or claims. A token is issued on a host blockchain rather than running its own; a claim stands for an asset already counted. Of the 412 non-native assets CoinSpectrum lists above it by market cap, about 47% are claims on other assets, 46% are tokens, 7% are memecoins and under 1% are NFT collections.
| CoinSpectrum Grade | B · 62/100 · provisional, B to A |
|---|---|
| Rank among cryptocurrencies | #73 |
| Rank counting claims | #402 |
| Market capitalisation | $56M |
| Price | $3.60 |
| Circulating supply | 15,493,783 ZANO |
| Maximum supply | no fixed cap |
| Consensus family | Hybrid |
| Consensus mechanism | ProgPoWZ PoW + PoS |
| Own hashrate | 229 GH/s |
| Network purpose | Private payments |
| Ledger type | Multi-asset ledger |
Market figures from the 10 November 2026 build. Open the live view for every exchange's price, and charts.
CoinSpectrum Grade (Source)
B — 62 out of 100, provisional (from 10 of 10 sections, 10 November 2026 build). With what is not yet measured anywhere from nothing to full marks, the score would be 57 to 66 (B to A).
| Section and criteria | Score | Basis |
|---|---|---|
| Consensus | 4.5 | average of 2 criteria |
| By leader (its largest chain's market cap) (Source) | 4.5 | Hybrid: 4.5 of 10 on the ladder of consensus families ranked by their largest chain's market cap |
| By family (all its chains' market cap) (Source) | 4.5 | Hybrid: 4.5 of 10 on the ladder of families ranked by the combined market cap of their chains |
| Supply | 8.7 | the supply scale times 0.9, and a point for a fixed cap that holds |
| Supply (21 million scores 10) | 9.7 | no fixed maximum; 15.5 million in circulation |
| Distribution | 7.4 | average of 3 parts |
| Holder concentration (Source) | – | Not yet measured |
| Active addresses | – | Not yet measured |
| Premine (allocated at launch) | 2.6 | 74.2% of today's supply allocated at launch to founders, a company, a foundation or investors. At the 2019 launch 17.52M ZANO were reserved before mining: a 3.69M development premine (foundation 2.03M, team 1.11M, loan repayment 0.55M) and a 13.83M pool for a 1:1 coinswap from Boolberry, of which ~7.78M were claimed and the rest burned; 3.69M + 7.78M = 11.47M against ~15.47M current supply (CoinGecko). source |
| Fundraising (share sold) (Source) | 9.6 | Sold by its issuer or insiders: 3.6% of supply sold. There was no sale. The only coins delivered for money were the 553,500 ZANO from the premine used to repay Boolberry shareholders' 2018 development loan, effectively a pre-sale. 0.5535M / ~15.47M supply (CoinGecko) = 3.6%. No ICO/IEO/VC round. Boolberry shareholders lent development funds in early 2018; the loan was repaid with 553,500 ZANO from the premine. source |
| Developer share (after launch) | 10 | No developer share: every new coin goes to the miners or validators who produce blocks. The 1 ZANO block reward goes to the PoW miner or PoS staker who produces the block, and fees are burned. There is no dev fee; the 3.69M development share was a launch premine. source |
| Decentralisation | 2.7 | average of 3 parts |
| Governance (Source) | 0 | An authority can halt the chain or freeze funds: In Sep 2026 the core team shipped software restarting the chain from block 3,833,000, reversing about a month of transactions after an issuance bug. source |
| No central team (Source) | 0 | A central team directs it: The Zano core team (hyle-team, led by Andrey Sabelnikov) maintains the only node (MIT) and the roadmap. source |
| Who can mint (Source) | 8 | Open, with a stake vote: anyone can mine, and stakeholders vote on the blocks |
| Nodes (Source) | – | Not yet counted |
| Security | 6.4 | 3.9 of 6 points, 2 not yet measured source |
| Pool diversity (Largest pool 50% 0 to 20% 10, largest three 90% 0 to 50% 10; 2 points) | – | |
| Network activity (Transactions a day, 250 0, 500,000 or more 10; 2 points) | 2.1 | about 1,191 transactions a day |
| Hashrate (Own work 5, its power 1 kW 0 to 10 GW 5; 1 point) | 7.4 | own work 5; about 2.2 MW (estimated from its miner pay), 2.4 of 5; the largest on its algorithm |
| Clients (Separate code and teams 10, separate code or teams 9, a fork by the same team or a stale second 8; one client: a new version within 12 months 7, 24 months 6, none in 24 months 5, none in 48 months 3; a second in development +0.5, a second seen running +1, 8 at most with one client; chain ended 0; 1 point) | 7 | one client, latest version Oct 2026 |
| Open source (Node software) | ✓ | |
| No 51% attack (Nor a deep reorganisation, five years) | ✓ | |
| Scalability | 5.1 | average of 3 parts, +1 for an adaptive block size source |
| Fees ($0.001 or less 10, $1 or more 0) | 4.7 | typical fee $0.038 |
| Throughput (2,478 a second, the busiest network's peak day, 10; 121, the median of the ten busiest, 5) | – | not yet measured |
| Block time (10 minutes 10, less either side) | 7.5 | a block every 2 minutes |
| Block space per 10 minutes (24 MB or more 10: the ten busiest networks' median demand, 16.4 MB, and half again for growth) | – | not yet measured |
| Features (3 checks) | 0 | 0 of 2 passed, 1 not yet researched |
| Fast payments (Safe to accept within seconds · Whitepaper abstract, §1, §2 and §11) | ✗ | About one-minute alternating PoW/PoS blocks with probabilistic confirmation (10 recommended). |
| Pruned nodes (Old history dropped, every rule checked · Whitepaper §7) | – | No documented pruning mode found. |
| Light clients (Payments verified from headers · Whitepaper §8) | ✗ | No SPV-style light client; light wallets use a remote node. |
| Adaptive block size (a bonus point, at most 10) | +1 | A block may be at most twice the median size of the last 400 blocks (125 kB penalty-free floor), with a reward penalty above the median; inherited CryptoNote rule, in consensus since launch. |
| Privacy | 9.6 | 9.6 of 10: whitepaper privacy 7 of 7, extra features 2.6 of 3 source |
| Protocol level privacy (Keys not tied to an identity · Whitepaper §10) | 10 | Anyone can create keys and receive and send coins; the protocol carries no identity check. |
| UTXO ledger (Separate outputs, change to a new address · Whitepaper §2, §9) | 10 | Coins are separate unspent outputs: a payment spends whole outputs and sends the change to a new address, so the coins in one wallet need not share a history. |
| HD addresses (A new address for each payment, unlinked · Whitepaper §10) | 10 | One-time (stealth) addresses: every payment goes to a new address derived from the receiver's public address, unlinkable on chain |
| Hidden amounts (Amounts confidential) | 10 | Amount commitments with Bulletproofs+ and Zarcanum (HF4, 2024) hide all amounts, mandatory. |
| Hidden parties (Sender and receiver hidden) | 10 | d/v-CLSAG ring signatures hide the sender and one-time stealth addresses hide the receiver, mandatory. |
| Network privacy (Origin hidden by default) | 0 | Zano's privacy layers are on-chain; no Dandelion or built-in Tor relay for the node. |
| Programmability | 5.6 | 5 of 9 points source |
| Token issuance (At protocol level) | 2 | Confidential Assets in the protocol since the Zarcanum hard fork (HF4) of March 2024, deployable by any wallet for a fee. |
| Smart contracts | 0 | Fixed output types (key, multisig, HTLC) and confidential assets, with no user scripting. |
| Multisig and time locks (Without a third party) | ✓ | Native multisig outputs plus lock-times on HTLC outputs. |
| Atomic swaps (With other chains) | ✓ | Native HTLC output type activated by hard fork 3 (block 1,082,577, 2021) for swaps with Bitcoin. |
| Native DEX (Trades the coin itself, not a claim) | ✗ | No DEX found trading the coin itself: none on its own chain (DefiLlama), and not on THORChain, Maya, Chainflip, Komodo DeFi, BasicSwap, Bisq or Haveno (checked 2026-11-04). |
| Cross-chain messaging (Verified by the chain itself) | ✗ | No protocol messaging to other chains. |
| NFTs (Carried by the chain's rules) | ✓ | Confidential Assets (Zarcanum, March 2024) carry a configurable total_max_supply, used for NFTs such as Obscura's. |
| Demand | 5.4 | average of 7 measures |
| Exchanges (10 or more: 10) | 7 | 7 exchanges |
| Daily volume ($10K 0, $1B or more 10) | 4.1 | $758,487 traded in 24 hours; #599 by volume on the exchanges the site reads (scored on the median day of the last 30, $1,136,523) |
| Turnover (volume ÷ market cap, 5% a day: 10) | 7.5 | 1.7% of its market cap a day, median of the last 30 days |
| Order-book depth (±2% of the price ÷ market cap, 1%: 10) | 3.6 | $6,550 within 2% of the price on 1 exchange, 0.01% of its market cap, median of the last 15 days |
| Market cap ($1M 0, $10B or more 10) | 4.4 | $56M, 4.4 on a scale of 2.5 points per tenfold |
| Paper trading (futures, options and margin ÷ market cap, 0%: 10, 100%: 0) | 10 | no futures, options or margin on the exchanges read |
| Wallet support (wallets that hold it, 10 or more: 10) | 1 | its own node and wallet, counted as 1: no wallet in the site's directory lists it yet |
| Record | 7 | average of 3 criteria |
| Age (years since genesis) (Source) | 6 | 6 full years since 2020-01-17, the first day with a recorded price (genesis not yet researched, so the age can only be understated). |
| Development (work, fixes, vulnerabilities) | 6 | 3 positive, 1 negative, 3 not yet researched source |
| Positive | ||
| Steady work, 6 of 6 | ✓ | 761 commits in 12 of the last 12 months (github.com/hyle-team/zano); hyle-team/zano 2.2.3.603, 2026-10-05; 31 stable releases in 24 months. |
| Shipped a security fix in two years, +1 | ✓ | Zano v2.1.15.457, Feb 2026: security fixes in alt-block validation; v2.2.3.600, Sep 2026: emergency HF7 and rollback after an attack on coin and asset supply. |
| Exploit of the chain, 2026-08-29, flaw fixed (the security fix above) | ✓ | An attacker used a flaw in Gateway Addresses (added in Hard Fork 6) to mint about 36.9M unauthorised ZANO on 29 Aug and 25 Sep 2026, plus fUSD; the team restarted the chain from block 3,833,000, reversing about a month of transactions, and disabled gateway addresses. coinmarketcap.com github.com |
| Negative | ||
| Unfixed vulnerability, disclosed 2025-02-15, −1 | ✗ | Monero/epee CVE-2025-26819 (High) lets RPC clients exhaust node memory because HTTP server connections have no response size limit; Zano 2.2.3.608 still ships the older epee abstract_tcp_server2 with only a send-queue count limit and none of the ec74ff4 response limits added in Monero v0.18.4.0. github.com github.com github.com |
| Not yet researched | ||
| Shipped a privacy improvement in two years | – | |
| Shipped a scaling upgrade in two years | – | |
| Shipped a new capability for users in two years | – | |
| Conduct (origin, claims, halts) | 9 | 2 positive, 1 negative source |
| Positive record | ||
| Launched with a stated purpose, not as a joke | ✓ | |
| No claims by its founders that contradict its own design | ✓ | |
| Negative record | ||
| Halt, freeze or reversal, 2026-09-27 | ✗ | After a Gateway Address bug introduced in Hard Fork 6 let unauthorised ZANO and fUSD be issued, the core team released software restarting the chain from block 3,833,000 (26 Aug 2026), reversing about a month of transactions; exchanges paused deposits at the team's request. github.com crypto.news cointelegraph.com |
Ten sections, weighted equally, each 0 to 10: consensus (the two ladders), supply (the supply scale and a fixed cap that holds), distribution (premine, fundraising, developer share, holders), decentralisation (governance, no central team, who can mint, nodes), security, scalability, privacy, programmability (what the scripting layer can do beyond the whitepaper's payment system), demand, and record (age, development, conduct). They are built from the criteria in the second table: privacy, scalability, security and decentralisation are the Cryptocurrency Standards among them, as follows: privacy (the whitepaper's three checks a base of 7 of 10, three extra features up to 3 more), scalability (four measures and three features), security (pool diversity, network activity, hashrate, clients and two checks) and decentralisation (governance, no central team, who can mint, nodes, holders, premine, fundraising and developer share); programmability (token issuance, smart contracts and five checks) follows them, and supply and demand are two: the supply, scored against 21 million, and demand, the average of seven measures of the market and the wallets. Provisional: parts marked — are not yet measured and are left out of the average. A rating of structure and market depth, not a price forecast or investment advice. How the grade is built · Highest-graded cryptocurrencies.
Hybrid coins
Conflux 
Decred 
Abey 
Xphere 
Core 
Verus 
Elastos Proof of Work coins
Bitcoin BTCA+
Zcash ZECA+
Dogecoin DOGEA+
Monero XMRA+
Bitcoin Cash BCHA++
Litecoin LTCA+
Ethereum Classic ETCAAll Proof of Work chains →Supply
15,493,783 ZANO are in circulation, against no fixed cap — issuance has no defined end.
Launch and allocation
| Premine (allocated at launch) | 74.2% of today's supply |
|---|---|
| Sold by the issuer or insiders | 3.6% of today's supply |
| Developer share received since launch | 0% of today's supply |
| Developer share of new coins today | 0% |
| Fundraising | Private or venture funding |
At the 2019 launch 17.52M ZANO were reserved before mining: a 3.69M development premine (foundation 2.03M, team 1.11M, loan repayment 0.55M) and a 13.83M pool for a 1:1 coinswap from Boolberry, of which ~7.78M were claimed and the rest burned; 3.69M + 7.78M = 11.47M against ~15.47M current supply (CoinGecko).
No ICO/IEO/VC round. Boolberry shareholders lent development funds in early 2018; the loan was repaid with 553,500 ZANO from the premine.
There was no sale. The only coins delivered for money were the 553,500 ZANO from the premine used to repay Boolberry shareholders' 2018 development loan, effectively a pre-sale. 0.5535M / ~15.47M supply (CoinGecko) = 3.6%.
The 1 ZANO block reward goes to the PoW miner or PoS staker who produces the block, and fees are burned. There is no dev fee; the 3.69M development share was a launch premine.
Sources: docs.zano.org · coingecko.com · github.com · altfins.com · medium.com · medium.com. Researched 2026-10-24, low confidence.
The work behind it
Zano is secured by 229 GH/s of its own work. Hashrate does not compare across algorithms — a SHA-256 hash and a Scrypt hash cost different amounts to produce.
What a regulator has said
No SEC/CFTC determination — unclassified.
The regulator's position, reported as stated, not CoinSpectrum's. Assets nobody has ruled on are left unclassified rather than sorted by a guess.
How CoinSpectrum ranks Zano
Zano is #73 among cryptocurrencies and #402 in the market ranking, which lists wrapped coins, staked derivatives, stablecoins and tokens alongside them. CoinSpectrum counts an asset once, and counts only cryptocurrencies: assets with their own blockchain and their own consensus. A wrapped coin, a staked derivative or a stablecoin is a claim on something already counted; a token, memecoin or otherwise, runs on another chain's blocks. All of them are listed, each in its own section, and none is added to the total. The 329 places between Zano's two ranks are held by claims and tokens, not by other networks. The methodology sets out the rule and the counting rule argues for it.
The price above is the median of the exchanges the site reads live, checked every minute and cross-checked against a market snapshot (how market data is gathered). The grade is scored on published criteria, each with its source (the method). The site is independent, nothing on it is a paid placement, and its statements are signed (about CoinSpectrum, the manifesto).
See the 1 wrapped and staked claim on Zano →