bf7666
Zcash activates NU7 with 25-second block target
Zcash activated NU7 at block 3,543,405, targeting 25-second blocks while capping shielded activity and redirecting fees to future mining rewards.
The Hashbeam Desk··3 min read

Zcash activated its NU7 network upgrade at block 3,543,405 on Nov. 6, introducing a 25-second target block interval and changes to shielded transaction limits and fee allocation. The shorter target is intended to reduce the average wait for a first confirmation, though it does not guarantee that payments will be accepted sooner by exchanges or other services. The CoinDesk report on NU7’s activation says the block was mined at 02:34 UTC; by 04:59 UTC, the next 225 blocks had averaged about 39 seconds apart as mining difficulty adjusted.
The upgrade also changes consensus rules for block spacing, shielded activity, transaction versions and fees. The Zcash Foundation’s Zebra 7.0.0 release notes warn node operators to upgrade before activation: older nodes follow a different chain after NU7, while upgraded nodes disconnect peers running older versions.
How does NU7 shorten the wait for a confirmation?
ZIP 218 reduces the target spacing between blocks from 75 seconds to 25. A transaction included in a block can therefore receive its first confirmation sooner on average, but the target interval is not a promise that every block will arrive exactly 25 seconds later. CoinDesk reported the early post-activation average at about 39 seconds, while difficulty adjusted toward the new pace. Each exchange or service sets its own confirmation requirements, so the time before it credits or releases funds can differ from the block interval.
To keep issuance per unit of time unchanged, ZIP 218 divides the per-block subsidy by three, triples the remaining halving intervals and adjusts funding-stream periods. The upgrade therefore increases the frequency of blocks without tripling the amount of ZEC issued each day.
What limits and fee rules change under NU7?
NU7 sets per-block limits on Orchard, Ironwood and Sapling activity, and permits no new Sprout JoinSplits. Wallets scan the blockchain for payments addressed to them; limiting shielded activity constrains how much data a transaction flood can force light wallets to download. The Foundation says the limits more than double Orchard throughput, from 2.9 to 6.6 transactions per second, while reducing the worst-case sync bandwidth a spammer could impose by about 37%. Zebra applies the limits when admitting transactions to its mempool and when building block templates, rejecting oversized activity before it enters a block.
ZIP 235 sends 60% of each block’s transaction fees to a reserve and leaves 40% for miners. Under ZIP 237, a predictable portion of that reserve will later be reissued on top of normal block rewards; the Foundation’s release notes give mainnet height 8,939,664 as the start. They say the four-year halving schedule and 21 million ZEC supply cap remain unchanged.
Which older Zcash funds can no longer be spent?
NU7 makes version 4 transactions invalid under ZIP 2003 and ZIP 259; version 5 and version 6 transactions remain valid. Sprout transfers can only use version 4, so ZEC still held in the original Sprout pool becomes unspendable after activation. CoinDesk puts the stranded amount at about 12,224 ZEC and reports that no recovery mechanism had been approved as of its report. That is a direct cost of retiring the old transaction path, separate from the faster block target: users and services that needed to move Sprout funds had to do so before the new consensus rules took effect.
References
- CoinDesk report on NU7’s activation — coindesk.com
- Zebra 7.0.0 release notes — forum.zcashcommunity.com