Zcash NU 8 proposal compares an 8MB block limit with lighter-client demands

As reported on November 10, 2026, Zcash community developer ValarDragon had proposed a possible NU 8 network upgrade for a late-January 2027 target window. It was still under public technical discussion, not an approved upgrade. The proposal combines a new shielded pool, a larger block limit and changes intended to address quantum-computing risks.

Zcash NU 8 proposal compares an 8MB block limit with lighter-client demands (1)

Throughput versus synchronization

The proposed 8MB maximum block size is four times Zcash’s existing 2MB limit and about 2.67 times the limit in an earlier 3MB draft. ValarDragon’s proposed Tachyon shielded pool and other optimizations are intended to support an estimated 200 shielded transactions per second if implemented; that figure is a target, not a measured outcome.

The trade-off is more data for full nodes to process within each block window and potentially greater synchronization demands for mobile light clients. Core engineer str4d objected that specifications for the out-of-band communication and private information retrieval used by light wallets were not yet settled. Those requirements remain part of the case for—or against—moving directly to 8MB.

Zcash NU 8 proposal compares an 8MB block limit with lighter-client demands (2)

Proposed security and pool changes

Tachyon would use ML-KEM ciphertext encapsulation as part of the proposal’s post-quantum privacy design. For transparent addresses, the proposal calls for opcodes supporting 128-bit and 192-bit SPHINCS signatures, such as SLH-DSA, including for assets that have not moved to a shielded pool and for scenarios such as the Ironwood disaster-recovery path. These are proposed protections, not features already deployed.

The proposal also calls for adopting ZIP 248 to make transaction formats more extensible and address metadata fingerprints that can arise when hardware wallets support a new shielded pool. ValarDragon proposed ending mandatory Consensus Branch ID changes at every upgrade to reduce wallet compatibility disruptions. Str4d cautioned that the identifier protects against transaction replay across forks and that a replacement safeguard would be needed first.

Unlike the hard freeze applied to Sprout during NU 7, the proposed Sapling transition would set a point after which new deposits stop while existing users could still transfer and withdraw. It would also move a network sustainability mechanism (NSM) reallocation point to around Zcash’s seventh cumulative halving; the original report estimated that this would defer tail-issuance pressure by four to eight years.

Technical review of the light-client requirements and replay protection remained ahead. The proposal would proceed to finalized specifications and an NU 8 community governance vote only after agreement on the code.