Sunday 4 October 2026
Afternoon EditionRSS
ZOTPAPER

News without the noise

ZOTPAPER
Crypto

Zcash's NU7 Upgrade May Render Sprout Pool Funds Unspendable

Proposed network upgrade would disable legacy transaction format, freezing ZEC in the older shielded pool

By LineZotpaper
Published
Read Time2 min
Zcash users holding ZEC in the network's legacy Sprout shielded pool are being urged to move their funds before a planned network upgrade in November, or risk losing the ability to spend them. The change, proposed under Zcash Improvement Proposal-2003 and part of the NU7 upgrade, would stop accepting version 4 transactions, which are required to spend Sprout funds.

According to the proposal, the NU7 upgrade would disable the older transaction format that allows users to spend funds from the Sprout shielded pool. Any ZEC remaining in the pool after the upgrade would become unspendable under the new network rules.

The proposal explicitly states that it would not burn the Sprout funds, and it leaves open the possibility of restoring access later. However, it warns that holders may never be able to spend funds left in the pool.

The issue has sparked discussion among Zcash users. A user posting as "vaspholdings" on the Zcash Community Forum raised concerns about the potential loss of funds, according to a forum thread. The developers behind ZIP-2003 have framed the change as a necessary clean-up of legacy infrastructure, as the Sprout pool has been superseded by newer shielded pools with stronger privacy guarantees.

Zcash, a privacy-focused cryptocurrency, originally launched with the Sprout protocol in 2016. It was later replaced by the Sapling upgrade, which offered more efficient and secure shielded transactions. Funds have not been minted into Sprout for years, but some ZEC still remains in the pool from early users who never migrated.

The NU7 upgrade is part of the network's regular development cycle, and the proposal is currently under community review before a final decision to activate it in November.

§

Analysis

Why This Matters

  • ZEC holders who still have funds in the Sprout pool face a real risk of losing access if they do not migrate before the upgrade.
  • The upgrade highlights the ongoing tension in cryptocurrency networks between backward compatibility and protocol improvement.
  • If the upgrade proceeds, it could set a precedent for how other privacy coins handle legacy privacy pools.

Background

Zcash launched in 2016 with the Sprout shielded protocol, which provided strong privacy but was complex and resource-intensive. The 2018 Sapling upgrade introduced a more efficient shielded pool, and most users migrated away from Sprout. Over time, the Sprout pool has become nearly empty, but a small amount of ZEC remains from addresses that may have lost keys or been forgotten. The NU7 upgrade, specifically ZIP-2003, aims to simplify the network by removing support for the older Sprout transaction format, which is no longer actively used but still requires maintenance.

Key Perspectives

Zcash developers (ZIP-2003 authors): The change is a clean-up of obsolete code that reduces the network's attack surface and maintenance burden. They argue that ample warning has been given for users to migrate. ZEC holders with Sprout funds: These users may face unexpected loss of funds if they are unaware of the deadline or have lost access to their wallets. Some in the community have called for additional safeguards or a longer transition period. Critics/Skeptics: Some community members worry about the centralization risk of protocol changes rendering funds unspendable, and question whether the possibility of later restoration is sufficient assurance.

What to Watch

  • Whether the NU7 upgrade receives final approval and the activation date is confirmed.
  • Volume of ZEC migrated out of the Sprout pool ahead of the deadline.
  • Any proposals or mechanisms introduced to restore access to Sprout funds after the upgrade.

Sources

Zotpaper

Written by software from the reporting listed above, scored by an automated standards desk, and published without a person reading it first. If something here is wrong, tell the editor and it will be put right.

How we workReport an errorSubscribe