Bech32m unavailable for encrypted wallets

[hebasto]

#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:

• v23.0 testing bitcoin/bitcoin#24501 (comment)
• v23.0 testing bitcoin/bitcoin#24501 (comment)

[hebasto]

cc @Sjors @promag @achow101

[Sjors]

I'm able to reproduce. For some reason in the GUI we're not producing a taproot descriptor when encryption is enabled (see listdescriptors). This does not happen for wallets created via the createwallet RPC.

Thanks for catching that @eriknylund.

[Sjors]

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 getwalletinfo in the Console (make sure to select the correct wallet in the console too) and look if you see "descriptors": true. Only descriptor wallets have Taproot support.

[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 getwalletinfo in the Console (make sure to select the correct wallet in the console too) and look if you see "descriptors": true. Only descriptor wallets have Taproot support.

Something sure looks borked. I cannot even generate receive addresses on the other three types, the Create new receiving address button is disabled.

This is the output from the Console:

{
  "walletname": "Mainnet Wallet 1 Encrypted",
  "walletversion": 169900,
  "format": "sqlite",
  "balance": 0.00000000,
  "unconfirmed_balance": 0.00000000,
  "immature_balance": 0.00000000,
  "txcount": 0,
  "keypoolsize": 0,
  "keypoolsize_hd_internal": 0,
  "unlocked_until": 0,
  "paytxfee": 0.00000000,
  "private_keys_enabled": true,
  "avoid_reuse": false,
  "scanning": false,
  "descriptors": true,
  "external_signer": false
}

[Sjors]

@eriknylund this last screenshot is from after a restart?

[eriknylund]

@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.

getwalletinfo
{
  "walletname": "Mainnet Wallet 2 Encrypted",
  "walletversion": 169900,
  "format": "sqlite",
  "balance": 0.00000000,
  "unconfirmed_balance": 0.00000000,
  "immature_balance": 0.00000000,
  "txcount": 0,
  "keypoolsize": 3999,
  "keypoolsize_hd_internal": 4000,
  "unlocked_until": 0,
  "paytxfee": 0.00000000,
  "private_keys_enabled": true,
  "avoid_reuse": false,
  "scanning": false,
  "descriptors": true,
  "external_signer": false
}

[hebasto]

A fixed has been suggested in bitcoin/bitcoin#24711.