The height—not the date—activates NU7

ZIP 259 sets Zcash NU7’s mainnet activation at block 3,543,405. Project communications estimate that height will arrive around 5 November, but block production varies. A calendar estimate can move; the consensus height is the binding trigger.

The upgrade was tested on Zcash testnet before mainnet. Zebra 7.0.0 is the Zcash Foundation’s first stable Zebra release with NU7 mainnet support. Operators who remain on software without NU7 rules risk following an incompatible pre-upgrade chain.

What changes

NU7 reduces target block spacing from 75 seconds to 25 seconds. The protocol adjusts the reward per block and halving intervals so blocks arrive more frequently without raising the 21 million ZEC supply cap. Faster blocks can reduce time to confirmations, although exchanges and wallets decide their own deposit-crediting policies.

The upgrade also introduces the Network Sustainability Mechanism. Under the specification, 60% of transaction fees are removed from circulation into a public consensus balance, while miners retain 40%. Scheduled reissuance from that balance begins later, at mainnet height 8,939,664. This changes the timing of fee circulation, not the maximum supply.

Per-block limits on shielded actions are intended to bound validation and light-wallet sync costs as blocks become more frequent. NU7 does not introduce a new transaction format, but it makes version 4 transactions invalid.

Who needs to act now

Node operators, miners, indexers and block explorers: confirm that every production component supports NU7 before the activation height. Zebra’s stable 7.0.0 release includes the rules, but operators should follow the current release notes for their own implementation rather than assuming every older client is compatible.

People with Sprout funds: move them before activation. Sprout transfers rely on version 4 transactions; once NU7 rejects that transaction version, funds remaining in the Sprout pool become unspendable. This is the clearest hard deadline in the upgrade.

Ordinary wallet and exchange users: no protocol migration is advertised for modern transaction formats, but service providers may pause deposits and withdrawals around the fork. Check the provider’s official status page and never follow an unsolicited “upgrade,” “migration” or wallet-connect link.

Risks and unknowns

A coordinated network upgrade can expose software or integration failures even after testnet use. The Zcash Foundation says Zebra 7.0.0 fixed seven security issues and a testnet problem involving competing branches, which is useful evidence of testing but not a guarantee of flawless activation.

The precise activation time remains unknown until the chain approaches the specified height. Confirmation speed for an end user will also depend on wallet behaviour, exchange policy and actual block production. No responsible source can promise a price effect from the upgrade.

What to watch next

The first confirmation is the mainnet chain reaching height 3,543,405 under NU7 rules. After that, watch node and explorer agreement, exchange status pages and any release notes from Zebra or other supported clients. A successful activation means consensus participants follow the same chain; it does not by itself validate every wallet, custodian or market integration.

PRIMARY EVIDENCE

Documents you can open

01
Zcash Foundation — Zebra 7.0.0Stable NU7 support, operator guidance and implementation details.
OPEN ↗
02
ZIP 259 — NU7 deploymentActivation height and the consensus changes included in NU7.
OPEN ↗
03
Zcash network upgrade pageProject-maintained upgrade overview and status.
OPEN ↗
04
CoinDesk — independent corroborationReporting on the activation decision, faster blocks and Sprout cutoff.
OPEN ↗
Safety note

This report does not link to a wallet migration or claim page. Use only the official documentation for your client or wallet, verify software signatures where provided, and never disclose a seed phrase.