--- Log opened Sun May 19 00:00:59 2024
00:10 -!- puchka [~puchka@185.203.122.35] has joined #bitcoin-core-dev
01:10 -!- Guest8 [~Guest8@109.110.28.168] has joined #bitcoin-core-dev
01:11 -!- Guest8 [~Guest8@109.110.28.168] has quit [Client Quit]
01:19 -!- Lockesmith [~user@gateway/tor-sasl/lockesmith] has quit [Remote host closed the connection]
01:19 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
01:23 -!- Lockesmith [~user@gateway/tor-sasl/lockesmith] has joined #bitcoin-core-dev
01:27 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-dev
01:32 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev
01:57 -!- test_ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
02:01 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 260 seconds]
03:51 -!- adil1 [~Thunderbi@2402:d000:8134:f58:3498:9e01:833c:d054] has joined #bitcoin-core-dev
03:52 -!- qxs [~qxs@gateway/tor-sasl/qxs] has joined #bitcoin-core-dev
04:39 < laanwj> it looks like the "Drahtbot GUIX build requested" label isn't working
04:48 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has joined #bitcoin-core-dev
05:18 < 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
05:33 -!- Chris_Stewart_5 [~Chris_Ste@static-198-54-135-88.cust.tzulo.com] has quit [Ping timeout: 246 seconds]
05:33 -!- Chris_Stewart_5 [~Chris_Ste@static-198-54-135-88.cust.tzulo.com] has joined #bitcoin-core-dev
05:34 -!- adil1 [~Thunderbi@2402:d000:8134:f58:3498:9e01:833c:d054] has quit [Quit: adil1]
06:16 -!- nlhcd [~private@2603:7000:1300:1302::1222] has joined #bitcoin-core-dev
07:15 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
07:19 -!- test_ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 252 seconds]
07:22 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-dev
07:22 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
07:31 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
07:34 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-dev
07:38 -!- Lockesmith [~user@gateway/tor-sasl/lockesmith] has quit [Ping timeout: 260 seconds]
07:39 -!- Lockesmith [~user@gateway/tor-sasl/lockesmith] has joined #bitcoin-core-dev
07:49 -!- ___nick___ [~quassel@cpc68290-cdif17-2-0-cust24.5-1.cable.virginm.net] has joined #bitcoin-core-dev
08:01 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Quit: Leaving]
08:02 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-dev
08:06 -!- Zenton [~user@user/zenton] has quit [Ping timeout: 268 seconds]
08:14 < furszy> pinheadmz: there isn't a simple way. gettransaction 'details' does not include change outputs.
08:15 < pinheadmz> should it? or if verbose, `decoded` could include the ischange flag in the vout array
08:16 < furszy> yeah, could add a 'include_change' flag.
08:16 < furszy> we are already doing it everywhere else
08:17 < 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
08:19 < furszy> "it shows change outputs where they'd normaly not be shown" thats what the user would expect when it provides the flag.
08:20 < 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
08:21 < 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
08:22 < laanwj> ok
08:25 -!- nicky [~nicky@191.165.202.115] has joined #bitcoin-core-dev
08:28 < 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.
08:30 < pinheadmz> so perhaps makes the most sense to add "category":"change" in the "details" array
08:31 < pinheadmz> i dont think that would even necessitate a flag since we're already examining each txout?
08:32 < furszy> the 'change' category sounds good to me.
08:33 < 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).
08:49 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 260 seconds]
08:51 -!- ___nick___ [~quassel@cpc68290-cdif17-2-0-cust24.5-1.cable.virginm.net] has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
08:53 < 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...
08:53 -!- ___nick___ [~quassel@cpc68290-cdif17-2-0-cust24.5-1.cable.virginm.net] has joined #bitcoin-core-dev
08:54 -!- ___nick___ [~quassel@cpc68290-cdif17-2-0-cust24.5-1.cable.virginm.net] has quit [Client Quit]
08:56 -!- Zenton [~user@user/zenton] has joined #bitcoin-core-dev
08:56 -!- ___nick___ [~quassel@cpc68290-cdif17-2-0-cust24.5-1.cable.virginm.net] has joined #bitcoin-core-dev
09:17 -!- gmaxwell [~gmaxwell@user/gmaxwell] has left #bitcoin-core-dev []
09:30 -!- nlhcd [~private@2603:7000:1300:1302::1222] has quit [Quit: Quit]
09:31 -!- nlhcd [~private@2603:7000:1300:1302::1222] has joined #bitcoin-core-dev
09:33 -!- nlhcd [~private@2603:7000:1300:1302::1222] has quit [Remote host closed the connection]
09:36 -!- javi404_ is now known as javi404
10:09 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has left #bitcoin-core-dev [Closing Window]
10:23 -!- qxs [~qxs@gateway/tor-sasl/qxs] has quit [Ping timeout: 260 seconds]
10:25 -!- qxs [~qxs@gateway/tor-sasl/qxs] has joined #bitcoin-core-dev
10:29 -!- _cold is now known as cold
10:30 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
11:03 -!- zeropoint [~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-core-dev
11:15 -!- zeropoint [~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net] has quit [Quit: leaving]
11:41 -!- Lockesmith [~user@gateway/tor-sasl/lockesmith] has quit [Ping timeout: 260 seconds]
12:00 -!- gnaf [~pi@109.36.130.102] has joined #bitcoin-core-dev
12:02 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!]
12:08 -!- saffi [~saffi@203.215.167.41] has joined #bitcoin-core-dev
12:17 -!- test_ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
12:21 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 264 seconds]
12:27 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
12:30 -!- test_ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 252 seconds]
12:33 -!- test_ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
12:34 -!- gnaf [~pi@109.36.130.102] has quit [Read error: Connection reset by peer]
12:37 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 240 seconds]
12:41 -!- saffi [~saffi@user/saffi] has changed host
12:43 -!- saffi [~saffi@user/saffi] has quit [Quit: Connection closed]
12:44 -!- saffi [~saffi@user/saffi] has joined #bitcoin-core-dev
12:48 < saffi> Hi Everyone !
12:48 < saffi> https://github.com/bitcoin/bitcoin/pull/29500
12:49 < 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 ?
13:04 -!- ___nick___ [~quassel@cpc68290-cdif17-2-0-cust24.5-1.cable.virginm.net] has quit [Ping timeout: 240 seconds]
13:04 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 260 seconds]
13:05 -!- nlhcd [~private@2603:7000:1300:1302::1222] has joined #bitcoin-core-dev
13:05 -!- nlhcd1 [~private@2603:7000:1300:1302::1222] has joined #bitcoin-core-dev
13:08 -!- nlhcd [~private@2603:7000:1300:1302::1222] has quit [Remote host closed the connection]
13:08 -!- nlhcd1 [~private@2603:7000:1300:1302::1222] has quit [Client Quit]
13:25 -!- Guest24 [~Guest24@194.59.28.227] has joined #bitcoin-core-dev
13:27 -!- Guest24 [~Guest24@194.59.28.227] has quit [Client Quit]
14:05 -!- SpellChecker [~SpellChec@user/SpellChecker] has quit [Ping timeout: 260 seconds]
14:06 -!- SpellChecker [~SpellChec@user/SpellChecker] has joined #bitcoin-core-dev
14:28 < saffi> guys ?
14:36 -!- PaperSword [~Thunderbi@securemail.qrsnap.io] has joined #bitcoin-core-dev
14:38 -!- Guest60 [~Guest69@syn-172-091-172-231.res.spectrum.com] has joined #bitcoin-core-dev
14:40 -!- Guest60 [~Guest69@syn-172-091-172-231.res.spectrum.com] has left #bitcoin-core-dev []
14:50 -!- gnaf [~pi@109.36.130.102] has joined #bitcoin-core-dev
14:55 -!- qxs [~qxs@gateway/tor-sasl/qxs] has quit [Ping timeout: 260 seconds]
14:55 -!- gnaf [~pi@109.36.130.102] has quit [Quit: Konversation terminated!]
14:56 -!- qxs [~qxs@gateway/tor-sasl/qxs] has joined #bitcoin-core-dev
15:12 -!- qxs [~qxs@gateway/tor-sasl/qxs] has quit [Ping timeout: 260 seconds]
15:12 -!- qxs [~qxs@gateway/tor-sasl/qxs] has joined #bitcoin-core-dev
15:47 -!- Guest33 [~Guest33@2401:4900:1c71:3ed:3565:904:b23a:5cc0] has joined #bitcoin-core-dev
15:49 -!- saffi [~saffi@user/saffi] has quit [Ping timeout: 260 seconds]
15:50 -!- Guest33 [~Guest33@2401:4900:1c71:3ed:3565:904:b23a:5cc0] has quit [Client Quit]
15:58 -!- achow101 [~achow101@user/achow101] has quit [Remote host closed the connection]
15:58 -!- achow101 [~achow101@user/achow101] has joined #bitcoin-core-dev
17:50 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 260 seconds]
17:51 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
17:56 -!- c4pt00 [~c4pt@ip174-72-72-227.ph.ph.cox.net] has joined #bitcoin-core-dev
17:58 -!- c4pt_ [~c4pt@ip174-72-72-227.ph.ph.cox.net] has joined #bitcoin-core-dev
18:02 -!- c4pt00 [~c4pt@user/c4pt00] has changed host
18:02 < c4pt00> luke-jr, https://x.com/Bitnet_io/status/1792260906094887073
18:02 < c4pt00> luke-jr, https://x.com/LukeDashjr/status/1792348745251910027
18:02 < c4pt00> luke-jr, https://i.postimg.cc/pX8vCqw7/luke-dash-jr-nonsense.png
18:02 < c4pt00> luke-jr, https://i.postimg.cc/1RbPDLjw/luke-dash-jr-crazy.png
18:02 < c4pt00> luke-jr, https://i.postimg.cc/qvTT5207/luke-dash-jr-drugs.png
18:02 -!- c4pt00 [~c4pt@user/c4pt00] has quit [Quit: Leaving]
18:22 -!- c4pt_ [~c4pt@ip174-72-72-227.ph.ph.cox.net] has quit [Quit: Leaving]
19:14 -!- dermoth [~dermoth@user/dermoth] has quit [Ping timeout: 255 seconds]
19:17 -!- dermoth [~dermoth@user/dermoth] has joined #bitcoin-core-dev
19:49 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
20:00 -!- hel [el@libera/staff/el] has quit [Read error: Connection reset by peer]
20:00 -!- hel [el@libera/staff/el] has joined #bitcoin-core-dev
20:08 -!- SatoshiCl [~SatoshiCl@213.55.226.244] has joined #bitcoin-core-dev
20:24 -!- SatoshiCl [~SatoshiCl@213.55.226.244] has quit [Ping timeout: 250 seconds]
21:01 -!- cmirror [~cmirror@4.53.92.114] has quit [Remote host closed the connection]
21:01 -!- cmirror [~cmirror@4.53.92.114] has joined #bitcoin-core-dev
23:07 -!- tarotfied [~tarotfied@static.38.4.181.135.clients.your-server.de] has quit [Read error: Connection reset by peer]
23:33 -!- mailman [~mailman@119.155.170.51] has joined #bitcoin-core-dev
23:33 -!- mailman [~mailman@119.155.170.51] has quit [Client Quit]
23:46 -!- saffi [~saffi@user/saffi] has joined #bitcoin-core-dev
23:49 -!- dviola [~diego@user/dviola] has joined #bitcoin-core-dev
23:51 -!- saffi [~saffi@user/saffi] has quit [Quit: Connection closed]
--- Log closed Mon May 20 00:00:00 2024