After Orchard The Ironwood Hard Fork of Zcash Already Receives Keystone Support

The Ironwood hard fork of Zcash is approaching, and Keystone does not want to miss the start. The hardware wallet maker announces compatible firmware from the first day of the network switchover, after the recent fix of a flaw in the Orchard pool. ZEC holders in self-custody now have a clear roadmap. 

Why Ironwood intervenes after the Orchard patch

The Orchard pool, which ensures transaction privacy on the Zcash network, had a vulnerability theoretically allowing the creation of counterfeit ZEC without immediate detection. The development team deployed an emergency patch to isolate the threat before it could be exploited, according to information published by Shielded Labs.

Ironwood comes to definitively seal this pool. The upgrade also restores users’ ability to independently verify the protocol’s issuance limits, a fundamental point for any privacy-focused crypto. This security fix also caused a spectacular rebound of ZEC by 17% in ten hours, with more than 13 million dollars of short positions liquidated.

Wallet and application providers must update their software before the network change to avoid any service interruption.

What Keystone is concretely preparing for ZEC users

Keystone confirmed that its next firmware update will be compatible with Ironwood from its release. ZEC holders in self-custody will then be able to migrate their protected funds from Orchard to Ironwood via the zodl app, once it is updated. The final schedule nonetheless depends on the availability of this application.

At the same time, Keystone’s Nexus app will receive several improvements: an updated consensus branch identifier, expanded support for TEX addresses used during transfers to exchanges, and the addition of T3 addresses dedicated to multi-signature wallets.

These additions prepare for smoother use of Zcash after Ironwood, especially for users interacting with exchanges requiring transparent transfers.

In sum, Keystone offers ZEC holders structured preparation for a complex network upgrade. Compatible firmware from day one, new address options in Nexus, secure migration via zodl: the three levers are identified. It remains to monitor the zodl app schedule and the exact date of the Ironwood hard fork to adjust the custody strategy. For privacy-focused cryptos, this type of transition is rarely trivial.