12022-10-20T00:03:31 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
22022-10-20T00:10:24 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
32022-10-20T00:13:54 <bitcoin-git> [bitcoin] fanquake pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/a97791d9fb97...2ac71d20b2eb
42022-10-20T00:13:54 <bitcoin-git> bitcoin/master d256992 Greg Sanders: Verify PSBT inputs rather than check for fields being empty
52022-10-20T00:13:54 <bitcoin-git> bitcoin/master e133264 Greg Sanders: Add test for PSBT input verification
62022-10-20T00:13:55 <bitcoin-git> bitcoin/master 2ac71d2 fanquake: Merge bitcoin/bitcoin#25595: Verify PSBT inputs rather than check for fiel...
72022-10-20T00:14:04 <bitcoin-git> [bitcoin] fanquake merged pull request #25595: Verify PSBT inputs rather than check for fields being empty (master...verify_psbt_input) https://github.com/bitcoin/bitcoin/pull/25595
82022-10-20T00:15:57 *** Zenton <Zenton!~user@user/zenton> has quit IRC (Ping timeout: 252 seconds)
92022-10-20T00:23:49 *** sipsorcery <sipsorcery!~sipsorcer@37.228.225.67> has quit IRC (Ping timeout: 246 seconds)
102022-10-20T00:40:54 *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has joined #bitcoin-core-dev
112022-10-20T00:42:17 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
122022-10-20T00:42:35 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
132022-10-20T00:57:29 *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has quit IRC (Remote host closed the connection)
142022-10-20T00:58:49 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
152022-10-20T01:07:40 <bitcoin-git> [bitcoin] ishaanam opened pull request #26347: wallet: ensure the wallet is unlocked when needed for rescanning (master...rescanblockchain_unlock_wallet) https://github.com/bitcoin/bitcoin/pull/26347
162022-10-20T01:10:36 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 252 seconds)
172022-10-20T01:21:05 *** NorrinRadd <NorrinRadd!~me@188.215.95.44> has quit IRC (Ping timeout: 272 seconds)
182022-10-20T01:22:51 *** NorrinRadd <NorrinRadd!~me@85.237.194.112> has joined #bitcoin-core-dev
192022-10-20T01:26:59 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
202022-10-20T01:32:04 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
212022-10-20T01:32:57 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
222022-10-20T01:33:17 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
232022-10-20T01:43:25 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
242022-10-20T01:45:51 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
252022-10-20T01:48:55 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 255 seconds)
262022-10-20T01:50:59 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
272022-10-20T01:55:10 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
282022-10-20T02:05:30 *** jonatack1 <jonatack1!~jonatack@user/jonatack> has joined #bitcoin-core-dev
292022-10-20T02:09:20 *** PaperSwordAlt <PaperSwordAlt!~PaperSwor@50.126.96.22> has joined #bitcoin-core-dev
302022-10-20T02:10:48 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
312022-10-20T02:10:56 *** PaperSword <PaperSword!~PaperSwor@50.126.96.22> has quit IRC (Ping timeout: 260 seconds)
322022-10-20T02:15:08 *** PaperSwordAlt <PaperSwordAlt!~PaperSwor@50.126.96.22> has quit IRC (Ping timeout: 252 seconds)
332022-10-20T02:24:02 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
342022-10-20T02:24:20 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
352022-10-20T02:27:43 *** jonatack1 <jonatack1!~jonatack@user/jonatack> has quit IRC (Read error: Connection reset by peer)
362022-10-20T02:48:19 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 255 seconds)
372022-10-20T02:54:33 <bitcoin-git> [bitcoin] SergioDemianLerner opened pull request #26348: Make P2SH redeem script "IF .. PUSH x ELSE ... PUSH y ENDIF CHECKMULTISIG .. " standard (master...master) https://github.com/bitcoin/bitcoin/pull/26348
382022-10-20T03:11:14 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 252 seconds)
392022-10-20T03:42:43 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
402022-10-20T03:56:51 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
412022-10-20T04:01:01 *** cmirror <cmirror!~cmirror@4.53.92.114> has quit IRC (Remote host closed the connection)
422022-10-20T04:01:33 *** cmirror <cmirror!~cmirror@4.53.92.114> has joined #bitcoin-core-dev
432022-10-20T04:05:37 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
442022-10-20T04:06:01 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
452022-10-20T04:08:40 <bitcoin-git> [bitcoin] w0xlt opened pull request #26349: rpc: make `address` field optional `list{transactions, sinceblock}` response (master...issue_26338) https://github.com/bitcoin/bitcoin/pull/26349
462022-10-20T04:09:45 *** andrewtoth <andrewtoth!~andrewtot@gateway/tor-sasl/andrewtoth> has quit IRC (Remote host closed the connection)
472022-10-20T04:10:02 *** andrewtoth_ <andrewtoth_!~andrewtot@gateway/tor-sasl/andrewtoth> has joined #bitcoin-core-dev
482022-10-20T04:14:24 *** fanta1 <fanta1!~fanta1@78.48.143.94> has joined #bitcoin-core-dev
492022-10-20T04:15:04 *** andrewtoth_ <andrewtoth_!~andrewtot@gateway/tor-sasl/andrewtoth> has quit IRC (Remote host closed the connection)
502022-10-20T04:15:37 *** andrewtoth_ <andrewtoth_!~andrewtot@gateway/tor-sasl/andrewtoth> has joined #bitcoin-core-dev
512022-10-20T04:26:10 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
522022-10-20T04:26:30 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
532022-10-20T04:28:08 *** mikehu44 <mikehu44!~quassel@159.65.11.175> has joined #bitcoin-core-dev
542022-10-20T04:43:41 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Ping timeout: 258 seconds)
552022-10-20T04:46:32 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
562022-10-20T04:47:01 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
572022-10-20T04:55:12 *** dviola <dviola!~diego@179.235.13.211> has quit IRC (Quit: WeeChat 3.7)
582022-10-20T05:00:10 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 255 seconds)
592022-10-20T05:02:06 *** _andrewtoth_ <_andrewtoth_!~andrewtot@gateway/tor-sasl/andrewtoth> has joined #bitcoin-core-dev
602022-10-20T05:04:06 *** andrewtoth_ <andrewtoth_!~andrewtot@gateway/tor-sasl/andrewtoth> has quit IRC (Remote host closed the connection)
612022-10-20T05:16:50 *** sudoforge <sudoforge!~sudoforge@wireguard/tunneler/sudoforge> has quit IRC (Quit: 404)
622022-10-20T05:29:57 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
632022-10-20T05:31:16 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
642022-10-20T05:31:34 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
652022-10-20T05:34:16 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
662022-10-20T05:49:55 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
672022-10-20T06:04:30 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
682022-10-20T06:04:31 <bitcoin-git> [bitcoin] fanquake opened pull request #26350: [22.x] Revert "build: Use Homebrew's sqlite package if it is available" (22.x...revert_slow_macos_sqlite_22_x) https://github.com/bitcoin/bitcoin/pull/26350
692022-10-20T06:05:01 *** murrayn <murrayn!~murray@user/murrayn> has quit IRC (Ping timeout: 252 seconds)
702022-10-20T06:08:55 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
712022-10-20T06:11:57 *** jarthur <jarthur!~jarthur@user/jarthur> has quit IRC (Quit: jarthur)
722022-10-20T06:13:25 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
732022-10-20T06:51:33 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
742022-10-20T06:51:48 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
752022-10-20T06:54:50 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 272 seconds)
762022-10-20T07:01:07 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
772022-10-20T07:01:24 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
782022-10-20T07:08:17 *** Zenton <Zenton!~user@user/zenton> has joined #bitcoin-core-dev
792022-10-20T07:12:28 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
802022-10-20T07:12:34 *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has joined #bitcoin-core-dev
812022-10-20T07:16:49 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
822022-10-20T07:21:40 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 252 seconds)
832022-10-20T07:25:56 *** chipxxx <chipxxx!~chip@2001:8a0:f61c:9200:9c3d:d55a:c1aa:516e> has joined #bitcoin-core-dev
842022-10-20T07:27:14 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
852022-10-20T07:27:24 *** dermoth <dermoth!~dermoth@user/dermoth> has quit IRC (Ping timeout: 264 seconds)
862022-10-20T07:27:30 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
872022-10-20T07:28:21 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
882022-10-20T07:28:46 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has joined #bitcoin-core-dev
892022-10-20T07:40:13 *** dermoth <dermoth!~dermoth@user/dermoth> has joined #bitcoin-core-dev
902022-10-20T07:51:47 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
912022-10-20T07:52:26 *** Guest6268 <Guest6268!~Guest62@137.61.48.10> has joined #bitcoin-core-dev
922022-10-20T07:53:02 *** Guest6268 <Guest6268!~Guest62@137.61.48.10> has quit IRC (Client Quit)
932022-10-20T07:53:22 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
942022-10-20T07:56:33 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 255 seconds)
952022-10-20T07:57:36 *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has quit IRC (Ping timeout: 252 seconds)
962022-10-20T07:57:54 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 255 seconds)
972022-10-20T08:04:06 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has left #bitcoin-core-dev (Closing Window)
982022-10-20T08:06:05 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
992022-10-20T08:06:21 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
1002022-10-20T08:17:07 *** jespada <jespada!~jespada@nmal-24-b2-v4wan-166357-cust1764.vm24.cable.virginm.net> has quit IRC (Ping timeout: 248 seconds)
1012022-10-20T08:17:55 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
1022022-10-20T08:18:15 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
1032022-10-20T08:20:37 *** jespada <jespada!~jespada@nmal-24-b2-v4wan-166357-cust1764.vm24.cable.virginm.net> has joined #bitcoin-core-dev
1042022-10-20T08:20:39 *** SpellChecker <SpellChecker!~SpellChec@user/SpellChecker> has quit IRC (Remote host closed the connection)
1052022-10-20T08:20:39 *** vasild <vasild!~vd@user/vasild> has quit IRC (Remote host closed the connection)
1062022-10-20T08:22:43 *** SpellChecker <SpellChecker!~SpellChec@user/SpellChecker> has joined #bitcoin-core-dev
1072022-10-20T08:24:30 *** murrayn <murrayn!~murray@static.38.4.181.135.clients.your-server.de> has joined #bitcoin-core-dev
1082022-10-20T08:27:10 *** jespada <jespada!~jespada@nmal-24-b2-v4wan-166357-cust1764.vm24.cable.virginm.net> has quit IRC (Ping timeout: 255 seconds)
1092022-10-20T08:27:42 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
1102022-10-20T08:28:57 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
1112022-10-20T08:32:24 *** jespada <jespada!~jespada@nmal-24-b2-v4wan-166357-cust1764.vm24.cable.virginm.net> has joined #bitcoin-core-dev
1122022-10-20T08:33:07 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
1132022-10-20T08:39:17 <bitcoin-git> [bitcoin] Sjors opened pull request #26351: guix: bump time-machine to 39dcbc7fa3c02ff5c9682f25e1c29667dbfe7827 (master...2022/10/guix-bump-timemachine) https://github.com/bitcoin/bitcoin/pull/26351
1142022-10-20T08:46:01 *** vasild <vasild!~vd@user/vasild> has joined #bitcoin-core-dev
1152022-10-20T08:47:00 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
1162022-10-20T08:51:13 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Remote host closed the connection)
1172022-10-20T09:08:43 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
1182022-10-20T09:09:08 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
1192022-10-20T09:19:06 *** fanta1 <fanta1!~fanta1@78.48.143.94> has quit IRC (Quit: fanta1)
1202022-10-20T09:20:20 *** fanta1 <fanta1!~fanta1@2a01:c23:7156:2500:a98f:c325:a945:6964> has joined #bitcoin-core-dev
1212022-10-20T09:22:16 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
1222022-10-20T09:31:03 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 255 seconds)
1232022-10-20T09:32:49 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
1242022-10-20T09:33:04 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
1252022-10-20T09:36:32 *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has joined #bitcoin-core-dev
1262022-10-20T09:36:41 *** fanta1 <fanta1!~fanta1@2a01:c23:7156:2500:a98f:c325:a945:6964> has quit IRC (Quit: fanta1)
1272022-10-20T09:43:28 *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has quit IRC (Ping timeout: 246 seconds)
1282022-10-20T09:49:30 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 255 seconds)
1292022-10-20T09:59:20 *** TheRec <TheRec!~toto@user/therec> has quit IRC ()
1302022-10-20T09:59:29 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
1312022-10-20T09:59:48 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
1322022-10-20T10:01:28 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
1332022-10-20T10:03:18 *** kexkey <kexkey!~kexkey@198.54.132.120> has quit IRC (Ping timeout: 268 seconds)
1342022-10-20T10:04:19 *** kexkey <kexkey!~kexkey@static-198-54-132-120.cust.tzulo.com> has joined #bitcoin-core-dev
1352022-10-20T10:07:37 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
1362022-10-20T10:19:27 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
1372022-10-20T10:19:27 *** TheRec <TheRec!~toto@84-75-225-47.dclient.hispeed.ch> has joined #bitcoin-core-dev
1382022-10-20T10:21:07 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
1392022-10-20T10:23:14 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
1402022-10-20T10:23:28 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
1412022-10-20T10:24:46 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
1422022-10-20T10:38:14 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
1432022-10-20T10:46:47 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Remote host closed the connection)
1442022-10-20T10:50:44 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
1452022-10-20T10:51:01 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
1462022-10-20T10:55:02 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
1472022-10-20T10:56:24 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
1482022-10-20T11:03:59 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
1492022-10-20T11:13:31 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
1502022-10-20T11:13:52 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
1512022-10-20T11:19:34 *** jonatack1 <jonatack1!~jonatack@user/jonatack> has joined #bitcoin-core-dev
1522022-10-20T11:23:33 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 255 seconds)
1532022-10-20T11:40:40 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 255 seconds)
1542022-10-20T11:41:21 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
1552022-10-20T11:41:36 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
1562022-10-20T11:43:00 *** bomb-on_ <bomb-on_!~bomb-on@user/bomb-on> has joined #bitcoin-core-dev
1572022-10-20T11:44:11 *** bomb-on <bomb-on!~bomb-on@user/bomb-on> has quit IRC (Ping timeout: 252 seconds)
1582022-10-20T11:47:48 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Quit: = "")
1592022-10-20T11:51:35 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
1602022-10-20T11:54:45 *** fanta1 <fanta1!~fanta1@2a01:c23:7156:2500:a98f:c325:a945:6964> has joined #bitcoin-core-dev
1612022-10-20T11:55:46 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
1622022-10-20T12:08:39 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
1632022-10-20T12:09:37 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
1642022-10-20T12:09:48 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
1652022-10-20T12:15:01 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
1662022-10-20T12:26:14 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
1672022-10-20T12:45:21 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
1682022-10-20T12:56:55 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:401d:2d18:c10d:4831> has joined #bitcoin-core-dev
1692022-10-20T13:20:44 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has joined #bitcoin-core-dev
1702022-10-20T13:22:32 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
1712022-10-20T13:22:48 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
1722022-10-20T13:23:08 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has left #bitcoin-core-dev
1732022-10-20T13:29:33 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 255 seconds)
1742022-10-20T13:41:30 *** yanmaani2 <yanmaani2!~yanmaani@gateway/tor-sasl/yanmaani> has quit IRC (Ping timeout: 258 seconds)
1752022-10-20T13:44:57 *** vasild <vasild!~vd@user/vasild> has quit IRC (Ping timeout: 258 seconds)
1762022-10-20T13:45:22 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
1772022-10-20T13:45:39 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
1782022-10-20T13:47:46 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 252 seconds)
1792022-10-20T13:48:11 *** vasild <vasild!~vd@user/vasild> has joined #bitcoin-core-dev
1802022-10-20T13:48:57 *** yanmaani2 <yanmaani2!~yanmaani@gateway/tor-sasl/yanmaani> has joined #bitcoin-core-dev
1812022-10-20T13:57:31 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
1822022-10-20T14:00:22 *** mikehu44 <mikehu44!~quassel@159.65.11.175> has quit IRC (Ping timeout: 246 seconds)
1832022-10-20T14:01:58 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 255 seconds)
1842022-10-20T14:15:57 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
1852022-10-20T14:20:24 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 255 seconds)
1862022-10-20T14:33:26 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
1872022-10-20T14:33:37 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
1882022-10-20T14:47:25 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
1892022-10-20T14:47:39 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
1902022-10-20T15:11:05 <bitcoin-git> [bitcoin] achow101 pushed 6 commits to master: https://github.com/bitcoin/bitcoin/compare/2ac71d20b2eb...fabc0310480b
1912022-10-20T15:11:05 <bitcoin-git> bitcoin/master f159378 furszy: bench: place benchmark implementation inside benchmark namespace
1922022-10-20T15:11:05 <bitcoin-git> bitcoin/master 05b8c76 furszy: bench: add "priority level" to the benchmark framework
1932022-10-20T15:11:06 <bitcoin-git> bitcoin/master 3da7cd2 furszy: bench: explicitly make all current benchmarks "high" priority
1942022-10-20T15:11:11 <bitcoin-git> [bitcoin] achow101 merged pull request #26158: bench: add "priority level" to the benchmark framework (master...2022_bench_priority_level) https://github.com/bitcoin/bitcoin/pull/26158
1952022-10-20T15:15:36 *** dviola <dviola!~diego@user/dviola> has joined #bitcoin-core-dev
1962022-10-20T15:23:07 *** bomb-on_ <bomb-on_!~bomb-on@user/bomb-on> has quit IRC (Read error: Connection reset by peer)
1972022-10-20T15:23:41 *** bomb-on <bomb-on!~bomb-on@user/bomb-on> has joined #bitcoin-core-dev
1982022-10-20T15:33:39 *** hg <hg!~halosghos@user/halosghost> has joined #bitcoin-core-dev
1992022-10-20T15:35:34 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
2002022-10-20T15:36:58 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
2012022-10-20T15:43:00 *** elichai2 <elichai2!sid212594@id-212594.hampstead.irccloud.com> has joined #bitcoin-core-dev
2022022-10-20T15:43:12 *** hg <hg!~halosghos@user/halosghost> has quit IRC (Ping timeout: 255 seconds)
2032022-10-20T15:49:28 *** jonatack1 <jonatack1!~jonatack@user/jonatack> has quit IRC (Read error: Connection reset by peer)
2042022-10-20T15:51:23 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
2052022-10-20T15:51:53 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
2062022-10-20T15:55:03 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
2072022-10-20T15:55:20 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
2082022-10-20T15:56:15 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 255 seconds)
2092022-10-20T15:56:34 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
2102022-10-20T16:01:34 *** hg <hg!~halosghos@user/halosghost> has joined #bitcoin-core-dev
2112022-10-20T16:07:26 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
2122022-10-20T16:13:33 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Remote host closed the connection)
2132022-10-20T16:13:48 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
2142022-10-20T16:14:30 *** _Sam-- <_Sam--!~sam@20.171.51.152> has joined #bitcoin-core-dev
2152022-10-20T16:15:03 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Remote host closed the connection)
2162022-10-20T16:15:38 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
2172022-10-20T16:18:27 <dhruv> For the last couple days, when I try to run CirrusCI on my fork, most of the times, it fails with "Failed to checkout HEAD_SHA", and then occasionally it start to work. Are others seeing this too?
2182022-10-20T16:18:37 <dhruv> starts**
2192022-10-20T16:19:56 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 252 seconds)
2202022-10-20T16:21:31 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
2212022-10-20T16:24:00 <bitcoin-git> [bitcoin] theStack opened pull request #26352: doc: add `scanblocks` to list of descriptor RPCs (master...202210-doc-add_scanblocks_to_doc_descriptors) https://github.com/bitcoin/bitcoin/pull/26352
2222022-10-20T16:27:39 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:401d:2d18:c10d:4831> has quit IRC (Remote host closed the connection)
2232022-10-20T16:28:05 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:401d:2d18:c10d:4831> has joined #bitcoin-core-dev
2242022-10-20T16:32:24 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:401d:2d18:c10d:4831> has quit IRC (Ping timeout: 252 seconds)
2252022-10-20T16:35:42 *** kexkey <kexkey!~kexkey@static-198-54-132-120.cust.tzulo.com> has quit IRC (Ping timeout: 252 seconds)
2262022-10-20T16:36:03 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
2272022-10-20T16:38:20 *** kexkey <kexkey!~kexkey@static-198-54-132-124.cust.tzulo.com> has joined #bitcoin-core-dev
2282022-10-20T16:38:53 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:401d:2d18:c10d:4831> has joined #bitcoin-core-dev
2292022-10-20T16:40:48 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 255 seconds)
2302022-10-20T16:43:07 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:401d:2d18:c10d:4831> has quit IRC (Ping timeout: 246 seconds)
2312022-10-20T16:44:19 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
2322022-10-20T16:44:35 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
2332022-10-20T16:56:17 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:401d:2d18:c10d:4831> has joined #bitcoin-core-dev
2342022-10-20T16:59:43 *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has joined #bitcoin-core-dev
2352022-10-20T17:00:27 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
2362022-10-20T17:05:46 *** jarthur <jarthur!~jarthur@user/jarthur> has joined #bitcoin-core-dev
2372022-10-20T17:07:16 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
2382022-10-20T17:07:30 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
2392022-10-20T17:10:58 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 255 seconds)
2402022-10-20T17:15:41 *** Talkless <Talkless!~Talkless@mail.dargis.net> has joined #bitcoin-core-dev
2412022-10-20T17:18:51 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
2422022-10-20T17:24:20 *** ___nick___ <___nick___!~quassel@cpc68289-cdif17-2-0-cust317.5-1.cable.virginm.net> has joined #bitcoin-core-dev
2432022-10-20T17:24:46 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
2442022-10-20T17:25:49 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
2452022-10-20T17:29:01 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
2462022-10-20T17:31:48 *** ___nick___ <___nick___!~quassel@cpc68289-cdif17-2-0-cust317.5-1.cable.virginm.net> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
2472022-10-20T17:33:42 *** ___nick___ <___nick___!~quassel@cpc68289-cdif17-2-0-cust317.5-1.cable.virginm.net> has joined #bitcoin-core-dev
2482022-10-20T17:34:22 *** ___nick___ <___nick___!~quassel@cpc68289-cdif17-2-0-cust317.5-1.cable.virginm.net> has quit IRC (Client Quit)
2492022-10-20T17:36:11 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
2502022-10-20T17:36:17 *** ___nick___ <___nick___!~quassel@cpc68289-cdif17-2-0-cust317.5-1.cable.virginm.net> has joined #bitcoin-core-dev
2512022-10-20T17:36:26 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
2522022-10-20T17:37:08 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
2532022-10-20T17:37:49 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Remote host closed the connection)
2542022-10-20T17:38:03 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
2552022-10-20T17:38:33 *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has quit IRC (Remote host closed the connection)
2562022-10-20T17:38:49 *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has joined #bitcoin-core-dev
2572022-10-20T17:41:07 <luke-jr> dhruv: just a guess: are you force-pushing over it before it gets going?
2582022-10-20T17:44:30 <dhruv> luke-jr: nope, i didn't
2592022-10-20T17:44:55 <dhruv> here's another way it keeps failing too, in merge_base: https://cirrus-ci.com/task/5956454321487872?logs=merge_base#L305
2602022-10-20T17:45:26 <dhruv> i felt like there might be some issue with the Github APIs being used by Cirrus, but then bitcoin/bitcoin builds seems to work fine
2612022-10-20T17:45:54 <dhruv> potentially relevant is also this:
2622022-10-20T17:45:56 <dhruv> https://twitter.com/cirrus_labs/status/1573028317485211652
2632022-10-20T17:47:20 *** Guest9119 <Guest9119!~Guest91@2606:54c0:76a1:3e90::11:181> has joined #bitcoin-core-dev
2642022-10-20T17:50:28 *** Guest9144 <Guest9144!~Guest91@2606:54c0:76e1:5408::11:d8> has joined #bitcoin-core-dev
2652022-10-20T17:50:56 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
2662022-10-20T17:50:58 *** Guest9119 <Guest9119!~Guest91@2606:54c0:76a1:3e90::11:181> has quit IRC (Client Quit)
2672022-10-20T17:51:10 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
2682022-10-20T17:51:16 *** Guest9144 <Guest9144!~Guest91@2606:54c0:76e1:5408::11:d8> has quit IRC (Client Quit)
2692022-10-20T17:57:44 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
2702022-10-20T17:57:58 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
2712022-10-20T17:58:16 *** hg <hg!~halosghos@user/halosghost> has quit IRC (Quit: WeeChat 3.7)
2722022-10-20T18:00:17 *** sebareca <sebareca!~sebareca@190.194.221.154> has joined #bitcoin-core-dev
2732022-10-20T18:05:07 *** esneider <esneider!~esneider@190.194.221.154> has joined #bitcoin-core-dev
2742022-10-20T18:06:50 *** csgui <csgui!~csgui@221.194.115.89.rev.vodafone.pt> has joined #bitcoin-core-dev
2752022-10-20T18:20:29 <bitcoin-git> [bitcoin] dergoegge opened pull request #26355: p2p: Handle IsContinuationOfLowWorkHeadersSync return value correctly when new headers sync is started (master...2022-10-nbits-headerssync) https://github.com/bitcoin/bitcoin/pull/26355
2762022-10-20T18:22:22 *** sanket_cell <sanket_cell!~sanket172@ec2-100-24-255-95.compute-1.amazonaws.com> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)
2772022-10-20T18:22:22 *** sanket1729 <sanket1729!~sanket172@ec2-100-24-255-95.compute-1.amazonaws.com> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)
2782022-10-20T18:23:03 *** gnaf <gnaf!~gnaf@2a02-a454-54e2-1-10f6-6b6f-5432-2697.fixed6.kpn.net> has joined #bitcoin-core-dev
2792022-10-20T18:23:04 *** sanket1729 <sanket1729!~sanket172@ec2-100-24-255-95.compute-1.amazonaws.com> has joined #bitcoin-core-dev
2802022-10-20T18:23:35 *** sanket_cell <sanket_cell!~sanket172@ec2-100-24-255-95.compute-1.amazonaws.com> has joined #bitcoin-core-dev
2812022-10-20T18:31:31 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 255 seconds)
2822022-10-20T18:32:44 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
2832022-10-20T18:33:10 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
2842022-10-20T18:56:36 *** yanmaani2 <yanmaani2!~yanmaani@gateway/tor-sasl/yanmaani> has quit IRC (Ping timeout: 258 seconds)
2852022-10-20T18:56:45 *** champo <champo!~champo@host140.190-227-156.telecom.net.ar> has joined #bitcoin-core-dev
2862022-10-20T18:57:36 *** yanmaani2 <yanmaani2!~yanmaani@gateway/tor-sasl/yanmaani> has joined #bitcoin-core-dev
2872022-10-20T18:58:03 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
2882022-10-20T18:58:19 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
2892022-10-20T19:00:45 <laanwj> #startmeeting
2902022-10-20T19:00:55 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
2912022-10-20T19:00:59 <jarolrod> hi
2922022-10-20T19:01:01 <ariard> hi
2932022-10-20T19:01:02 <dergoegge> hi
2942022-10-20T19:01:04 <hebasto> hi
2952022-10-20T19:01:04 <stickies-v> hi
2962022-10-20T19:01:05 *** ChanServ sets mode: +o core-meetingbot
2972022-10-20T19:01:06 <NorrinRadd> Hi
2982022-10-20T19:01:07 <glozow> hi
2992022-10-20T19:01:08 <achow101> hi
3002022-10-20T19:01:10 <brunoerg> hi
3012022-10-20T19:01:14 <lightlike> hi
3022022-10-20T19:01:20 <luke-jr> hi
3032022-10-20T19:01:27 <laanwj> #bitcoin-core-dev Meeting: achow101 _aj_ amiti ariard b10c BlueMatt cfields Chris_Stewart_5 darosior digi_james dongcarl elichai2 emilengler fanquake fjahr gleb glozow gmaxwell gwillen hebasto instagibbs jamesob jarolrod jb55 jeremyrubin jl2012 jnewbery jonasschnelli jonatack jtimon kallewoof kanzure kvaciral laanwj larryruane lightlike luke-jr maaku marcofalke meshcollider michagogo
3042022-10-20T19:01:29 <laanwj> moneyball morcos nehan NicolasDorier paveljanik petertodd phantomcircuit promag provoostenator ryanofsky sdaftuar sipa vasild
3052022-10-20T19:01:31 <laanwj> hi
3062022-10-20T19:01:32 <kanzure> hi
3072022-10-20T19:01:37 <vasild> hi
3082022-10-20T19:01:47 <instagibbs> hi
3092022-10-20T19:02:01 <LarryRuane> hi
3102022-10-20T19:02:15 <_aj_> hi
3112022-10-20T19:02:48 <ajonas> hi
3122022-10-20T19:03:09 <laanwj> four meeting topics have been proposedin advance this time: Drop GUI repo and bring GUI work back to the main repo for now (achow101), Adding (more) maintainers as GitHub org owners (achow101), Moratorium on refactors that are not part of larger projects that bring tangible features and fixes (achow101), defer fullrbf for 24.0(or not) (instagibbs)
3132022-10-20T19:03:41 <laanwj> any last minute ones?
3142022-10-20T19:03:57 <b10c> hi
3152022-10-20T19:04:38 <laanwj> #topic High priority for review
3162022-10-20T19:04:39 <core-meetingbot> topic: High priority for review
3172022-10-20T19:04:59 <laanwj> https://github.com/orgs/bitcoin/projects/1 has 4 blockers, 6 chasing concept ACK
3182022-10-20T19:05:07 <laanwj> anything to add/remove?
3192022-10-20T19:05:18 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 252 seconds)
3202022-10-20T19:05:37 <LarryRuane> could you add #16981 for me?
3212022-10-20T19:05:39 <gribble> https://github.com/bitcoin/bitcoin/issues/16981 | Improve runtime performance of --reindex by LarryRuane · Pull Request #16981 · bitcoin/bitcoin · GitHub
3222022-10-20T19:05:43 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has quit IRC (Remote host closed the connection)
3232022-10-20T19:05:55 *** greypw2546002 <greypw2546002!~greypw254@grey.pw> has joined #bitcoin-core-dev
3242022-10-20T19:06:01 <furszy> hi
3252022-10-20T19:06:25 <laanwj> LarryRuane: added
3262022-10-20T19:07:19 <sipsorcery> hi
3272022-10-20T19:08:09 <kouloumos> hi
3282022-10-20T19:08:12 <laanwj> btw PSA: rc2 binaries were uploaded a few days ago, please help testing https://github.com/bitcoin-core/bitcoin-devwiki/wiki/24.0-Release-Candidate-Testing-Guide
3292022-10-20T19:08:23 <dergoegge> #25515 has quite a few concept acks now, so no longer chasing i guess
3302022-10-20T19:08:24 <gribble> https://github.com/bitcoin/bitcoin/issues/25515 | net, test: Virtualise CConnman and add initial PeerManager unit tests by dergoegge · Pull Request #25515 · bitcoin/bitcoin · GitHub
3312022-10-20T19:08:41 <laanwj> dergoegge: move it to blockers?
3322022-10-20T19:08:45 <dergoegge> sure
3332022-10-20T19:08:55 <stickies-v> LarryRuane: should we wait with (re-)reviewing until you've added the benchmark test, as you just announced?
3342022-10-20T19:09:20 <LarryRuane> yes good idea, thanks
3352022-10-20T19:09:35 *** Guest35 <Guest35!~Guest35@197.210.77.43> has joined #bitcoin-core-dev
3362022-10-20T19:09:36 *** Guest35 <Guest35!~Guest35@197.210.77.43> has quit IRC (Client Quit)
3372022-10-20T19:10:12 <bitcoin-git> [bitcoin] NorrinRadd opened pull request #26356: test: Use a consistent assert functions: ref #23119 (master...issue/23119/part-1) https://github.com/bitcoin/bitcoin/pull/26356
3382022-10-20T19:10:36 <laanwj> #topic Drop GUI repo and bring GUI work back to the main repo for now (achow101)
3392022-10-20T19:10:36 <core-meetingbot> topic: Drop GUI repo and bring GUI work back to the main repo for now (achow101)
3402022-10-20T19:11:11 <jarolrod> i don't have a strong opinion on wether we move in the development from bitcoin-core/gui into bitcoin/bitcoin
3412022-10-20T19:11:25 <achow101> I was speaking with some contributors last week at CoreDev about repo separation, and some dissastisfaction with the current GUI repo split was discussed. In particular, some contributors felt that the separation makes it difficult to work on the GUI as it is not that obvious that there is a separate GUI repo. This has lead to things in the GUI repo getting little review since many forget that it even exists. It is also confusing to new
3422022-10-20T19:11:26 <achow101> contributors as the GUI is in the main repo, so work can be done in a fork of the main repo before realizing that the GUI repo exists. There was also a concern about funding as some funders may not recognize that the GUI repo is in fact part of Bitcoin Core.
3432022-10-20T19:12:27 <luke-jr> a fork of the main repo can push to the GUI repo just as wellâ¦
3442022-10-20T19:12:41 <achow101> While I agree that we should want to have components of Bitcoin Core separated into separate repos, I think doing so now is premature. We should perhaps wait until it is possible to fully separate componenets before doing so. That way, cloning the main repo does not fetch the GUI repo, and work on each specific component requires going to each individual repo to even get the code.
3452022-10-20T19:12:49 <vasild> it is somewhat confusing for me too
3462022-10-20T19:12:51 <glozow> fanquake is asleep, so i'm relaying this gist from him on the topic https://gist.github.com/fanquake/2448cfac814c633c9109670ed4152ea8
3472022-10-20T19:12:52 <luke-jr> and funding issues should be sorted out at the funding level, which really should not be specific to Core at all, much less a single repo :/
3482022-10-20T19:12:52 <hebasto> quoting fanquake from oct 15 "I think merging GUI development back into the main repo would quite be a regression. As far as I'm aware, for non-GUI contributors, it's been a great filter for keeping all the not-related-to-bitcoin GUI stuff out of their inboxes (probably similar for the thousands of bitcoin/bitcoin subscribers)."
3492022-10-20T19:13:01 <laanwj> it's mostly to have the PRs and issues separate, we can't really move them back
3502022-10-20T19:13:23 <hebasto> agree with fanquake
3512022-10-20T19:13:27 <jarolrod> The reality with gui development is that sometimes trivial things are discussed or trivial pr's are opened, if it's really annoying for some to see these discussions pop up, then it's best to keep the repo's as they are
3522022-10-20T19:13:34 <laanwj> it would involve closing everything and reopening it in the main repo, which, yeah seems a lot of hassle
3532022-10-20T19:13:38 <luke-jr> I don't feel strongly for keeping them split, but I don't think all the reasons are great for a re-merge
3542022-10-20T19:13:39 <ariard> i think you're point is bundling few different things: a) a communication issue about the component existence, b) the management of interdependency and c) the social/professional recognition of working on the GUI
3552022-10-20T19:13:39 <achow101> luke-jr: AFAICT GitHub does not allow you to open PRs unless the repo is a direct fork
3562022-10-20T19:13:50 <luke-jr> achow101: you can still push your git repo to the fork of the GUI
3572022-10-20T19:14:16 <achow101> luke-jr: yes, but this may be confusing to new contributors
3582022-10-20T19:14:39 <hebasto> re "is not that obvious that there is a separate GUI repo" it is clearly documented, starting from https://github.com/bitcoin/bitcoin/blob/master/README.md
3592022-10-20T19:14:54 <achow101> hebasto: personally there are some gui things that I would like to review, but they always fall off my list because I forget it's existence
3602022-10-20T19:14:57 <luke-jr> perhaps better docs?
3612022-10-20T19:15:02 <luke-jr> and/or getting Github to fix it
3622022-10-20T19:15:09 <luke-jr> if we move to Gitlab, does that resolve it?
3632022-10-20T19:15:13 <achow101> I would find it easier if its issues and prs would be in the same repo
3642022-10-20T19:15:15 <laanwj> add a link in the top-level README maybe?
3652022-10-20T19:15:32 <laanwj> if there isn't, i wouldn't know
3662022-10-20T19:16:01 <achow101> I don't think "user education" (dev education I guess) is really a good solution. It's just not intuitive
3672022-10-20T19:16:29 <ariard> achow101: tbh, few contributors have already to live in a multi repo world, in the sense monitoring libsecp256k1, the bips repo, the bolts repo, maybe a lightning implem, maybe bitcoin-inquisition, sounds more a question of personal time-management
3682022-10-20T19:16:40 *** fanta1 <fanta1!~fanta1@2a01:c23:7156:2500:a98f:c325:a945:6964> has quit IRC (Quit: fanta1)
3692022-10-20T19:18:24 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
3702022-10-20T19:18:44 <jarolrod> I would be ok with either option, but in terms of not redoing a time of work moving between repo's, I'd think that we should keep the repo's as they are
3712022-10-20T19:18:53 <jarolrod> another point brought up was on the qml gui and the future of the gui
3722022-10-20T19:18:56 <brunoerg> jarolrod: +1
3732022-10-20T19:18:59 <jarolrod> information on that has been condensed here: https://bitcoincore.app/
3742022-10-20T19:19:14 <jarolrod> development on bitcoin-core/gui-qml has been slow, at times it's only been me working on it, but that is where the future of the gui is
3752022-10-20T19:19:24 <jarolrod> What I can promise is i'll be spending as much time as possible as I can to finish this before the next release, it doesn't mean we'd include it in core at that time, but the conversation can start on what we're going to do with the gui in terms of the development process and the structure of repo's
3762022-10-20T19:19:39 <jarolrod> We're building something special there, if you're interested in seeing how we're progressing you can join in on our calls every wednesday at 14 UTC here: https://meet.jit.si/BitcoinCoreAppDesignCall
3772022-10-20T19:19:47 <achow101> re trivial stuff in gui: I don't think that's a strong argument. we get lots of dumb and trivial stuff in the main repo too
3782022-10-20T19:20:17 <achow101> I don't think it would be any more annoying than it already is
3792022-10-20T19:20:25 <hebasto> merging repos is going to bring more dissatisfaction among developers then now...
3802022-10-20T19:20:26 <luke-jr> jarolrod: I'm against prematurely deciding QML is going to replace Widgets..
3812022-10-20T19:20:50 <jarolrod> ^ of course, not dictating, just my opinion :D
3822022-10-20T19:21:40 <achow101> ariard: for the most part, those repos don't share any code. right now, the main repo and the gui repo are completely clones of each other, so if you want the gui, you can still get it in the main repo. this is not the case for the others you mentioned
3832022-10-20T19:21:58 <achow101> my point was that repo separation should follow with code separation
3842022-10-20T19:22:11 <luke-jr> achow101: I don't think you've made a strong argument for that
3852022-10-20T19:22:24 <luke-jr> half of the reasons seem frankly like reasons _to_ keep them separated
3862022-10-20T19:23:02 <laanwj> right it's just an organizational thing, so you an ignore GUI stuff if you want to
3872022-10-20T19:23:10 <achow101> people forget that it exists and it's harder for new contributors is a reason to keep them separate??
3882022-10-20T19:24:33 <ariard> achow101: at least, they share libsecp256k1; though my point was more an answer to "oh wait i've to remember there is a GUI repo" thought, it sounds to belong more to one's workflow and personal priorities
3892022-10-20T19:24:35 *** Talkless <Talkless!~Talkless@mail.dargis.net> has quit IRC (Quit: Konversation terminated!)
3902022-10-20T19:24:38 <laanwj> if new contributors file a GUI pr/issue in the main repo it's not a big deal they usually just get pointed to the right one
3912022-10-20T19:24:43 <luke-jr> achow101: no, those are the arguments to re-merge; but ultimately problems better dealt with other ways even then
3922022-10-20T19:25:00 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:401d:2d18:c10d:4831> has quit IRC (Remote host closed the connection)
3932022-10-20T19:25:18 <luke-jr> I need to go pick up kids from school; but FWIW: there are some maintainers I don't trust with org ownership (and others I would); no opinion on refactor freeze; and against "anti-feature" fullrbf changes
3942022-10-20T19:25:28 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:401d:2d18:c10d:4831> has joined #bitcoin-core-dev
3952022-10-20T19:26:15 <furszy> I personally haven't seen much movement on the current GUI repo, which pulled me down from continue contributing there. Not sure if that is because of the separated repository or because all our resources are focused on the QML project (which make sense if we are just going to replace the GUI entirely)
3962022-10-20T19:26:16 <laanwj> there's still 3 other topics left, we might want to move to a next one
3972022-10-20T19:26:30 <glozow> (meta-meeting comment: i wonder if we'll run out of time to discuss v24.0 full rbf? not to discount achow's proposed topics, but perhaps worth reordering based on urgency...?)
3982022-10-20T19:26:58 <laanwj> glozow: agree
3992022-10-20T19:27:04 <NorrinRadd> achow101 would it help if the gui code is removed from the main report and instead referenced?
4002022-10-20T19:27:05 <ariard> glozow: +1, we're already half-meeting time, and other subjects could be post-pone to next meetings
4012022-10-20T19:27:09 <achow101> glozow: yes (my topics are not urgent)
4022022-10-20T19:27:19 <instagibbs> glozow, sounds like volunteering to take on the topic]
4032022-10-20T19:27:25 * instagibbs logs off
4042022-10-20T19:27:44 <NorrinRadd> anecdote: I'm a very new comer and I came across the documentation that teh gui is maintained in a different repo
4052022-10-20T19:28:03 <achow101> NorrinRadd: I think so. If we could get to a point where the gui could be removed from the main repo, and put into it's own repo with just the gui, then I think repo separation makes sense there
4062022-10-20T19:28:07 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
4072022-10-20T19:28:33 <laanwj> yes, true gui repo separation would definitely be better
4082022-10-20T19:28:47 <laanwj> i think that's something to work towards, not going backwards
4092022-10-20T19:28:59 <hebasto> our release process should be modified for that
4102022-10-20T19:29:04 <glozow> agree working towards true separation would be great
4112022-10-20T19:29:07 <jonatack> hi
4122022-10-20T19:29:18 <laanwj> hi
4132022-10-20T19:29:45 *** bytes1440000 <bytes1440000!~bytes1440@212-129-37-129.rev.poneytelecom.eu> has joined #bitcoin-core-dev
4142022-10-20T19:30:24 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:401d:2d18:c10d:4831> has quit IRC (Ping timeout: 272 seconds)
4152022-10-20T19:30:31 <laanwj> ok, ew can continue this next meeting if needed, going for next topic
4162022-10-20T19:30:36 <laanwj> #topic defer fullrbf for 24.0(or not) (instagibbs)
4172022-10-20T19:30:36 <core-meetingbot> topic: defer fullrbf for 24.0(or not) (instagibbs)
4182022-10-20T19:30:45 <instagibbs> mempoolfullrbf in mainnet(or not): #26323 does two things: disables mempoolfullrbf on mainnet until ~6 months from now, then switches the argument to default true. The intention was to get it into 24.0 This needs to be decided
4192022-10-20T19:30:47 <gribble> https://github.com/bitcoin/bitcoin/issues/26323 | Make full RBF default, but defer mainnet enablement by ajtowns · Pull Request #26323 · bitcoin/bitcoin · GitHub
4202022-10-20T19:31:28 <ariard> this mail published today is a good resume of the alternatives and dimensions of analysis https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-October/021075.html
4212022-10-20T19:31:33 <instagibbs> specifically the "disable on mainnet" or not part, due to release. I have my own opinion, and there are many others of course
4222022-10-20T19:31:33 <achow101> nack-ish. I don't like that I can't turn it on before the flag day.
4232022-10-20T19:32:05 *** sebareca <sebareca!~sebareca@190.194.221.154> has quit IRC (Quit: Client closed)
4242022-10-20T19:32:25 *** sebareca <sebareca!~sebareca@190.194.221.154> has joined #bitcoin-core-dev
4252022-10-20T19:32:48 <ariard> instagibbs: i think there are still voices of 0confs operators who sounds to oppose full-rbf itself, maybe a preliminary concern to think about before the deployment method we pick up
4262022-10-20T19:33:25 <instagibbs> ariard, I feel pretty safe not stalling to people who dont understand it's changing eventually
4272022-10-20T19:34:00 <achow101> I feel like we had this conversation 7 years ago
4282022-10-20T19:34:43 <instagibbs> Anyways, this is about the release specifically. If there's general consensus against disabling, we should just say we're not doing that
4292022-10-20T19:34:52 <instagibbs> then work on part 2 which is flag day window/strategy
4302022-10-20T19:34:57 <ariard> instagibbs: i think this is reasonable outcome, evaluating we have done a satisfying work of communication ahead, and those folks are running after a subject already reaching majority of opinions
4312022-10-20T19:35:05 <ariard> just notifiying the existence of those voices
4322022-10-20T19:35:08 <_aj_> achow101: wasn't the result of the conversation 7 years ago that people who wanted rbf would opt-in to it, per bip 125?
4332022-10-20T19:35:31 <instagibbs> I'd rather not relitigate, this is about 24.0 :)
4342022-10-20T19:36:53 <instagibbs> If we need more time to discuss flag day, we need more time to discuss it and should just work that direction
4352022-10-20T19:37:06 <ariard> i don't think 7 years ago the pinning issues which are affecting lightning/coinjoins and have been the original technical motivation of this renewed full-rbf deployment were known by the community, to be fair
4362022-10-20T19:37:47 <achow101> I don't mind a flag day so long as it is _only_ to change the default to true. a flag day for disabling the option is nack from me
4372022-10-20T19:38:10 <achow101> but then in that case, it doesn't seem to be much different from just releasing 25.0 with -mempoolfullrbf=1
4382022-10-20T19:38:16 <instagibbs> so I motion to keep arg static and false, and continue conversation about flag day
4392022-10-20T19:39:01 <jonatack> (fwiw, i found the serge kotliar (bitrefill) ML post on the topic (relating to FX volatility in addition to zero conf) interesting as well, though i haven't finished parsing it; suggest reading it along with the post by dario (muun wallet) regarding zero conf
4402022-10-20T19:39:17 <glozow> I think whatever option we take, it should be made abundantly clear to users that Core does not control whether full RBF happens or not. We could revert 25353 and it could still happen. We could do a flag day activation and it could happen sooner than that. I imagine that a coordinated full RBF activation is the smoothest/safest if everybody reasonable agrees to it, but then others might yell at Core for "dictating policy."
4412022-10-20T19:39:34 <ariard> let's phrase the discussion in another way; do we think the activation of full-rbf X months from now would cause unsolvable dangers for 0confs apps/services ?
4422022-10-20T19:39:42 <instagibbs> achow101, heck 26.0. It's simpler yes
4432022-10-20T19:39:56 <ariard> in the sense, do we think the issues raised by full-rbf on their services, are technicall solvable if they allocate the engineering and operational efforts
4442022-10-20T19:41:04 <achow101> ariard: I think all of the issues these services have raised are solvable, with the most basic solution that most services have decided to use being wait for a confirmation
4452022-10-20T19:41:24 <instagibbs> "solve the free option problem" is a bit out of scope for Core
4462022-10-20T19:41:40 <glozow> the free option problem is already a thing, according to Sergej's ml post
4472022-10-20T19:41:44 <_aj_> ariard: for muun, which is lightning focussed anyway; 6 months sounds fine; for bitrefill, seems like it would take 2 years or more to get lightning adoption high enough to be smooth
4482022-10-20T19:41:54 <_aj_> ariard: (going from what they've said on list)
4492022-10-20T19:42:06 <instagibbs> _aj_, it would tie policy directly to a specific L2 protocol, so I nack on any metric like this
4502022-10-20T19:42:23 <ariard> instagibbs: to me, that's a bit of the crux of the discussions between core and business, what is the scope of policy mechanisms and from what they should be responsible of?
4512022-10-20T19:42:34 <_aj_> instagibbs: huh?
4522022-10-20T19:42:58 <instagibbs> _aj_, "my deposits must be X% in this specific type"
4532022-10-20T19:43:06 <ariard> _aj_: yes, the last muun replied also underscore other 0confs services, with less manpower/engineering resources might need more time
4542022-10-20T19:43:09 <_aj_> instagibbs: it'd tie policy to having some replacement for on-chain zeroconf; with lightning being the most likely replacement
4552022-10-20T19:43:29 <_aj_> instagibbs: if fedimint or something comes along and takes over in the meantime, that's fine too?
4562022-10-20T19:43:35 <instagibbs> failed TTP business-y ideas have been around for almost 8 years
4572022-10-20T19:43:41 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:401d:2d18:c10d:4831> has joined #bitcoin-core-dev
4582022-10-20T19:43:46 <glozow> ariard: the technical issues are solvable, it sounds like muun just wants more time. Bitrefill is able to detect payment replacements and already has some double spend protections, the problem there is UX
4592022-10-20T19:44:34 <ariard> glozow: i'm converging, though note a bad UX might be a source of users funds loss or freezing or mistakes, especially if they have to shipped it fast
4602022-10-20T19:44:57 <instagibbs> _aj_, well, if they said "2 years", maybe I'd be fine
4612022-10-20T19:45:11 <glozow> i mean they also told me they had revert using bech32 addresses because most users couldn't pay them
4622022-10-20T19:45:17 <glozow> back in the day
4632022-10-20T19:45:36 <_aj_> instagibbs: ziggamon just said "years", definitely not 2
4642022-10-20T19:45:47 <instagibbs> _aj_, 1.01 years
4652022-10-20T19:45:52 <ariard> on the other hand, advocating the coinjoin/lightning-side, the pinning vector has been exercised on mainet https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-July/020737.html
4662022-10-20T19:46:23 <ariard> and as we see more collaboritve constructions applications, we could deanonymizing attackers leveraging this vector during the next X months/years period of full-rbf transition, just saying
4672022-10-20T19:47:26 <ariard> s/collaboritve/collaborative/g
4682022-10-20T19:48:11 *** _Sam-- <_Sam--!~sam@20.171.51.152> has quit IRC (Remote host closed the connection)
4692022-10-20T19:49:23 <NorrinRadd> have the workarounds for 0 conf operators been documented in any one place where they can be easily referenced?
4702022-10-20T19:49:41 <_aj_> there aren't workaround, though?
4712022-10-20T19:49:47 <ariard> NorrinRadd: no single point documentation i'm aware of
4722022-10-20T19:50:09 <ariard> _aj_: distributed monitoring of network mempools, Bitrefill does something like this iiuc
4732022-10-20T19:50:32 <_aj_> ariard: they do that for txs that don't opt-in to rbf; things that are rbf-able just get excluded from zeroconf
4742022-10-20T19:50:53 <NorrinRadd> 'waiting for confirmation' doesn't seem desirable. stores with large foot traffic would have people standing around for an hour sometimes waiting for their payment to confirm.
4752022-10-20T19:51:36 <NorrinRadd> if bitrefill is waiting to see if replacement transactions appear, then they're essentially not doing zero conf anymore?
4762022-10-20T19:52:10 <ariard> _aj_: so i'm following correctly, if full-rbf happens and all the incoming transaction traffic is repleacable such protection would still allow to accept 0conf traffic
4772022-10-20T19:52:12 <NorrinRadd> _aj_ oh thanks
4782022-10-20T19:52:57 <NorrinRadd> so once everything is rbf it would effectively kill their zero conf transactions.
4792022-10-20T19:53:15 <ariard> okay as we're reaching end of meeting, do we think we prefer to go with a smooth, uncoordinated deployment or a flag day activation ?
4802022-10-20T19:53:34 <instagibbs> achow101, makes a reasoanble point, why not just flip it for future release
4812022-10-20T19:53:39 <instagibbs> like.... 26.0
4822022-10-20T19:53:41 <ariard> #26305 or #26323
4832022-10-20T19:53:42 <gribble> https://github.com/bitcoin/bitcoin/issues/26305 | Enable `mempoolfullrbf=1` by default by ariard · Pull Request #26305 · bitcoin/bitcoin · GitHub
4842022-10-20T19:53:44 <gribble> https://github.com/bitcoin/bitcoin/issues/26323 | Make full RBF default, but defer mainnet enablement by ajtowns · Pull Request #26323 · bitcoin/bitcoin · GitHub
4852022-10-20T19:53:56 <_aj_> ariard: at the moment, 15% of their txs are lightning, 20% are opt-in rbf, and the remaining 65% aren't rbf-able. of the 65% -- 60% are treated as zeroconf, 5% are excluded from zeroconf due to negative signals from the monitoring. with fullrbf, that entire 65% gets excluded from zeroconf, and lightning is the only way to get instant confirmations
4862022-10-20T19:53:59 <achow101> 26305 for a future release
4872022-10-20T19:54:19 <instagibbs> right
4882022-10-20T19:54:34 <_aj_> if we're not going to remove the mempoolfullrbf option from 24.0, we're going for an uncoordinated deployment either way
4892022-10-20T19:54:48 <instagibbs> im already running full rbf with preferential peering...
4902022-10-20T19:55:12 <instagibbs> ship has sailed, the question is will 5%+ set a variable. I suspect not
4912022-10-20T19:55:20 <ariard> _aj_: that's a correct, though i don't think it's something like binary, more uncoordinated with the option existent or something like preferential peering
4922022-10-20T19:56:31 <_aj_> instagibbs: uasf uacomment demonstrated it's easy to get ~11% to set a variable in just a couple of weeks
4932022-10-20T19:56:37 <lightlike> i think that if a meaningful number of node operators and miners want a specific policy, it shouldn't be on the devs to tell them "you can't have that now". Devs can and should give a recommendation (by picking the default), but providing options to informed users should never be a problem.
4942022-10-20T19:57:00 <bytes1440000> if 24.0 has mempoolrbf, devs have lot of time to discuss and convince a few nodes and miners to run it. no default required or will have better insights.
4952022-10-20T19:57:01 <laanwj> lightlike: +1
4962022-10-20T19:57:01 <bytes1440000> making default on signet, testnet still makes sense for testing
4972022-10-20T19:57:02 <instagibbs> _aj_, exception that proves the rule
4982022-10-20T19:57:07 <ariard> _aj_: about the 65% aren't rbf-able, what i don't understand is if Bitrefill is aware that you can still double-spend not rbf-able transactions, it's just higher technical bar?
4992022-10-20T19:57:23 <ariard> (well i think they're aware of, what they say is they don't see that happening)
5002022-10-20T19:57:46 <vasild> lightlike: +1
5012022-10-20T19:57:56 <ariard> lightlike: that was the original thinking with #25600
5022022-10-20T19:57:58 <_aj_> ariard: "can" equates to "less than a 0.0001% chance of it actually happening" according to ziggamon
5032022-10-20T19:57:59 <gribble> https://github.com/bitcoin/bitcoin/issues/25600 | p2p: Advertise `NODE_FULL_RBF` and connect to 4 outbound full-rbf peers if `-mempoolfullrbf` is set by ariard · Pull Request #25600 · bitcoin/bitcoin · GitHub
5042022-10-20T19:58:42 <bytes1440000> 25600 is the worst possible way to make fullrbf default
5052022-10-20T19:58:54 <instagibbs> 2 minutes
5062022-10-20T19:58:59 <ariard> _aj_: so according to that statement, they might be still be fine to not exclude this future 65% traffic from zero-conf acceptance
5072022-10-20T19:59:13 <_aj_> ariard: no
5082022-10-20T19:59:17 <b10c> i think only having an option defaulting to false for 24 (no preferable peering) won't result in a lot of node operators actually enabling it. Especially if no Umbrel/RaspiBlitz/etc enables it by default
5092022-10-20T20:00:22 <NorrinRadd> someone can link to a document that shows the arguments for fullrbf?
5102022-10-20T20:00:26 <laanwj> we'll have to close the meeting in a minute... but feel free to continue afterwards ofc
5112022-10-20T20:00:26 <instagibbs> We'll put a blanket ban on hats in the interim
5122022-10-20T20:00:57 <ariard> _aj_: let me read again Sergej mails, what's Bitrefill position if full-rbf become the norm? (we might def invite 0confs operators to irc meetings)
5132022-10-20T20:01:35 <ariard> NorrinRadd: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-June/020557.html
5142022-10-20T20:01:53 <glozow> ariard: my impression is an agreement that it is inevitable, but if it happens before users have a lot of access to LN, it might just make Bitcoin worse
5152022-10-20T20:02:39 <lightlike> b10c: I think enabling it for the miners is more critical anyway. Anyone could set up some manually adjusted full-RBF nodes that make hundreds of outbound connections to all reachable peers at quite low costs.
5162022-10-20T20:03:14 *** gnaf <gnaf!~gnaf@2a02-a454-54e2-1-10f6-6b6f-5432-2697.fixed6.kpn.net> has quit IRC (Quit: Konversation terminated!)
5172022-10-20T20:03:50 <NorrinRadd> ariard i read it. it basically kills zero conf but he also said there's something worse; replacements will be further incentized by changes in exchange rates, where customers will adjust their sats paid lower if bitcoin goes up in price after the purchase was made. which creates business risk for the zero conf merchants.
5182022-10-20T20:04:08 <NorrinRadd> ariard thank you
5192022-10-20T20:04:17 *** ___nick___ <___nick___!~quassel@cpc68289-cdif17-2-0-cust317.5-1.cable.virginm.net> has quit IRC (Ping timeout: 260 seconds)
5202022-10-20T20:04:28 <ariard> glozow: and letting dual-funded lightning channels susceptible to a DoS vector might slow down further the access to LN, maybe a bit of "chicken-and-eggs" here...
5212022-10-20T20:05:29 <ariard> NorrinRadd: yeah see instagibbs thought expressed earlier, is fiat volatility risk really in the scope of Core, dik
5222022-10-20T20:05:30 <glozow> ariard: i agree.
5232022-10-20T20:05:32 <ariard> idk
5242022-10-20T20:06:10 <NorrinRadd> Sergej did also mention that when they've asked people to pay in bech32 before, instead of filing issues, they simple left the site. so his thought is that if he's asking customers for LN, they will not seek out an LN wallet. They'll simple leave and go somewhere else.
5252022-10-20T20:06:26 <glozow> quoted from Sergej's post about the american call option, "It's already possible to execute this form of abuse with opt-in RBF"
5262022-10-20T20:06:48 <instagibbs> I noted that its in their incentive structure to CPFP if the price goes their way...
5272022-10-20T20:07:06 <instagibbs> Merchants can only offload so much of their business complexity to others, sorry
5282022-10-20T20:07:15 <ariard> NorrinRadd: i can opinate here, deploying a LN infrastructure server-side is a hard requirement on merchants, managing funds safety/liquidity, a different key management, hopefully we don't centralize the merchant ecosystem with short-timed full-rbf deployment
5292022-10-20T20:07:37 <_aj_> instagibbs: easy to diss on stakeholders that aren't present...
5302022-10-20T20:08:01 <instagibbs> not a diss, and I've personally discussed this issue with sergej many times
5312022-10-20T20:08:47 <ariard> _aj_: i share the sentiment, sounds we don't have the right crowd to have a best-informed technical view
5322022-10-20T20:08:50 <instagibbs> We just have different goals, and that's ok!
5332022-10-20T20:10:19 <instagibbs> when goals conflict, we try for maximum understanding, and that's what we're doing I hope
5342022-10-20T20:10:22 <jonatack> it may still be good to have this discussion with them present and participating
5352022-10-20T20:10:37 <ariard> okay as it would be better to end the meeting at some point, i'm thinking to reply to last Dario's mail, saying while full-rbf is still liked people, there is no emergening majority opinion on the deployment method and what's an adequate timeframe would still benefit from more feedbacks from the merchant community
5362022-10-20T20:10:39 <jonatack> instagibbs: yes!
5372022-10-20T20:10:46 <instagibbs> the email thread is pretty high quality
5382022-10-20T20:11:01 <glozow> i guess something that should be said is "for the people who want to turn full rbf on their own nodes, does it matter if the -mempoolfullrbf option doesn't go in v24.0?"
5392022-10-20T20:12:41 <ariard> glozow: i think full-rbf setting is already used by at least one electrum server operator, and few other services
5402022-10-20T20:14:25 <laanwj> #endmeeting
5412022-10-20T20:14:25 <core-meetingbot> topic: Bitcoin Core development discussion and commit log | Feel free to watch, but please take commentary and usage questions to #bitcoin | Channel logs: http://www.erisian.com.au/bitcoin-core-dev/, http://gnusha.org/bitcoin-core-dev/ | Meeting topics http://gnusha.org/bitcoin-core-dev/proposedmeetingtopics.txt / http://gnusha.org/bitcoin-core-dev/proposedwalletmeetingtopics.txt
5422022-10-20T20:14:25 <core-meetingbot> Meeting ended Thu Oct 20 20:14:25 2022 UTC.
5432022-10-20T20:14:25 <core-meetingbot> Minutes: https://bitcoin.jonasschnelli.ch/ircmeetings/logs/bitcoin-core-dev/2022/bitcoin-core-dev.2022-10-20-19.00.moin.txt
5442022-10-20T20:14:29 <glozow> so then the question is, if this is one of our only blockers for v24.0, and the people who would use the option don't need it anyway... why not just take it out?
5452022-10-20T20:14:35 <glozow> *ducks*
5462022-10-20T20:14:43 <glozow> (just putting it out there)
5472022-10-20T20:15:34 <ariard> glozow: imho, their use-cases are as much legitimate than the 0confs ones, and i have no strong idea on how we should arbiter in the present case...
5482022-10-20T20:16:09 <instagibbs> I'm lobbying for it not to be a blocker
5492022-10-20T20:16:10 <instagibbs> :P
5502022-10-20T20:16:52 *** bytes1440000 <bytes1440000!~bytes1440@212-129-37-129.rev.poneytelecom.eu> has left #bitcoin-core-dev
5512022-10-20T20:17:09 <_aj_> glozow: if you really want answers to that question, create a PR reverting it, and collect the nacks
5522022-10-20T20:18:08 <glozow> well yes, that was #26287 and i nacked it. just wanted to put it out there
5532022-10-20T20:18:10 <gribble> https://github.com/bitcoin/bitcoin/issues/26287 | Temporarily disable -mempoolfullrbf for the main chain by MarcoFalke · Pull Request #26287 · bitcoin/bitcoin · GitHub
5542022-10-20T20:20:31 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 258 seconds)
5552022-10-20T20:26:35 *** esneider <esneider!~esneider@190.194.221.154> has quit IRC (Quit: Client closed)
5562022-10-20T20:26:42 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 252 seconds)
5572022-10-20T20:27:17 <hebasto> some discussions related to the GUI code separation can be found in #24911
5582022-10-20T20:27:18 <gribble> https://github.com/bitcoin/bitcoin/issues/24911 | [POC] [RFC] build: Separate GUI application build system · Issue #24911 · bitcoin/bitcoin · GitHub
5592022-10-20T20:30:51 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:401d:2d18:c10d:4831> has quit IRC ()
5602022-10-20T20:32:18 *** amovfx <amovfx!~amovfx@d75-156-179-9.abhsia.telus.net> has joined #bitcoin-core-dev
5612022-10-20T20:37:03 *** champo <champo!~champo@host140.190-227-156.telecom.net.ar> has quit IRC (Quit: Client closed)
5622022-10-20T20:37:32 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Remote host closed the connection)
5632022-10-20T20:37:46 *** amovfx <amovfx!~amovfx@d75-156-179-9.abhsia.telus.net> has quit IRC (Ping timeout: 258 seconds)
5642022-10-20T20:38:05 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
5652022-10-20T20:43:34 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
5662022-10-20T20:48:44 *** sebareca <sebareca!~sebareca@190.194.221.154> has quit IRC (Quit: Client closed)
5672022-10-20T20:49:20 *** csgui <csgui!~csgui@221.194.115.89.rev.vodafone.pt> has quit IRC (Quit: Client closed)
5682022-10-20T20:56:29 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
5692022-10-20T21:00:48 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 252 seconds)
5702022-10-20T21:06:51 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
5712022-10-20T21:10:30 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
5722022-10-20T21:31:40 *** hg <hg!~halosghos@user/halosghost> has joined #bitcoin-core-dev
5732022-10-20T22:07:55 *** _andrewtoth_ <_andrewtoth_!~andrewtot@gateway/tor-sasl/andrewtoth> has quit IRC (Remote host closed the connection)
5742022-10-20T22:09:20 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
5752022-10-20T22:10:12 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 255 seconds)
5762022-10-20T22:13:31 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
5772022-10-20T22:21:23 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
5782022-10-20T22:21:34 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
5792022-10-20T22:25:46 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)
5802022-10-20T22:33:26 *** dermoth <dermoth!~dermoth@user/dermoth> has quit IRC (Ping timeout: 272 seconds)
5812022-10-20T22:45:26 *** dermoth <dermoth!~dermoth@user/dermoth> has joined #bitcoin-core-dev
5822022-10-20T22:46:04 *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has quit IRC (Ping timeout: 246 seconds)
5832022-10-20T22:46:30 *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has joined #bitcoin-core-dev
5842022-10-20T22:55:02 *** amovfx <amovfx!~amovfx@node-1w7jr9yi65te5ujpx628y9xci.ipv6.telus.net> has joined #bitcoin-core-dev
5852022-10-20T23:13:04 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Remote host closed the connection)
5862022-10-20T23:23:48 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 252 seconds)
5872022-10-20T23:38:28 *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has quit IRC (Ping timeout: 252 seconds)
5882022-10-20T23:43:17 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has joined #bitcoin-core-dev
5892022-10-20T23:45:04 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
5902022-10-20T23:48:22 *** amovfx_ <amovfx_!~amovfx@node-1w7jr9yi65te76avgv6tof5ba.ipv6.telus.net> has quit IRC (Ping timeout: 246 seconds)