12024-05-19T01:00:49  *** test_ <test_!flooded@gateway/vpn/protonvpn/flood/x-43489060> has joined #bitcoin-core-dev
  22024-05-19T01:04:24  *** flooded <flooded!flooded@gateway/vpn/protonvpn/flood/x-43489060> has quit IRC (Ping timeout: 260 seconds)
  32024-05-19T01:12:09  *** zeropoint <zeropoint!~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net> has quit IRC (Quit: leaving)
  42024-05-19T01:43:39  *** nlhcd <nlhcd!~private@2603:7000:1300:1302::1222> has joined #bitcoin-core-dev
  52024-05-19T02:59:23  *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 264 seconds)
  62024-05-19T03:01:04  *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
  72024-05-19T03:06:48  *** nlhcd <nlhcd!~private@2603:7000:1300:1302::1222> has quit IRC (Quit: Quit)
  82024-05-19T03:36:16  *** zeropoint <zeropoint!~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net> has joined #bitcoin-core-dev
  92024-05-19T04:01:01  *** cmirror <cmirror!~cmirror@4.53.92.114> has quit IRC (Remote host closed the connection)
 102024-05-19T04:01:32  *** cmirror <cmirror!~cmirror@4.53.92.114> has joined #bitcoin-core-dev
 112024-05-19T04:47:56  *** zeropoint <zeropoint!~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net> has quit IRC (Quit: leaving)
 122024-05-19T06:18:45  *** flooded <flooded!flooded@gateway/vpn/protonvpn/flood/x-43489060> has joined #bitcoin-core-dev
 132024-05-19T06:22:12  *** test_ <test_!flooded@gateway/vpn/protonvpn/flood/x-43489060> has quit IRC (Ping timeout: 260 seconds)
 142024-05-19T06:47:08  *** puchka1101 <puchka1101!~puchka@185.203.122.22> has quit IRC (Ping timeout: 268 seconds)
 152024-05-19T07:10:22  *** puchka <puchka!~puchka@185.203.122.35> has joined #bitcoin-core-dev
 162024-05-19T08:10:54  *** Guest8 <Guest8!~Guest8@109.110.28.168> has joined #bitcoin-core-dev
 172024-05-19T08:11:42  *** Guest8 <Guest8!~Guest8@109.110.28.168> has quit IRC (Client Quit)
 182024-05-19T08:19:31  *** Lockesmith <Lockesmith!~user@gateway/tor-sasl/lockesmith> has quit IRC (Remote host closed the connection)
 192024-05-19T08:19:31  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
 202024-05-19T08:23:11  *** Lockesmith <Lockesmith!~user@gateway/tor-sasl/lockesmith> has joined #bitcoin-core-dev
 212024-05-19T08:27:10  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
 222024-05-19T08:32:43  *** Talkless <Talkless!~Talkless@mail.dargis.net> has joined #bitcoin-core-dev
 232024-05-19T08:57:45  *** test_ <test_!flooded@gateway/vpn/protonvpn/flood/x-43489060> has joined #bitcoin-core-dev
 242024-05-19T09:01:20  *** flooded <flooded!flooded@gateway/vpn/protonvpn/flood/x-43489060> has quit IRC (Ping timeout: 260 seconds)
 252024-05-19T10:51:50  *** adil1 <adil1!~Thunderbi@2402:d000:8134:f58:3498:9e01:833c:d054> has joined #bitcoin-core-dev
 262024-05-19T10:52:24  *** qxs <qxs!~qxs@gateway/tor-sasl/qxs> has joined #bitcoin-core-dev
 272024-05-19T11:39:57  <laanwj> it looks like the "Drahtbot GUIX build requested" label isn't working
 282024-05-19T11:48:45  *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has joined #bitcoin-core-dev
 292024-05-19T12:18:33  <pinheadmz> Is there a single RPC call to determine the change output of a transaction from my own wallet? So far im calling gettransaction then looping through vout with getaddressinfo
 302024-05-19T12:33:10  *** Chris_Stewart_5 <Chris_Stewart_5!~Chris_Ste@static-198-54-135-88.cust.tzulo.com> has quit IRC (Ping timeout: 246 seconds)
 312024-05-19T12:33:35  *** Chris_Stewart_5 <Chris_Stewart_5!~Chris_Ste@static-198-54-135-88.cust.tzulo.com> has joined #bitcoin-core-dev
 322024-05-19T12:34:51  *** adil1 <adil1!~Thunderbi@2402:d000:8134:f58:3498:9e01:833c:d054> has quit IRC (Quit: adil1)
 332024-05-19T13:16:39  *** nlhcd <nlhcd!~private@2603:7000:1300:1302::1222> has joined #bitcoin-core-dev
 342024-05-19T14:15:43  *** flooded <flooded!flooded@gateway/vpn/protonvpn/flood/x-43489060> has joined #bitcoin-core-dev
 352024-05-19T14:19:18  *** test_ <test_!flooded@gateway/vpn/protonvpn/flood/x-43489060> has quit IRC (Ping timeout: 252 seconds)
 362024-05-19T14:22:04  *** ghost43_ <ghost43_!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
 372024-05-19T14:22:04  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
 382024-05-19T14:31:57  *** ghost43_ <ghost43_!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
 392024-05-19T14:34:58  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
 402024-05-19T14:38:10  *** Lockesmith <Lockesmith!~user@gateway/tor-sasl/lockesmith> has quit IRC (Ping timeout: 260 seconds)
 412024-05-19T14:39:46  *** Lockesmith <Lockesmith!~user@gateway/tor-sasl/lockesmith> has joined #bitcoin-core-dev
 422024-05-19T14:49:39  *** ___nick___ <___nick___!~quassel@cpc68290-cdif17-2-0-cust24.5-1.cable.virginm.net> has joined #bitcoin-core-dev
 432024-05-19T15:01:35  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Quit: Leaving)
 442024-05-19T15:02:58  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
 452024-05-19T15:06:01  *** Zenton <Zenton!~user@user/zenton> has quit IRC (Ping timeout: 268 seconds)
 462024-05-19T15:14:30  <furszy> pinheadmz: there isn't a simple way. gettransaction 'details' does not include change outputs.
 472024-05-19T15:15:12  <pinheadmz> should it? or if verbose, `decoded` could include the ischange flag in the vout array
 482024-05-19T15:16:15  <furszy> yeah, could add a 'include_change' flag.
 492024-05-19T15:16:22  <furszy> we are already doing it everywhere else
 502024-05-19T15:17:58  <laanwj> i think it'd make sense to add that to the verbose output (assuming it doesn't make "decoding" much less efficient), but include_change does something different, it shows change outputs where they'd normaly not be shown
 512024-05-19T15:19:43  <furszy> "it shows change outputs where they'd normaly not be shown" thats what the user would expect when it provides the flag.
 522024-05-19T15:20:48  <laanwj> then i'm misunderstanding the point here, i thought it did show all change and non-change outputs, and @pinheadmz wants to add a flag (to the output) to distinguish what is what
 532024-05-19T15:21:50  <furszy> gettransaction 'details' does not retrieve the change outputs. Thus why he is providing the verbose=1 flag to decode the entire tx, then loop through the vouts etc
 542024-05-19T15:22:10  <laanwj> ok
 552024-05-19T15:25:10  *** nicky <nicky!~nicky@191.165.202.115> has joined #bitcoin-core-dev
 562024-05-19T15:28:39  <furszy> internally; gettransaction loops over the outputs, organizes the info and returns a record for each output owned by the wallet. So, he is basically doing the work twice.
 572024-05-19T15:30:36  <pinheadmz> so perhaps makes the most sense to add "category":"change" in the "details" array
 582024-05-19T15:31:44  <pinheadmz> i dont think that would even necessitate a flag since we're already examining each txout?
 592024-05-19T15:32:37  <furszy> the 'change' category sounds good to me.
 602024-05-19T15:33:50  <furszy> the flag is at the RPC level, because we would be showing something that wasn't previously shown (at least not in this command).
 612024-05-19T15:49:12  *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 260 seconds)
 622024-05-19T15:51:08  *** ___nick___ <___nick___!~quassel@cpc68290-cdif17-2-0-cust24.5-1.cable.virginm.net> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
 632024-05-19T15:53:06  <pinheadmz> hm yeah ok (about the flag) although i dunno how that could break a consumer of this RPC, its not like adding extra "receive" items...
 642024-05-19T15:53:22  *** ___nick___ <___nick___!~quassel@cpc68290-cdif17-2-0-cust24.5-1.cable.virginm.net> has joined #bitcoin-core-dev
 652024-05-19T15:54:41  *** ___nick___ <___nick___!~quassel@cpc68290-cdif17-2-0-cust24.5-1.cable.virginm.net> has quit IRC (Client Quit)
 662024-05-19T15:56:40  *** Zenton <Zenton!~user@user/zenton> has joined #bitcoin-core-dev
 672024-05-19T15:56:41  *** ___nick___ <___nick___!~quassel@cpc68290-cdif17-2-0-cust24.5-1.cable.virginm.net> has joined #bitcoin-core-dev
 682024-05-19T16:17:05  *** gmaxwell <gmaxwell!~gmaxwell@user/gmaxwell> has left #bitcoin-core-dev
 692024-05-19T16:30:37  *** nlhcd <nlhcd!~private@2603:7000:1300:1302::1222> has quit IRC (Quit: Quit)
 702024-05-19T16:31:21  *** nlhcd <nlhcd!~private@2603:7000:1300:1302::1222> has joined #bitcoin-core-dev
 712024-05-19T16:33:03  *** nlhcd <nlhcd!~private@2603:7000:1300:1302::1222> has quit IRC (Remote host closed the connection)
 722024-05-19T16:36:16  *** javi404_ is now known as javi404
 732024-05-19T17:09:23  *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has left #bitcoin-core-dev (Closing Window)
 742024-05-19T17:23:22  *** qxs <qxs!~qxs@gateway/tor-sasl/qxs> has quit IRC (Ping timeout: 260 seconds)
 752024-05-19T17:25:13  *** qxs <qxs!~qxs@gateway/tor-sasl/qxs> has joined #bitcoin-core-dev
 762024-05-19T17:29:37  *** _cold is now known as cold
 772024-05-19T17:30:33  *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
 782024-05-19T18:03:51  *** zeropoint <zeropoint!~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net> has joined #bitcoin-core-dev
 792024-05-19T18:15:06  *** zeropoint <zeropoint!~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net> has quit IRC (Quit: leaving)
 802024-05-19T18:41:18  *** Lockesmith <Lockesmith!~user@gateway/tor-sasl/lockesmith> has quit IRC (Ping timeout: 260 seconds)
 812024-05-19T19:00:58  *** gnaf <gnaf!~pi@109.36.130.102> has joined #bitcoin-core-dev
 822024-05-19T19:02:25  *** Talkless <Talkless!~Talkless@mail.dargis.net> has quit IRC (Quit: Konversation terminated!)
 832024-05-19T19:08:04  *** saffi <saffi!~saffi@203.215.167.41> has joined #bitcoin-core-dev
 842024-05-19T19:17:18  *** test_ <test_!flooded@gateway/vpn/protonvpn/flood/x-43489060> has joined #bitcoin-core-dev
 852024-05-19T19:21:35  *** flooded <flooded!flooded@gateway/vpn/protonvpn/flood/x-43489060> has quit IRC (Ping timeout: 264 seconds)
 862024-05-19T19:27:25  *** flooded <flooded!flooded@gateway/vpn/protonvpn/flood/x-43489060> has joined #bitcoin-core-dev
 872024-05-19T19:30:36  *** test_ <test_!flooded@gateway/vpn/protonvpn/flood/x-43489060> has quit IRC (Ping timeout: 252 seconds)
 882024-05-19T19:33:41  *** test_ <test_!flooded@gateway/vpn/protonvpn/flood/x-43489060> has joined #bitcoin-core-dev
 892024-05-19T19:34:08  *** gnaf <gnaf!~pi@109.36.130.102> has quit IRC (Read error: Connection reset by peer)
 902024-05-19T19:37:17  *** flooded <flooded!flooded@gateway/vpn/protonvpn/flood/x-43489060> has quit IRC (Ping timeout: 240 seconds)
 912024-05-19T19:43:48  *** saffi <saffi!~saffi@user/saffi> has quit IRC (Quit: Connection closed)
 922024-05-19T19:44:11  *** saffi <saffi!~saffi@user/saffi> has joined #bitcoin-core-dev
 932024-05-19T19:48:24  <saffi> Hi Everyone !
 942024-05-19T19:48:58  <saffi> https://github.com/bitcoin/bitcoin/pull/29500
 952024-05-19T19:49:48  <saffi> I was going through this PR for python testcases and what it actually does is that it replaces all the != operator with assert not equal. in line with this I see there other operators like greater than and less than in the testcases will it make sense to also replace those with assert greater operators ?
 962024-05-19T20:04:05  *** ___nick___ <___nick___!~quassel@cpc68290-cdif17-2-0-cust24.5-1.cable.virginm.net> has quit IRC (Ping timeout: 240 seconds)
 972024-05-19T20:04:28  *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 260 seconds)
 982024-05-19T20:05:47  *** nlhcd <nlhcd!~private@2603:7000:1300:1302::1222> has joined #bitcoin-core-dev
 992024-05-19T20:05:48  *** nlhcd1 <nlhcd1!~private@2603:7000:1300:1302::1222> has joined #bitcoin-core-dev
