Expanding Zcash in Unstoppable Wallet: Liquidity, Swaps & Distribution (Retroactive Grant)

[Dadybayo]

Hi everyone! We’ve submitted a new retroactive grant proposal for Unstoppable Wallet and wanted to share the details with the community. This proposal builds on our previous work and focuses on expanding Zcash from a usable asset inside the wallet into something that can be actively used across liquidity networks and multiple environments.

Unstoppable Wallet has been a long-term contributor to the Zcash ecosystem, focusing on practical usability, privacy, and non-custodial design.

Key contributions include:

• One of the first multi-coin wallets to support ZEC, expanding access beyond single-asset wallets

• First wallet to introduce shielded-only mode, encouraging use of the privacy pool

• First ZEC wallet to implement duress mode - designed for real-world coercion scenarios

These contributions were driven by real-world constraints, not just technical requirements.

We’ve consistently focused on:

• reducing friction in shielded usage

• improving reliability of non-custodial wallets

• designing for realistic threat models

• maintaining interoperability by avoiding non-standard implementations

This work continues in our latest updates. Over the past months, we focused on making ZEC more usable in real-world flows not just inside the wallet, but across different environments.

• Expanded liquidity access (DEX + RFQ)

• Enabled cross-chain swaps

• Introduced risk-aware routing (provider classification)

• Launched additional access points (web + bots)

We’re already seeing growing usage including $1.5M+ in ZEC swap volume in April alone.

Retroactive Grant Application - Unstoppable Wallet

Happy to answer questions or go deeper into any part

[Dadybayo]

Hi folks! Since the original proposal was submitted for the Q2 round, we continued working on Zcash and completed another substantial set of improvements.

As the Q2 vote was moved to Q3, we have now updated our grant application to include this additional completed work.

Since the original submission, we:

• Migrated the Zcash integration to the official Zcash SDK stack

• Continued updating Zcash SDK dependencies

• Added the ability to select a Zcash server on Android and iOS

• Added Zcash transaction resend functionality

• Added support for shielded Zcash swaps through supported liquidity providers

• Completed and released NU6.3 / Ironwood support.

The Ironwood implementation in particular was considerably more than an SDK update.

We added Ironwood balance accounting, detection of remaining Orchard funds, a dedicated migration-required state, migration confirmation and fee handling, transaction signing and execution, migration transaction tracking, and dedicated transaction-history classification.

We also handled several important edge cases around synchronization, available Orchard balances, balance privacy, and transaction re-scanning.

As official upstream Ironwood support became available, the implementation was moved to the official Zcash SDK migration flow using proposeOrchardToIronwoodMigration.

This allowed Unstoppable Wallet to remain compatible through the NU6.3 transition and gives Android users with remaining Orchard funds a native path to migrate them into Ironwood.

Given the additional Zcash-specific engineering completed between the original submission and July, we have:

• Extended the covered work period through July 2026

• Updated the proposal with the new completed work and proof of completion

• Increased the requested retroactive grant amount from $50,000 to $80,000

The broader goal remains the same: we want Zcash to be more than simply another supported asset inside Unstoppable Wallet.

We continue investing in ZEC liquidity, shielded usability, cross-chain accessibility, wallet reliability, infrastructure choice, and compatibility with the evolution of the Zcash protocol. All of this work is already completed, released, and publicly verifiable in our open-source repositories.

Happy to answer any questions about the updated scope or the Ironwood implementation.