-
Notifications
You must be signed in to change notification settings - Fork 288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using an unencrypted read-only wallet, pressing "Create Unsigned", shows "This operation needs you wallet passphrase to unlock the wallet" #772
Comments
Are you able to reproduce this on master? I am unable to reproduce this issue. On regtest, I created a new wallet with private keys disabled and was able to use the "Create Unsigned" button as expected. This is likely an issue specific to your wallet. Is it possible that you had used it with unreleased software or an unmerged PR? Would you be willing to share this wallet file? This is possibly related to #631, perhaps the fix was incomplete. |
If your watchonly was encrypted with an older version of Bitcoin Core that accidentally allowed that, then it is possible to hit this error. The obvious solution is to enter the password. If you don't remember it, and are feeling particularly adventurous, you can open the wallet.dat file with your choice of sqlite tool, find the record beginning with |
… wallets 69e95c2 tests: Test cleanup of mkeys from wallets without privkeys (Andrew Chow) 2b9279b wallet: Remove unused encryption keys from watchonly wallets (Andrew Chow) 813a16a wallet: Add HasCryptedKeys (Andrew Chow) Pull request description: An earlier version allowed users to create watchonly wallets (wallets without private keys) that were "encrypted". Such wallets would have a stored encryption keys, but nothing would actually be encrypted with them. This can cause unexpected behavior such as bitcoin-core/gui#772. We can detect such wallets as they will have the disable private keys flag set, no encrypted keys, and encryption keys. For such wallets, we can remove those encryption keys thereby avoiding any issues that may result from this unexpected situation. ACKs for top commit: sipa: utACK 69e95c2. laanwj: Code review re-ACK 69e95c2 furszy: Code review ACK 69e95c2 Tree-SHA512: 901932cd709c57e66c598f011f0105a243b5a8b539db2ef3fcf370dca4cf35ae09bc1110e8fca8353be470f159468855a4dd96b99bc9c1112adc86ccc50e1b9d
Is there an existing issue for this?
Current behaviour
When using an unencrypted, read-only (descriptor) wallet, when trying to make a new transaction and pressing the "Create Unsigned" button, a dialog is shown with the message "This operation needs you wallet passphrase to unlock the wallet". There is no wallet passphrase as I have never created it. It's also not possible to enter the empty passphrase as the submit button is grayed out.
Expected behaviour
"Create Unsigned" creates an unsigned PSBT.
Steps to reproduce
Relevant log output
no log output without debugging enabled
How did you obtain Bitcoin Core
Package manager
What version of Bitcoin Core are you using?
v25.1
Operating system and version
Guix
Machine specifications
No response
The text was updated successfully, but these errors were encountered: