Block Matrix
Menu

Zcash NU 8 proposal pairs a larger block limit with a new shielded pool

On November 10, 2026, Zcash community developer ValarDragon posted a proposal for the NU 8 network upgrade on Zcash’s official forum. It targeted late January 2027, but remained under public technical discussion—not an approved upgrade.

The proposal would introduce a Tachyon shielded pool and raise the maximum block size from 2 MB to 8 MB. ValarDragon projected that the proposed architecture could support 200 shielded transactions per second. That figure is a target, not measured network throughput. An earlier draft ZIP had proposed a 3 MB limit.

Zcash NU 8 proposal pairs a larger block limit with a new shielded pool (1)

The capacity trade-off is data handling. An 8 MB limit is four times the current 2 MB limit and about 2.67 times the earlier 3 MB proposal. Full nodes would have more data to process within each block interval. Core engineer str4d objected that specifications for out-of-band communication and private information retrieval used by light wallets were not yet settled, and warned that larger blocks could increase mobile light-client synchronization demands.

For transaction privacy, the proposal calls for Tachyon to use ML-KEM. The source describes this as protection against future quantum attacks that might expose historical transaction relationships; that remains a proposed security claim, not an observed property of a deployed pool. For transparent addresses, ValarDragon proposed opcodes supporting 128-bit and 192-bit SPHINCS signatures, such as SLH-DSA, including for assets not moved into a shielded pool and the Ironwood disaster-recovery path.

Zcash NU 8 proposal pairs a larger block limit with a new shielded pool (2)

The proposed transaction-format changes include ZIP 248, intended to reduce hardware-wallet metadata fingerprints when new shielded pools are added. ValarDragon also suggested ending mandatory Consensus Branch ID changes at every upgrade. Str4d cautioned that the identifier helps prevent transactions from being replayed across forks and that a replacement safeguard would be needed first.

Under the proposal, Sapling would stop accepting new deposits at a specified point while existing users could still transfer and withdraw funds. It would also move a network sustainability mechanism redistribution point to around Zcash’s seventh halving; the source estimates this would defer tail-issuance pressure by four to eight years. As of the November 10 report, technical review—including light-wallet specifications and replay protection—still lay ahead of any finalized specification or NU 8 governance vote.