Deep Web3

SYSTEMS.
PEOPLE.
POSSIBILITIES.

Menu

Go beneath
the surface.

Zcash NU 8 proposal puts an 8 MB block limit and Tachyon shielded pool up for debate

As reported on November 10, 2026, Zcash community developer ValarDragon had proposed a potential NU 8 network upgrade on the Zcash forum, targeting a window in late January 2027. The proposal remained under public technical discussion—not an approved upgrade. It combined a new Tachyon shielded pool, a higher block-size limit and proposed post-quantum protections.

The throughput trade-off

ValarDragon proposed raising Zcash’s maximum block size from 2 MB to 8 MB, compared with an earlier 3 MB expansion draft. The proposed limit is four times the current one and roughly 2.67 times the draft limit. Alongside the proposed shielded-pool changes, the design targets an estimated 200 shielded transactions per second. That figure is a proposal target, not a measured result.

Larger blocks would also leave full nodes with more data to process per block. Core engineer str4d raised a separate concern for mobile light clients: specifications for the out-of-band communication and private information retrieval methods on which light wallets depend had not yet been settled. In str4d’s view, moving directly to 8 MB could increase their synchronization burden.

Zcash NU 8 proposal puts an 8 MB block limit and Tachyon shielded pool up for debate (1)

Privacy, signatures and transaction format

The proposal describes Tachyon as using ML-KEM ciphertext encapsulation to protect historical shielded transaction information against future quantum attacks. That is the proposal’s security claim; the reported discussion does not establish the protection as a verified outcome. For transparent addresses, it also proposes opcodes supporting 128-bit and 192-bit SPHINCS signatures, such as SLH-DSA, including for assets that have not moved into a shielded pool and the Ironwood disaster-recovery path.

ValarDragon also proposed integrating ZIP 248 to make the transaction format more extensible and address metadata fingerprints associated with hardware-wallet support for new shielded pools. Another proposed change would stop requiring a new Consensus Branch ID at every upgrade. Str4d cautioned that branch IDs protect against transactions being replayed across forks, so an alternative replay defense would be needed before removing that requirement.

Zcash NU 8 proposal puts an 8 MB block limit and Tachyon shielded pool up for debate (2)

Migration and remaining decisions

Rather than freezing Sapling, the proposal would set a point at which it stops accepting new deposits while allowing existing users to transfer and withdraw. It would also move a network sustainability mechanism reallocation point to around Zcash’s seventh cumulative halving; the original report characterized this as deferring tail-issuance pressure by four to eight years, based on a four-year halving interval.

At the November 10 reporting date, the proposal had not reached specification finalization or a NU 8 governance vote. Private information retrieval requirements and replacement replay protection were among the issues requiring technical review before those steps.