< hebasto>
promag: ryanofsky: why Q_DECLARE_METATYPE(interfaces::WalletBalances) works for queued connections even w/o qRegisterMetaType<interfaces::WalletBalances>() as required by Qt docs?
< bitcoin-git>
[bitcoin] cryptogopher opened pull request #16431: Allow proper linearize-data execution on pruned node (master...master) https://github.com/bitcoin/bitcoin/pull/16431
< achow101>
sipa: meshcollider: any thoughts on how labels should work with imported descriptors? Issue is with labels being applied to newly generated addresses in a descriptor that is set as "active". For some context: https://github.com/achow101/bitcoin/pull/4#discussion_r305564366
< sipa>
achow101: i think labels should just remain per address like now (not per descriptor or anything like that)
< sipa>
oh for imported ones... arguably there really isn't a label for an imported ranged descriptor
< achow101>
well the label could apply to everything from the descriptor. I believe that's what we do in importmulti
< sipa>
yeah
< sipa>
though i'm not sure it's that useful
< achow101>
but I don't think it makes sense for new addresses from the imported descriptor to have this preapplied label
< sipa>
perhaps a descriptor could have a diefault label, or even a label template
< sipa>
*default
< sipa>
so that newly constructed addresses from that descriotor get that label by default, if no other is requested
< achow101>
meh.
< sipa>
but i'm not sure there is demand for that
< sipa>
yeah, agree.
< achow101>
not allowing ranged descriptors to have labels is making more and more sense to me
< achow101>
if someone wants labels on their old addresses, they can set them after the import