They state the problem as the wallet wont accept the password to decrypt the keys of which there are no decrypted backups and no seed backup. Key encryption has been enabled since v1 though I don’t use it and there’s no mention of a commit change. Also mentioned txs were attempted multiple times before the fault so it seems like it might be a corruption problem and suggested salvagewallet with a fullnode which I believe rebuilds the database. But whether or not it would execute properly with the keys encrypted idk though, assuming they copy the file beforehand, then there’s not much to lose but some time syncing.
Yeah but @nankuse8 said he is using LW Lite. That doesn’t use a full node. Maybe it is trying to share the same wallet.dat as an existing installation of zcashd? Personally, I would just recover from the secret key at this point and not fiddle with the installation anymore.
Yes lite but that it (salvagewallet) would require a new full node instance to try (if it even can be done) I don’t know the encryption method used for locking the wallet but yeah just trying to manually decrypt with another program is a good idea.
salvagewallet is a command from bitcoin-core, I don’t know if it even works with zcashd. zcashd wallets are not encrypted unless you run it in experimental mode. The encryption comes from ZW. It seems that there is confusion around which app owns which wallet files and that can’t be good ™.
I am not recommending to attempt decrypting the wallet file. Forget about this file. If OP knows the secret key (the stuff that begins with secret-key), then fire up a new installation and import it directly.