Zecnero
Zecnero vs Zcash

What Zecnero changes, and what it keeps.

Zecnero (ZMR) is Zcash at NU6 with a fixed list of changes to proof of work, difficulty, issuance, network identity and chain selection. Everything else is Zcash, taken from the specification.

At a glance

Zecnero is Zcash at network upgrade NU6 with a short, fixed list of changes. The specification (§7) lists every one; this table covers the ones a user, miner or integrator will notice.

ZecneroZcash (NU6)
Proof of workRandomX-Zecnero: RandomX v1 settings, Argon2 salt ZecneroRX + 0x01. CPU-oriented.Equihash. GPU and ASIC mined.
Header141 bytes: the Zcash layout with an empty solution fieldCarries the Equihash solution
Difficultyaserti3-2d with a 1-hour half-life from network upgrade NU1: Mainnet from block 1, anchored at genesis. The testnet uses a 2-hour half-life until its network upgrade, then re-anchorsAverages 17 blocks with limited adjustment; Testnet minimum-difficulty rule
Subsidy6.25 ZMR from block 1, halving every 1,680,000 blocks, 30 halvings, 20,999,993.5652 ZMR totalSlow start and the Blossom adjustment (removed in Zecnero)
AllocationFounder stream: 3% of subsidy until the first halving, about 1.5% of all ZMRFounders’ Reward, funding streams and the development fund lockbox (all removed in Zecnero)
TimestampsAt most 2,700 s past the median of 11; 900 s into the future90 minutes; 2 hours
Reorganisation limit20 blocks, about 25 minutes100 blocks
TransactionsVersion 5 onlyVersions 4 and 5
Shielded poolsMainnet: Orchard. Testnet: Orchard from NU2, Sapling and Orchard before it. Sprout removedSprout, Sapling and Orchard
Orchard circuitThe corrected NU6.2 circuit from height 1The earlier circuit from NU5 until NU6.2
P2P port8733 (Testnet 18733)8233 (Testnet 18233)
RPC port8732 (Testnet 18732)8232 (Testnet 18232)
Branch ID0x02524D5A (“ZMR” + 0x02, network upgrade NU1) on Mainnet from block 1. The testnet uses 0x01524D5A (“ZMR” + 0x01) until its network upgrade. Network magic 7A 6D 72 D1Zcash’s own; differs from every Zecnero value
AddressesN1… and N3… (coinbase outputs only), nu1… (an Orchard receiver only); ns1… is defined, but no Mainnet transaction can pay it. Testnet nm…, n2…, ntestsapling1…, nutest1…t1…, t3…, zs1…, u1…
GenesisCommits to a recent Bitcoin block—

What was kept

  • All of the shielded cryptography. Sapling and Orchard keys, notes, commitments, nullifiers, note encryption, signatures and proofs are instantiated exactly as in Zcash, down to the Zcash domain-separation strings.
  • The Sapling parameters from Zcash’s multi-party ceremony, unchanged; only the testnet uses them, until NU2. Orchard’s Halo 2 needs none.
  • The node. zecnerod is Zebra with the changes above; everything the specification does not change follows Zcash.
  • The shape of issuance: about 21 million coins with a halving about every four years, then fees only.
  • Transparent addresses and scripts, as in Bitcoin and Zcash, for mining rewards. From network upgrade NU1 (Mainnet from block 1, the testnet from block 16,529) only a coinbase transaction may create a transparent output; every other output is shielded. Mined coins must be shielded before they are spent.

One consequence of keeping the cryptography: the same spending key produces the same shielded addresses on Zcash and on Zecnero. Use a separate seed, account or coin type for each network, or someone who sees both can link them. (Spec §3.1, §11.)

What was removed

  • Sprout, Zcash’s first shielded pool, with its JoinSplits and BCTV14 proofs. A new chain has no Sprout funds to support, and carrying the code adds risk.
  • Equihash and Zcash’s difficulty algorithm.
  • The Founders’ Reward, funding streams and development fund lockbox. The founder stream replaces them, at 3% instead.
  • The slow start: the full subsidy is paid from block 1.
  • Transaction versions 1 to 4, and rules that only exist to manage the transition into an upgrade Zecnero activates at height 1.
  • Zcash upgrades after NU6, NU6.1 and later, except the two NU6.2 security fixes below.

Orchard and Sapling

Orchard. The node verifies Orchard proofs only under the corrected circuit Zcash introduced at NU6.2, from height 1, and never enables the temporary rule Zcash used to switch Orchard off while that fix was prepared. On the testnet the wallet has had Orchard and unified addresses since block 16,529, and from the testnet’s network upgrade NU2 every shielded payment goes to Orchard.

Mainnet. Not yet launched. Mainnet has one shielded pool, Orchard: from block 1 no transaction, coinbase included, may have a Sapling spend or output, and a Mainnet unified address carries an Orchard receiver only. Mining rewards arrive at a transparent address and are shielded into Orchard before they can be spent. The testnet becomes Orchard only at its network upgrade NU2, expected on Sunday, November 8, 2026, at a height announced with the release. See the roadmap.

Why these changes

The goal is a launch in which ordinary computers compete on equal terms. RandomX has run Monero since 2019 and was audited before deployment; a private salt separates Zecnero from Monero’s hashrate without touching the audited design. A new chain sees sudden hashrate swings, which ASERT absorbs within hours where Zcash’s averaging window would leave blocks slow for a long time. The tighter timestamp bounds and the 20-block reorganisation limit follow from that choice. The full reasoning is in §9 of the specification.