Thanks a million Ivan Gromakovskii, I now managed to do the same and finally move my ZEC. Thanks again.
2 Likes
Unbelievable. No working ZEC full-node wallet in 2025 to restore wallet.dat?
How is it possible that in 2025 there’s still no stable Zcash (ZEC) full-node wallet that can simply restore a standard wallet.dat file? Every “official” or “recommended” solution either fails to install, crashes during sync, or is missing critical components.
All the previously working releases seem to have been deprecated or broken by updates. Even the so-called “lightwallet” versions are incomplete and useless for actual fund recovery.
This isn’t some obscure altcoin. Zcash is supposedly a top 20 crypto by market cap. Yet there’s no reliable way to restore your own funds using the original wallet file. That’s absurd.
And if you were wondering whether the devs are getting paid while you struggle: yes, they are. 20% of each block reward goes into the Zcash Dev Fund.
So while users are left trying to recover legacy wallets and facing broken clients, 20% of issuance is flowing off-chain to dev/slice funds. This isn’t just neglect - it looks like a maintenance failure at its best.
Can anyone confirm if there’s any working full-node wallet or documented recovery path for wallet.dat on macOS, windows or mobile in 2025?
FYI, walled.dat has never been a reliable way to store your assets on any existing blockchain, including Bitcoin. Only private keys are reliable, and this information was clearly stated in the description of how to use any full node wallets. It’s like squeezing toothpaste from the other end and complaining that the manufacturers have undermined your trust.
Use the private key extraction method in my topic, which you have already found. It is a working method.
2 Likes
Hello,
I am experiencing a critical issue with the Zkool wallet while using it together with my Ledger device.
Recently, I made a small test transaction from Zkool. The transaction was broadcast successfully, but the wallet unexpectedly sent the change output to an address that I did not generate and that does not exist in my wallet. After this happened, the wallet stopped sending any new transactions — every attempt shows brief synchronization messages, but nothing is broadcast and no error is displayed.
At the same time, the on-chain explorer shows that the funds still exist, but Zkool is unable to detect or use them. Other wallets do not show the correct balance either, suggesting that Zkool may have created an incorrect change address or that its local database is corrupted.
I would appreciate your help with the following:
-
How can I force Zkool to fully rescan all notes and rebuild the local database?
-
Is it possible that Zkool created an invalid or unintended change output when used with Ledger?
-
What is the correct way to restore access to the shielded funds in this scenario?
-
Where exactly does Zkool store its data on macOS, so I can perform a clean reinstall safely?
I can provide logs, screenshots, transaction IDs, and system details if needed.
Thank you for your time and assistance.
I see you opened Bug report · Issue #669 · hhanh00/zkool2 · GitHub
Do you prefer to continue there or here?
1 Like
Let’s continue there, on GitHub.
Ledger and @hanh worked together to create this procedure
https://support.ledger.com/es/article/connecting-a-ledger-signer-to-zkool-wallet
Check it out please leave your feedback
Well … They wrote the article and posted it…
1 Like
You can avoid shielded synchronization by making the account Transparent only.
Then recovery will only take a few seconds.
1 Like
I downloaded Zkool and imported Zcash from my Ledger Nano, did a test send on Nov 19 and it went through fine. Today I tried to send some Zcash to my new Trezor wallet after updating my Ledger Wallet and installing the newest Zkool. The transaction failed with the following error:
Transaction ID: failed to validate tx: WtxId(“private”), error: transaction did not pass consensus validation: Downcast from BoxError to redjubjub::Error failed: downcast to known transaction error type failed, original error: ScriptInvalid
Anyone encountered the same issue? Any idea how to resolve this?
Thanks for any help you can provide.
Folks, if you have an original era ZECWallet, that’s been a brick on your phone for years…
@pacu seems to have set up a redirect such that the phone will now point to an active lightwalletd server. Thanks @pacu et. al.!!!
This means that your app should be able to get past the first screen.
If you are in this situation you should:
Immediately write down your seed.
Do not try to recover your wallet, do not do anything else, do not pass go.
WRITE DOWN YOUR SEED
From there we will be able to help with subsequent recovery steps.
9 Likes
Where do we get this update?
The domain name has been redirected. The hard-coded URL in the app now points to an active server.
2 Likes
it was a DNS redirect so there’s nothing that you need to do other than BACKING UP YOUR SEED PHRASE
2 Likes