# Can't Send from Any Wallet - Issues Related to Ledger and Coinbase

**URL:** <https://forum.zcashcommunity.com/t/cant-send-from-any-wallet-issues-related-to-ledger-and-coinbase/41951>\
**Category:** Technical Support\
**Created:** [June 2, 2022, 7:46pm UTC](https://forum.zcashcommunity.com/t/cant-send-from-any-wallet-issues-related-to-ledger-and-coinbase/41951 "2022-06-02T19:46:47Z")\
**Posts on this page:** 14\
**Page:** 2

<div class="post-metadata">

**Author:** ![eth03](https://avatars.discourse-cdn.com/v4/letter/e/a5b964/32.png) [@eth03](https://forum.zcashcommunity.com/u/eth03)\
**Post date:** [June 4, 2022, 10:32pm UTC](https://forum.zcashcommunity.com/t/cant-send-from-any-wallet-issues-related-to-ledger-and-coinbase/41951/21 "2022-06-04T22:32:03Z")

</div>

Not sure if anyone knows if they’re close to resolving this but coinbase pro has paused deposits and withdrawals of zcash since 6/1.  
[https://status.pro.coinbase.com/](https://status.pro.coinbase.com/)

Update: also cannot send on ledger live to any address. It’s an API error when trying to send. I have to assume they haven’t updated their nodes yet.

---

<div class="post-metadata">

**Author:** ![noamchom](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/noamchom/32/20269_2.png) [@noamchom](https://forum.zcashcommunity.com/u/noamchom)\
**Post date:** [June 5, 2022, 2:54am UTC](https://forum.zcashcommunity.com/t/cant-send-from-any-wallet-issues-related-to-ledger-and-coinbase/41951/22 "2022-06-05T02:54:22Z")

</div>

That potentially explains the shortage of Zcash coins for sale on Coinbase! Whoever their supply provider was must not have stock piled them enough to sell.

---

<div class="post-metadata">

**Author:** ![Fringle](https://avatars.discourse-cdn.com/v4/letter/f/dec6dc/32.png) [@Fringle](https://forum.zcashcommunity.com/u/Fringle)\
**Post date:** [June 6, 2022, 12:44am UTC](https://forum.zcashcommunity.com/t/cant-send-from-any-wallet-issues-related-to-ledger-and-coinbase/41951/23 "2022-06-06T00:44:25Z")

</div>

Interesting. Found this on Twitter earlier [https://goblincrypto.com/coinbase-abruptly-freezes-zcash/](https://goblincrypto.com/coinbase-abruptly-freezes-zcash/)

---

<div class="post-metadata">

**Author:** ![eth03](https://avatars.discourse-cdn.com/v4/letter/e/a5b964/32.png) [@eth03](https://forum.zcashcommunity.com/u/eth03)\
**Post date:** [June 6, 2022, 9:42pm UTC](https://forum.zcashcommunity.com/t/cant-send-from-any-wallet-issues-related-to-ledger-and-coinbase/41951/24 "2022-06-06T21:42:22Z")

</div>

I hope ledger and coinbase can resolve this soon. It’s been down for several days now and I have transactions waiting. This seems to be affecting a lot of people. As far as I know, the issue is with their clients being able to broadcast a transaction. I don’t have any reason to believe this is more than a client side issue.

---

<div class="post-metadata">

**Author:** ![Fringle](https://avatars.discourse-cdn.com/v4/letter/f/dec6dc/32.png) [@Fringle](https://forum.zcashcommunity.com/u/Fringle)\
**Post date:** [June 6, 2022, 11:37pm UTC](https://forum.zcashcommunity.com/t/cant-send-from-any-wallet-issues-related-to-ledger-and-coinbase/41951/25 "2022-06-06T23:37:21Z")

</div>

You don’t think it’s intentional? I noticed Binance announced they would support the upgrade. No such announcement from Coinbase that I could find.

---

<div class="post-metadata">

**Author:** ![steven-ecc](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/steven-ecc/32/26556_2.png) [@steven-ecc](https://forum.zcashcommunity.com/u/steven-ecc)\
**Post date:** [June 6, 2022, 11:41pm UTC](https://forum.zcashcommunity.com/t/cant-send-from-any-wallet-issues-related-to-ledger-and-coinbase/41951/26 "2022-06-06T23:41:34Z")

</div>

We’ve been working with the Coinbase engineers for months to support NU5. They neglected to upgrade part of their infrastructure and have a new team working on it that is unfamiliar with the code. We’ve been in multiple pairings and have been helping them test today. Hopefully this will be resolved soon.

---

<div class="post-metadata">

**Author:** ![eth03](https://avatars.discourse-cdn.com/v4/letter/e/a5b964/32.png) [@eth03](https://forum.zcashcommunity.com/u/eth03)\
**Post date:** [June 6, 2022, 11:58pm UTC](https://forum.zcashcommunity.com/t/cant-send-from-any-wallet-issues-related-to-ledger-and-coinbase/41951/27 "2022-06-06T23:58:48Z")

</div>

I don’t think it’s intentional. I was told by Ledger support that it’s a technical issue they are working on and lots of people are affected. They stated they’re working on it, so it’s not a decision to not support it.

---

<div class="post-metadata">

**Author:** ![eth03](https://avatars.discourse-cdn.com/v4/letter/e/a5b964/32.png) [@eth03](https://forum.zcashcommunity.com/u/eth03)\
**Post date:** [June 7, 2022, 8:47pm UTC](https://forum.zcashcommunity.com/t/cant-send-from-any-wallet-issues-related-to-ledger-and-coinbase/41951/28 "2022-06-07T20:47:21Z")

</div>

Just curious. Is anyone able to transact zcash on a trezor? If so, I found out I can restore a ledger seed to a trezor. So whoever supports NU5 first so I can transact anything is who I’ll be a customer to.

Update: This is fixed now with an update to the zcash app on ledger devices. Tested it and it worked.

---

<div class="post-metadata">

**Author:** ![Fringle](https://avatars.discourse-cdn.com/v4/letter/f/dec6dc/32.png) [@Fringle](https://forum.zcashcommunity.com/u/Fringle)\
**Post date:** [June 10, 2022, 12:53am UTC](https://forum.zcashcommunity.com/t/cant-send-from-any-wallet-issues-related-to-ledger-and-coinbase/41951/29 "2022-06-10T00:53:22Z")

</div>

Why are my posts about Coinbase being merged to this thread about Ledger? It has nothing to do with Ledger.

---

<div class="post-metadata">

**Author:** ![eth03](https://avatars.discourse-cdn.com/v4/letter/e/a5b964/32.png) [@eth03](https://forum.zcashcommunity.com/u/eth03)\
**Post date:** [June 11, 2022, 1:43am UTC](https://forum.zcashcommunity.com/t/cant-send-from-any-wallet-issues-related-to-ledger-and-coinbase/41951/30 "2022-06-11T01:43:28Z")

</div>

Does anyone know if Trezor new beta application for their wallet supports shielded addresses?

> <https://github.com/trezor/trezor-firmware/pull/1847>
>
> \# Orchard shielded transactions for Trezor T.
> 
> work in progress . you can use …this PR for tracking my activity
> 
> \### Links
> \[ZFND grant\](https://grants.zfnd.org/proposals/1792958360-trezor-support-for-zcash-shielded-transactions)
> \[documentation\](https://github.com/jarys/ztrezor/blob/main/doc/README.md)
> \[milestone M.1 report\](https://github.com/jarys/ztrezor/blob/main/M.1\_report.md)
> \[milestone M.2 report\](https://github.com/jarys/ztrezor/blob/main/M.2\_report.md)
> 
> \### Orchard addresses and keys
> \- \[x\] orchard addresses
> \- \[x\] unified addresses
> \- \[x\] viewing keys export
> \- \[x\] layouts
> \- \[x\] ZIP-32 support
> \*\*Connectivity:\*\*
> \- \[x\] \`trezorlib.zcash\` module 
> \- \[x\] \`trezorctl zcash\` commands
> \- \[\] ~Connect support~
> \*\*Tests:\*\*
> \- \[x\] unit tests
> \- \[x\] tests on real device
> \- \[x\] reviewed
> \- \[\] typing
> \### Orchard transactions
> \- \[x\] v5 transaction format
> \- \[x\] signing workflow
> \- \[x\] orchard inputs and outputs
> \- \[x\] ZIP-244 (txid and sighash) implementation
> \- \[x\] layouts
> \- \[\] graphically distinguish transparent and orchard outputs 
> \- \[x\] mixed transactions (transparent + orchard)
> \*\*Connectivity:\*\*
> \- \[x\] python bridge to orchard crate (\[pyorchard\](https://github.com/jarys/pyorchard)) e.i. the prover is callable from python
> \- \[\] \`trezorlib.zcash\` module (raw version)
> \- \[\] \`trezorctl zcash\` commands
> \- \[\] Connect support
> \*\*Tests:\*\*
> \- \[\] unit tests
> \- \[\] tests on real device
> \- \[\] typing
> \- \[\] reviewed
> \### Zcash crates
> \- \[x\] \`librustzcash\` https://github.com/zcash/librustzcash/pull/450
> \- \[x\] \`librustzcash\` https://github.com/zcash/librustzcash/pull/446
> \- \[x\] \`pasta\_curves\` https://github.com/zcash/pasta\_curves/pull/4
> \- \[x\] \`reddsa\` https://github.com/ZcashFoundation/reddsa/pull/11
> \- \[x\] \`orchard\` https://github.com/zcash/orchard/pull/309
> \- \[x\] \`orchard\` https://github.com/zcash/orchard/issues/297
> \- \[x\] \`orchard\` https://github.com/zcash/orchard/issues/287
> \- \[x\] \`orchard\` https://github.com/zcash/orchard/pull/299
> \### Firmware team
> \- \[\] reserve more memory for Zcash app
> \- \[\] integrate Sinsemilla table
> \- \[x\] ~check Rust allocator correctness~
> \- \[\] implementation review
> \### Documentation
> \- \[\] \[implementation documentation\](https://github.com/jarys/ztrezor/blob/main/doc/README.md) (need to be updated)
> \- \[x\] M.1 report
> \- \[x\] M.2 report
> \- \[\] M.3 report

> <https://github.com/trezor/trezor-suite/issues/5344>
>
> Zcash will soon \[1\] deploy the NU5 upgrade to mainnet. Currently NU5 is running …on Zcash testnet. Suite only supports v4 transactions. As a result of the upgrade Suite users will not be able to spend UTXOs created in v5 transactions. However, they will still be able to spend UTXOs created in v4 transactions and earlier-version transactions.
> 
> In order to spend a UTXO created in a v5 transaction, Suite needs to spend it in a v5 transaction, which can be done as follows:
> \- The \`version\` field in \`SignTx\` needs to be set to 5.
> \- The \`branchId\` needs to be set to 0xc2d6d0b4, see https://zips.z.cash/zip-0252.
> \- The \`versionGroupId\` needs to be set to 0x26a7270a, I think (no source available).
> \- When signing v5 transactions the client does not need to provide the previous transaction(s).
> 
> The accounts and addresses remain the same as for version 4. The serialized transaction structure is different, but that is taken care of by Trezor firmware. Suite should not need to make any updates in this regard, just broadcast the transaction that Trezor spits out.
> 
> There are two implementation options for signing Zcash transactions:
> 1. Once this is implemented Suite will only create v5 transactions.
> 2. Suite will create a v5 transaction only if at least one transaction input comes from a v5 transaction. Otherwise it will create a v4 transaction.
> 
> The advantage of Option 1 is that no prev\_tx streaming is needed. The advantage of Option 2 is that we only create v5 UTXOs if it's necessary to spend our selected UTXOs. This way if the wallet used by the recipient of the payment does not support v5 transactions yet, they might still be able to receive the payment, i.e. see that the payment was received and be able to spend it.
> 
> We can implement Option 2 for a transition period and switch to Option 1 later.
> 
> On Trezor NU5 support will be available starting with the upcoming releases of T1 firmware v1.11.1 and TT firmware v2.5.1. If Suite intends to sign a v5 transaction, it will need to ensure that the user has this firmware version or a later version.
> 
> This issue might be related to https://github.com/trezor/trezor-suite/issues/3749 (maybe \`branchId\` and \`versionGroupId\` can be retrieved from blockbook?). But implementing it is certainly not a prerequisite for this issue.
> 
> \[1\] Zcash schedule: https://z.cash/support/schedule/
> \[2\] Firmware issue: https://github.com/trezor/trezor-firmware/issues/2031
> \[3\] TT firmware PR: https://github.com/trezor/trezor-firmware/pull/2166
> \[4\] T1 firmware PR: https://github.com/trezor/trezor-firmware/pull/2244

It looks like this is close to finished. Just wasn’t sure what to expect when I first try out a Model T and create a new wallet address. I just want to migrate my entire savings into the shielded pool and never look back. I’ll still use Ledger for other cryptocurrencies but for zcash I just wanted to have it shielded going forward.

---

<div class="post-metadata">

**Author:** ![sightseeer](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/sightseeer/32/19156_2.png) [@sightseeer](https://forum.zcashcommunity.com/u/sightseeer)\
**Post date:** [June 13, 2022, 4:25pm UTC](https://forum.zcashcommunity.com/t/cant-send-from-any-wallet-issues-related-to-ledger-and-coinbase/41951/31 "2022-06-13T16:25:45Z")

</div>

Any update? (Concerning Ledger. I don’t care much about coinbase.)

---

<div class="post-metadata">

**Author:** ![eth03](https://avatars.discourse-cdn.com/v4/letter/e/a5b964/32.png) [@eth03](https://forum.zcashcommunity.com/u/eth03)\
**Post date:** [June 13, 2022, 4:34pm UTC](https://forum.zcashcommunity.com/t/cant-send-from-any-wallet-issues-related-to-ledger-and-coinbase/41951/32 "2022-06-13T16:34:14Z")

</div>

Ledger zcash transactions are completely operational. It was resolved last week.

---

<div class="post-metadata">

**Author:** ![tokidoki](https://avatars.discourse-cdn.com/v4/letter/t/dc4da7/32.png) [@tokidoki](https://forum.zcashcommunity.com/u/tokidoki)\
**Post date:** [June 14, 2022, 4:20am UTC](https://forum.zcashcommunity.com/t/cant-send-from-any-wallet-issues-related-to-ledger-and-coinbase/41951/33 "2022-06-14T04:20:57Z")

</div>

Orchard support for Trezor Model T is under development here [GitHub - jarys/ztrezor: Orchard shielded transactions for Trezor T.](https://github.com/jarys/ztrezor)

---

<div class="post-metadata">

**Author:** ![eth03](https://avatars.discourse-cdn.com/v4/letter/e/a5b964/32.png) [@eth03](https://forum.zcashcommunity.com/u/eth03)\
**Post date:** [June 15, 2022, 6:03pm UTC](https://forum.zcashcommunity.com/t/cant-send-from-any-wallet-issues-related-to-ledger-and-coinbase/41951/34 "2022-06-15T18:03:10Z")

</div>

Thanks. I’m very excited about this. Looks like it’s in pre-release so a production version should be out soon hopefully.

[Previous page](https://forum.zcashcommunity.com/t/cant-send-from-any-wallet-issues-related-to-ledger-and-coinbase/41951.md?page=1)
