< jonatack>
instagibbs: i'm not quite sure what you are asking wrt labels. labels are set by the user in rpc getnewaddress or setlabel, and i use this functionality
< jonatack>
instagibbs: the label purpose is assigned by bitcoin core based on the address, and is currently usable as an optional filter in rpc listlabels
< jonatack>
the label purpose is either send or receive. in listtransactions, send or receive is returned as a category, and not part of the label field. this is how i would see the "purpose" being used.
< jonatack>
in getaddressinfo, there is no category field returned, but ismine instead. perhaps i'm confused, but it looks to me like purpose, category, and ismine are being used interchangeably
< jonatack>
anyone with context here, please enlighten me regarding the planned roadmap here
< jonatack>
nvm the comment on the terms being interchanngeable. to me txn category and address ismine make sense, but label purpose less so.
< bitcoin-git>
bitcoin/master 7d26357 Andrew Chow: rpc: require second argument only for scantxoutset start action
< bitcoin-git>
bitcoin/master a595011 Wladimir J. van der Laan: Merge #17728: rpc: require second argument only for scantxoutset start act...
< bitcoin-git>
[bitcoin] laanwj merged pull request #17728: rpc: require second argument only for scantxoutset start action (master...fix-scantxoutset-args) https://github.com/bitcoin/bitcoin/pull/17728
< elichai2>
Is there a cmd flag to tell bitcoind to ignore `bitcoin.conf`? or I need to remember to rename it back and forth whenever i'm benchmarking stuff?
< kinlo>
just point it to an empty file?
< wumpus>
maybe even -conf=/dev/null works :-)
< wumpus>
an empty file will definitely work though
< elichai2>
thx
< bitcoin-git>
[bitcoin] jnewbery opened pull request #17750: util: change GetWarnings parameter to bool (master...2019-12-getwarnings) https://github.com/bitcoin/bitcoin/pull/17750
< phantomcircuit>
instagibbs, labels are exactly the same