Hi, my full node has been forced to zcashd 6.2.0. After restoring my wallet.dat file from backup, I have 2 sapling shielded addresses (create NOVEMBER 2023) that I can see “zip32 keypath” with “zcash-cli listaddresses”. However, that seems to be the end of the road. No balance is given and I seem unable to manipulate these addresses in any other way, resulting from a lack of understanding in what exactly is going on here.
Anyway, I’m getting the idea that YWALLET is what I need to do. However, I have searched and been unable to find anything that would explain how to use YWALLET with an old zcashd wallet.dat file. Is there a link I am missing that you could post to this thread?
Have a look here and maybe you can turn on some deprecated RPC’s to make it work still.
Each feature in the table below may be enabled by adding -allowdeprecated= to the CLI arguments when starting the node, or by adding an allowdeprecated= line to zcash.conf
Another option is to get a hold of the ZeWIF team, they are dialed in with wallet formats and may be able to assist
Yes, I have reconsidered that page and I have added the deprecated commands I would like to use to my startup. It would not let me add z_sendmany as a deprecated command, which surprised me.
Anyway, I am reindexing with my backup wallet in place and when that’s completed I will be back on here. Thanks for the suggestion.
Ywallet can’t use the wallet.dat directly, only import seeds or keys (or Ywallet backups). Sapling uses private spending keys and both keys could be imported into Ywallet as two seperate accounts to recover them individually. Seed import may be trickier and require the Sweep option.
Zwif could be a future option as it aims to be compatible with this file but in some wallet framework. Zallet (assumedly) would be compatible as it intends to replace the zcashd internal wallet but it’s a work in progress (and may leverage zwif for that functionality) but in the meantime, you can use Ywallet and quickly recover.
The 2023 Bdays mean it will fully sync in just a few minutes (meaning you can actually just test out if you can recover it in Ywallet waaay before zcashd will complete the reindex)
Hey thanks, I’m sure you’re probably tired of going over this. I have tried to find something that outlines this process in general but have failed and so that’s why I’m bugging here.
Anyway, I was able to use
zcash_cli z_exportwallet
and I have captured that output. My sapling address “zs…” is there, along with text “secret-extended-key” and I’m guessing I need to get this into YWallet somehow. However, that process has eluded me. Is there somewhere that outlines what I am trying to do? Again, I have searched on my own for this but come up with ZNOTHING.
On the Ywallet account creation screen it asks for a seed or a key in the “restore an account” option. The sapling keys do begin with “secret-extended” prefix and they get copy and pasted in the same way the seed does. The zcashd account system is different from Ywallet so deriving these same addresses from the single seed might require using the Ywallet sweep tool. Importing the keys into seperate accounts will ensure you get the proper addresses.
I appreciate dismad’s YWallet documentation reference, these were the exact instructions I accessed when attempting to use the mnemonic generated by
zcash-cli exportwallet
My hunch is, they’re working on the YWallet UX…as it stands currently, there isn’t much in the way of success/failure in these processes.
Furthermore, from other reading, I’m guessing this mnemonic method isn’t going to work.
The good news is, after reading Auto’s subsequent post, I was able to determine that the string YWallet wants SHOULD INCLUDE “secret-extended” which was not apparent to me before.
Once I pasted that into YWallet, it seems to have “done something” (not judging) as I can now see these sapling addresses in the accounts I created for them.
Balance still zero, but I’m thinking some rescanning is in order that will take care of that.
1- inputting the mnemonic for my sapling addresses and generated by
zcash-cli exportwallet (zcashd 6.2)
into YWallet 1.8.1 did not work. YWallet did not explicity inform of the failure, however, as Auto had clearly stated that it wouldn’t work, I didn’t waste alot of time trying to get it to work.
2- Further following Auto’s instructions, I created an account for each sapling address I wanted to import to YWallet 1.8.1. During the import, I was sure to paste the privkey INCLUDING the “secret-extended” prefix into YWallet. Then, I started a rescan in YWallet and it’s beautiful progress bar appeared across the top, 0% on the left to 100% on the right.
Incidentally, I could see the rescan progress bar intermittently flickering as I tried in vain to use the mnemonic in my attempt (1) above…forget it. YWallet wants to do it, but it can’t! If you don’t see the progress bar moving from left to right over a couple of hours and instead see it flickering off and on…it’s a fail.
I hope this helps someone else, thanks again Auto and dismad.
Hmm, when I searched “Ywallet” and took the link for ywallet.app I wound up being offered 1.8.1 from November 24. It appears there has been development after this release? 1.13.4? I’m not sure if 1.13.4 would have done what I needed but it seems a little strange.
When I start connecting these dots I don’t like where I wind up.
zcashd wallet deprecations followed by, “use YWallet for that now” and then a stale YWallet download is not a good look. Furthermore, isn’t ZCASH converting it’s consensus mechanism from POWork to POStake? ZKsnarks and the shielded pool are fantastic innovations but the roadmap since sapling has been a little shaky. I had been thinking things were under control and that I was unreasonable but this episode strains credulity.