< sipa>
wumpus: the popups i saw were mostly for bad configuration options
< sipa>
so i guess init errors
< wumpus>
ah, right
< wumpus>
having the test screengrab and read out error dialogs probably goes a bit too far, so invalid option tssts should probably be skipped for the GUI
< gribble>
https://github.com/bitcoin/bitcoin/issues/17373 | wallet: Various fixes and cleanup to keypool handling in LegacyScriptPubKeyMan and CWallet by achow101 . Pull Request #17373 . bitcoin/bitcoin . GitHub
< bitcoin-git>
bitcoin/master 9fcf8ce Andrew Chow: Rename Keep/ReturnKey to Keep/ReturnDestination and remove the wrapper
< bitcoin-git>
bitcoin/master 65833a7 Andrew Chow: Add OutputType and CPubKey parameters to KeepDestination
< bitcoin-git>
[bitcoin] fanquake merged pull request #17373: wallet: Various fixes and cleanup to keypool handling in LegacyScriptPubKeyMan and CWallet (master...wallet-box-pr-6) https://github.com/bitcoin/bitcoin/pull/17373
< bitcoin-git>
[bitcoin] practicalswift opened pull request #17685: tests: Fix bug in the descriptor parsing fuzzing harness (descriptor_parse) (master...fix-descriptor_parse-fuzzing-harness) https://github.com/bitcoin/bitcoin/pull/17685
< instagibbs>
achow101 needs a rebase :)
< jonatack>
wallet meeting?
< achow101>
I think meshcollider isn't around
< achow101>
Does anyone have any wallet meeting topics? otherwise we can just skip this week's
< sipa>
very short question: what do people think of permitting a list of public keys as public key expression in a descriptor?
< sipa>
so you could have sh(wsh({03.....,02.....,03.....,....})) for example
< achow101>
seems reasonable
< sipa>
it means you can pre-expand other key derivation schemes into descritptors... though perhaps very long ones
< Talkless>
jonatack: I've heard about "wallet meetings", do they have separate channel like PR club?
< achow101>
Talkless: no, they happen here. meshcollider isn't here today and it doesn't seem like there would be much to say about it, so I didn't start the meeting