Zcash's NU7 upgrade contains one clause that settles a decade-old argument about what a private key actually controls. Under the proposal, ZEC held in the legacy Sprout shielded pool would become unspendable. Not because the keys are lost. Because the protocol would stop recognizing them.
The key stays valid. The balance stays visible. The transaction does not settle.
Trust is a bug, not a feature. Here is the balance sheet.
I have read the coverage of this proposal four times, and every pass returns the same structural finding. A network upgrade is being framed as maintenance while its actual function is to reclassify a class of user assets as inert. There is no ZIP number attached to the reporting. No freeze mechanism is described. No figure is given for how much ZEC sits in Sprout today. Three variables, all absent, and one of them decides whether this is housekeeping or confiscation. That absence is not a reporting failure. It is the state of the information, and it should govern how anyone prices this.
Context: a pool that was always on a clock
Sprout was Zcash's first shielded pool. It shipped in 2016 on an early zk-SNARK construction that required a trusted setup ceremony. Participants generated public parameters and were expected to destroy the randomness behind them. If any single participant retained that randomness โ the toxic waste โ they could forge proofs without holding the underlying funds. The ceremony was elaborate. The assumption was social, not mathematical.
Sapling replaced Sprout in 2018. Orchard replaced Sapling in 2022, and Orchard's Halo 2 proving system removed the trusted setup requirement entirely. Sprout has been legacy infrastructure for four years. Every pool retirement discussion since 2018 has pointed at the same conclusion: the oldest pool closes eventually.
NU7 is the seventh network upgrade package. Packages bundle multiple ZIPs, and the governance path runs through the ZIP editors, Electric Coin Company, and the Zcash Foundation rather than an on-chain token vote. Activation height is undecided. That detail matters more than the headline. The freeze is not live. It is a proposal with a direction of travel.
The word 'planned' in the coverage is doing quiet work. Freezes of this kind are not improvised. They follow a pool lifecycle schedule that has existed for years. If the deadline arrives, it will arrive on a timetable that was visible to anyone who read the specifications.
Core: three implementation paths, three different liabilities
The reporting does not describe how the freeze would be enforced. That gap is the entire analysis, because the plausible implementations differ enormously in reversibility.
Path one: reject validity proofs against the legacy commitment tree root. Path two: reject transactions that reference old anchors. Path three: mark the legacy pool balance unspendable at the consensus layer.
Paths one and two are verification filters. They can be reversed by a later upgrade, because the notes still exist in state. Path three is a state edit. It does not filter. It reclassifies. Reversing a state edit requires a second state edit, and the second edit has to decide what the balance is worth and to whom. That is the difference between a locked door and a demolished room.
Based on my audit experience, this is where teams systematically understate their own exposure. In 2018 I reviewed the 0x Protocol v2 exchange contracts and found three logic flaws in the signature verification path that earlier reviewers had passed. The pattern held across all three: a check that executed correctly but did not constrain the thing it appeared to constrain. The failure was never arithmetic. It was the assumption that a passing check implied a bounded outcome.
NU7 inverts that pattern. Here the check is the constraint. Signature verification returns true. Balance lookup returns true. Spendability returns false. Nothing is broken. Everything works. The funds simply cannot move.
A private key becomes a necessary condition, not a sufficient one. That sentence is the entire event. Pool state becomes an antecedent to spendability, and the key drops one tier in the hierarchy of control. Every custody model, every backup procedure, every 'not your keys' heuristic in this industry assumes sufficiency. NU7 would demonstrate on mainnet that the assumption is false.
The economic consequences cut two ways, and I am confident about direction while holding no confidence at all about magnitude.
Direction one: permanent lockup is supply contraction. ZEC in Sprout stops circulating. If the pool holds a meaningful balance, that is deflationary by construction, and the reflexive read is bullish.
Direction two: the same action destroys the monetary premium. An asset a protocol can reclassify is not a store of value. It is a claim on a governance process. Holders who internalize that will demand a discount, and the discount persists after the freeze because the precedent does.
The ledger does not lie, only the interpreters do. The chain will show exactly how much ZEC was locked, at which block, in which notes. The market will then decide whether the number was small enough to ignore.
Here is what the coverage misses. Rational Sprout holders will not wait for activation. They will migrate to Orchard before the activation height, because migration costs a transaction fee and non-migration costs total loss of disposal rights. A freeze with a known date is a deadline. Deadlines produce runs. That migration wave will not show up in price. It will show up in shielded pool composition, and it will happen before the news cycle catches up.
Then there is the downstream layer. Custodians and exchanges holding Sprout balances will have to display a number that cannot be withdrawn. That starts as an interface problem. It becomes a solvency disclosure the first time a customer asks why the balance on screen is not the balance they can move.
History repeats, but the gas fees change. In 2022 I reverse-engineered the UST de-pegging sequence and traced it to Anchor risk parameters that were presented as tuning knobs and functioned as solvency triggers. The mechanism was technical. The consequence was a balance sheet. NU7 has the same shape at smaller scale: a parameter decision, presented as protocol hygiene, with a balance sheet attached.
Contrarian: the bulls are right about the pool, wrong about the lesson
The charitable read deserves a fair hearing, and it is stronger than the market will grant.
Sprout's trusted setup is a live liability. If any ceremony participant retained toxic waste, they could forge proofs against the pool. Sprout balances therefore already carry a cryptographic asterisk no auditor can remove. The pool is not merely old. It is unverifiable in the way that matters. From that angle, freezing is not confiscation. It is an admission โ the protocol stating, in the only language it has, that a class of notes was never as sound as the marketing implied. Retiring it also removes a verification branch from the proving path, and complexity hides risk. The pool was already impaired. NU7 makes the impairment legible. Legibility is unpleasant, but it beats a silent assumption.
Where the bulls err is the lesson they draw. Retiring a compromised pool is defensible. Establishing that protocol upgrades can void spendability is a different act, and it carries no sunset clause. Code is law; intent is irrelevant. The intent here may be hygiene. The code will say what the code says.
Takeaway: the checklist nobody ran
Three questions decide whether NU7 is maintenance or expropriation, and none are answered in the current reporting. How many ZEC sit in Sprout today? Which of the three enforcement paths does the ZIP specify? What is the activation height? Until those are answered, the correct posture is neither panic nor accumulation. It is documentation.
Compliance checklist: ZIP identifier published โ no. Freeze mechanism specified โ no. Audit status disclosed โ no. Peer review referenced โ no. Affected balance quantified โ no. Migration window defined โ no. Six boxes. Zero checked. That is the finding.
The next pool to be retired is somebody's current pool. The only open question is whether the Sprout precedent turns that retirement into a schedule, or an event.