Skip to main content
Hashbeam

Crypto protocols, markets and policy

db094d

Zcash activates NU7 with 25-second block target

Zcash activated NU7 at block 3,543,405, moving its proof-of-work target from 75 to 25 seconds while resizing rewards and changing fee and shielded-transaction rules.

The Hashbeam Desk··3 min read

Zcash activates NU7 with 25-second block target

Zcash activated its NU7 network upgrade at mainnet block 3,543,405 on Nov. 5, changing the target block spacing from 75 seconds to 25 and revising issuance and transaction rules. The Block’s report on the activation says the subsidy per block was reduced by the same factor, while the number of blocks between halvings was tripled to preserve the existing halving schedule and 21 million ZEC supply cap.

The shorter interval is a consensus target, not a guarantee that blocks will arrive exactly 25 seconds apart. Under ZIP 218, the proof-of-work difficulty adjustment uses the new spacing after activation. Three times as many blocks can be produced per unit of time at the target rate, so the scheduled per-block subsidy is divided by three. ZIP 218 specifies that integer rounding makes issuance slightly lower over time than under the former schedule.

How does NU7 shorten block spacing without tripling issuance?

ZIP 218 changes the post-upgrade proof-of-work target spacing to 25 seconds and sets the post-NU7 halving interval to 5,040,000 blocks. The protocol applies the new spacing and halving interval to blocks at or above the NU7 activation height; before that height, the prior rules apply. Because the reward per block falls as blocks become more frequent, the intended ZEC issuance per day remains approximately the same, subject to the specification’s rounding effect.

ZIP 218 also introduces per-block limits on shielded-pool activity. Blocks may include at most 330 Orchard actions, 330 Ironwood actions and a combined 300 Sapling inputs and outputs; Sprout JoinSplits are set to zero. These limits constrain the work a block can impose on nodes and shielded-wallet syncing as block frequency rises. The proposal’s stated throughput estimate for Orchard increases from 2.9 to 6.6 transactions per second under its assumptions, while its modeled worst-case light-client sync bandwidth falls by 37%.

What happens to fees and old Sprout transactions?

NU7 activates the Network Sustainability Mechanism through ZIP 235 and ZIP 237. Under ZIP 235, consensus rules remove 60% of each block’s transaction fees from circulation and place them in a reserve; miners receive the remaining 40%. ZIP 237 specifies how reserve funds can later be reissued as an additional part of block rewards. The Zcash Foundation’s Zebra 7.0.0 release notes identify mainnet block 8,939,664 as the start of that reissuance. The scheduled subsidy and reserve reissuance are separate components of a block reward.

ZIP 2003 disables version 4 transactions at NU7 activation. Sprout transfers can only use version 4, so ZEC still held in the Sprout pool can no longer be spent under the activated rules. The Block reported that approximately 12,224 ZEC remained there at activation. ZIP 218’s no-Sprout-JoinSplit limit enforces the same boundary at the block level.

What must node operators change to follow the upgraded chain?

They had to run NU7-compatible node software before block 3,543,405. The Foundation said nodes that had not upgraded would follow a different chain, while Zebra 7.0.0 was its first stable release with NU7 mainnet support. After activation, NU7 nodes disconnect peers running older versions. The upgrade therefore changes which blocks a node accepts under consensus; it is not only a wallet or interface update.

References