12022-06-30T00:03:06 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 264 seconds)
22022-06-30T00:03:46 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
32022-06-30T00:04:58 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:56a:641f:feb9:7ea5> has quit IRC (Remote host closed the connection)
42022-06-30T00:05:28 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
52022-06-30T00:05:31 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
62022-06-30T00:08:38 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 272 seconds)
72022-06-30T00:10:05 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 268 seconds)
82022-06-30T00:10:48 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
92022-06-30T00:11:48 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 272 seconds)
102022-06-30T00:14:52 *** emcy <emcy!~emcy@user/emcy> has quit IRC (Read error: Connection reset by peer)
112022-06-30T00:15:08 *** emcy <emcy!~emcy@user/emcy> has joined #bitcoin-core-dev
122022-06-30T00:16:17 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
132022-06-30T00:16:52 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 272 seconds)
142022-06-30T00:19:22 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
152022-06-30T00:20:18 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 240 seconds)
162022-06-30T00:22:43 *** emcy <emcy!~emcy@user/emcy> has quit IRC (Read error: Connection reset by peer)
172022-06-30T00:22:49 *** emcy_ <emcy_!~emcy@user/emcy> has joined #bitcoin-core-dev
182022-06-30T00:24:01 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
192022-06-30T00:24:52 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
202022-06-30T00:28:18 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 240 seconds)
212022-06-30T00:29:10 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
222022-06-30T00:30:10 *** emcy_ <emcy_!~emcy@user/emcy> has quit IRC (Read error: Connection reset by peer)
232022-06-30T00:30:19 *** emcy <emcy!~emcy@user/emcy> has joined #bitcoin-core-dev
242022-06-30T00:33:23 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has joined #bitcoin-core-dev
252022-06-30T00:33:27 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 246 seconds)
262022-06-30T00:37:39 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has quit IRC (Ping timeout: 246 seconds)
272022-06-30T00:37:52 *** emcy <emcy!~emcy@user/emcy> has quit IRC (Read error: Connection reset by peer)
282022-06-30T00:38:01 *** emcy_ <emcy_!~emcy@user/emcy> has joined #bitcoin-core-dev
292022-06-30T00:47:40 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
302022-06-30T00:49:14 <ariard> can i get #25353 in high-prio plz?
312022-06-30T00:49:16 <gribble> https://github.com/bitcoin/bitcoin/issues/25353 | Add a `-mempoolfullrbf` node setting by ariard · Pull Request #25353 · bitcoin/bitcoin · GitHub
322022-06-30T00:51:20 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
332022-06-30T00:52:20 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 272 seconds)
342022-06-30T00:56:08 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 272 seconds)
352022-06-30T00:57:59 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
362022-06-30T00:59:51 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
372022-06-30T01:00:48 *** emcy <emcy!~emcy@user/emcy> has joined #bitcoin-core-dev
382022-06-30T01:01:21 *** emcy_ <emcy_!~emcy@user/emcy> has quit IRC (Read error: Connection reset by peer)
392022-06-30T01:02:30 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
402022-06-30T01:04:21 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
412022-06-30T01:05:32 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
422022-06-30T01:08:15 *** emcy <emcy!~emcy@user/emcy> has quit IRC (Remote host closed the connection)
432022-06-30T01:08:19 *** emcy_ <emcy_!~emcy@user/emcy> has joined #bitcoin-core-dev
442022-06-30T01:09:38 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 240 seconds)
452022-06-30T01:15:38 *** emcy_ <emcy_!~emcy@user/emcy> has quit IRC (Read error: Connection reset by peer)
462022-06-30T01:15:58 *** emcy <emcy!~emcy@user/emcy> has joined #bitcoin-core-dev
472022-06-30T01:16:17 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
482022-06-30T01:16:19 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
492022-06-30T01:20:59 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
502022-06-30T01:22:50 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 268 seconds)
512022-06-30T01:27:41 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
522022-06-30T01:32:03 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 255 seconds)
532022-06-30T01:40:52 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
542022-06-30T01:44:39 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
552022-06-30T01:45:32 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 272 seconds)
562022-06-30T01:49:22 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
572022-06-30T02:01:50 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
582022-06-30T02:03:07 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
592022-06-30T02:06:54 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 246 seconds)
602022-06-30T02:12:47 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 268 seconds)
612022-06-30T02:19:39 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
622022-06-30T02:24:30 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
632022-06-30T02:24:43 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
642022-06-30T02:29:52 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 272 seconds)
652022-06-30T02:30:48 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
662022-06-30T02:35:36 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 268 seconds)
672022-06-30T02:36:05 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
682022-06-30T02:36:58 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
692022-06-30T02:38:42 *** kexkey <kexkey!~kexkey@static-198-54-132-110.cust.tzulo.com> has quit IRC (Ping timeout: 268 seconds)
702022-06-30T02:39:24 *** kexkey <kexkey!~kexkey@178.249.214.27> has joined #bitcoin-core-dev
712022-06-30T02:40:18 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 240 seconds)
722022-06-30T02:41:18 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 240 seconds)
732022-06-30T02:42:09 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
742022-06-30T02:46:54 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 264 seconds)
752022-06-30T02:47:22 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
762022-06-30T02:52:02 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 272 seconds)
772022-06-30T02:53:11 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
782022-06-30T02:58:10 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
792022-06-30T02:59:02 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
802022-06-30T03:00:38 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
812022-06-30T03:02:44 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 268 seconds)
822022-06-30T03:05:12 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 255 seconds)
832022-06-30T03:14:47 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
842022-06-30T03:18:14 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
852022-06-30T03:19:18 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 264 seconds)
862022-06-30T03:20:53 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
872022-06-30T03:23:05 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
882022-06-30T03:25:34 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 268 seconds)
892022-06-30T03:34:10 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
902022-06-30T03:37:31 *** vysn <vysn!~vysn@user/vysn> has joined #bitcoin-core-dev
912022-06-30T03:37:32 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
922022-06-30T03:38:18 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 240 seconds)
932022-06-30T03:41:44 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 248 seconds)
942022-06-30T03:48:20 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
952022-06-30T03:48:48 <bitcoin-git> [gui] jarolrod opened pull request #627: qt: apply translator comments to reset options confirmation dialog (master...617-followup) https://github.com/bitcoin-core/gui/pull/627
962022-06-30T03:49:27 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
972022-06-30T03:51:56 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Read error: Connection reset by peer)
982022-06-30T03:53:19 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 268 seconds)
992022-06-30T03:59:27 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1002022-06-30T04:00:41 *** Guest22 <Guest22!~Guest22@182.239.114.217> has joined #bitcoin-core-dev
1012022-06-30T04:01:01 *** cmirror <cmirror!~cmirror@4.53.92.114> has quit IRC (Remote host closed the connection)
1022022-06-30T04:01:32 *** cmirror <cmirror!~cmirror@4.53.92.114> has joined #bitcoin-core-dev
1032022-06-30T04:04:24 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
1042022-06-30T04:05:00 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1052022-06-30T04:09:18 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 240 seconds)
1062022-06-30T04:11:06 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1072022-06-30T04:16:11 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1082022-06-30T04:21:04 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 268 seconds)
1092022-06-30T04:21:42 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 264 seconds)
1102022-06-30T04:26:46 <dhruv> Just pushed to #23233, but CI just refused to trigger altogether https://github.com/bitcoin/bitcoin/pull/23233/checks. Is there a way to trigger it without force-pushing a new sha?
1112022-06-30T04:26:48 <gribble> https://github.com/bitcoin/bitcoin/issues/23233 | BIP324: Add encrypted p2p transport {de}serializer by dhruv · Pull Request #23233 · bitcoin/bitcoin · GitHub
1122022-06-30T04:33:04 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1132022-06-30T04:34:08 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1142022-06-30T04:38:26 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 272 seconds)
1152022-06-30T04:39:04 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 272 seconds)
1162022-06-30T04:39:38 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has joined #bitcoin-core-dev
1172022-06-30T04:44:15 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has quit IRC (Ping timeout: 260 seconds)
1182022-06-30T04:47:03 <dhruv> force-pushed to re-trigger. it turns out sometimes cirrus doesn't figure out a new sha was pushed and keeps trying to checkout the old git objects that don't exist on that branch anymore.
1192022-06-30T04:50:25 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1202022-06-30T04:50:25 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1212022-06-30T04:54:38 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 240 seconds)
1222022-06-30T04:54:38 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 240 seconds)
1232022-06-30T04:56:35 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has joined #bitcoin-core-dev
1242022-06-30T05:00:51 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has quit IRC (Ping timeout: 246 seconds)
1252022-06-30T05:07:23 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1262022-06-30T05:08:01 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1272022-06-30T05:12:00 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 272 seconds)
1282022-06-30T05:12:33 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 255 seconds)
1292022-06-30T05:18:11 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1302022-06-30T05:22:43 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 268 seconds)
1312022-06-30T05:25:28 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1322022-06-30T05:30:07 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
1332022-06-30T05:35:03 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1342022-06-30T05:39:36 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 248 seconds)
1352022-06-30T05:41:07 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1362022-06-30T05:41:27 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1372022-06-30T05:45:18 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 240 seconds)
1382022-06-30T05:46:05 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 260 seconds)
1392022-06-30T05:51:55 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1402022-06-30T05:56:59 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 272 seconds)
1412022-06-30T05:58:32 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1422022-06-30T06:02:42 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1432022-06-30T06:07:00 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 255 seconds)
1442022-06-30T06:07:20 *** meshcoll- <meshcoll-!meshcollid@meshcollider.jujube.ircnow.org> has quit IRC (Ping timeout: 248 seconds)
1452022-06-30T06:08:22 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 268 seconds)
1462022-06-30T06:11:01 *** meshcollider <meshcollider!meshcollid@meshcollider.jujube.ircnow.org> has joined #bitcoin-core-dev
1472022-06-30T06:12:52 *** Guest22 <Guest22!~Guest22@182.239.114.217> has quit IRC (Quit: Client closed)
1482022-06-30T06:15:22 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1492022-06-30T06:19:43 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1502022-06-30T06:23:14 *** cold <cold!~cold@user/cold> has quit IRC (Quit: Quitting...)
1512022-06-30T06:23:34 *** cold <cold!~cold@user/cold> has joined #bitcoin-core-dev
1522022-06-30T06:24:24 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
1532022-06-30T06:25:28 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 272 seconds)
1542022-06-30T06:26:28 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1552022-06-30T06:30:48 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 248 seconds)
1562022-06-30T06:36:27 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1572022-06-30T06:37:17 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1582022-06-30T06:41:39 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 255 seconds)
1592022-06-30T06:43:20 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1602022-06-30T06:47:38 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 240 seconds)
1612022-06-30T06:57:10 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 240 seconds)
1622022-06-30T07:03:24 <bitcoin-git> [bitcoin] S3RK opened pull request #25507: wallet: don't add change fee to target if subtracting fees from output (master...correct_target_with_sffo) https://github.com/bitcoin/bitcoin/pull/25507
1632022-06-30T07:06:11 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has joined #bitcoin-core-dev
1642022-06-30T07:08:52 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1652022-06-30T07:11:16 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has quit IRC (Ping timeout: 268 seconds)
1662022-06-30T07:11:43 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1672022-06-30T07:13:18 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 264 seconds)
1682022-06-30T07:16:38 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 240 seconds)
1692022-06-30T07:25:50 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1702022-06-30T07:29:16 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Read error: Connection reset by peer)
1712022-06-30T07:40:04 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1722022-06-30T07:44:11 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1732022-06-30T07:46:28 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
1742022-06-30T07:47:30 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 264 seconds)
1752022-06-30T07:48:46 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has joined #bitcoin-core-dev
1762022-06-30T07:48:52 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
1772022-06-30T07:51:12 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has joined #bitcoin-core-dev
1782022-06-30T07:53:30 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has quit IRC (Ping timeout: 264 seconds)
1792022-06-30T08:01:46 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1802022-06-30T08:04:14 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Read error: Connection reset by peer)
1812022-06-30T08:16:02 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1822022-06-30T08:18:28 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1832022-06-30T08:20:56 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 268 seconds)
1842022-06-30T08:22:07 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1852022-06-30T08:22:13 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Remote host closed the connection)
1862022-06-30T08:24:01 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
1872022-06-30T08:27:07 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 268 seconds)
1882022-06-30T08:27:39 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has joined #bitcoin-core-dev
1892022-06-30T08:32:39 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has quit IRC (Ping timeout: 268 seconds)
1902022-06-30T08:33:06 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1912022-06-30T08:35:22 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1922022-06-30T08:36:18 *** belcher <belcher!~belcher@user/belcher> has joined #bitcoin-core-dev
1932022-06-30T08:37:54 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 264 seconds)
1942022-06-30T08:38:24 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1952022-06-30T08:40:22 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 272 seconds)
1962022-06-30T08:43:32 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 272 seconds)
1972022-06-30T08:44:00 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
1982022-06-30T08:47:31 *** blkncd <blkncd!sid505676@helmsley.irccloud.com> has quit IRC (Ping timeout: 256 seconds)
1992022-06-30T08:47:39 *** blkncd <blkncd!sid505676@id-505676.helmsley.irccloud.com> has joined #bitcoin-core-dev
2002022-06-30T08:48:24 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 248 seconds)
2012022-06-30T08:51:46 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2022022-06-30T08:52:43 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
2032022-06-30T08:55:14 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
2042022-06-30T08:56:42 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
2052022-06-30T08:59:36 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 248 seconds)
2062022-06-30T09:06:02 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
2072022-06-30T09:08:41 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2082022-06-30T09:10:54 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 264 seconds)
2092022-06-30T09:12:06 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
2102022-06-30T09:13:18 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 264 seconds)
2112022-06-30T09:17:06 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 272 seconds)
2122022-06-30T09:17:24 *** jespada <jespada!~jespada@cpc121022-nmal24-2-0-cust171.19-2.cable.virginm.net> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzzâ¦)
2132022-06-30T09:17:34 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
2142022-06-30T09:22:30 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 260 seconds)
2152022-06-30T09:23:00 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
2162022-06-30T09:25:54 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2172022-06-30T09:25:58 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Ping timeout: 240 seconds)
2182022-06-30T09:27:52 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 272 seconds)
2192022-06-30T09:29:18 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
2202022-06-30T09:30:40 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 260 seconds)
2212022-06-30T09:33:47 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
2222022-06-30T09:38:30 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 255 seconds)
2232022-06-30T09:39:57 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has joined #bitcoin-core-dev
2242022-06-30T09:42:35 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2252022-06-30T09:46:38 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 240 seconds)
2262022-06-30T09:47:58 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has quit IRC (Ping timeout: 240 seconds)
2272022-06-30T10:00:53 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2282022-06-30T10:04:31 *** jarthur <jarthur!~jarthur@user/jarthur> has quit IRC (Quit: jarthur)
2292022-06-30T10:06:03 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 246 seconds)
2302022-06-30T10:11:24 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
2312022-06-30T10:16:15 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 268 seconds)
2322022-06-30T10:19:16 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2332022-06-30T10:21:44 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Read error: Connection reset by peer)
2342022-06-30T10:21:47 *** test_ <test_!flooded@gateway/vpn/protonvpn/flood/x-43489060> has joined #bitcoin-core-dev
2352022-06-30T10:24:55 *** flooded <flooded!flooded@gateway/vpn/protonvpn/flood/x-43489060> has quit IRC (Ping timeout: 260 seconds)
2362022-06-30T10:26:53 *** SpellChecker <SpellChecker!~SpellChec@user/SpellChecker> has quit IRC (Remote host closed the connection)
2372022-06-30T10:27:39 *** SpellChecker <SpellChecker!~SpellChec@user/SpellChecker> has joined #bitcoin-core-dev
2382022-06-30T10:33:27 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
2392022-06-30T10:34:28 *** flooded <flooded!flooded@gateway/vpn/protonvpn/flood/x-43489060> has joined #bitcoin-core-dev
2402022-06-30T10:35:59 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2412022-06-30T10:36:29 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Remote host closed the connection)
2422022-06-30T10:37:13 *** test_ <test_!flooded@gateway/vpn/protonvpn/flood/x-43489060> has quit IRC (Ping timeout: 268 seconds)
2432022-06-30T10:37:54 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 264 seconds)
2442022-06-30T10:39:33 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
2452022-06-30T10:40:42 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 272 seconds)
2462022-06-30T10:45:06 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 255 seconds)
2472022-06-30T10:45:50 *** vysn <vysn!~vysn@user/vysn> has quit IRC (Read error: Connection reset by peer)
2482022-06-30T10:50:39 <bitcoin-git> [bitcoin] fanquake opened pull request #25508: guix: use elfesteem 2eb1e5384ff7a220fd1afacd4a0170acff54fe56 (master...update_elfesteem) https://github.com/bitcoin/bitcoin/pull/25508
2492022-06-30T10:51:19 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
2502022-06-30T10:52:31 *** Guest48 <Guest48!~Guest48@110.87.32.95> has joined #bitcoin-core-dev
2512022-06-30T10:52:41 *** Guest48 <Guest48!~Guest48@110.87.32.95> has quit IRC (Client Quit)
2522022-06-30T10:53:10 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2532022-06-30T10:55:38 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 240 seconds)
2542022-06-30T10:57:23 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
2552022-06-30T10:57:35 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 260 seconds)
2562022-06-30T10:58:35 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
2572022-06-30T11:01:10 *** blkncd <blkncd!sid505676@id-505676.helmsley.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)
2582022-06-30T11:01:53 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 268 seconds)
2592022-06-30T11:09:49 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2602022-06-30T11:14:21 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 255 seconds)
2612022-06-30T11:16:41 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Remote host closed the connection)
2622022-06-30T11:17:23 <laanwj> ariard: added
2632022-06-30T11:19:01 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has joined #bitcoin-core-dev
2642022-06-30T11:23:21 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has quit IRC (Ping timeout: 255 seconds)
2652022-06-30T11:25:05 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
2662022-06-30T11:28:03 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2672022-06-30T11:29:39 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 268 seconds)
2682022-06-30T11:32:18 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 240 seconds)
2692022-06-30T11:41:25 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
2702022-06-30T11:43:53 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2712022-06-30T11:44:50 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 260 seconds)
2722022-06-30T11:46:58 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has joined #bitcoin-core-dev
2732022-06-30T11:48:15 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 246 seconds)
2742022-06-30T11:51:24 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has quit IRC (Ping timeout: 246 seconds)
2752022-06-30T11:53:03 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
2762022-06-30T11:58:00 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 268 seconds)
2772022-06-30T11:58:28 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
2782022-06-30T12:01:05 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2792022-06-30T12:01:47 *** ronoaldo <ronoaldo!~ronoaldo@2804:1b3:a8c0:f607:cae2:65ff:fe9b:69e6> has joined #bitcoin-core-dev
2802022-06-30T12:03:06 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 264 seconds)
2812022-06-30T12:04:28 *** z9z0b3t1c <z9z0b3t1c!~z9z0b3t1c@145.224.65.157> has quit IRC (Remote host closed the connection)
2822022-06-30T12:06:38 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
2832022-06-30T12:09:15 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
2842022-06-30T12:13:18 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 240 seconds)
2852022-06-30T12:15:19 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
2862022-06-30T12:18:24 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2872022-06-30T12:23:17 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
2882022-06-30T12:25:12 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 272 seconds)
2892022-06-30T12:26:08 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
2902022-06-30T12:30:41 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 268 seconds)
2912022-06-30T12:33:01 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has left #bitcoin-core-dev (Closing Window)
2922022-06-30T12:33:27 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
2932022-06-30T12:35:27 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2942022-06-30T12:38:50 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2952022-06-30T12:39:51 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 255 seconds)
2962022-06-30T12:42:18 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Read error: Connection reset by peer)
2972022-06-30T12:45:53 *** furszy <furszy!~furszy@user/furszy> has joined #bitcoin-core-dev
2982022-06-30T12:53:57 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2992022-06-30T12:55:16 <darosior> If you have a confirmed transaction, you `gettransaction` it. You then query `listsinceblock`with the 'blockhash' from the result of the `gettransaction`Â call. The transaction will not be returned. If you pass the blockhash of the previous block, however, it will. Is it the intended behaviour?
3002022-06-30T12:58:54 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 264 seconds)
3012022-06-30T13:00:39 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3022022-06-30T13:03:20 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Read error: Connection reset by peer)
3032022-06-30T13:03:55 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3042022-06-30T13:04:49 <laanwj> darosior: it's not clear to me from the RPC help how "since" is to be interpreted
3052022-06-30T13:05:00 <bitcoin-git> [bitcoin] MarcoFalke closed pull request #25505: test: passing a negative value to `-peertimeout` should throw an error (master...2022-06-peertimeout-negative) https://github.com/bitcoin/bitcoin/pull/25505
3062022-06-30T13:05:17 <darosior> Yes, it looks like this behaviour is tested so it is (hopefully) be intended
3072022-06-30T13:05:30 <bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/5bc10b39abbc...bae8a66d42d6
3082022-06-30T13:05:30 <bitcoin-git> bitcoin/master 748a10e /dev/fd0: rephrase error for invalid timeout
3092022-06-30T13:05:30 <bitcoin-git> bitcoin/master bae8a66 MacroFake: Merge bitcoin/bitcoin#25506: Rephrase error message for invalid value of `...
3102022-06-30T13:05:31 <laanwj> it could definitely be documented better
3112022-06-30T13:05:33 <darosior> I'll open an issue to clarify, as at the very least the documentation is confusing
3122022-06-30T13:05:35 <bitcoin-git> [bitcoin] MarcoFalke merged pull request #25506: Rephrase error message for invalid value of `-peertimeout` (master...peertimeout-error-msg) https://github.com/bitcoin/bitcoin/pull/25506
3132022-06-30T13:05:39 <laanwj> right
3142022-06-30T13:06:15 <laanwj> i'd personally expect it to be inclusive of the specified block, too
3152022-06-30T13:06:37 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3162022-06-30T13:08:37 *** gnaf <gnaf!gnaf@gateway/vpn/protonvpn/gnaf> has joined #bitcoin-core-dev
3172022-06-30T13:08:56 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
3182022-06-30T13:12:15 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 246 seconds)
3192022-06-30T13:12:47 <sipa> I think the behavior makes sense, see my comment.
3202022-06-30T13:13:40 <darosior> Yeah your explanation makes sense.
3212022-06-30T13:14:03 <sipa> It could certainly be better documented.
3222022-06-30T13:17:19 <bitcoin-git> [bitcoin] darosior opened pull request #25510: rpc: explicit the range for listsinceblock's filtering by block hash is exclusive (master...doc_listsinceblock) https://github.com/bitcoin/bitcoin/pull/25510
3232022-06-30T13:17:52 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3242022-06-30T13:19:23 <laanwj> sipa: yes, that makes sense
3252022-06-30T13:19:34 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Read error: Connection reset by peer)
3262022-06-30T13:20:09 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3272022-06-30T13:20:31 <jamesob> Random question: was there ever a rationale for the bitcoin/bitcoin-core github org split? I.e. why isn't everything just under one or the other?
3282022-06-30T13:21:31 <ariard> laanwj: thanks
3292022-06-30T13:21:34 <bitcoin-git> [bitcoin] brunoerg opened pull request #25511: test: non-positive integer value to `-peertimeout` should throw an error (master...2022-06-peertimeout-positive-integer) https://github.com/bitcoin/bitcoin/pull/25511
3302022-06-30T13:21:39 <laanwj> jamesob: ideally everything should be under bitcoin-core, that said, the bitcoin/bitcoin repo name is hardcoded in so many places
3312022-06-30T13:21:46 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3322022-06-30T13:21:55 <jamesob> laanwj: ah gotcha
3332022-06-30T13:22:38 <laanwj> well, bips is the thing that can be argued to belong under bitcoin itself
3342022-06-30T13:22:40 <laanwj> anyhow, old wounds
3352022-06-30T13:23:32 <jamesob> right
3362022-06-30T13:24:58 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
3372022-06-30T13:25:19 <laanwj> i guess it becomes relevant again if we ever split up the repo (e.g. in a consensus part and the rest), but that's not even a consideration right now
3382022-06-30T13:26:19 <jamesob> for sure
3392022-06-30T13:26:20 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 260 seconds)
3402022-06-30T13:29:00 *** SpellChecker_ <SpellChecker_!~SpellChec@user/SpellChecker> has joined #bitcoin-core-dev
3412022-06-30T13:29:52 *** SpellChecker <SpellChecker!~SpellChec@user/SpellChecker> has quit IRC (Remote host closed the connection)
3422022-06-30T13:32:06 *** z9z0b3t1c <z9z0b3t1c!~z9z0b3t1c@145.224.65.157> has joined #bitcoin-core-dev
3432022-06-30T13:38:56 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3442022-06-30T13:43:27 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
3452022-06-30T13:54:13 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3462022-06-30T14:02:39 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 255 seconds)
3472022-06-30T14:05:42 <bitcoin-git> [bitcoin] ayush933 opened pull request #25512: test: refactor rpc_signrawtransaction.py (master...rpc_signrawtransactionwithkey_no_wallet) https://github.com/bitcoin/bitcoin/pull/25512
3482022-06-30T14:11:27 <bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/bae8a66d42d6...b6cf0f8848ed
3492022-06-30T14:11:28 <bitcoin-git> bitcoin/master d22bd54 brunoerg: test: passing a non-positive integer value to `-peertimeout` should throw ...
3502022-06-30T14:11:28 <bitcoin-git> bitcoin/master b6cf0f8 MacroFake: Merge bitcoin/bitcoin#25511: test: non-positive integer value to `-peertim...
3512022-06-30T14:11:31 <bitcoin-git> [bitcoin] MarcoFalke merged pull request #25511: test: non-positive integer value to `-peertimeout` should throw an error (master...2022-06-peertimeout-positive-integer) https://github.com/bitcoin/bitcoin/pull/25511
3522022-06-30T14:12:35 <instagibbs> does github let you "ACK" someone's comment, so it's re-exposed in your gihub review thread thing?
3532022-06-30T14:12:50 <instagibbs> like "yeah this needs to be fixed" without making an entirely new comment
3542022-06-30T14:14:42 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3552022-06-30T14:15:44 *** sdaftuar <sdaftuar!~sdaftuar@user/sdaftuar> has joined #bitcoin-core-dev
3562022-06-30T14:18:22 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3572022-06-30T14:18:44 *** kouloumos <kouloumos!uid539228@id-539228.tinside.irccloud.com> has joined #bitcoin-core-dev
3582022-06-30T14:18:58 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 240 seconds)
3592022-06-30T14:21:21 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3602022-06-30T14:21:26 *** furszy <furszy!~furszy@user/furszy> has quit IRC ()
3612022-06-30T14:22:55 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
3622022-06-30T14:23:53 *** furszy <furszy!~furszy@user/furszy> has joined #bitcoin-core-dev
3632022-06-30T14:27:09 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 246 seconds)
3642022-06-30T14:39:08 <bitcoin-git> [bitcoin] MarcoFalke pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/b6cf0f8848ed...1ee597817fb0
3652022-06-30T14:39:09 <bitcoin-git> bitcoin/master f319287 Sebastian Falbesoner: test: assert serialized txouts size of `gen_return_txouts` helper
3662022-06-30T14:39:10 <bitcoin-git> bitcoin/master b1ba3ed Sebastian Falbesoner: test: let `gen_return_txouts` create a single large OP_RETURN output
3672022-06-30T14:39:10 <bitcoin-git> bitcoin/master 475aae8 Sebastian Falbesoner: test: pass `datacarriersize` option for tests using large outputs (instead...
3682022-06-30T14:39:10 <bitcoin-git> [bitcoin] MarcoFalke merged pull request #25503: test: pass `datacarriersize` option for tests using large outputs (instead of `acceptnonstdtxn`) (master...202206-test-replace_acceptnonstdxn_with_datacarriersize_option) https://github.com/bitcoin/bitcoin/pull/25503
3692022-06-30T14:39:26 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3702022-06-30T14:43:36 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 246 seconds)
3712022-06-30T14:44:00 <bitcoin-git> [bitcoin] fanquake pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/1ee597817fb0...6adae27f8c75
3722022-06-30T14:44:00 <bitcoin-git> bitcoin/master fa07651 glozow: [rpc] add new submitpackage RPC
3732022-06-30T14:44:00 <bitcoin-git> bitcoin/master e866f0d glozow: [functional test] submitrawpackage RPC
3742022-06-30T14:44:01 <bitcoin-git> bitcoin/master 6adae27 fanquake: Merge bitcoin/bitcoin#24836: add RPC (-regtest only) for testing package p...
3752022-06-30T14:44:20 <bitcoin-git> [bitcoin] fanquake merged pull request #24836: add RPC (-regtest only) for testing package policy (master...client-submitpackage) https://github.com/bitcoin/bitcoin/pull/24836
3762022-06-30T14:53:18 <kouloumos> Has anyone ever tried to add tracepoints support for macOS? Except of the kind of related reference in #22238 I couldn't find any other tangible mention.
3772022-06-30T14:53:20 <gribble> https://github.com/bitcoin/bitcoin/issues/22238 | build: improve detection of eBPF support by fanquake · Pull Request #22238 · bitcoin/bitcoin · GitHub
3782022-06-30T14:56:43 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3792022-06-30T14:59:12 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Read error: Connection reset by peer)
3802022-06-30T15:06:56 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3812022-06-30T15:09:15 *** szkl <szkl!uid110435@id-110435.uxbridge.irccloud.com> has joined #bitcoin-core-dev
3822022-06-30T15:11:20 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 260 seconds)
3832022-06-30T15:15:59 <bitcoin-git> [bitcoin] achow101 opened pull request #25513: psbt: Check Taproot tree depth and leaf versions (master...taproot-psbt-check-leaf-ver) https://github.com/bitcoin/bitcoin/pull/25513
3842022-06-30T15:23:27 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3852022-06-30T15:23:28 *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has joined #bitcoin-core-dev
3862022-06-30T15:28:17 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
3872022-06-30T15:37:42 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3882022-06-30T15:42:10 <bitcoin-git> [bitcoin] MarcoFalke pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/6adae27f8c75...5d68d6840d9c
3892022-06-30T15:42:10 <bitcoin-git> bitcoin/master eec23da Ayush Sharma: test: remove wallet dependency from feature_nulldummy.py
3902022-06-30T15:42:10 <bitcoin-git> bitcoin/master 50ba669 Ayush Sharma: remove unused functions
3912022-06-30T15:42:10 <bitcoin-git> bitcoin/master 5d68d68 MacroFake: Merge bitcoin/bitcoin#25364: test: remove wallet dependency from feature_n...
3922022-06-30T15:42:15 <bitcoin-git> [bitcoin] MarcoFalke merged pull request #25364: test: remove wallet dependency from feature_nulldummy.py (master...nulldummy_no_wallet) https://github.com/bitcoin/bitcoin/pull/25364
3932022-06-30T15:42:28 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
3942022-06-30T15:49:13 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3952022-06-30T15:51:50 *** furszy <furszy!~furszy@user/furszy> has quit IRC ()
3962022-06-30T15:54:18 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 246 seconds)
3972022-06-30T16:06:31 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3982022-06-30T16:11:05 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3992022-06-30T16:11:28 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
4002022-06-30T16:15:30 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 260 seconds)
4012022-06-30T16:27:40 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
4022022-06-30T16:32:25 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
4032022-06-30T16:41:00 <bitcoin-git> [bitcoin] MarcoFalke pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/5d68d6840d9c...c892cb7d8d8d
4042022-06-30T16:41:01 <bitcoin-git> bitcoin/master bda8ebe furszy: wallet: don't read db every time that a new WalletBatch is created
4052022-06-30T16:41:01 <bitcoin-git> bitcoin/master c318211 furszy: walletdb: fix last client version update
4062022-06-30T16:41:01 <bitcoin-git> bitcoin/master c892cb7 MacroFake: Merge bitcoin/bitcoin#25383: wallet: don't read db every time that a new '...
4072022-06-30T16:41:06 <bitcoin-git> [bitcoin] MarcoFalke merged pull request #25383: wallet: don't read db every time that a new 'WalletBatch' is created (master...2022_wallet_db_read) https://github.com/bitcoin/bitcoin/pull/25383
4082022-06-30T16:41:35 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
4092022-06-30T16:44:03 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Read error: Connection reset by peer)
4102022-06-30T16:44:32 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
4112022-06-30T16:49:09 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 255 seconds)
4122022-06-30T16:55:19 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
4132022-06-30T16:56:38 *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has quit IRC (Ping timeout: 240 seconds)
4142022-06-30T16:59:38 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 240 seconds)
4152022-06-30T17:02:57 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
4162022-06-30T17:05:07 *** Talkless <Talkless!~Talkless@mail.dargis.net> has joined #bitcoin-core-dev
4172022-06-30T17:06:45 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
4182022-06-30T17:09:35 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 256 seconds)
4192022-06-30T17:15:22 *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has joined #bitcoin-core-dev
4202022-06-30T17:26:20 *** furszy <furszy!~furszy@2800:810:440:4cf:cb2:6038:fac4:8615> has joined #bitcoin-core-dev
4212022-06-30T17:45:29 *** furszy <furszy!~furszy@user/furszy> has quit IRC (Remote host closed the connection)
4222022-06-30T17:51:47 *** kouloumos <kouloumos!uid539228@id-539228.tinside.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)
4232022-06-30T17:52:35 *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has quit IRC (Ping timeout: 268 seconds)
4242022-06-30T18:01:06 *** realies <realies!~realies@user/realies> has quit IRC (Quit: Ping timeout (120 seconds))
4252022-06-30T18:01:27 *** realies <realies!~realies@user/realies> has joined #bitcoin-core-dev
4262022-06-30T18:01:29 <bitcoin-git> [bitcoin] dergoegge opened pull request #25514: net processing: Move CNode::nServices and CNode::nLocalServices to Peer (master...2022-06-move-services) https://github.com/bitcoin/bitcoin/pull/25514
4272022-06-30T18:04:21 <MacroFake> Is there a meeting today?
4282022-06-30T18:04:44 <fanquake> in ~1hr i think?
4292022-06-30T18:04:52 <sipa> I think so? 1 hour from now.
4302022-06-30T18:05:01 <bitcoin-git> [bitcoin] dergoegge opened pull request #25515: [draft] PeerManager unit tests (master...2022-06-virt-connman) https://github.com/bitcoin/bitcoin/pull/25515
4312022-06-30T18:06:19 <MacroFake> ah thx
4322022-06-30T18:11:57 *** kexkey <kexkey!~kexkey@178.249.214.27> has quit IRC (Quit: kexkey)
4332022-06-30T18:13:56 *** kexkey <kexkey!~kexkey@178.249.214.27> has joined #bitcoin-core-dev
4342022-06-30T18:19:58 *** bomb-on <bomb-on!~bomb-on@user/bomb-on> has joined #bitcoin-core-dev
4352022-06-30T18:38:07 *** szkl <szkl!uid110435@id-110435.uxbridge.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)
4362022-06-30T18:58:59 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Remote host closed the connection)
4372022-06-30T18:59:32 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has joined #bitcoin-core-dev
4382022-06-30T19:00:31 <laanwj> #startmeeting
4392022-06-30T19:00:31 <core-meetingbot> Meeting started Thu Jun 30 19:00:31 2022 UTC. The chair is laanwj. Information about MeetBot at https://bitcoin.jonasschnelli.ch/ircmeetings.
4402022-06-30T19:00:31 <core-meetingbot> Available commands: action commands idea info link nick
4412022-06-30T19:00:49 <hebasto> hi
4422022-06-30T19:00:50 <jarolrod> hi
4432022-06-30T19:00:50 <sdaftuar> hi
4442022-06-30T19:00:54 <cfields_> hi
4452022-06-30T19:00:58 <sipa> hi
4462022-06-30T19:01:00 <fanquake> hi
4472022-06-30T19:01:01 <instagibbs> hi
4482022-06-30T19:01:02 <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
4492022-06-30T19:01:02 <glozow> hi
4502022-06-30T19:01:04 <laanwj> moneyball morcos nehan NicolasDorier paveljanik petertodd phantomcircuit promag provoostenator ryanofsky sdaftuar sipa vasild
4512022-06-30T19:01:07 <lightlike> hi
4522022-06-30T19:01:14 <MacroFake> hi
4532022-06-30T19:01:19 <ariard> hi
4542022-06-30T19:01:21 <laanwj> welcome to the weekly general bitcoin-core-dev meeting
4552022-06-30T19:01:36 <kvaciral> hi
4562022-06-30T19:01:43 <michaelfolkson> hi
4572022-06-30T19:01:48 <laanwj> there has been one topic proposed in advance: glozow for rbf / mempool / validation maintainer (fanquake)
4582022-06-30T19:02:01 <laanwj> you can propose topics at any time during the week with #proposedmeetingtopic
4592022-06-30T19:02:06 <laanwj> any last minute topics?
4602022-06-30T19:02:45 <achow101> hi
4612022-06-30T19:02:59 <b10c> hi
4622022-06-30T19:03:49 <kanzure> hi
4632022-06-30T19:04:09 *** brunoerg <brunoerg!~brunoerg@187.183.43.40> has quit IRC (Ping timeout: 255 seconds)
4642022-06-30T19:04:32 <laanwj> #topic High priority for review
4652022-06-30T19:04:32 <core-meetingbot> topic: High priority for review
4662022-06-30T19:05:12 <laanwj> there are 7 blockers, 2 chasing concept ACK in https://github.com/orgs/bitcoin/projects/1
4672022-06-30T19:05:14 <MacroFake> #24697 for me pls (It makes removing adjusted time a little bit easier, but it is not strictly required)
4682022-06-30T19:05:16 <gribble> https://github.com/bitcoin/bitcoin/issues/24697 | refactor address relay time by MarcoFalke · Pull Request #24697 · bitcoin/bitcoin · GitHub
4692022-06-30T19:05:26 <laanwj> (the URL moved, as we migrated the project to the new github projects)
4702022-06-30T19:06:18 <dongcarl> #25487 for me please!
4712022-06-30T19:06:20 <gribble> https://github.com/bitcoin/bitcoin/issues/25487 | [kernel 3b/n] Make `{Dump,Load}Mempool` `CTxMemPool` methods, decouple from `ArgsManager` by dongcarl · Pull Request #25487 · bitcoin/bitcoin · GitHub
4722022-06-30T19:06:51 <laanwj> MacroFake: added
4732022-06-30T19:07:01 <MacroFake> Maybe #21702 can be removed for needing rebase?
4742022-06-30T19:07:03 <gribble> https://github.com/bitcoin/bitcoin/issues/21702 | Implement BIP-119 Validation (CheckTemplateVerify) by JeremyRubin · Pull Request #21702 · bitcoin/bitcoin · GitHub
4752022-06-30T19:07:26 <laanwj> dongcarl: also added
4762022-06-30T19:07:26 <dongcarl> Ping jeremyrubin
4772022-06-30T19:07:31 <MacroFake> Same for #22693 ?
4782022-06-30T19:07:33 <gribble> https://github.com/bitcoin/bitcoin/issues/22693 | RPC/Wallet: Add "use_txids" to output of getaddressinfo by luke-jr · Pull Request #22693 · bitcoin/bitcoin · GitHub
4792022-06-30T19:07:43 <fanquake> Can I have https://github.com/bitcoin/bitcoin/pull/25484. Few changes building on top of that
4802022-06-30T19:08:03 <achow101> #24699 for me
4812022-06-30T19:08:06 <gribble> https://github.com/bitcoin/bitcoin/issues/24699 | wallet: Improve AvailableCoins performance by reducing duplicated operations by achow101 · Pull Request #24699 · bitcoin/bitcoin · GitHub
4822022-06-30T19:08:47 <luke-jr> I can prioritise a rebase of that
4832022-06-30T19:09:02 <laanwj> achow101: added
4842022-06-30T19:09:25 <laanwj> MacroFake: depends on how long it has needed rebase imo
4852022-06-30T19:10:18 <MacroFake> Yeah, one week seems fine, but if something is sitting for several weeks, I am not sure what reviewers can do
4862022-06-30T19:10:20 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
4872022-06-30T19:10:29 <Murch> hi
4882022-06-30T19:10:50 <laanwj> agree
4892022-06-30T19:11:44 <laanwj> looks like it has needed rebase since may 6
4902022-06-30T19:11:51 <laanwj> so yes removing it for now
4912022-06-30T19:13:11 <laanwj> okay, anything else to add/remove, or that is in the list and almost ready for merge?
4922022-06-30T19:15:46 * luke-jr squashes a cricket
4932022-06-30T19:16:07 <laanwj> (btw, if you have a project board, and want to migrate it to the new github projects beta, let me know, this is possible now)
4942022-06-30T19:16:18 <laanwj> #topic glozow for rbf / mempool / validation maintainer
4952022-06-30T19:16:19 <core-meetingbot> topic: glozow for rbf / mempool / validation maintainer
4962022-06-30T19:16:28 <fanquake> Cool
4972022-06-30T19:16:38 <laanwj> ack
4982022-06-30T19:16:39 <fanquake> Per the topic, I'm proposing we make Gloria (https://github.com/glozow) a maintainer; over ~ rbf / mempool / policy
4992022-06-30T19:16:47 <fanquake> She has been actively working on Bitcoin Core for > 2 years. Predominately in the mempool & validation code.
5002022-06-30T19:16:57 <fanquake> Her current project is package rbf/relay, and I know she has a number of thoughts in regards to improving the surrounding code.
5012022-06-30T19:17:08 <fanquake> More recently she has also been reviewing / helping improve in /wallet/, which I'm sure achow appreciates
5022022-06-30T19:17:14 <fanquake> I think she is a great candidate for being a maintainer
5032022-06-30T19:17:25 <achow101> ack
5042022-06-30T19:17:31 <cfields_> +1
5052022-06-30T19:17:37 <hebasto> ack
5062022-06-30T19:17:40 <sipa> The obvious question, glozow: are you interested in helping out with maintaining?
5072022-06-30T19:17:47 <instagibbs> lol
5082022-06-30T19:17:57 <MacroFake> sipa: sssh
5092022-06-30T19:17:57 <instagibbs> (ack)
5102022-06-30T19:17:59 <luke-jr> who said she has a choice? /s
5112022-06-30T19:17:59 <cfields_> err.. assuming ^^ :)
5122022-06-30T19:18:16 <glozow> thanks fanquake, I appreciate the recognition. Yes I'd like to help out in any way I can.
5132022-06-30T19:18:18 <dongcarl> ack if she wants it
5142022-06-30T19:18:21 <michaelfolkson> Who is currently merging mempool/policy PRs? Marco?
5152022-06-30T19:18:28 <Murch> ack
5162022-06-30T19:18:34 <sipa> ack, in that case
5172022-06-30T19:18:40 <b10c> ack
5182022-06-30T19:18:53 <MacroFake> sgtm
5192022-06-30T19:19:08 <laanwj> awesome!
5202022-06-30T19:19:16 <b10c> nit: brink would then fund 3 maintainers. not that this is a problem, i just want to mention it.
5212022-06-30T19:19:27 <jeremyrubin> i am mild nack on it -- i think that Gloria is suitable and qualified, but i think that maintainership might hinder more than help her progress
5222022-06-30T19:19:44 <jeremyrubin> since it seems it would largely be her with merge resposnibility over her own work
5232022-06-30T19:20:17 <dongcarl> what does glozow think?
5242022-06-30T19:20:19 <instagibbs> this seems like a larger question(which is valid) on self-merges
5252022-06-30T19:20:30 <achow101> jeremyrubin: the same was with the wallet for me
5262022-06-30T19:20:31 <MacroFake> jeremyrubin: Somewhat it is a requirement to have worked extensively on a piece of code before you can maintain it
5272022-06-30T19:20:33 <cfields_> jeremyrubin: doesn't seem far off from fanquake's role/work to me.
5282022-06-30T19:20:38 <cfields_> right, and achow101.
5292022-06-30T19:20:40 <luke-jr> jeremyrubin: I don't know that's a problem. Maintainers tend to work in the area they merge in
5302022-06-30T19:20:41 <achow101> at least it will help with getting other people's work in too
5312022-06-30T19:21:02 <luke-jr> the process of merging still requires third party review
5322022-06-30T19:21:12 <sipa> I think this was brought up with achow101's maintainership as well, and I think the counterpoints are similar: it's better than having their own work merged at all, and that is something other maintainers can still do.
5332022-06-30T19:21:14 <sipa> *not merged at all
5342022-06-30T19:21:51 <glozow> Spending time in this area of the codebase has led me to understand that we have plenty of non-package-relay limitations to address, and reviewing mempool and policy-related things is often the best use of my time. So I had planned to do more of that anyway. Not that this means dropping package relay, but there are lots of non-package relay things to look after. And if people are not comfortable with me merging my own code, then I won't do
5352022-06-30T19:21:51 <glozow> that.
5362022-06-30T19:21:56 <laanwj> luke-jr: sipa: exactly
5372022-06-30T19:22:26 <ariard> i think it's always okay to say to a maintainer we have found the merge too fast or not matching the historical level of reviews for a critical area of the codebase
5382022-06-30T19:22:46 <lightlike> ack
5392022-06-30T19:23:05 <luke-jr> ariard: counterpoint, last time that was ignored and the PR not reverted as it ought to have been
5402022-06-30T19:23:34 <ariard> luke-jr: as usual, one contributor viewpoint might not express the project consensus
5412022-06-30T19:23:37 *** bytes1440000 <bytes1440000!~bytes1440@198.252.153.109> has joined #bitcoin-core-dev
5422022-06-30T19:24:15 <luke-jr> it means there is no consensus; and I certainly was not alone
5432022-06-30T19:24:16 <jeremyrubin> well to be clear this is very different role than maybe fanquake or achow
5442022-06-30T19:24:29 <jeremyrubin> since this is -- as desrcribed here -- "validation maintainer"
5452022-06-30T19:24:30 <bytes1440000> b10c: its a good point and maintainers funded by different orgs is always better for a project like bitcoin core
5462022-06-30T19:24:38 <sipa> luke-jr: ignoring specific cases, i agree that nobody should feel restricted from commenting on too-fast-merges.
5472022-06-30T19:24:39 <luke-jr> in any case, it's not related to the topic of glozow's role IMO
5482022-06-30T19:24:41 <ariard> though to express wider thought on the mempool maintership, imo it's one area of the codebase expected to grow in complexity in the coming years with upper layers requirements
5492022-06-30T19:24:56 *** Guest17 <Guest17!~Guest17@46.197.60.131> has joined #bitcoin-core-dev
5502022-06-30T19:25:03 <ariard> like we'll likely have a bunch of other beasts like package relay to land in the coming decade for all the covenants/eltoo stuff
5512022-06-30T19:25:27 <bytes1440000> i am not sure if bitcoin core needs another person with commit access with already 6 but always felt it needs more reviewers looking at open pull requests
5522022-06-30T19:25:31 *** Talkless <Talkless!~Talkless@mail.dargis.net> has quit IRC (Quit: Konversation terminated!)
5532022-06-30T19:25:33 <jeremyrubin> a wallet maintainer affects mostly those who choose to user the software, it's not clear what the scope is of a validation maintainter to me
5542022-06-30T19:25:56 <laanwj> mempool maintainer is much clearer
5552022-06-30T19:26:07 <bytes1440000> ariard: you could also be a mempool maintainer?
5562022-06-30T19:26:28 <cfields_> bytes1440000: that's not the discussion now.
5572022-06-30T19:26:34 <MacroFake> I think "validation" is meant in the context of mempool validation? (ATMP is in validation.cpp)
5582022-06-30T19:26:38 <laanwj> i'm also not really sure what 'validation maintainer' would be
5592022-06-30T19:26:41 <jeremyrubin> maybe we could do a better job of drafting an actual "Job Description" for what glozow is being appiinted as?
5602022-06-30T19:26:55 <ariard> bytes1440000: no, i don't intend to be maintainer, i don't have the profile for and when it has been proposed to me for LDK, i did refuse
5612022-06-30T19:26:57 <sipa> ariard: I'm not sure that's all that related to specific consensus changes, but sure... i do expect significant complexity and the need for people keeping a good overview over it, regarding tx relay
5622022-06-30T19:26:59 <fanquake> I did clarify to mempool / rbf / policy, in the sentences above
5632022-06-30T19:27:01 <luke-jr> jeremyrubin: as with all maintainers, it's supposed to be janitorial
5642022-06-30T19:27:14 <luke-jr> running a script when there's review and consensus on a PR
5652022-06-30T19:27:20 <laanwj> fanquake: makes sense to me said like that
5662022-06-30T19:27:20 <bytes1440000> ariard: okay
5672022-06-30T19:27:24 <fanquake> i may have said validation in the proposed topic, but not specifically in this discussion
5682022-06-30T19:27:32 <fanquake> i did say she had worked on the code in validation
5692022-06-30T19:27:33 <sipa> Yeah, I prefer the role to be "mempool / rbf / policy" rather than validation.
5702022-06-30T19:27:54 <luke-jr> I'd drop "rbf" - seems like too minor a detail :p
5712022-06-30T19:28:15 <achow101> mempool/policy, components of which live in validation.cpp.. our naming sucks
5722022-06-30T19:28:33 <sipa> If we're bikeshedding, "mempool and transaction relay policy" ?
5732022-06-30T19:28:38 <jeremyrubin> i think it would make sense to draft a Job Description of what the appointment is for and scoping, and have people ack that when it exists.
5742022-06-30T19:29:00 <cfields_> jeremyrubin: that would've made sense for every prior nomination as well.
5752022-06-30T19:29:04 <jeremyrubin> yeah
5762022-06-30T19:29:04 <laanwj> the name can be more abstract it doesn't have to be precise a specfic cpp or so, we've never divided things up like that
5772022-06-30T19:29:05 <jeremyrubin> it would have
5782022-06-30T19:29:09 <ariard> sipa: sure, my thought was the mempool is a good candidate to get a maintainer in the coming years, if the complexity keeps increasing
5792022-06-30T19:29:10 <jeremyrubin> we probably should have done that
5802022-06-30T19:29:23 <Murch> mempool+policy sgtm
5812022-06-30T19:29:25 <jeremyrubin> as noted, i am not opposed to glozow having some set of responsibilities, it just doesn't seem like we're holding ourselves to a good standard to not do this
5822022-06-30T19:29:37 <glozow> Mempool / Policy is a scope I am fine with and plan to review anyway. Maybe we can one day more them out of validation.cpp if that's important to people. It seems the core question is whether or not people think I am knowledgeable enough to gauge whether a PR has enough review to be merged, since that's what a maintainer does.
5832022-06-30T19:29:50 <michaelfolkson> ack
5842022-06-30T19:29:57 <laanwj> glozow: i'm sure you are!
5852022-06-30T19:30:03 <luke-jr> sipa: policy affects more than relay in practice; and often relay isn't even given the priority
5862022-06-30T19:30:24 <ariard> jeremyrubin: yes, i agree we might do a Job Description to get the scoping right
5872022-06-30T19:30:33 * dongcarl is fully in support of inverting the validation -> mempool dependency
5882022-06-30T19:30:46 <BlueMatt[m]> dongcarl: lol good luck
5892022-06-30T19:30:46 <cfields_> :)
5902022-06-30T19:30:50 <laanwj> we don't have that kind of precise scoping for maintainers, i don't think that's necessary
5912022-06-30T19:31:12 <luke-jr> glozow: IIRC you seemed confused about the relation between miners and relay policy; but I may be misremembering, and/or maybe cleared that up
5922022-06-30T19:31:13 <laanwj> we all have an idea what mempool+transaction relay is
5932022-06-30T19:31:15 <sipa> maintainers also learn, and responsibilities evolve
5942022-06-30T19:31:18 <achow101> tbh maintainers have merged things outside of their explicit scopes, and I don't think that's necessarily a bad thing
5952022-06-30T19:31:32 <dongcarl> I do like an "inclusionary" list of responsibilities, not an "exclusionary" one
5962022-06-30T19:31:42 <achow101> so long as every PR has been reviewed by multiple people and there is consensus for merging, it doesn't particularly matter who is merging
5972022-06-30T19:31:44 <laanwj> achow101: right, as long as there is agreement that's fine
5982022-06-30T19:31:45 <jeremyrubin> ok so then we aren't discussing adding gloria as a scoped maintainer, it's as a general maintainer?
5992022-06-30T19:31:56 <jeremyrubin> that seems like a different discussion, which is also OK to have
6002022-06-30T19:31:57 <MacroFake> Agree with achow101 and laanwj
6012022-06-30T19:32:00 <luke-jr> x.x
6022022-06-30T19:32:04 <achow101> jeremyrubin: all maintainers are basically general maintainers
6032022-06-30T19:32:13 <achow101> but have a focus
6042022-06-30T19:32:17 <laanwj> achow101: yes, that
6052022-06-30T19:32:32 <ariard> okay that might be the discussion, should we evolve towards scoped maintainance
6062022-06-30T19:32:45 <laanwj> i'm not sure
6072022-06-30T19:33:00 <luke-jr> I don't see that would improve things
6082022-06-30T19:33:05 <Murch> It's not like the parts of the codebases are that isolated
6092022-06-30T19:33:09 <sipa> i hope we don't need to have discussions about whether or not something was someone's purview to merge
6102022-06-30T19:33:18 <laanwj> sipa: +1
6112022-06-30T19:33:23 <sipa> the role is janitorial, as already pointed out
6122022-06-30T19:33:29 <laanwj> i don't think that has ever happened anyway, and probably shouldn't
6132022-06-30T19:33:47 <jeremyrubin> i think i would just like clarity -- you see how it is not good that gloria was proposed to be a scoped maintainer, everyone ACK'd that, and now it's backtracking into well it's always general purpose overall project maintenance?
6142022-06-30T19:33:56 <sipa> and i hope that the people given maintainer responsibilities are expected to judge their own expertise in making that decision
6152022-06-30T19:33:57 <jeremyrubin> Adding a maintainer is a serious, important thing
6162022-06-30T19:34:16 <bytes1440000> +1
6172022-06-30T19:34:17 <jeremyrubin> so I think as a project we should communicate more clearly about what exactly is being done and expected
6182022-06-30T19:34:28 <jeremyrubin> and if people are ACK voting, they should know what for
6192022-06-30T19:34:34 <MacroFake> jeremyrubin: It would be suspicious if glozow went out and merged a ton of build system changes that are reviewed, but not by her
6202022-06-30T19:34:37 <laanwj> i don't think that's necessary, but feel free to write something up if you want
6212022-06-30T19:34:49 <cfields_> jeremyrubin: as has adding every past maintainer. I think if you're going to call for procedural changes, you need to make it clear why this one's different.
6222022-06-30T19:34:51 <MacroFake> However, if she decides to work on the build system in 2 years, that should be reasonable
6232022-06-30T19:35:06 <jeremyrubin> cfields_ i have been asking for maintainers to give more clarity for a while
6242022-06-30T19:35:14 <jeremyrubin> so i am not personally departing from any prior stance
6252022-06-30T19:35:36 <luke-jr> jeremyrubin: people want to spend time on code, not necessarily process
6262022-06-30T19:35:39 <luke-jr> at least myself
6272022-06-30T19:35:44 <laanwj> luke-jr: +100
6282022-06-30T19:36:11 <dongcarl> I'm ACKing for glozow to be focused on mempool / policy but have the ability to act in a general maintainer way as long as it's not repeatedly unilaterally stepping on other maintainers' toes
6292022-06-30T19:36:25 <achow101> ^ that
6302022-06-30T19:36:38 <sipa> dongcarl: +1
6312022-06-30T19:37:26 <laanwj> sure, i mean given that she even wants that
6322022-06-30T19:37:29 <glozow> Thank you dongcarl. I agree to "be focused on mempool / policy but have the ability to act in a general maintainer way as long as it's not repeatedly unilaterally stepping on other maintainers' toes."
6332022-06-30T19:37:47 <ariard> from my viewpoint, the worthiness of a scoped maintainership is when you have a security issue to talk about you know at least whom should be the default interlocutor (even if I know we have a catch-all mailist endpoint)
6342022-06-30T19:38:10 <laanwj> that also works for semi-scoped
6352022-06-30T19:38:18 <Murch> Well, I'd have rephrased the second half of that to, and "expect to judge their own expertise in making merge decisions" as mentioned by Pieter above
6362022-06-30T19:39:01 *** bomb-on <bomb-on!~bomb-on@user/bomb-on> has quit IRC (Quit: aллилѹÑа!)
6372022-06-30T19:39:03 <jeremyrubin> i want to spend time on a beach with a pina colada -- however, process work is a part of the development of the "bitcoin core organization", so you can't just stick your head in the sand and ignore it, especially when it comes to doling out commit access
6382022-06-30T19:39:08 <laanwj> if there's some urgent issue you talk to the person who has the focus on a certain area
6392022-06-30T19:39:40 <laanwj> no, i don't think adding more bureaucracy and formality makes things better
6402022-06-30T19:40:30 <luke-jr> there is no bitcoin core organization
6412022-06-30T19:40:41 <ariard> yeah, the "who has the focus on a certain area" might not always be clear, and it's more then whom you should nudge to get covert a fix done
6422022-06-30T19:41:22 <MacroFake> As a general rule, if you have an idea to improve the process, suggestions are welcome.
6432022-06-30T19:41:22 <sipa> As the project grows, some form of process/organization is expected to come into play. Until a few years ago, maintainers had barely any focus, let alone a well-defined focus. I think it suffices to talk about maintainers with a focus: people who have maintainer rights, but are expected to mostly focus on one aspect.
6442022-06-30T19:41:44 <sipa> Let's not rush adding more formality to this, it's already burdensome enough.
6452022-06-30T19:41:48 <laanwj> yes
6462022-06-30T19:42:11 <dongcarl> That sounds right to me!
6472022-06-30T19:42:22 <jeremyrubin> how burdensome is it to write a simple Job Description describing what "mempool / policy / validation / RBF" is so that we know what the focus actually is of the proposed new maintainer?
6482022-06-30T19:42:40 <michaelfolkson> I think being willing and available to discuss a controversial merge decision on IRC is important. Beyond that every PR has its own subtleties
6492022-06-30T19:42:56 <dongcarl> jeremyrubin: EPARSE
6502022-06-30T19:43:07 <laanwj> i think you're dragging things out now jeremyrubin
6512022-06-30T19:43:28 <laanwj> any other topics?
6522022-06-30T19:43:39 <ariard> anyway, i think a mempool maintainer is a good thing and I think glozow is a valuable candidate, however maybe we could take more time to think about the effective scope and if we have other candidates interested (again: i'm not interested)
6532022-06-30T19:44:31 <luke-jr> jeremyrubin: so write it yourself and propose it for merging to project docs in a PR
6542022-06-30T19:44:39 <dongcarl> I have a small implementation detail thing that's probs not important enough for the meeting but would like to chat a bit afterwards
6552022-06-30T19:44:48 <jeremyrubin> perhaps I am dragging it out -- i would fire back that you're avoiding important discourse on accountability of maintainers, something that you shouldn't shy away from in general. All maintainers should be able to produce 5 sentences on what areas they are focused on.
6562022-06-30T19:45:03 <cfields_> jeremyrubin: not 6?
6572022-06-30T19:45:10 <jeremyrubin> gotta start somewhere
6582022-06-30T19:45:27 <michaelfolkson> Regardless the work Gloria has done on mempool, policy, package relay, PR review club is great. This discussion isn't Gloria related, just process questions
6592022-06-30T19:45:33 *** bomb-on <bomb-on!~bomb-on@user/bomb-on> has joined #bitcoin-core-dev
6602022-06-30T19:45:36 <laanwj> sigh
6612022-06-30T19:45:53 <bytes1440000> ariard: +1 will be interesting to see if others are also interested to be a maintainer for different things
6622022-06-30T19:45:56 <dongcarl> I think "mempool / policy" is quite clear
6632022-06-30T19:46:08 <cfields_> bytes1440000: stop.
6642022-06-30T19:46:16 <achow101> jeremyrubin: how specific do you want this description to be? I find "mempool / rbf / policy" to be clear in scope
6652022-06-30T19:46:18 <jeremyrubin> generally the more the better -- achow101 has done a good job detailing his course of action / wallet priorities IMO
6662022-06-30T19:46:45 <achow101> per file? per line? The codebase is complex enough that a PR in one area still has effects on code in other places that are "out of scope"
6672022-06-30T19:47:08 * luke-jr echos laanwj's sigh
6682022-06-30T19:47:10 <instagibbs> If I'm made policy maintainer, I'll make sure the snack bar is refilled on consistent intervals
6692022-06-30T19:47:16 <bytes1440000> cfields_ : are people not allowed to respond in this channel?
6702022-06-30T19:47:18 <luke-jr> lol
6712022-06-30T19:47:19 <jeremyrubin> i don
6722022-06-30T19:47:47 <jeremyrubin> i don't find that to be sufficiently descriptive personally
6732022-06-30T19:48:02 * luke-jr imagines instagibbs flying around the world to each dev's office to refill snacks
6742022-06-30T19:48:25 <laanwj> hehe
6752022-06-30T19:49:03 <jeremyrubin> glozow is it a problem to write up your intended focus areas and prioritizations for the project?
6762022-06-30T19:49:33 <laanwj> if she wants to write something up that's fine ofc
6772022-06-30T19:49:33 <glozow> jeremyrubin: I'm sure people have varying ideas of what amount of prioritizing or "roadmapping" would be appropriate, but I did prepare a list of things I consider important and would work on https://gist.github.com/glozow/5b8cfa27945371921dfe4d99b17e0424
6782022-06-30T19:49:43 <sipa> FWIW, I think it's a good idea in general for everyone (not just maintainers) to talk about their priorities and current focus.
6792022-06-30T19:49:46 <MacroFake> jeremyrubin: I'd say a personal roadmap is different from the tasks of a maintainer
6802022-06-30T19:49:47 <jeremyrubin> for example, achow101 has made docs like this https://achow101.com/2020/10/0.21-wallets
6812022-06-30T19:50:12 <jeremyrubin> MacroFake: i think that's a theoretical distinction
6822022-06-30T19:50:26 <jeremyrubin> practically, maintainers work on what they are interested in.
6832022-06-30T19:50:36 <luke-jr> jeremyrubin: achow101 is great at community/social publication of his work efforts; but that doesn't mean it needs to become a standard everyone has to abide by
6842022-06-30T19:50:55 <jeremyrubin> everyone doesn't get to be a maintainer either
6852022-06-30T19:50:56 <laanwj> it isn't a theoretical distinction only, as maintainer you're not supposed to only merge what you're working on yourself
6862022-06-30T19:51:05 <luke-jr> jeremyrubin: it's a responsibility, not a privilege
6872022-06-30T19:51:07 <instagibbs> I guess the question is what is the writeup for, who is the audience
6882022-06-30T19:51:10 <ariard> glozow: I think that's a good start, maybe open a GH issue, I would be interested to feed thoughts there and roll the ball forward on mempool maintenance
6892022-06-30T19:51:30 <sipa> The role of maintainers, jointly, is merging PRs that are ready. The question of focus is mostly about determining who among them is best placed to judge a particular PR's status.
6902022-06-30T19:51:42 <laanwj> sipa: right!
6912022-06-30T19:52:33 <fanquake> ariard: I think issues for specific topics would be fine. Although not a single catch-all for discussion of the entire contents of that gist
6922022-06-30T19:53:02 <jarolrod> i dont think glozow has to do all of these write-ups, we know what she works on and the idea of what she will be maintaining is fairly clear
6932022-06-30T19:53:05 <ariard> I would say we're missing few folks who has spent time on the mempool recently at that meeting: darosior, realtbast, jamesob and maybe few others L2 devs, they might have thoughts on mempool maintenance
6942022-06-30T19:53:26 <laanwj> ariard: agree, we don't take final descisions in meetings anyway
6952022-06-30T19:53:30 <ariard> fanquake: yeah anything to have more visibility on what are people interested with and allocate review time would be great
6962022-06-30T19:53:41 <luke-jr> ^
6972022-06-30T19:53:45 <jeremyrubin> glozow ariard +1 -- it's a good start
6982022-06-30T19:54:11 <jeremyrubin> laanwj: ah, what is the process then for decision on maintainership then?
6992022-06-30T19:54:17 <jeremyrubin> I thought it was being decided here
7002022-06-30T19:54:20 <laanwj> jeremyrubin: i'm done arguing process with you
7012022-06-30T19:54:21 <achow101> ariard: yes, we let people see the pr to add the merge key for a few days / weeks before actually merging it and granting rights
7022022-06-30T19:54:35 <luke-jr> jeremyrubin: btw, just to be clear, do you have any reservations with glozow merging PRs with the same expectations for maintainers in general?
7032022-06-30T19:54:40 <jeremyrubin> well you just said "ariard: agree, we don't take final descisions in meetings anyway"
7042022-06-30T19:55:03 <achow101> ack/nack on the merge key pr is the "final decision"
7052022-06-30T19:55:05 <fanquake> because nothing is actually done until a pr has been open, reviewed, merged
7062022-06-30T19:55:06 <laanwj> but it's prbably good to let some time pass so people can bring up potential issues they have with glozow being maintainer, or proposed alternatives
7072022-06-30T19:55:20 <jarolrod> ^ laanwj agree
7082022-06-30T19:55:32 <luke-jr> there can always be multiple maintainers - I don't know that alternatives are an objection
7092022-06-30T19:55:47 <laanwj> no, that's true
7102022-06-30T19:55:53 <jeremyrubin> laanwj: if you can't civilly discuss what process in your decision making you're not suited to be a maintainer... accountability is part of the job.
7112022-06-30T19:56:13 <laanwj> jeremyrubin: not everything is about your opinions
7122022-06-30T19:56:20 <jeremyrubin> i never said it is
7132022-06-30T19:56:32 <jeremyrubin> but you're trying to quash a relevant discussion for what reason?
7142022-06-30T19:56:33 <laanwj> jeremyrubin: you keep stating your preferences as some kind of facts that is very annoying to me
7152022-06-30T19:57:03 <instagibbs> I'm just going to venture that continuing this isnt helping
7162022-06-30T19:57:10 <michaelfolkson> +1
7172022-06-30T19:57:11 *** belcher <belcher!~belcher@user/belcher> has quit IRC (Quit: Leaving)
7182022-06-30T19:57:17 <jeremyrubin> i'm sorry to have annoyed you?
7192022-06-30T19:57:21 <ariard> jeremyrubin: i think accountability of maintainers is an interesting topic, however i think it's better to talk about it in a chill venues like coredev or on the mailing list, there is a lot of context IRC might not be the best medium
7202022-06-30T19:57:41 <achow101> jeremyrubin: you've been around long enough to see multiple people receive (and renounce) maintainership, I'm surprised that you are not already aware of the process.
7212022-06-30T19:57:45 <glozow> I care about the health of mempool/policy and Bitcoin Core, and I take it very seriously so I'm happy to be held to a high standard. All of the work we do is entirely in public, so you are always free to audit me, tell me I've done something wrong, or request I prioritize other things. If you want to test my knowledge or preparedness, please let me know what the standard is beforehand and apply it equally to everyone in the same role.
7222022-06-30T19:58:09 <ariard> achow101: sgtm, to have a PR open for a while and see if we have any objections, I think it's worhty to have a discussion there or elsewhere on the scope
7232022-06-30T19:58:11 <jeremyrubin> glozow: +1
7242022-06-30T19:59:34 <jeremyrubin> re luke-jr: I'd probably want to have a 1-1 convo with gloria about her views on general maintainership before i'd personally endorse, but I don't have a nack presently
7252022-06-30T20:00:19 <cfields_> in that case i think we can continue without jeremyrubin's endorsement.
7262022-06-30T20:00:29 <laanwj> time is up, closing the meeting
7272022-06-30T20:00:33 <laanwj> #endmeeting
7282022-06-30T20:00:33 <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
7292022-06-30T20:00:33 <core-meetingbot> Meeting ended Thu Jun 30 20:00:33 2022 UTC.
7302022-06-30T20:00:33 <core-meetingbot> Minutes: https://bitcoin.jonasschnelli.ch/ircmeetings/logs/bitcoin-core-dev/2022/bitcoin-core-dev.2022-06-30-19.00.moin.txt
7312022-06-30T20:02:00 <michaelfolkson> Demanding a 1-1 conversation before "endorsing" is absurd, gosh. Anyway did dongcarl have a mini project update?
7322022-06-30T20:02:13 <dongcarl> Not a mini project update
7332022-06-30T20:02:27 <MacroFake> 3a/n was merged :party:
7342022-06-30T20:02:32 <jeremyrubin> i don't think that's at all unreasonable
7352022-06-30T20:02:39 <jeremyrubin> i also work on this part of the code
7362022-06-30T20:03:00 <jeremyrubin> why would it be weird to want to get a better sense of how gloria intends philisophically to maintain it?
7372022-06-30T20:03:38 <cfields_> jeremyrubin: because there's zero precedent for that and you need to say whatever it is that you really mean or stop derailing.
7382022-06-30T20:03:40 <ariard> jeremyrubin: while you wouldn't start a ML post and invite politely glozow to express her thoughts ?
7392022-06-30T20:03:51 <dongcarl> MacroFake: 3a/n was merged thanks to all the reviewers who got through the many changes. Thanks!
7402022-06-30T20:04:00 <instagibbs> \o/
7412022-06-30T20:04:04 <jeremyrubin> well this is the first i'm hearing of a nomination for mempool maintainer
7422022-06-30T20:04:19 <jeremyrubin> i think it'd be great to have a ML post or something?
7432022-06-30T20:04:31 <dongcarl> I think 3a sets a good example for all the following Argsman decoupling PRs
7442022-06-30T20:04:31 <jeremyrubin> cfields_: ...
7452022-06-30T20:04:48 <MacroFake> dongcarl: Apologies for my last minute nit-attack, feel free to ignore them when the pr is in a late stage
7462022-06-30T20:04:51 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Remote host closed the connection)
7472022-06-30T20:05:02 <jeremyrubin> there's no hidden agenda or anything here and I don't think it is derailing to ask basic questions like this
7482022-06-30T20:05:06 <dongcarl> As for my question... I wanted to ask about the split of -maxsigachesize between InitSignatureCache and InitScriptExecutionCache
7492022-06-30T20:05:26 <dongcarl> Is that intended to stay longer term or should I deal with it as I do my decoupling?
7502022-06-30T20:05:45 <sipa> the fact that 50% goes to the sigcache and 50% to the script exec cache?
7512022-06-30T20:05:53 <sipa> or is this about code orgnanization
7522022-06-30T20:06:01 <jeremyrubin> glozow is perfectly eloquent and capable of justifying and explaining herself, and I don't think a pile on which amounts to "we don't need to answer questions" is doing her any favors
7532022-06-30T20:06:02 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
7542022-06-30T20:06:19 <dongcarl> sipa: Yup! Wondering if we intend to make 2 separate flags for them, or if splitting 50/50 is good for now
7552022-06-30T20:06:50 <dongcarl> Also okay if no one has strong opinions haha
7562022-06-30T20:07:00 <sipa> dongcarl: My guideline for "should something be configurable" is: can you clearly express the conditions under which someone should use it.
7572022-06-30T20:07:18 <sipa> If you can't do that, how do you expect the user to know better.
7582022-06-30T20:07:22 <laanwj> dongcarl: i don't have a strong opinion on it, but adding too many options is overwhelming
7592022-06-30T20:07:32 <dongcarl> Okay! I will keep the existing then :-)
7602022-06-30T20:07:39 <laanwj> sipa: right
7612022-06-30T20:07:42 <dongcarl> yeah one cache doesn't make sense without the other
7622022-06-30T20:07:58 <laanwj> like "does anyone want to fine-tune this manually in the first place? why?"
7632022-06-30T20:08:08 <sipa> I'm not sure I can even express when someone should change the size of the cache at all, except in very low-memory situations perhaps.
7642022-06-30T20:08:49 <sipa> dongcarl: Oh they have very different purposes, one of them without the other is certainly better than nothing. But both is even better.
7652022-06-30T20:09:18 <bytes1440000> jeremyrubin: There is nothing unreasonable with your questions or thoughts about the process. Commit access being given is a big thing and anyone reading the chat could understand some people don't like questions or different opinions or freedom to participate in this discussion and share thoughts.
7662022-06-30T20:10:45 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 255 seconds)
7672022-06-30T20:10:47 *** bytes1440000 <bytes1440000!~bytes1440@198.252.153.109> has left #bitcoin-core-dev
7682022-06-30T20:10:51 <Murch> It's a janitorial duty where people assess what's ready to merge and merge it
7692022-06-30T20:13:42 <michaelfolkson> The work over 2+ years speaks for itself. Especially if you've worked on this part of the codebase with that person during that time. What can be said in a 1-1 conversation that could change your mind?
7702022-06-30T20:14:29 <michaelfolkson> "If you endorse me I'll merge all your PRs"? It is just absurd. Anyway...
7712022-06-30T20:14:45 *** jarthur <jarthur!~jarthur@user/jarthur> has joined #bitcoin-core-dev
7722022-06-30T20:16:21 <jeremyrubin> my comment was w.r.t. luke-jr's comment about *general maintainership*
7732022-06-30T20:18:14 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
7742022-06-30T20:20:13 *** Guest17 <Guest17!~Guest17@46.197.60.131> has quit IRC (Quit: Client closed)
7752022-06-30T20:21:28 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
7762022-06-30T20:22:54 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 264 seconds)
7772022-06-30T20:25:54 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 246 seconds)
7782022-06-30T20:27:50 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
7792022-06-30T20:30:08 <dongcarl> BTW, I want to reiterate my thanks to all the reviewers for libbitcoinkernel. I can't do it without you guys. If there are things I can improve on in responding to review, feel free to let me know either here or direct message me!
7802022-06-30T20:31:58 <ariard> can we have a "libbitcoinkernel" mug plz :) ?
7812022-06-30T20:32:48 <dongcarl> ariard: Lmao nice idea! I'll see what I can do :-)
7822022-06-30T20:32:55 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
7832022-06-30T20:33:05 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
7842022-06-30T20:35:36 <jeremyrubin> fwiw for anyone interested, C/F a meeting in Feb-22 https://gnusha.org/bitcoin-core-dev/2022-02-24.log with laanwj pointing out that glozow as mempool maintainer would be a bad idea, given it's her prime area of work
7852022-06-30T20:35:37 <jeremyrubin> 11:37 < laanwj> so like, the mempool is notoriously difficult to get people to review for, so, we make glozow mempool maintainer
7862022-06-30T20:35:37 <jeremyrubin> 11:38 < jeremyrubin> laanwj: glozow is currently one of the main people writing new mempool code, so her being a maintainer probably doesn't help much
7872022-06-30T20:35:37 <jeremyrubin> 11:38 < laanwj> jeremyrubin: that was exactly my point
7882022-06-30T20:36:11 <laanwj> i changed my mind
7892022-06-30T20:36:36 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
7902022-06-30T20:36:47 <jeremyrubin> but do you see how given this was our prior conversation on the matter, it's not odd that i reiterate the question to see what's changed?
7912022-06-30T20:37:18 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 240 seconds)
7922022-06-30T20:37:20 <laanwj> asking questions is fine
7932022-06-30T20:37:28 <cfields_> that is a reasonable thing to bring up, yes.
7942022-06-30T20:38:01 <laanwj> making random demands from people is not
7952022-06-30T20:38:34 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
7962022-06-30T20:39:08 <jeremyrubin> a random demand would be one unrelated to the work, e/g. "draw an owl"
7972022-06-30T20:39:26 <jeremyrubin> if it's related to the work it's not really random...
7982022-06-30T20:40:56 <jeremyrubin> anyways i'd be curious to know in particular what made you change your mind about the suitability of glozow as mempool maintainer (e.g., something about the project, about gloria, about the role of maint, etc)
7992022-06-30T20:40:57 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 246 seconds)
8002022-06-30T20:41:13 <cfields_> jeremyrubin: trying to defuse a bit... please step back and consider that it looks like you're moving the goalposts and you're being met with pushback there because it's generally not in anyone's best interests to engage with such demands.
8012022-06-30T20:42:06 <jeremyrubin> which goalpost moved?
8022022-06-30T20:42:57 <jeremyrubin> and also what is the random demand in particular that i'd made?
8032022-06-30T20:43:05 <cfields_> jeremyrubin: demands for a formal job description and interview as a requirement for your approval.
8042022-06-30T20:43:21 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8052022-06-30T20:43:24 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
8062022-06-30T20:45:20 <laanwj> jeremyrubin: glozow being maintainer doesn't prevent other maintainers from merging her PRs, just like it is done now, it does allow her to merge other people's mempool related PRs so reducing our burden in that regard
8072022-06-30T20:48:02 <laanwj> if she was the only person working on the mempool then yeah, it would make very little difference
8082022-06-30T20:48:20 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
8092022-06-30T20:48:59 <laanwj> but whether she's officially maintainer or not she's definitely one of the most qualified persons to review mempool PRs at this point
8102022-06-30T20:49:18 <jeremyrubin> no doubt!
8112022-06-30T20:49:58 <dongcarl> Weird question: is there a reason why we use angled brackets for includes? When I work with the clang suite it seems to prefer double quotes instead. Just curious.
8122022-06-30T20:50:33 <laanwj> dongcarl: yes, it forces all include paths to be relative to the project root
8132022-06-30T20:50:37 <sipa> dongcarl: we switched to that at some point, you can probably find a rationale in the PR.
8142022-06-30T20:50:39 <laanwj> instead of current directory
8152022-06-30T20:50:40 <cfields_> dongcarl: we converted them all a while back. There's a PR that should be easy enough to find with a few git blame's.
8162022-06-30T20:50:46 <sipa> Ah yes, what laanwj says.
8172022-06-30T20:50:55 <laanwj> there were some issues with same-name include files
8182022-06-30T20:51:17 <dongcarl> Ah I see!
8192022-06-30T20:51:20 <dongcarl> thanks
8202022-06-30T20:51:24 <laanwj> this rules out potential ambiguity (except with system headers, but...)
8212022-06-30T21:01:08 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8222022-06-30T21:03:36 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Read error: Connection reset by peer)
8232022-06-30T21:06:48 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Remote host closed the connection)
8242022-06-30T21:07:16 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
8252022-06-30T21:11:57 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 255 seconds)
8262022-06-30T21:11:58 *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has joined #bitcoin-core-dev
8272022-06-30T21:17:03 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8282022-06-30T21:21:12 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 246 seconds)
8292022-06-30T21:21:12 *** Guest17 <Guest17!~Guest17@46.197.60.131> has joined #bitcoin-core-dev
8302022-06-30T21:21:32 *** kexkey <kexkey!~kexkey@178.249.214.27> has quit IRC (Quit: kexkey)
8312022-06-30T21:21:41 *** Guest17 <Guest17!~Guest17@46.197.60.131> has left #bitcoin-core-dev
8322022-06-30T21:23:10 *** cryptapus_ is now known as cryptapus
8332022-06-30T21:24:04 *** kexkey <kexkey!~kexkey@178.249.214.27> has joined #bitcoin-core-dev
8342022-06-30T21:28:18 *** kexkey <kexkey!~kexkey@178.249.214.27> has quit IRC (Ping timeout: 240 seconds)
8352022-06-30T21:28:38 *** kexkey <kexkey!~kexkey@178.249.214.10> has joined #bitcoin-core-dev
8362022-06-30T21:33:09 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8372022-06-30T21:35:44 *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has quit IRC (Remote host closed the connection)
8382022-06-30T21:37:44 *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has joined #bitcoin-core-dev
8392022-06-30T21:38:30 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 264 seconds)
8402022-06-30T21:43:04 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
8412022-06-30T21:48:00 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 260 seconds)
8422022-06-30T21:49:33 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8432022-06-30T22:10:27 *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has quit IRC (Ping timeout: 255 seconds)
8442022-06-30T22:12:50 *** yanmaani <yanmaani!~yanmaani@gateway/tor-sasl/yanmaani> has quit IRC (Ping timeout: 268 seconds)
8452022-06-30T22:14:05 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Remote host closed the connection)
8462022-06-30T22:15:12 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8472022-06-30T22:20:18 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 240 seconds)
8482022-06-30T22:24:34 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
8492022-06-30T22:27:04 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8502022-06-30T22:29:30 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 264 seconds)
8512022-06-30T22:31:56 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
8522022-06-30T22:38:29 *** yanmaani <yanmaani!~yanmaani@gateway/tor-sasl/yanmaani> has joined #bitcoin-core-dev
8532022-06-30T22:44:19 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8542022-06-30T22:44:23 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Quit: Leaving...)
8552022-06-30T22:49:41 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Read error: Connection reset by peer)
8562022-06-30T22:52:00 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8572022-06-30T22:58:02 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Remote host closed the connection)
8582022-06-30T22:58:19 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
8592022-06-30T22:58:38 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8602022-06-30T23:01:24 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Read error: Connection reset by peer)
8612022-06-30T23:01:58 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8622022-06-30T23:02:38 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 240 seconds)
8632022-06-30T23:05:01 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8642022-06-30T23:06:12 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 246 seconds)
8652022-06-30T23:09:21 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 246 seconds)
8662022-06-30T23:15:22 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8672022-06-30T23:19:05 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8682022-06-30T23:19:30 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 246 seconds)
8692022-06-30T23:22:27 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Read error: Connection reset by peer)
8702022-06-30T23:32:13 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8712022-06-30T23:33:14 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has joined #bitcoin-core-dev
8722022-06-30T23:36:51 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 255 seconds)
8732022-06-30T23:37:55 *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:6549:45d:1b21:9b9> has quit IRC (Ping timeout: 268 seconds)
8742022-06-30T23:39:35 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8752022-06-30T23:44:05 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
8762022-06-30T23:49:52 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8772022-06-30T23:52:41 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8782022-06-30T23:54:34 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
8792022-06-30T23:56:23 *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
8802022-06-30T23:57:06 *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 255 seconds)