Zcash’s scheduled Ironwood network upgrade is now set to activate on the mainnet on July 28, according to a statement from Zcash core developer Sean Bowe. The upgrade is designed to address an “infinity” bug tied to the Orchard shielded pool, a problem first disclosed in May and linked to the chain’s private transaction pool behavior.
Ironwood will close the current Orchard pool to new activity and establish a new shielded pool. Crucially, any funds moving out of Orchard would need to pass through an accounting checkpoint before they can enter Ironwood—an approach intended to generate evidence about whether any counterfeit Zcash tokens were produced via the Orchard issue.
Key takeaways
- Zcash core developer Sean Bowe says Ironwood mainnet activation is set for block height 3428143, approximately July 28 at 8:00 a.m. EST.
- Ironwood shuts down new entries to Orchard, forcing subsequent shielded activity into a newly created private pool.
- Withdrawals from Orchard must route through an accounting checkpoint before entering Ironwood, potentially surfacing traces tied to the earlier Orchard bug.
- The upgrade proceeds about a week later than a previously targeted July 21 activation date.
- Zcash reports that more than 80% of its 21 million ZEC maximum supply has already been issued, with a figure posted by ruZCASH showing 16,806,723 ZEC in circulation.
Ironwood activation locked in at a specific mainnet height
In a Thursday update, Bowe said the “Ironwood mainnet activation height has been set and tagged,” adding that major ecosystem organizations are committed to activating NU6.3 at block height 3428143. He described the expected time as approximately July 28 at 8 a.m. EST.
The activation timing matters for Zcash users and service providers because NU6.3 touches how shielded transactions are routed and accounted for. Exchanges, wallets, and other infrastructure operators typically need a predictable window to ensure compatibility—especially when a change involves closing one privacy pool and switching users to another.
How Ironwood changes Orchard and the pathway to the new pool
Ironwood was announced in June as the solution to an “infinity” bug that was identified earlier on Zcash’s Orchard shielded pool. The upgrade’s core operational change is straightforward: Orchard is closed to new activity, and a new private pool is brought online.
Rather than letting funds flow freely from the old shielded pool into the new one, the upgrade requires a checkpoint-based accounting step. Zcash’s design intent, as framed by Shielded Labs when discussing potential implications of Orchard-related activity, is that moving any potentially counterfeit funds through the migration process would force a decision point—either to attempt movement (and risk exposure) or to leave funds behind and risk losing the ability to move them later.
In other words, the checkpoint layer is meant to reduce the odds that problematic funds can move silently during the transition from Orchard to Ironwood.
Why a late-July timeline became a concern
Not everyone had been comfortable with the schedule. Shielded Labs previously floated the possibility of delaying Ironwood, warning that some parts of the ecosystem might not have enough time to prepare for a late-July mainnet activation. That concern included entities such as exchanges, mining pools, and wallet providers—groups that typically need to coordinate software support, operational procedures, and testing.
Bowe’s latest comment now confirms that Ironwood’s launch will occur about a week later than an earlier target date of July 21. The shift underscores how upgrades that alter transaction pathways in privacy systems are as much an infrastructure readiness challenge as they are a protocol change.
For Zcash participants, the practical takeaway is that readiness checks should be centered on the NU6.3 activation height window rather than assuming the previously announced July 21 date holds.
Orchard bug fallout and what investors have been watching
The Orchard vulnerability disclosure in early June had market repercussions. According to Cointelegraph’s earlier coverage of the event, ZEC fell sharply after the June 3 disclosure, dropping by roughly half—from $602.68 to $299.25—before partially recovering in the following weeks.
While token price reactions don’t prove whether a specific vulnerability was exploited, Ironwood’s design is still relevant to holders because it targets the mechanism of how private transactions transition from Orchard to the replacement pool. In this case, the upgrade is not merely cosmetic; it changes how migrated shielded funds are processed and accounted for, with potential forensic value if counterfeit activity ever occurred through the Orchard bug.
Beyond the security work, Zcash is also approaching a different kind of milestone. A post from ruZCASH on Monday stated that Zcash has now issued 16,806,723 ZEC out of a maximum 21 million supply—more than 80% of total issuance. This kind of supply progression matters for long-term stakeholders because it affects the rate at which new supply continues to enter circulation over time.
What to monitor as Ironwood goes live
As July 28 approaches, the most important watchpoints are whether NU6.3 activates cleanly at the announced height and how exchanges and wallets handle the Orchard-to-Ironwood transition operationally. Equally, ecosystem participants will likely focus on whether the accounting checkpoint mechanism delivers the evidence Shielded Labs described—particularly if there is any lingering uncertainty about Orchard’s “infinity” bug and its real-world impact.
https://www.cryptobreaking.com/zcash-schedules-ironwood-upgrade-for/?utm_source=blogger%20&utm_medium=social_auto&utm_campaign=Zcash%20Schedules%20Ironwood%20Upgrade%20for%20July%2028%20Launch%20
Comments
Post a Comment