Status as reported on November 10, 2026: A Zcash forum proposal, not an approved network upgrade. Community developer ValarDragon proposed a late-January 2027 target window for NU 8; that window was not a confirmed activation date.
The proposal combines a new Tachyon shielded pool, an increase in the maximum block size from 2 MB to 8 MB, and post-quantum security measures. ValarDragon’s proposed architecture targets roughly 200 shielded transactions per second. An 8 MB limit would be four times the current cap and about 2.67 times a previously proposed 3 MB limit, but the throughput target remains contingent on implementation.

Capacity remains contested. Core engineer str4d cautioned that specifications for out-of-band communication and private information retrieval used by light wallets had not been settled. Larger blocks could increase mobile light-client synchronization demands, as well as full-node processing and bandwidth requirements.
The proposed security and transaction changes include using ML-KEM in Tachyon, adding opcodes for 128-bit and 192-bit SPHINCS signatures, such as SLH-DSA, for transparent-address assets and uses including the Ironwood disaster-recovery path, and incorporating ZIP 248 to address transaction-format extensibility and hardware-wallet metadata fingerprints. These are proposed protections, not capabilities already deployed through NU 8.

ValarDragon also proposed ending mandatory Consensus Branch ID changes at each upgrade. str4d warned that a replacement replay-protection mechanism would be needed first. For the older Sapling pool, the proposal calls for a cutoff for new deposits while allowing existing users to transfer and withdraw; it does not specify a cutoff date in the report. It would also move a network sustainability mechanism (NSM) reallocation point to around Zcash’s seventh cumulative halving. The report estimates that this would defer the associated tail-issuance pressure by four to eight years.
As of the original report, the proposal was undergoing public technical discussion. Review of light-client specifications and replay protection, agreement on code, specification finalization and a community governance vote were still described as future steps—not completed decisions.

