The Final Sunset of Zcash’s Legacy Sprout Pool
The Zcash network is approaching a pivotal technical milestone with the proposed Network Upgrade 7 (NU7), which marks the definitive retirement of its oldest privacy pool, Sprout. This upgrade aims to streamline the protocol by disabling legacy transaction formats, a move that would effectively lock any funds remaining in the Sprout pool unless holders migrate them before the activation deadline. As of mid-October, over 22,000 ZEC remain in this legacy environment, facing a permanent loss of mobility if the community moves forward with the scheduled transition.
Technical Necessity and the End of Version 4 Transactions
The core of the NU7 upgrade lies in ZIP 2003, a proposal that mandates the rejection of version 4 transactions. Because Sprout transfers rely exclusively on this aging format—which is not supported by the more modern version 5 or 6 transaction structures—the upgrade would remove the network's ability to process Sprout spends. This decision is driven by a desire to reduce the "complexity burden" on the Zcash ecosystem. Maintaining the specialized verification requirements for Sprout adds significant work to transaction processing and creates potential denial-of-service (DoS) vulnerabilities, despite the pool seeing very little active use in recent years.
Migration Challenges and the Path to Modern Pools
For holders still localized in the Sprout pool, the path to preservation involves migrating assets to the newer Sapling pool. This process is not as simple as updating a wallet; it often requires specialized recovery tools like Argos to scan the blockchain and reconstruct necessary data, a task that can take days of processing. Furthermore, migration carries a distinct privacy trade-off. Under the ZIP 308 migration design, funds moving from Sprout to Sapling must pass through public pool accounting, which exposes the transaction amounts even if the addresses remain shielded.
Final Decisions and Activation Timeline
The Zcash community is currently in a critical observation phase, with the NU7 upgrade already successfully passing activation on the testnet. A final decision regarding the mainnet activation height is expected on October 20, with a target implementation date set for early November. This timeline serves as a final warning for legacy holders: once the upgrade goes live at a specific block height, the authority granted by a Sprout private key will no longer be recognized by the network. This shift emphasizes a broader commitment to protocol efficiency, favoring a lean, modern infrastructure over the preservation of legacy compatibility.
