Decentradge
Menu

Zcash NU 8 proposal targets a new shielded pool and 8 MB blocks

As reported on November 10, 2026, Zcash community developer ValarDragon had posted a proposal on the official Zcash forum for a potential NU 8 network upgrade, targeting late January 2027. It remained under public technical discussion, not an approved upgrade.

The proposal pairs a new Tachyon shielded pool with an increase in the maximum block size from 2 MB to 8 MB. ValarDragon projects that the proposed design could support 200 shielded transactions per second. That figure is a target, not measured network performance. The proposed block limit is four times the reported current limit and about 2.67 times a previously proposed 3 MB limit.

Capacity and light-client costs. Larger blocks would require full nodes to process more data within each block interval. Core engineer str4d objected that specifications for the out-of-band communication and private information retrieval used by light wallets were not yet settled. In str4d’s view, moving directly to 8 MB could increase mobile light-client synchronization demands, making bandwidth a significant trade-off against throughput.

Privacy and quantum-resistant designs. ValarDragon proposes using ML-KEM in the Tachyon shielded pool as part of a design intended to protect past transaction information against future quantum attacks. The proposal also calls for opcodes supporting 128-bit and 192-bit SPHINCS signatures, such as SLH-DSA, for transparent assets that have not moved into a shielded pool and for scenarios including the Ironwood disaster-recovery path. These are proposed defenses, not protections already deployed through NU 8.

Zcash NU 8 proposal targets a new shielded pool and 8 MB blocks

The proposal would incorporate ZIP 248 to make the transaction format more extensible. It aims to avoid metadata fingerprints that could arise when hardware wallets support an additional shielded pool. ValarDragon also suggests ending mandatory Consensus Branch ID changes at every upgrade to reduce wallet compatibility breaks. Str4d warned that the identifier protects against transaction replay across forks and said a replacement replay defense would be needed before removing that requirement.

For the existing Sapling pool, the proposal would set a point after which new deposits stop while allowing existing users to continue transfers and withdrawals. It also proposes moving a network sustainability mechanism redistribution point to around Zcash’s seventh halving; the original report estimated this could defer tail-issuance pressure by four to eight years.

The next steps described in the November 10 report were technical review—including the unresolved light-wallet specifications and replay protection—followed by specification work and a community NU 8 governance vote if code consensus is reached. None of those steps was described as complete.

Further reading