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
Bech32m unavailable for encrypted wallets #571
Comments
I'm able to reproduce. For some reason in the GUI we're not producing a taproot descriptor when encryption is enabled (see Thanks for catching that @eriknylund. |
Uh no never mind, it does generate the descriptor. I selected the wrong wallet in the console. Pfew. So it's a pure UI issue, investigating... Restarting Bitcoin Core does add Bech32m to the menu. Maybe some reference to the receive screen got borked in the passphrase dialogs? See #509. @eriknylund if you're not seeing Bech32m after a restart, are you sure you checked the "Descriptor" box (it's selected by default)? You can run |
Something sure looks borked. I cannot even generate receive addresses on the other three types, the
|
@eriknylund this last screenshot is from after a restart? |
@Sjors Correct. However, this could also be the wallet that I started seeing problems with as I continued testing. See comment bitcoin/bitcoin#24501 (comment) I tried creating a new encrypted wallet and there the receive address button is enabled, yet I still only have three options, missing Taproot.
|
A fixed has been suggested in bitcoin/bitcoin#24711. |
… encrypted wallets 0c12f01 wallet: Postpone NotifyWalletLoaded() for encrypted wallets (Hennadii Stepanov) aeee419 wallet, refactor: Add wallet::NotifyWalletLoaded() function (Hennadii Stepanov) Pull request description: Fixes bitcoin-core/gui#571. `CWallet::Create()` notifies about wallet loading too early, that results the notification goes before `DescriptorScriptPubKeyMan`s were created and added to an encrypted wallet. And `interfaces::Wallet::taprootEnabled()` in https://github.com/bitcoin/bitcoin/blob/ecf692b466860f44334a1da967fc2559da913bec/src/qt/receivecoinsdialog.cpp#L100-L102 erroneously returns `false` for just created encrypted descriptor wallets. ACKs for top commit: Sjors: utACK 0c12f01 achow101: ACK 0c12f01 Tree-SHA512: 2694bacd12748cd5f6c95d9d3bf8bcf4502ee67fecd8d057f33236b72069c61401b08f49deb013fc71c3f1e51ae16bdfd827ddcbc2a083d7044589be7a78982e
#459 introduced an ability to chose Bech32m address type in the GUI.
On master and on v23.0rc2 this option is unavailable for a just created encrypted wallet, at least on Ubuntu 22.04.
For macOS a slightly different behavior reported.
See details:
The text was updated successfully, but these errors were encountered: