Hi, I am new here and I am glad that I could find a topic about this issue since I have the exact same problem like @unibros ZecMan . This is ongoing for at least 2 weeks
Thanks for picking this up @pacu
3 Likes
At the moment you can only send/move ZEC that has been transacted in the last 12 months. Even the coins with the last transaction from the early 2024 are not spendable. When did you last transact with the coins you are trying to send?
I’m probably going off-topic, but can someone please explain why this happens so often with Zcash? Let’s take Dash for example. Many would say that these two cryptos are somewhat similar. Both for the last couple of years have been depreciated quite a lot, so I would say they are kinda in the same boat. But there’s a difference - since the date I’ve started using Dash (give or take 10 years) I never had a problem when I couldn’t move/send it. I’m not trying to say it’s better, I lost money because of the value depreciation with both coins, but at the end of the day it is more reliable because I don’t have to worry that something like this will happen with my Dash.
Same issue here. Never had any issue with Ledger until ZEC app just updated today.
Oldest coins were moved into this wallet 3/21/24.
Reply from Ledger Support - no clear timeline:
Thanks for sharing that - this is a known issue relating to the UTXO(s) it/themselves. If you are trying to send pre-NU5 (Zcash’s network upgrade) UTXOs that error will pop up - rest assured our app developers are in contact with the ZCash team working on a resolution to be deployed as soon as possible.
In the meantime, the only current workaround would be to expose your 24-word recovery phrase in YWallet
1 Like
regardless of the last txn timestamp… just a few weeks ago i was able to move my ZEC upon ledger’s recent update… now I can’t
i regrettably wish i sent all my ZEC off of my ledger when i had the chance lol
5 Likes
It is not really a new solution, users could get their funds out using the sweep function on ywallet. Ironically, it is documented on the Ledger website 
.
A solution would be that Ledger … works?
4 Likes
This is amazing!
But also, do not wish to enter my ledger seed elsewhere — I have more than just ZEC tied to it.
I will personally be waiting for a ledger fix.
4 Likes
Last update from Ledger about the latest issues reported by Zcash users.
Hi Pacu ! Yes we’re working on this with both the firmware (app) team and the Ledger Live team, (and yes the disconnect is identified), still some work ongoing and tests added to ensure we handle different tx_version / nversiongroupid / consensusBranchid cases.
I’ll keep you all updated here
3 Likes
Hi, I used to manage my zec using ledger nano x in a t address, but they are stuck because of well known zec app crash and device disconnection issues.
I imported my seed phrase in keystone 3 pro with the latest cypherpunk firmware and paired it with zashi (latest release on Android), now I can see all my Zec, but shielding them failed because of a connection with server error.
My network works fine, I tried on my home wifi under VPN, without VPN, using 5g connection. I also switched to different public servers.
Have you any hints to understand what’s are going on?
1 Like
You can try changing your lightwalletd server in the app.
Thanks, I tried four random zec.rocks and zcash-infra servers, same results… 
@andrea, user reporting problem with Zashi Android and Keystone.
2 Likes
I have some updates on this matter.
I’ve been testing some dev builds from Ledger which unstuck t2t transactions for funds that don’t have shielded inputs on them and verified being able to create and submit transactions. We haven’t reached the point where transparent Zec received from a deshielding transaction can be spent. but Ledger is actively working on it.
4 Likes
Impressive how this issue has been going on for months with no solution from ledger besides exposing seed phrase …
2 Likes
@pacu Could you elaborate why Z->T makes a difference for the Ledger app?
Thanks
1 Like
Interesting tweet here from the ledger CTO… its only taken 6 months to show that they are working on a fix
Update: As a lot had suspected, ledger only needed binance to pressure them into making a fix for the zcash app 
1 Like
There are a few theories that back in December ECC engineers had suggested ledger to look into.
I don’t want to get into any details because the root of the problem is still unknown, and these are possible theorized sources of the problem, otherwise it would have been fixed already.
One of the problems it’s definitely that the moment the shielded inputs come into play ledger live shows this disconnection error. These problems are in both ledger live and the ledger Zcash transparent application.
We are not CURRENTY delving into their code (we already did back when NU6 activated), we are just limiting ourselves to assist ledger engineers at a support level. They are the ones that know their code best and the ones that will be the most qualified to put the fixes in place.
Additionally I volunteered for helping to test one of their fixes since I could reproduce the problem and had the adequate funds received at the specific time that was causing the problem they wanted to fix.
EDIT: clarified some things
2 Likes
Why aren’t you looking at their code? It’s open source, and you guys are the most qualified to understand the Zcash logic.
It seems to me that if we want the matter resolved, we need to be more proactive.
2 Likes
We are proactive, we are in permanent contact and responsive to ledger to any questions, requests and questions they may have and even testing on our own devices with our own funds.
I assume that I represented it poorly in my last post 
Let me reiterate. As I probably very poorly explained, we did look at the code. We (ECC, Myself and even Zondax) did make the recommendations back when NU6 activated and ledger engineers are the ones to take them and implement them.
1 Like