1002024-05-19T20:08:34  *** nlhcd <nlhcd!~private@2603:7000:1300:1302::1222> has quit IRC (Remote host closed the connection)
1012024-05-19T20:08:40  *** nlhcd1 <nlhcd1!~private@2603:7000:1300:1302::1222> has quit IRC (Client Quit)
1022024-05-19T20:25:54  *** Guest24 <Guest24!~Guest24@194.59.28.227> has joined #bitcoin-core-dev
1032024-05-19T20:27:35  *** Guest24 <Guest24!~Guest24@194.59.28.227> has quit IRC (Client Quit)
1042024-05-19T21:05:30  *** SpellChecker <SpellChecker!~SpellChec@user/SpellChecker> has quit IRC (Ping timeout: 260 seconds)
1052024-05-19T21:06:02  *** SpellChecker <SpellChecker!~SpellChec@user/SpellChecker> has joined #bitcoin-core-dev
1062024-05-19T21:28:24  <saffi> guys ?
1072024-05-19T21:36:13  *** PaperSword <PaperSword!~Thunderbi@securemail.qrsnap.io> has joined #bitcoin-core-dev
1082024-05-19T21:38:56  *** Guest60 <Guest60!~Guest69@syn-172-091-172-231.res.spectrum.com> has joined #bitcoin-core-dev
1092024-05-19T21:40:27  *** Guest60 <Guest60!~Guest69@syn-172-091-172-231.res.spectrum.com> has left #bitcoin-core-dev
1102024-05-19T21:50:23  *** gnaf <gnaf!~pi@109.36.130.102> has joined #bitcoin-core-dev
1112024-05-19T21:55:26  *** qxs <qxs!~qxs@gateway/tor-sasl/qxs> has quit IRC (Ping timeout: 260 seconds)
1122024-05-19T21:55:27  *** gnaf <gnaf!~pi@109.36.130.102> has quit IRC (Quit: Konversation terminated!)
1132024-05-19T21:56:26  *** qxs <qxs!~qxs@gateway/tor-sasl/qxs> has joined #bitcoin-core-dev
1142024-05-19T22:12:14  *** qxs <qxs!~qxs@gateway/tor-sasl/qxs> has quit IRC (Ping timeout: 260 seconds)
1152024-05-19T22:12:49  *** qxs <qxs!~qxs@gateway/tor-sasl/qxs> has joined #bitcoin-core-dev
1162024-05-19T22:47:49  *** Guest33 <Guest33!~Guest33@2401:4900:1c71:3ed:3565:904:b23a:5cc0> has joined #bitcoin-core-dev
1172024-05-19T22:49:40  *** saffi <saffi!~saffi@user/saffi> has quit IRC (Ping timeout: 260 seconds)
1182024-05-19T22:50:06  *** Guest33 <Guest33!~Guest33@2401:4900:1c71:3ed:3565:904:b23a:5cc0> has quit IRC (Client Quit)
1192024-05-19T22:58:12  *** achow101 <achow101!~achow101@user/achow101> has quit IRC (Remote host closed the connection)
1202024-05-19T22:58:45  *** achow101 <achow101!~achow101@user/achow101> has joined #bitcoin-core-dev