Zcash developers are weighing a network upgrade that could permanently strand funds held in the privacy coin's oldest shielded pool, raising fresh questions about how blockchains handle deprecated legacy systems.
What the NU7 Upgrade Proposes
The upcoming NU7 upgrade, slated for November, includes a proposal to disable version 4 transactions on the Zcash network. Because coins held in the legacy Sprout shielded pool rely on that transaction format to move, deactivating it would effectively render any remaining ZEC in Sprout unspendable.
Sprout was Zcash's original privacy technology, introduced when the project launched in 2016. It has since been superseded by the more efficient and secure Sapling shielded pool, and developers have long encouraged users to migrate their holdings away from the aging system.
Turning off version 4 transactions would leave any coins left in Sprout permanently locked, with no way to spend them.
The Case for Retiring Sprout
Supporters of the change argue that maintaining backward compatibility with obsolete transaction types imposes ongoing costs and complexity on the protocol. Cleaning up legacy code can reduce the surface area for bugs and streamline future development.
The amount of ZEC still sitting in the Sprout pool has dwindled substantially over the years as users moved to Sapling and later shielded systems. Anyone with funds remaining in Sprout would need to migrate before the upgrade takes effect to avoid losing access.
Key considerations for Zcash users include:
- Sprout is the network's original, now-deprecated privacy pool
- Migrating to Sapling or newer pools protects funds from being frozen
- The NU7 change is targeted for a November activation
What Happens Next
The proposal is still part of the broader NU7 discussion, and its final form could shift before deployment. For holders of legacy Sprout balances, the practical takeaway is clear: move funds out ahead of the upgrade or risk seeing them locked indefinitely.
The situation underscores a recurring tension in blockchain governance, where the drive to modernize a protocol can collide with the principle that users should never permanently lose access to their assets.