Hello @abhi-ledger , today is the Ironwood activation day and we are three days to july ending… I saw some activities on zcash-related ledger repositories, any news about the new zcash app with full ironwood support?
3 Likes
Any updates for us?
2 Likes
Zcash Community Forum - August 2026 Update
Hi everyone,
Update from the Ledger integration team, covering everything since the June update. We owe you an explanation for skipping July, that’s at the end of this post. The short version of the whole update: Ironwood support shipped before activation, shielded send and receive is now complete across the stack and in QA hardening, and the reported swap and error issues are fixed and released.
1. NU6.3 / Ironwood
Support for the new consensus rules shipped across the whole stack (signer, wallet, device app) two weeks before the July 28 mainnet activation. Transparent ZEC send and receive were unaffected by the upgrade.
2. Shielded send and receive
As announced in June, the implementation was re-based onto Ironwood rather than shipped on Orchard first. It is now complete across all four layers:
- Crafting library (ledger-zcash-utils): Ironwood pool sync, V6 transaction builder, finalize and broadcast.
- Device app (app-zcash): shielded transaction signing, clear signing of every flow, security fixes.
- Signer (device-sdk-ts): shielded signing on device, Ironwood bundle support, on-device address verification.
- Ledger Wallet (ledger-live, filter by “zcash”): a standalone Zcash module, Ironwood balance and send routing, the complete send flow (source selection, address validation, sync status, fees, summary, shield/unshield), and the private address in the Receive screen.
Where it stands: real shielded sends now sign on a physical Ledger and broadcast on mainnet in internal builds. We are in QA hardening; what it has surfaced so far is wallet-side and fixed as found. One item remains open on the device side: the memory footprint of a shielded spend on the smallest devices. The device app goes through an independent security audit before release.
3. Swap failures and other reported errors
Swap: the rise in generic errors when swapping ZEC in late July, across all providers, came from two bugs in how Ledger Wallet handled the transaction that had funded a user’s coins. Neither was in the Zcash device app, which is why updating the app changed nothing, and why the failures looked random: being affected depended on which transactions had funded your coins, not on your app version. Both are fixed and released in Ledger Wallet Mobile 4.14 (August 7) and Desktop 4.15 (August 11).
Also fixed and released: the device prompt never appearing, broadcast failures after signing, incorrect fees and maximum amounts, transparent balance mismatches, shielded state lost between sessions, and wrong amounts in shielded history. The incorrect consensus branch id error reported in this thread came from wallets stuck on an old version by an auto-update bug; it resolves on update, as confirmed in that post.
Still open: spending coins received from an Ironwood transaction (the wallet now refuses clearly instead of erroring; full support needs the next device app), and one case of very old pre-Sapling transparent coins failing to spend through a third-party wallet, under investigation.
Scoped, not started: retiring the legacy Sapling app, so other wallets can drop it without stranding anyone’s funds.
4. Grant scope and Ironwood
To be explicit about how this relates to Grant #152: the deliverables remain the same, with the Orchard-specific components delivered as their Ironwood equivalents, since Ironwood is now the network’s shielded pool. We will publish a written mapping of the original grant scope against the Ironwood deliverables for ZCG’s review, so there is a clear shared record of what is being delivered against the grant.
5. On the communication gap
We missed the July update. Part of the reason: the Ironwood pivot created additional engineering effort that was not anticipated by the original grant, and much of the past weeks went into the commercial and legal groundwork for covering it, including a potential sponsorship from within the Zcash community for that additional technical effort. We held this update longer than we should have waiting for that to conclude. In hindsight, the technical progress you’ve just read deserved its own post regardless.
The next update will be a bigger, formal one.
– Abhi
Product | Coin & Blockchain Integration | Ledger
7 Likes
Hi please check the formal update here: A Path Forward for Ledger and Zcash - #170 by abhi-ledger
1 Like
Ledger and Zcash: Ironwood funding agreement and Grant #152 scope mapping
Hi everyone, major update!
In the August update we said the next post would be a bigger, formal one, covering the commercial and legal groundwork mentioned there. That work has concluded, so here is the full picture.
1. The Ironwood funding agreement
The Ironwood pivot created additional engineering work that was not anticipated by the original grant. That additional work, and only that work, is now covered by a Blockchain Integration and Funding Agreement between Ledger and Zcash Labs LLC (their announcement), under which Zcash Labs funds USD 80,000 for adapting the original Orchard-scoped deliverables to Ironwood (NU6.3).
To be explicit about governance, because it matters here:
- This is a bilateral agreement between Ledger and Zcash Labs. It is separate from, and independent of, Grant #152.
- It changes nothing about Grant #152: not the deliverables owed to the community, not ZCG’s review and acceptance process.
- Zcash Labs has no authority of any kind over Grant #152. It cannot modify, approve, or direct anything under the grant. That remains entirely between Ledger and ZCG.
- Any steps Zcash Labs may take within Zcash community processes regarding its sponsorship are its own initiative, in its sole discretion. Ledger is not a party to any such process.
2. Grant #152 deliverable mapping
As promised in August, the written mapping of the original grant scope against the Ironwood deliverables is now posted on the grant issue for ZCG’s review: Github Issue #152 Comment.
The one-line summary: every deliverable stands as originally defined in Grant #152, with the Orchard-specific components delivered as their Ironwood equivalents, since Ironwood is now the network’s shielded pool following NU6.3 activation. The comment also lists explicitly what is not covered, so there is no ambiguity at acceptance time.
3. Where delivery stands
Shielded send and receive remain complete across the stack and in QA hardening, as described in August. Release is gated on completion of the independent security audit of the device app and final QA; we are targeting end of September. The regular monthly update follows at the end of the month.
We are grateful for constant and proactive support from Tom (Zcash Labs LLC), ZCG, FPF and ZODL team. And we are looking forward to long term collaboration with Zcash community
– Abhi
Product | Coin & Blockchain Integration | Ledger
14 Likes
Huge for Zcash Ecosystem. Thankyou for this Ledger team
1 Like
Curious if v1 transactions are still on your guys radar. Charles had said this would be supported. Tom Zarebczan 🛡 on X: "@P3b7_ @lopp Hey Charles, do you know if v1 transactions still plan to be addressed? This thread made it sound like it, but it hasn't made it into a release yet. I was excited to test the recent version announced by some Zcash wallets today, only to find that I still cannot … / X
For anyone in this boat, I was able to recover via Zkool + Ledger. Happy to help anyone through it.
2 Likes
7 Likes
Zcash Ironwood is now live in Ledger Wallet Desktop
Hi everyone,
It shipped. Shielded send and receive is live in Ledger Wallet desktop app as of today, on the end-of-September target we gave in the September update. This is the shielded scope of Grant #152, delivered on Ironwood.
The short version of the whole update: private send, private receive, memos and shield/unshield are live on desktop; the device app is Ironwood-only, so Sapling and Orchard funds do not appear; the legacy Zondax “Zcash Shielded” app is being retired at NU7, with a dedicated migration post to follow; and the grant now goes to ZCG for acceptance.
1. What shipped
-
Private balance sync. Your Unified Full Viewing Key is exported once, on first sync, and stored locally on your own computer.
-
Receive to a private address, verified on the device before you share it.
-
Private to private send, with a memo.
-
Public to private. Move funds from your transparent balance into your private balance.
-
Private to public. Move them back out.
Every flow is clear-signed on the device.
What you need: Ledger Wallet desktop 4.21 or later, and the new Zcash (ZEC) app 3.9.4 or later from My Ledger. Every current signer is supported. Nano S is not, and will not be.
The same device app is already supported by zkool and Vizor, so Ledger Wallet is not the only way to use it.
Step-by-step documentation is here: How to use your private ZEC balance through Ledger Wallet desktop
2. Scope of this release
-
Desktop only. There is no private balance on mobile.
-
Ironwood only. Ledger Wallet reads and spends the Ironwood pool. Sapling and Orchard funds will not appear, which is the subject of section 4.
-
Swaps use your transparent balance. To swap private ZEC, unshield it first.
-
Memos work when the recipient is private, capped at 250 characters. Not yet available on public-to-private self transfers.
Sapling and Orchard support is out of scope permanently.
3. Known limitations
-
Maturing period. Newly shielded funds need roughly 10 confirmations, about 15 minutes, before they are spendable.
-
Size caps. The device app caps a transaction at 32 shielded actions, 32 transparent inputs and 10 transparent outputs.
-
Mobile still uses the older signing path. Very old transparent coins, where the funding transaction was v1, v2 or v3, or was a v4 carrying Sapling data, can fail to send on mobile with “Unsupported transaction version.” On desktop this no longer applies, because the device does not read the funding transaction at all. If this affected you before, try again on desktop and tell us here.
4. Action needed: retiring the legacy “Zcash Shielded” app
In August we flagged retiring the legacy Sapling app as scoped but not started. It is now in motion, it affects funds, and it deserves immediate attention.
The “Zcash Shielded” device app (4.3.5), built by Zondax and used through ywallet and zkool, stops working at NU7, currently targeting mainnet on 5 November. Ledger will not be carrying it through the upgrade. After that, Sapling funds held through that app can no longer be moved with a Ledger device. The app derives shielded keys from a non-standard input, so those accounts cannot be reproduced by the new Ledger app, and the new app’s viewing key carries no Sapling component, so they will not appear in Ledger Wallet at all. Recovering them by other means after NU7 is not guaranteed, so the reliable route is to move them now, while the old app still works.
Transparent funds in those accounts are less exposed, since they use standard derivation, but the same guide covers them and it is simplest to move everything at once.
If that describes you, start now. The full step-by-step is here: Transfer Zcash (ZEC) from legacy accounts to Ledger Wallet.
6. Grant #152
Grant #152. The deliverable mapping posted on the grant issue last week stands as written. Every deliverable is delivered as originally defined, with the Orchard-specific components shipped as their Ironwood equivalents, since Ironwood is the network’s shielded pool following NU6.3. This release is what that mapping described. With it live, the milestone is complete from our side and now goes to ZCG for review and acceptance. We will answer anything ZCG raises in the open, on the grant issue rather than by email, so the record stays public.
The separate Ironwood funding agreement with Zcash Labs LLC, disclosed in the September update, remains independent of the grant and changes none of the above.
———
Thank you to the team of Zcash Labs, ZCG, FPF and ZODL for the support through the Ironwood pivot, and to everyone in this thread who kept pushing for a date. It was a pleasure working with Zcash community.
– Abhi
Product | Coin & Blockchain Integration | Ledger
13 Likes
Ledger Stax x Zcash Shielded is 
Have a small feedback @abhi-ledger tho, on the ui/ux of the ledger: i believe it would be smoother for a lambda user if the ledger clearly stated when they’re sending to their own address. Not having might creates a lot of friction in the ux imho. Would be awesome if you could fix that in the next version.
3 Likes
Grant #152 – Milestone 1 completed: delivery recap
Hi everyone,
First of all nice to meet you, my name is Livio and I am Product Manager on the Coin Integration at Ledger and I will be taking over the work that Abhi did so far as he recently left Ledger.
Following the release announcement on September 23, 2026, we’ve posted the formal completion request for Grant #152 on the grant issue. Here is the same recap, so everyone can see each Milestone 1 deliverable as originally submitted and what we shipped against it.
As detailed in our Orchard → Ironwood deliverable mapping, shielded deliverables are delivered on Ironwood (NU6.3) following ZIP 257; the scope itself is unchanged.
Release references
- Ledger Wallet Desktop 4.21+ and Zcash device app 3.9.4+
- Devices: Nano S Plus, Nano X, Flex, Stax, Nano Gen5
- Announcement: New in Ledger Wallet™: Native Shielded Zcash Support | Ledger
Deliverables
| Deliverable (as submitted) | Delivered |
|---|---|
| Ledger OS | |
| ZIP-32 support at OS level for Orchard address derivation |  Shipped in the following Ledger OS versions:• LNX: 2.7.0 • LNSP: 1.6.0 • Flex: 1.6.0 • Stax: 1.10.0 • Gen5: 1.1.0 Fully rolled out. Ironwood reuses the Orchard key hierarchy, so it applies as-is |
| Pallas and Vesta curve support in the crypto stack | Shipped in the following Ledger OS versions: • LNX: 2.6.0 • LNSP: 1.5.0 • Flex: 1.5.0 • Stax: 1.9.0 • Gen5: 1.0.3 |
| Dedicated security audit of the new crypto and derivation logic | Audit completed by Ledger Donjon |
| Zcash device app | |
| Redeveloped Zcash app supporting transparent and shielded operations | Zcash app 3.9.4+, transparent + shielded (Ironwood) |
| On-device PCZT parsing and validation | Extended to the V6 transaction format and the Ironwood bundle |
| Clear signing for transparent, shielding, deshielding and shielded flows | All four flows: recipient, amount, fee and memo displayed on device |
| Integration with the OS derivation and curve updates | Done |
| Backward compatibility for transparent ZEC + Ledger app review and certification | Transparent flows supported in the same app; app passed Ledger review and is published in the Ledger Wallet catalog |
| Signing of transparent swap transactions | Live, including app-exchange adaptations |
| Security review | Completed by Ledger Donjon, findings remediated before release |
| Ledger Wallet Desktop | |
| Shielded account support: address display, balance sync, transaction history | One account showing transparent and Ironwood balances, sync through zaino, history with memos |
| PCZT-based transaction construction and device signing | Done |
| New TypeScript Ledger Signer for Zcash | Done: LedgerHQ/device-sdk-ts – signer-zcash |
| Send, receive and memo for shielded ZEC | Shield, deshield and private send, private address on the Receive screen, memo support, ZIP 317 fees |
| Testing integration | E2E integration tests and unit tests |
| Transparent ZEC in Swap: UI, partner connection, quotes, transaction crafting | Live with NEAR Intents, MoonPay Trade and Exodus |
Success metrics from the application
- Device app audited, QA’d and released
- Ledger Wallet Desktop release with shielded ZEC support
- Transparent ZEC swap live, end-to-end validated with at least one partner
Out-of-scope items are unchanged from the original application (Nano S, Sapling, Ledger Wallet Mobile, plus the legacy Orchard pool as detailed in the mapping).
We consider Milestone 1 complete and have asked ZCG to proceed with the review, acceptance and payment. Any questions from ZCG will be handled on the grant issue so the record stays public, and we’re happy to answer community questions here as well.
Thanks a lot
Livio | PM Coin Integration
4 Likes