Josh Swihart Blocks Zcash (ZEC) Staking Upgrade Backed by Vitalik Buterin

Swihart's Veto on Crosslink

Whether Zcash (ZEC) should ever pay its holders to help secure the network is the question hanging over the project right now, and one of its most senior engineers has answered it with a flat no. Josh Swihart, founder of the Zcash Open Development Lab and former chief executive of the Electric Coin Company, has publicly rejected Crosslink, the staking design put forward by the independent team Shielded Labs, saying he does not believe it would benefit Zcash. His stance, made public on October 25, all but removes the prospect that a large staking upgrade wins adoption across the community. Crosslink is built as a compromise. New coin issuance would still come from the existing mining process, with a shielded staking layer added on top to blunt transaction reorganizations and hostile network attacks. To keep outside observers from picking stakers out of the shielded Orchard pool, deposits would be fixed to powers of ten: 1, 10, 100 or 1,000 ZEC. The design choice is deliberate, since a fixed-amount system keeps the staking layer as private as the rest of the Orchard pool. The proposal carries outside money and names behind it: Vitalik Buterin and the Winklevoss twins have backed the effort, with the stated aim of turning Zcash into a yield-bearing asset. Swihart judges the structural cost of that compromise too high. The extra layer, in his reading, burdens the protocol and introduces new critical vulnerabilities that are not worth the advertised benefit, and he has argued Zcash belongs on classical Nakamoto consensus. Zcash, a privacy chain built on zero-knowledge proofs, has otherwise kept its consensus rules close to the Bitcoin template since launch, which is why the clash has surfaced while attention on the ZEC price stays elevated but the dispute is about code rather than charts, and about a rewrite at the protocol's deepest layer.

The fight has history. Zcash developers first examined a move away from proof-of-work in 2021, five years after a launch-era Zcash ceremony that still shapes how the project talks about trust. Swihart, who had returned as chief executive of the Electric Coin Company at the time, stopped that review directly, calling the project a destructive distraction from the team's work on coin scaling. Shielded Labs later picked the effort back up, and Crosslink is the shape that revival has taken. The proposal now splits the ecosystem into two camps. One side holds the outside backers, Buterin and the Winklevoss twins among them, whose funding aims to make Zcash a yield-bearing asset. On the other side, security skepticism has grown inside Zcash's own core, and Swihart's refusal to bargain makes the point plainly: the broad agreement needed to rewrite the code does not exist at the moment. A change of this scale would reach the mainnet itself and amount, in practice, to a fork of the protocol's rules rather than an upgrade anyone can ship alone. The dispute lands during a stretch in which Zcash has drawn fresh institutional attention. Grayscale Research has argued ZEC is a mispriced currency sector asset, and Grayscale's Zcash ETF crossed $1 billion in assets within 30 days of launch, giving outsiders more exposure to the coin than at any earlier point in its history. Earlier in the quarter, derivatives data recorded $14 million in futures liquidations from ZEC longs before price rebounded, a sign that positioning around the coin already runs leveraged. Inflows do not decide consensus, though. That decision rests with Zcash's developers and its community, and right now they do not agree.

No Recorded Vote Fixes the Question

For all the noise, no on-chain vote record settles Crosslink. The governance trail carries no snapshot, no quorum figure and no recorded outcome; what exists is a proposal text and one prominent objection from inside the core. The upgrade moves forward only if Shielded Labs answers the vulnerabilities Swihart named, point by point, and rebuilds agreement among the developers who would have to implement it. If it cannot, mining continues and the yield case rests on inflows alone. The matter closes on the condition the record does not yet fix: a security case the core accepts.