CoinSearcher

On-chain methodology, source charts, protocol analysis and valuation research

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

As reported on November 10, 2026, Zcash community developer ValarDragon had proposed a possible NU 8 network upgrade on the Zcash official forum, targeting late January 2027. It was a proposal under technical discussion, not an approved upgrade. Its central question is whether Zcash can increase shielded-transaction capacity while managing the bandwidth, privacy and security trade-offs that the changes introduce.

Capacity and the light-client constraint

The proposal calls for a new Tachyon shielded pool and an increase in the maximum block size from 2 MB to 8 MB. An earlier community ZIP draft had considered 3 MB. ValarDragon argued that underlying optimizations could support a direct move to 8 MB, with an estimated shielded-transaction throughput of 200 transactions per second if the proposed architecture is implemented. That figure is a projection, not a measured result.

An 8 MB limit would be four times the existing 2 MB limit and about 2.67 times the size contemplated in the 3 MB draft. Larger blocks would also require full nodes to process more data within each block interval. Core engineer str4d raised a related concern for mobile light clients: specifications for the out-of-band communication and private information retrieval (PIR) on which light wallets depend had not yet been settled. In that context, a higher block limit could increase synchronization bandwidth demands.

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

Proposed privacy and security changes

ValarDragon’s design describes Tachyon as using ML-KEM for post-quantum protection of shielded transaction privacy. The proposal’s aim is to prevent future quantum capabilities from exposing historical transaction relationships; the source does not establish that this protection has been implemented or independently validated.

For transparent addresses, the proposal calls for opcodes supporting 128-bit and 192-bit SPHINCS signatures, with SLH-DSA given as an example. These are intended to provide a post-quantum path for transparent assets that have not moved into a shielded pool and for scenarios such as the Ironwood disaster-recovery path.

The proposal also recommends incorporating ZIP 248 to make transaction formats more extensible and address metadata fingerprinting associated with hardware-wallet support for new shielded pools. It would end mandatory Consensus Branch ID changes at every upgrade to reduce wallet compatibility disruptions. str4d cautioned that the branch ID helps prevent transactions from being replayed across forks; an alternative replay defense would need to be established before removing that mechanism.

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

Migration and unresolved decisions

Rather than applying the hard freeze used for Sprout during NU 7, the proposal would set a point after which the Sapling pool accepts no new deposits while allowing existing users to transfer and withdraw funds. It also proposes moving a network sustainability mechanism (NSM) reallocation point to around Zcash’s seventh cumulative halving. Using a four-year halving interval, the source estimates that this would defer the associated tail-issuance pressure by four to eight years.

At the November 10 reporting date, the proposal remained in public technical discussion. PIR specifications and a replacement replay-protection mechanism were among the issues requiring review. Specification finalization and a community NU 8 governance vote were described as later steps, contingent on agreement over the code.

Further reading