Members of the Zcash community continue to debate how the network’s upcoming Ironwood upgrade will affect shielded users, with developers providing additional clarification on how funds will migrate from the existing Orchard pool to the new shielded pool.
The discussion follows the disclosure of the Orchard counterfeiting vulnerability earlier this year and the proposed remediation outlined in the Ironwood network upgrade. While developers have repeatedly stated that there is no evidence the vulnerability has been exploited, community members continue to raise questions about fairness, wallet support, migration timing, and potential user experience.
One community participant expressed concern that users could rush to migrate funds once Ironwood becomes available, potentially creating network congestion and higher transaction fees. The commenter suggested migration-specific fee reductions or temporary fee exemptions to avoid penalizing users seeking to secure their holdings.
Another participant proposed temporarily lifting Zcash’s 21 million supply accounting limit during the migration process to allow a more equitable conversion between the Orchard and Ironwood shielded pools.
Developers Explain Why Migration Is Designed as a First-Come Process
Responding to concerns, Zcash protocol developer Daira Hopwood confirmed that the migration behavior described in the proposed ZIP specifications is intentional.
According to Hopwood, the proposed “turnstile” mechanism allows only the valid amount of ZEC to migrate from Orchard into the new shielded pool. Because the protocol cannot determine legitimate ownership beyond consensus rules, the migration effectively operates on a first-come basis.
Related: Zcash Ecosystem Update Highlights Wallet, Infrastructure, and Grant Activity
Hopwood explained that this behavior is specified in the draft protocol because it is currently the only approach considered feasible to implement at the consensus level.
The design has prompted debate within the community because, in a hypothetical scenario where counterfeit funds existed, users migrating earlier would preserve more value than those migrating later. However, developers have consistently emphasized that no evidence currently indicates the vulnerability has ever been exploited.
Wallet Automation Expected to Simplify the Process
Questions also emerged about whether users would need to manually migrate their funds.
Zcash founder Zooko Wilcox responded that the migration experience will ultimately depend on individual wallet developers, although he believes wallets should automate the process wherever possible.
As an example, Wilcox highlighted a demonstration by Vizor Wallet and Valar Group, which successfully tested an automated migration workflow on the Ironwood testnet. In the demonstration, users simply scan a QR code using a hardware wallet, after which the wallet automatically prepares and gradually submits the required migration transactions in the background.
The demonstration suggests that many users may experience little manual interaction during the migration once supporting wallets implement the feature.
Related: Zcash Foundation Explores Privacy-Preserving Blockchain Use for Humanitarian Aid Delivery
The broader discussion reflects the complexity of upgrading privacy-focused blockchain infrastructure while maintaining consensus integrity. Ironwood is designed to eliminate risks associated with the Orchard vulnerability while preserving the network’s privacy guarantees, but developers continue to refine both the technical implementation and the user experience ahead of deployment.
Although debate continues over migration mechanics, the latest forum discussion indicates that development remains focused on minimizing disruption for users while ensuring the long-term security of the Zcash protocol.
