A private ledger still needs auditors and exchanges. Zano’s history is the attempt to hide ordinary money flows without confusing secrecy with solvency, asset ownership or upgrade power.
Zano’s first mainnet block landed in May 2019. Lead developer Andrey Sabelnikov had written the original CryptoNote reference implementation, but this chain was built anew rather than copied from Monero.
That distinction shaped the ambition. Zano was not only another private coin: it aimed to make private staking, user-issued assets and commerce share one ledger.
Ring signatures hide which earlier output was actually spent. Stealth addresses create one-time destinations for recipients. Cryptographic commitments hide amounts, Bulletproofs+ proves those amounts lie within the permitted range, and blinded tags hide the asset type.
Those guarantees end at the chain boundary. A network observer can still correlate IP traffic, and wallet security can still fail. “Private by default” describes ledger fields, not every layer of a user’s life.
The original chain mixed proof of work and proof of stake. At HF4 block 2,555,000, Zarcanum let stake prove block eligibility without exposing its amount.
Mining did not disappear. ProgPowZ blocks and private PoS blocks still alternate, each with a one-ZANO base reward and no validator registry or minimum stake.
The 2026 Zenith paper proposes ending PoW and moving to pure private PoS. Its faster blocks and final emission allocation remained design work, so describing Zano as pure PoS today would turn a roadmap into history.
Confidential Assets inherit hidden addresses, amounts and asset types. Observers can verify conservation rules without learning which asset moved.
The issuer relationship remains. An asset owner can emit more up to the immutable maximum, burn, change allowed metadata and transfer ownership. A hidden stablecoin transfer proves neither its reserves nor redemption.
Native ZANO is different: it has no Confidential Asset owner key. Its supply changes through consensus rewards and fee burns rather than an issuer calling emit_asset.
Auditable wallets deliberately remove decoys and share a tracking seed, which is how the unlocked foundation fund can be inspected. The privacy system contains its own disclosure tool.
HF6 went further in August 2026. Gateway Addresses expose a service account’s asset and amount in exchange for simpler exchange and bridge integration; a transferable owner key controls that gateway.
Zano disclosed a 3.69 million premine for development and an initial loan. The fund is not locked, and the private ledger prevents a public holder-distribution table even though its auditable wallet offers a view.
Since 2025, stakers can signal through the PoS blocks they find. The first votes concerned whether assets appear in official wallets and Zano Trade, not consensus engineering.
Hyle Team, named as the website counterparty in its terms, stewards the technical roadmap and publishes hard-fork software. Node operators can adopt it, reject it or maintain a separate fork. The reviewed materials establish native ZANO transfers, fee payments and staking. They did not identify an instrument granting equity, issuer redemption, guaranteed income, foundation ownership or a claim on reserves backing third-party assets merely through holding ZANO. Rights attached to a separately issued asset must be assessed from that asset’s own terms.
A new CryptoNote-descended chain starts with hybrid consensus.
HF4 at block 2,555,000 brings private staking and assets.
The Core Team limits its scope to ecosystem-facing choices.
Stakers signal on first-party asset whitelisting.
The terms dated 12 February name Hyle Team as the website counterparty and describe the site as informational, without financial services.
Block 3,833,000 activates service-oriented Gateway Addresses.
Last evidence review: 2026-09-04
Zano is a native privacy-focused layer-one launched in 2019. Standard transactions conceal sender, recipient, amount and asset type; auditable wallets and HF6 Gateway Addresses expose selected data by design. The chain currently alternates ProgPowZ mining with Zarcanum private staking. ZANO pays fees, can stake and follows protocol issuance.
A transparent ledger reveals commercial relationships and balances, yet total opacity makes exchange, audit and bridge integration difficult. Zano tries to make private transfers the normal path while supplying explicit exits for auditors and services. That creates a second question: who controls each issued private asset and who decides protocol changes?
d/v-CLSAG rings obscure the spent output, stealth addresses create one-time destinations, blinded asset tags hide token type, and Bulletproofs+ proves hidden amounts remain in range. Zarcanum lets a staker prove eligibility without publishing stake value. PoW and PoS blocks alternate today. Confidential Asset owners retain issuance authority up to an immutable cap; native ZANO instead follows one-coin block rewards and fee burns.
Standard wallet transfers hide sender, receiver, amount and asset type. Network metadata such as IP is separate; auditable wallets omit decoys, and HF6 Gateway Addresses intentionally publish service balances and amounts.
Yes. The live chain alternates ProgPowZ PoW and Zarcanum PoS blocks. Zenith proposes pure PoS, but it was still under implementation at review.
Yes. Current staking has no validator registry, minimum stake or protocol lock. Rewards depend on finding PoS blocks, and operating a wallet exposes network metadata unless the user protects it.
No. Current PoW and PoS blocks each create a one-ZANO base reward, while transaction fees are burned. Net supply depends on issuance minus burns.
Its creator sets an immutable maximum and an owner key. That owner may authorize additional issuance up to the maximum and transfer ownership. Those powers are separate from native ZANO.
No. Current voting lets stakers signal on ecosystem matters such as wallet whitelists. The Core Team expressly retains engineering-roadmap stewardship, and hard forks take effect through compatible software adoption.
The reviewed materials establish native ZANO transfers, fee payments and staking. They did not identify an instrument granting equity, issuer redemption, guaranteed income, foundation ownership or a claim on reserves backing third-party assets merely through holding ZANO. Rights attached to a separately issued asset must be assessed from that asset’s own terms.
Choose a tracking site for Zano:
