19:00:13 #startmeeting 19:00:13 Meeting started Fri Nov 8 19:00:13 2019 UTC. The chair is meshcollider. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:13 Useful Commands: #action #agreed #help #info #idea #link #topic. 19:00:19 #bitcoin-core-dev Wallet Meeting: wumpus sipa gmaxwell jonasschnelli morcos luke-jr sdaftuar jtimon cfields petertodd kanzure bluematt instagibbs phantomcircuit codeshark michagogo marcofalke paveljanik NicolasDorier jl2012 achow101 meshcollider jnewbery maaku fanquake promag provoostenator aj Chris_Stewart_5 dongcarl gwillen jamesob ken281221 ryanofsky gleb moneyball 19:00:30 hi 19:00:31 hi 19:00:31 hi 19:00:37 Topics? 19:00:47 hi 19:00:59 how goes the wallet boxes review? 19:02:09 Suggested topic: deprecating getaddressinfo label in favor of labels, and adding multiple labels associated with an address (currently only one) 19:02:13 hi 19:03:31 jonatack: is it useful to have multiple labels with an address? 19:03:57 #topic deprecating getsddressinfo label (jonatack) 19:04:01 oh yeah, clocks changed 19:04:02 achow101: it seems to have been planned to be done 19:04:20 being the reason for adding the labels field? 19:04:31 in addition to the label field 19:04:47 which causes app developer confusion 19:04:54 see rationale in https://github.com/bitcoin/bitcoin/pull/17283/ 19:05:18 oh, i see 19:05:20 app devs wonder which field should be consumed, label or labels[] 19:06:16 oh 19:06:41 I didn't even notice labels was added 19:07:06 me either 19:07:14 was added by jnewbery i believe? https://github.com/bitcoin/bitcoin/pull/12892 19:07:38 er, label 19:08:07 right, label[] has no tests, so added in 17283 19:08:17 labels[]* 19:08:43 ack deprecating label 19:08:48 is there a use case for having multiple labels per address? 19:09:07 jnewbery: what use case did you have in mind 19:09:09 i don't object, but just because we merged an API that is extensible enough to support it doesn't mean it's needed 19:09:31 as in: support can be added whenever there is a use case for it 19:09:32 meshcollider: just refreshing my memory now! 19:10:31 logically to me, it makes sense to be able to associate multiple labels to an address 19:10:51 From 12892: "labels are 19:10:51 associated with addresses, instead of addresses associated with labels. (unlike 19:10:54 with accounts.)" 19:11:27 I picked up that work from an older wumpus PR, and I can't remember all the details right now 19:11:33 I mean, it makes sense if people want to do short labels like GitHub does for PRs 19:11:33 some reasons in https://github.com/bitcoin/bitcoin/pull/12892#issuecomment-379016369 19:11:37 I'll review jonatack's suggested changes in #17283 19:11:39 https://github.com/bitcoin/bitcoin/issues/17283 | rpc: improve getaddressinfo test coverage, help, code docs by jonatack · Pull Request #17283 · bitcoin/bitcoin · GitHub 19:11:46 Yeah that's true actually 19:12:04 when I do my taxes, I take the label and match multiple regexs to extract metadata - having separate labels could simplify it 19:12:16 if it's not an enormous change to support multiple labels then concept ack 19:12:25 that being said, there is always a primary label, so maybe we should keep / should have kept it 19:12:41 There's no concept of a primary label 19:12:43 eg, "bought my pet hamster" isn't likely to have more than one tx 19:12:51 jnewbery: maybe there should be 19:13:43 Depends if label is for categorising or label is for describing I guess 19:14:26 I've always used it for the latter, with the former thrown in 19:14:48 categories without a description has limited usability 19:15:23 I'd suggest instead a "notes" with the description part, but .. we've had label for years 19:15:24 jonatack: I'll take a look at the PR and give concept feedback 19:15:36 luke-jr: say, ability to designate one of the labels as a primary, and one only? 19:15:38 I think having multiple labls would be somewhat invasive due to all of the legacy accounts stuff associated with labels 19:15:53 jnewbery: ty 19:16:34 I mean, I don't think it matters if the distinction is in the code. Supporting multiple labels allows the user to do whatever they like with them, I don't think it needs a "primary" one 19:17:31 Ok yeah this can be discussed in the PR 19:17:43 Other topics? 19:17:44 a) it seems we should decide re multiple labels before deprecating 19:17:56 jonatack: maybe 19:18:06 achow101: maybe rename "labels" to "tags"? 19:18:17 b) back to a) :D 19:18:21 Please not another rename lol 19:19:04 what's the "labels" PR? 19:19:14 #12892 19:19:17 https://github.com/bitcoin/bitcoin/issues/12892 | [wallet] [rpc] introduce label API for wallet by jnewbery · Pull Request #12892 · bitcoin/bitcoin · GitHub 19:19:58 PR description doesn't suggest it does that.. :/ 19:21:33 luke-jr: i don't think there's a PR yet 19:21:38 ok, so it adds a "labels" array with only one possible value 19:21:53 next topic? 19:22:19 achow101: is there anything you want to discuss about boxes or just review beg? 19:22:30 review beg 19:22:40 (yes it is indeed https://github.com/bitcoin/bitcoin/pull/12892 despite the PR name) 19:23:02 luke-jr: right 19:23:28 #16944 is finally nearly ready too which is nice, hopefully we can get it in after provoostenator rebases 19:23:30 https://github.com/bitcoin/bitcoin/issues/16944 | gui: create PSBT with watch-only wallet by Sjors · Pull Request #16944 · bitcoin/bitcoin · GitHub 19:24:44 Alright no other topics then :) 19:24:49 #endmeeting