SnifferCoin

Wallet custody, cryptographic trust boundaries, vulnerabilities, audits and practical defensive habits

Zcash NU 8 proposal raises wallet sync and recovery questions

For Zcash holders, a network upgrade can change more than transaction capacity: it can affect how easily a wallet syncs and how safely transactions work across forks. As reported on November 10, 2026, community developer ValarDragon had proposed an NU 8 upgrade for a target window in late January 2027. It was still a forum proposal, not an approved network change.

A larger block, with a light-wallet trade-off

The proposal would introduce a new Tachyon shielded pool and raise Zcash’s maximum block size from 2 MB to 8 MB—four times the current limit and about 2.67 times a previously proposed 3 MB limit. ValarDragon projected that the proposed architecture could support 200 shielded transactions per second. That figure is a goal, not a demonstrated network result.

Larger blocks would also 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 had not yet been settled. In str4d’s view, moving directly to 8 MB could make syncing more demanding for mobile light clients. For holders who rely on a phone wallet, that accessibility question matters alongside throughput.

Zcash NU 8 proposal raises wallet sync and recovery questions (1)

Proposed privacy and security changes

The proposed Tachyon pool would use ML-KEM. The report describes its intended design as protecting the privacy of past transaction relationships against future quantum attacks; that is a claim about the proposed design, not a protection already available to users.

For transparent addresses, ValarDragon also proposed opcodes supporting 128-bit and 192-bit SPHINCS signatures, such as SLH-DSA. The intended uses include assets that have not moved into a shielded pool and the Ironwood disaster-recovery path.

The proposal calls for adopting ZIP 248 to make transaction formats more extensible and address metadata fingerprints that could arise when hardware wallets sign transactions involving a new shielded pool. It also suggests ending mandatory Consensus Branch ID changes at every upgrade to reduce wallet compatibility disruptions. str4d cautioned that the branch identifier helps prevent transaction replay across forks; any removal would need an alternative replay defense.

Zcash NU 8 proposal raises wallet sync and recovery questions (2)

What remains undecided

Rather than freezing the Sapling pool, the proposal would set a point after which it could receive no new deposits while allowing existing users to transfer and withdraw. It would also shift a network sustainability mechanism redistribution point to around Zcash’s seventh cumulative halving. The November report estimated that this could defer tail-issuance pressure by four to eight years.

At the time of reporting, the proposal remained in public technical discussion. Private information retrieval specifications and a replacement replay defense still needed review. Specification work and an NU 8 community governance vote would follow only if participants reached agreement on the code. Holders should not treat any of these proposed wallet or protocol changes as active rules.