I had sent Zcash from an unshielded address to my Ledger Wallet. This address started with t1, which means unshielded for me. So as far as I know, this cannot be the problem.
1 Like
Hello @BarryAllen! It could be the cases that you have transparent UTXOs that come from shielded inputs and that the Ledger algorithm for meeting the amount you are trying to transfer is picking those up and thatās when it all goes wrong. If you go to the advanced mode you can switch how ledger will pick your funds. also you should because by default ledger pays too much Zats per bytes and your fees will be higher than needed anyway
Wow, Iām shocked that issues like this are still occurringā¦.I encountered a similar issue about 6 months ago.. not good prospects for Zcash at all.
I know itās a ledger issue but ledger is so popular. How can this be prevented next time?
What if I told you part of this has been a problem since NU5 
It was thanks to Zcashers and the adaptation skills that these problemsā impact were minimized
We are working on paving a new road with Ledger so these problems are thing of the past.
3 Likes
@hanh I tried to use the sweep function to recover my zcash from my old ZEC lite wallet and it says ānot enough funds to pay for the feesā but there should be plenty in both the lost wallet and the one I am transferring to. Any suggestions?
The fee is determined by the amount of notes being combined as enforced by zip317. Each one costs 0.00005. Any note less than this value cannot currently be spent. It could be another problem but this is otherwise a classic issue.
Iām also having trouble sending ZEC from an old t address on ledger nano x. When I go to broadcast, it just gets stuck on the last step, and the zcash app on the device itself seems to exit (no errors). Then it just spins on Ledger Live. Anyone else seeing that?
Whatās the best path forward?
Hmm, I was actually able to get one to send right now using coin control. Even though I put something like 0.1 ZEC to send, it by default had all my UTXOs selected in coin control - no idea why. Is that a ledger bug? Wasnāt expecting that? So I unselected all, and selected a few at the top to cover the 0.1, and then I was able to sign and send!
It could be because the Ledger isnāt capable of handling too many inputs. The app crashed silently on the device.
I have a secret-extended-main key from an old zcashd full node I ran. I imported the key to ywallet that is now fully synced and when I attempt to send the zcash balance it does not work and just gets struck at the send screen (appears to be attempting to broadcast the transaction?).
I also tried sweeping from the secret-extended-key to a transparent address and ywallet does not recognize the private key (gives an āinvalid keyā response).
I want to send my zcash to a new wallet where it is usable. How do I do this?
1 Like
use zkool.
1 Like
Ok well is there another wallet I can try? I donāt know how to fix this Iām not technical.
i added a step by step video.
Yes Iāve followed all of the same steps. My secret-extended-main key address emerged around 900k block height. I put in 100k birth height to restore the wallet - perhaps this impacted? My balance is appears in the wallet and is fully synced - I just get that issue when I attempt to send. Iām running windows and used cursor to compile zkool as I donāt know how to myself so perhaps this impacted something?
100k is too low
Sapling activated at 419200. Put something like 500k.
why donāt you donwload the binary release for windows?
1 Like
Tried all of this and still getting the same errorā¦
I dunno then. Iād need a video recording to investigate further (redact any sensitive data).
It wonāt let me upload a video and I canāt add links to my posts paste the below
youtu.be/_Vn14SvSIU4