Zcash entered a new market phase after trading began for ZCSH on August 25, following a May 29 disclosure of an Orchard shield protocol vulnerability and the July 28 activation of the Ironwood NU6.3 upgrade designed to introduce a new shield pool while limiting the existing Orchard pool.

The sequence began on May 29, when security researcher Taylor Hornby reported a soundness vulnerability in Zcash’s Orchard shield protocol. According to the community statement cited in the original report, there was no evidence that the issue had been exploited in practice.

Zcash then activated the Ironwood NU6.3 upgrade on July 28 at block height 3,428,143. The upgrade was intended to introduce a new shield pool and place limits on the existing Orchard pool, making the network transition the core technical step between the vulnerability disclosure and the later product launch.

On August 25, Grayscale began trading ZCSH, described in the original report as an exchange-traded product that provides exposure to Zcash’s spot price. The report said the launch was followed by net inflows of $34.4 million. It also said Zcash reached $1,023 on September 4, though the broader article focus is on the product launch and protocol transition rather than market pricing.

The same report said that, as of September 7, 2026, about 4.876 million of the 16.92 million ZEC issued were in the shield pool, based on JetStats data, for a shielded share of 28.8% of supply. It also cited CoinDesk research saying shielded transactions accounted for 59.3% of Zcash transactions in February 2026. Zcash uses an optional privacy model, allowing both shielded and transparent transactions, so adoption of shielded usage remains a live measure of how much privacy capacity is actually being used.

Why It Matters

This development brings together three issues that rarely align cleanly in crypto: privacy-preserving infrastructure, a disclosed protocol vulnerability, and a listed product aimed at institutional access. For Zcash, the significance is not just that a new product started trading, but that it did so after the network moved to contain a sensitive shielded-pool issue.

More broadly, the episode highlights a recurring test for privacy-focused crypto networks: technical privacy features alone are not enough. Their relevance depends on post-upgrade user migration, continued confidence in supply integrity, and whether institutional access products can expand participation without weakening the project’s core privacy proposition.