12022-01-13T00:06:41  *** anandn <anandn!~anandn@2601:600:a27f:d92d:6c3b:dc86:41f9:d3cb> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)
  22022-01-13T00:10:39  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has quit IRC (Ping timeout: 276 seconds)
  32022-01-13T00:12:53  *** yanmaani <yanmaani!~yanmaani@gateway/tor-sasl/yanmaani> has joined #bitcoin-core-dev
  42022-01-13T00:15:57  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has joined #bitcoin-core-dev
  52022-01-13T00:18:26  *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
  62022-01-13T00:19:17  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has quit IRC (Ping timeout: 240 seconds)
  72022-01-13T00:21:42  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has quit IRC (Ping timeout: 276 seconds)
  82022-01-13T00:24:58  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 256 seconds)
  92022-01-13T00:27:40  *** sdfgsdfg <sdfgsdfg!~sdfgsdfg@user/sdfgsdfg> has joined #bitcoin-core-dev
 102022-01-13T00:29:05  *** anandn <anandn!~anandn@98.232.3.180> has joined #bitcoin-core-dev
 112022-01-13T00:35:53  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has joined #bitcoin-core-dev
 122022-01-13T00:37:53  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
 132022-01-13T00:38:57  *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Quit: Leaving...)
 142022-01-13T00:40:05  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has quit IRC (Remote host closed the connection)
 152022-01-13T00:43:04  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 250 seconds)
 162022-01-13T00:54:17  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has joined #bitcoin-core-dev
 172022-01-13T00:54:48  *** Common <Common!~Common@user/common> has quit IRC (Quit: Leaving)
 182022-01-13T00:55:14  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
 192022-01-13T00:56:37  *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Remote host closed the connection)
 202022-01-13T00:57:01  *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
 212022-01-13T00:59:32  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 256 seconds)
 222022-01-13T01:00:03  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has quit IRC (Ping timeout: 276 seconds)
 232022-01-13T01:11:47  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has joined #bitcoin-core-dev
 242022-01-13T01:12:48  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
 252022-01-13T01:17:36  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has quit IRC (Ping timeout: 276 seconds)
 262022-01-13T01:27:21  *** yanmaani <yanmaani!~yanmaani@gateway/tor-sasl/yanmaani> has quit IRC (Ping timeout: 276 seconds)
 272022-01-13T01:29:24  *** yanmaani <yanmaani!~yanmaani@gateway/tor-sasl/yanmaani> has joined #bitcoin-core-dev
 282022-01-13T01:30:03  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Remote host closed the connection)
 292022-01-13T01:30:29  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
 302022-01-13T01:31:48  *** anandn <anandn!~anandn@98.232.3.180> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)
 312022-01-13T01:32:19  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Remote host closed the connection)
 322022-01-13T01:33:23  *** stickies-v <stickies-v!~stickies-@host-92-8-97-28.as13285.net> has quit IRC (Ping timeout: 256 seconds)
 332022-01-13T01:33:50  *** stickies-v <stickies-v!~stickies-@81.178.231.129> has joined #bitcoin-core-dev
 342022-01-13T01:37:28  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
 352022-01-13T01:41:47  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Ping timeout: 252 seconds)
 362022-01-13T01:42:51  *** anandn <anandn!~anandn@2601:600:a27f:d92d:e83d:324a:8daa:9f9f> has joined #bitcoin-core-dev
 372022-01-13T01:48:16  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
 382022-01-13T01:52:51  *** arythmetic <arythmetic!~arythmeti@2607:fea8:85c1:db00:dc92:7b25:3f64:205b> has quit IRC (Remote host closed the connection)
 392022-01-13T01:53:23  *** arythmetic <arythmetic!~arythmeti@2607:fea8:85c1:db00:2565:e593:51c4:7af1> has joined #bitcoin-core-dev
 402022-01-13T01:57:29  *** anandn <anandn!~anandn@2601:600:a27f:d92d:e83d:324a:8daa:9f9f> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)
 412022-01-13T01:57:37  *** arythmetic <arythmetic!~arythmeti@2607:fea8:85c1:db00:2565:e593:51c4:7af1> has quit IRC (Ping timeout: 240 seconds)
 422022-01-13T02:00:02  *** evanlinjin <evanlinjin!evanlinjin@gateway/vpn/protonvpn/evanlinjin> has quit IRC (Quit: WeeChat 3.3)
 432022-01-13T02:00:50  *** arythmetic <arythmetic!~arythmeti@2607:fea8:85c1:db00:dc92:7b25:3f64:205b> has joined #bitcoin-core-dev
 442022-01-13T02:02:14  *** arythmetic <arythmetic!~arythmeti@2607:fea8:85c1:db00:dc92:7b25:3f64:205b> has quit IRC (Remote host closed the connection)
 452022-01-13T02:16:02  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 256 seconds)
 462022-01-13T02:20:23  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has joined #bitcoin-core-dev
 472022-01-13T02:23:54  *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Ping timeout: 276 seconds)
 482022-01-13T02:25:18  *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
 492022-01-13T02:25:51  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has quit IRC (Ping timeout: 276 seconds)
 502022-01-13T02:25:51  *** yanmaani <yanmaani!~yanmaani@gateway/tor-sasl/yanmaani> has quit IRC (Ping timeout: 276 seconds)
 512022-01-13T02:29:05  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
 522022-01-13T02:31:38  *** arythmetic <arythmetic!~arythmeti@2607:fea8:85c1:db00:2565:e593:51c4:7af1> has joined #bitcoin-core-dev
 532022-01-13T02:32:34  *** arythmetic <arythmetic!~arythmeti@2607:fea8:85c1:db00:2565:e593:51c4:7af1> has quit IRC (Remote host closed the connection)
 542022-01-13T02:33:34  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 250 seconds)
 552022-01-13T02:33:40  *** arythmetic <arythmetic!~arythmeti@2607:fea8:85c1:db00:2565:e593:51c4:7af1> has joined #bitcoin-core-dev
 562022-01-13T02:45:03  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
 572022-01-13T02:45:29  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Remote host closed the connection)
 582022-01-13T02:45:44  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
 592022-01-13T02:53:17  *** anandn <anandn!~anandn@98.232.3.180> has joined #bitcoin-core-dev
 602022-01-13T02:53:37  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Ping timeout: 240 seconds)
 612022-01-13T02:55:19  *** anandn <anandn!~anandn@98.232.3.180> has quit IRC (Client Quit)
 622022-01-13T02:55:45  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
 632022-01-13T02:56:52  *** Lightsword <Lightsword!~Lightswor@user/lightsword> has quit IRC (Quit: ZNC)
 642022-01-13T02:57:55  *** Lightsword <Lightsword!~Lightswor@user/lightsword> has joined #bitcoin-core-dev
 652022-01-13T02:59:00  *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Ping timeout: 276 seconds)
 662022-01-13T02:59:53  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Ping timeout: 252 seconds)
 672022-01-13T03:00:58  *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
 682022-01-13T03:04:05  *** sdfgsdfg <sdfgsdfg!~sdfgsdfg@user/sdfgsdfg> has quit IRC (Quit: ZzzZ)
 692022-01-13T03:10:29  *** anandn <anandn!~anandn@2601:600:a27f:d92d:e83d:324a:8daa:9f9f> has joined #bitcoin-core-dev
 702022-01-13T03:19:34  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
 712022-01-13T03:22:20  *** arythmetic <arythmetic!~arythmeti@2607:fea8:85c1:db00:2565:e593:51c4:7af1> has quit IRC (Remote host closed the connection)
 722022-01-13T03:23:24  *** arythmetic <arythmetic!~arythmeti@2607:fea8:85c1:db00:dc92:7b25:3f64:205b> has joined #bitcoin-core-dev
 732022-01-13T03:34:45  *** anandn <anandn!~anandn@2601:600:a27f:d92d:e83d:324a:8daa:9f9f> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)
 742022-01-13T03:36:53  *** Ting_Jun <Ting_Jun!~Ting_Jun@2603-7000-a701-2362-9b58-f688-93f3-b954.res6.spectrum.com> has quit IRC (Quit: Client closed)
 752022-01-13T03:37:36  *** arythmetic <arythmetic!~arythmeti@2607:fea8:85c1:db00:dc92:7b25:3f64:205b> has quit IRC (Remote host closed the connection)
 762022-01-13T03:41:15  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has joined #bitcoin-core-dev
 772022-01-13T03:42:26  *** arythmetic <arythmetic!~arythmeti@2607:fea8:85c1:db00:2565:e593:51c4:7af1> has joined #bitcoin-core-dev
 782022-01-13T03:45:05  *** vysn <vysn!~vysn@user/vysn> has joined #bitcoin-core-dev
 792022-01-13T03:45:05  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has quit IRC (Remote host closed the connection)
 802022-01-13T03:46:37  *** arythmetic <arythmetic!~arythmeti@2607:fea8:85c1:db00:2565:e593:51c4:7af1> has quit IRC (Ping timeout: 240 seconds)
 812022-01-13T03:46:54  *** mikehu44 <mikehu44!~quassel@159.65.11.175> has joined #bitcoin-core-dev
 822022-01-13T04:04:42  *** vysn <vysn!~vysn@user/vysn> has quit IRC (Remote host closed the connection)
 832022-01-13T04:07:50  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has joined #bitcoin-core-dev
 842022-01-13T04:13:06  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has quit IRC (Ping timeout: 276 seconds)
 852022-01-13T04:15:41  *** saranshsharma <saranshsharma!~saranshsh@202.12.82.245> has joined #bitcoin-core-dev
 862022-01-13T04:15:50  *** Guest65 <Guest65!~Guest65@2001:8f8:1b65:a697:a9d1:9847:4da1:538b> has joined #bitcoin-core-dev
 872022-01-13T04:22:57  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Ping timeout: 240 seconds)
 882022-01-13T04:25:03  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
 892022-01-13T04:26:13  *** Guest65 <Guest65!~Guest65@2001:8f8:1b65:a697:a9d1:9847:4da1:538b> has quit IRC (Ping timeout: 256 seconds)
 902022-01-13T04:32:44  *** anandn <anandn!~anandn@98.232.3.180> has joined #bitcoin-core-dev
 912022-01-13T04:34:09  *** anandn <anandn!~anandn@98.232.3.180> has quit IRC (Client Quit)
 922022-01-13T04:34:37  *** earnestly <earnestly!~earnest@user/earnestly> has quit IRC (Ping timeout: 240 seconds)
 932022-01-13T04:36:06  *** saranshsharma <saranshsharma!~saranshsh@202.12.82.245> has quit IRC (Remote host closed the connection)
 942022-01-13T04:36:48  *** anandn <anandn!~anandn@2601:600:a27f:d92d:a176:1395:81f9:b649> has joined #bitcoin-core-dev
 952022-01-13T04:38:32  *** anandn <anandn!~anandn@2601:600:a27f:d92d:a176:1395:81f9:b649> has quit IRC (Client Quit)
 962022-01-13T04:50:01  *** mikehu44 <mikehu44!~quassel@159.65.11.175> has quit IRC (Ping timeout: 256 seconds)
 972022-01-13T04:51:00  *** anandn <anandn!~anandn@2601:600:a27f:d92d:a908:fe4a:67d7:11cf> has joined #bitcoin-core-dev
 982022-01-13T04:52:20  *** mikehu44 <mikehu44!~quassel@159.65.11.175> has joined #bitcoin-core-dev
 992022-01-13T04:52:41  *** saranshsharma <saranshsharma!~saranshsh@202.12.82.245> has joined #bitcoin-core-dev
1002022-01-13T05:01:10  *** cmirror <cmirror!~cmirror@4.53.92.114> has joined #bitcoin-core-dev
1012022-01-13T05:06:57  *** Evel-Knievel <Evel-Knievel!~Evel-Knie@user/evel-knievel> has joined #bitcoin-core-dev
1022022-01-13T05:17:32  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Remote host closed the connection)
1032022-01-13T05:18:35  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1042022-01-13T05:23:02  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 256 seconds)
1052022-01-13T05:24:51  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has joined #bitcoin-core-dev
1062022-01-13T05:27:44  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has quit IRC (Remote host closed the connection)
1072022-01-13T05:29:29  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Ping timeout: 252 seconds)
1082022-01-13T05:32:31  *** saranshsharma <saranshsharma!~saranshsh@202.12.82.245> has quit IRC (Remote host closed the connection)
1092022-01-13T05:34:58  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1102022-01-13T05:57:36  *** meshcollider <meshcollider!meshcollid@user/meshcollider> has quit IRC (Ping timeout: 256 seconds)
1112022-01-13T05:58:35  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
1122022-01-13T06:00:04  *** meshcollider <meshcollider!meshcollid@meshcollider.jujube.ircnow.org> has joined #bitcoin-core-dev
1132022-01-13T06:02:24  *** sdfgsdfg <sdfgsdfg!~sdfgsdfg@user/sdfgsdfg> has joined #bitcoin-core-dev
1142022-01-13T06:04:49  *** Yihen <Yihen!~textual@114.113.238.18> has quit IRC (Ping timeout: 256 seconds)
1152022-01-13T06:13:19  *** jb55 <jb55!~jb55@user/jb55> has quit IRC (Ping timeout: 256 seconds)
1162022-01-13T06:29:46  *** morcos <morcos!~morcos@gateway/tor-sasl/morcos> has quit IRC (Quit: ZNC 1.8.2+deb1+bionic2 - https://znc.in)
1172022-01-13T06:29:52  *** morcos_ <morcos_!~morcos@gateway/tor-sasl/morcos> has joined #bitcoin-core-dev
1182022-01-13T06:30:17  *** morcos_ is now known as morcos
1192022-01-13T06:34:32  *** grettke <grettke!~grettke@cpe-65-29-228-30.wi.res.rr.com> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)
1202022-01-13T06:35:33  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has joined #bitcoin-core-dev
1212022-01-13T06:38:24  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 250 seconds)
1222022-01-13T06:41:57  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has quit IRC (Ping timeout: 276 seconds)
1232022-01-13T06:51:03  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1242022-01-13T06:55:10  *** Ting_Jun <Ting_Jun!~Ting_Jun@2603-7000-a701-2362-9b58-f688-93f3-b954.res6.spectrum.com> has joined #bitcoin-core-dev
1252022-01-13T06:55:24  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 256 seconds)
1262022-01-13T06:58:06  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has joined #bitcoin-core-dev
1272022-01-13T07:01:53  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Ping timeout: 252 seconds)
1282022-01-13T07:03:45  *** brunoerg <brunoerg!~brunoerg@187.183.47.88> has joined #bitcoin-core-dev
1292022-01-13T07:07:53  *** bairen <bairen!~bairen@gateway/tor-sasl/bairen> has quit IRC (Remote host closed the connection)
1302022-01-13T07:08:08  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1312022-01-13T07:08:26  *** jonatack <jonatack!jonatack@user/jonatack> has quit IRC (Ping timeout: 256 seconds)
1322022-01-13T07:10:13  *** bairen <bairen!~bairen@gateway/tor-sasl/bairen> has joined #bitcoin-core-dev
1332022-01-13T07:12:49  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 256 seconds)
1342022-01-13T07:25:43  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1352022-01-13T07:27:08  *** noonien <noonien!~noonien@user/noonien> has quit IRC (Ping timeout: 256 seconds)
1362022-01-13T07:27:29  *** noonien <noonien!~noonien@user/noonien> has joined #bitcoin-core-dev
1372022-01-13T07:30:56  *** bairen <bairen!~bairen@gateway/tor-sasl/bairen> has quit IRC (Remote host closed the connection)
1382022-01-13T07:31:44  *** bairen <bairen!~bairen@gateway/tor-sasl/bairen> has joined #bitcoin-core-dev
1392022-01-13T07:32:14  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 256 seconds)
1402022-01-13T07:40:52  <S3RK> any wallet expert can confirm whether CWallet::mapTxSpends should track spends _to_ the wallet (as ooposed to only spends from the wallet)?
1412022-01-13T07:41:51  <S3RK> asking because of https://github.com/bitcoin/bitcoin/pull/22929#issuecomment-1011559903
1422022-01-13T07:44:21  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1432022-01-13T07:46:26  *** lukedashjr <lukedashjr!~luke-jr@user/luke-jr> has joined #bitcoin-core-dev
1442022-01-13T07:46:57  *** vasild <vasild!~vd@user/vasild> has quit IRC (Ping timeout: 276 seconds)
1452022-01-13T07:47:27  *** vasild <vasild!~vd@user/vasild> has joined #bitcoin-core-dev
1462022-01-13T07:49:39  *** luke-jr <luke-jr!~luke-jr@user/luke-jr> has quit IRC (Ping timeout: 256 seconds)
1472022-01-13T07:49:41  *** lukedashjr is now known as luke-jr
1482022-01-13T07:57:12  *** saranshsharma <saranshsharma!~saranshsh@202.12.82.241> has joined #bitcoin-core-dev
1492022-01-13T08:00:17  *** anandn <anandn!~anandn@2601:600:a27f:d92d:a908:fe4a:67d7:11cf> has quit IRC (Ping timeout: 240 seconds)
1502022-01-13T08:08:21  *** brunoerg <brunoerg!~brunoerg@187.183.47.88> has quit IRC (Ping timeout: 256 seconds)
1512022-01-13T08:16:10  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
1522022-01-13T08:16:13  *** donchate <donchate!~donchate@user/donchate> has quit IRC (Quit: in /dev/null no one can hear you scream...)
1532022-01-13T08:19:09  *** sdfgsdfg <sdfgsdfg!~sdfgsdfg@user/sdfgsdfg> has quit IRC (Quit: ZzzZ)
1542022-01-13T08:35:06  *** sdfgsdfg <sdfgsdfg!~sdfgsdfg@user/sdfgsdfg> has joined #bitcoin-core-dev
1552022-01-13T08:36:36  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1562022-01-13T08:36:36  <bitcoin-git> [gui] promag closed pull request #385: Always log context function of QtDebugMsg messages (master...2021-07-qdebug-func) https://github.com/bitcoin-core/gui/pull/385
1572022-01-13T08:36:37  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1582022-01-13T08:37:47  *** Guyver2 <Guyver2!~Guyver@guyver2.xs4all.nl> has joined #bitcoin-core-dev
1592022-01-13T08:38:01  *** saranshsharma <saranshsharma!~saranshsh@202.12.82.241> has quit IRC (Remote host closed the connection)
1602022-01-13T08:43:29  *** saranshsharma <saranshsharma!~saranshsh@202.12.82.241> has joined #bitcoin-core-dev
1612022-01-13T08:47:32  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 250 seconds)
1622022-01-13T08:56:31  *** saranshs_ <saranshs_!~saranshsh@2402:3a80:41b:d2bb:3802:41e8:d2ca:f597> has joined #bitcoin-core-dev
1632022-01-13T08:57:05  *** saranshsharma <saranshsharma!~saranshsh@202.12.82.241> has quit IRC (Ping timeout: 256 seconds)
1642022-01-13T09:00:03  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1652022-01-13T09:04:27  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 256 seconds)
1662022-01-13T09:04:59  *** ___nick___ <___nick___!~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net> has joined #bitcoin-core-dev
1672022-01-13T09:10:23  *** saranshsharma <saranshsharma!~saranshsh@202.12.82.241> has joined #bitcoin-core-dev
1682022-01-13T09:13:37  *** saranshs_ <saranshs_!~saranshsh@2402:3a80:41b:d2bb:3802:41e8:d2ca:f597> has quit IRC (Ping timeout: 240 seconds)
1692022-01-13T09:16:37  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1702022-01-13T09:19:21  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Ping timeout: 250 seconds)
1712022-01-13T09:21:27  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 256 seconds)
1722022-01-13T09:27:32  *** provoostenator_ <provoostenator_!~quassel@user/provoostenator> has quit IRC (Ping timeout: 240 seconds)
1732022-01-13T09:32:40  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1742022-01-13T09:36:35  *** saranshsharma <saranshsharma!~saranshsh@202.12.82.241> has quit IRC (Remote host closed the connection)
1752022-01-13T09:36:57  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 240 seconds)
1762022-01-13T09:37:26  *** provoostenator <provoostenator!~quassel@user/provoostenator> has joined #bitcoin-core-dev
1772022-01-13T09:41:54  *** saranshsharma <saranshsharma!~saranshsh@2401:4900:4bb4:c978:24b9:b2f8:8a00:3882> has joined #bitcoin-core-dev
1782022-01-13T09:45:57  *** saranshsharma <saranshsharma!~saranshsh@2401:4900:4bb4:c978:24b9:b2f8:8a00:3882> has quit IRC (Ping timeout: 240 seconds)
1792022-01-13T09:47:05  *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
1802022-01-13T09:49:08  *** brunoerg <brunoerg!~brunoerg@187.183.47.88> has joined #bitcoin-core-dev
1812022-01-13T09:50:06  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1822022-01-13T09:52:29  *** Jackielove4u <Jackielove4u!uid43977@user/jackielove4u> has joined #bitcoin-core-dev
1832022-01-13T10:02:56  *** kexkey <kexkey!~kexkey@static-198-54-132-91.cust.tzulo.com> has quit IRC (Ping timeout: 250 seconds)
1842022-01-13T10:04:47  *** kexkey <kexkey!~kexkey@static-198-54-132-139.cust.tzulo.com> has joined #bitcoin-core-dev
1852022-01-13T10:24:24  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1862022-01-13T10:24:24  <bitcoin-git> [bitcoin] laanwj pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/290ff5ef6d38...31db3dd874df
1872022-01-13T10:24:24  <bitcoin-git> bitcoin/master 18f304d Hennadii Stepanov: build: Improve error message when pkg-config is not installed
1882022-01-13T10:24:24  <bitcoin-git> bitcoin/master 31db3dd laanwj: Merge bitcoin/bitcoin#24048: build: Improve error message when pkg-config ...
1892022-01-13T10:24:26  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1902022-01-13T10:24:40  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1912022-01-13T10:24:40  <bitcoin-git> [bitcoin] laanwj merged pull request #24048: build: Improve error message when pkg-config is not installed (master...220112-m4) https://github.com/bitcoin/bitcoin/pull/24048
1922022-01-13T10:24:43  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1932022-01-13T10:25:58  *** earnestly <earnestly!~earnest@user/earnestly> has joined #bitcoin-core-dev
1942022-01-13T10:45:24  *** brunoerg <brunoerg!~brunoerg@187.183.47.88> has quit IRC (Remote host closed the connection)
1952022-01-13T10:45:56  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
1962022-01-13T10:50:09  *** x88x88x <x88x88x!~x88x88x@2001:19f0:5:39a8:5400:3ff:feb6:73cb> has quit IRC (Remote host closed the connection)
1972022-01-13T10:51:05  *** x88x88x <x88x88x!~x88x88x@149.28.53.172> has joined #bitcoin-core-dev
1982022-01-13T10:55:22  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 250 seconds)
1992022-01-13T10:58:20  *** bomb-on <bomb-on!~bomb-on@194.144.47.113> has joined #bitcoin-core-dev
2002022-01-13T11:00:18  *** bomb-on <bomb-on!~bomb-on@194.144.47.113> has quit IRC (Read error: Connection reset by peer)
2012022-01-13T11:00:33  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2022022-01-13T11:00:33  <bitcoin-git> [bitcoin] brunoerg opened pull request #24054: test: rest /tx with an invalid/unknown txid (master...2022-01-rest-functional) https://github.com/bitcoin/bitcoin/pull/24054
2032022-01-13T11:00:34  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2042022-01-13T11:05:19  *** mikehu44 <mikehu44!~quassel@159.65.11.175> has quit IRC (Ping timeout: 256 seconds)
2052022-01-13T11:08:27  *** SpellChecker <SpellChecker!~SpellChec@user/SpellChecker> has quit IRC (Ping timeout: 276 seconds)
2062022-01-13T11:08:55  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2072022-01-13T11:09:02  *** orionwl is now known as laanwj
2082022-01-13T11:11:10  *** SpellChecker <SpellChecker!~SpellChec@user/SpellChecker> has joined #bitcoin-core-dev
2092022-01-13T11:14:57  *** sdfgsdfg <sdfgsdfg!~sdfgsdfg@user/sdfgsdfg> has quit IRC (Quit: ZzzZ)
2102022-01-13T11:33:17  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2112022-01-13T11:33:17  <bitcoin-git> [bitcoin] fanquake opened pull request #24057: build: point to latest commit on 1.4.0 branch (master...actually_fix_guix) https://github.com/bitcoin/bitcoin/pull/24057
2122022-01-13T11:33:18  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2132022-01-13T11:35:19  <b10c> https://github.com/bitcoin/bitcoin/issues/23902 looks like spam to me and can be closed?
2142022-01-13T11:36:16  <fanquake> b10c: thanks. Not sure how that was missed
2152022-01-13T11:37:59  *** bomb-on <bomb-on!~bomb-on@194.144.47.113> has joined #bitcoin-core-dev
2162022-01-13T11:42:06  <laanwj> sometimes, github hides (shadowbans?) accounts and their issues and somehow unhides them later, so they escape notice at creation
2172022-01-13T11:43:37  *** bomb-on <bomb-on!~bomb-on@194.144.47.113> has quit IRC (Read error: Connection reset by peer)
2182022-01-13T11:51:29  *** bomb-on <bomb-on!~bomb-on@194.144.47.113> has joined #bitcoin-core-dev
2192022-01-13T12:05:25  *** TheCharlatan <TheCharlatan!~drgrid@2a01:4f9:4a:2adc::2> has joined #bitcoin-core-dev
2202022-01-13T12:09:17  *** saranshsharma <saranshsharma!~saranshsh@202.12.82.245> has joined #bitcoin-core-dev
2212022-01-13T12:13:48  *** saranshsharma <saranshsharma!~saranshsh@202.12.82.245> has quit IRC (Ping timeout: 250 seconds)
2222022-01-13T12:19:21  *** jonatack <jonatack!jonatack@user/jonatack> has joined #bitcoin-core-dev
2232022-01-13T12:30:45  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2242022-01-13T12:30:45  <bitcoin-git> [bitcoin] kallewoof opened pull request #24058: BIP-322 basic support (master...202201-bip322) https://github.com/bitcoin/bitcoin/pull/24058
2252022-01-13T12:30:46  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2262022-01-13T12:31:57  *** gnaf_ <gnaf_!gnaf@gateway/vpn/protonvpn/gnaf> has quit IRC (Ping timeout: 240 seconds)
2272022-01-13T12:32:49  *** ___nick___ <___nick___!~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
2282022-01-13T12:34:32  *** ___nick___ <___nick___!~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net> has joined #bitcoin-core-dev
2292022-01-13T12:36:48  *** ___nick___ <___nick___!~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net> has quit IRC (Client Quit)
2302022-01-13T12:38:27  *** ___nick___ <___nick___!~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net> has joined #bitcoin-core-dev
2312022-01-13T12:39:09  *** jonatack <jonatack!jonatack@user/jonatack> has quit IRC (Quit: Connection closed)
2322022-01-13T12:41:36  *** bomb-on <bomb-on!~bomb-on@194.144.47.113> has quit IRC (Read error: Connection reset by peer)
2332022-01-13T12:51:59  *** jonatack <jonatack!jonatack@user/jonatack> has joined #bitcoin-core-dev
2342022-01-13T12:59:14  *** yanmaani <yanmaani!~yanmaani@gateway/tor-sasl/yanmaani> has joined #bitcoin-core-dev
2352022-01-13T13:01:06  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2362022-01-13T13:01:06  <bitcoin-git> [bitcoin] MarcoFalke closed pull request #24047: Uninstall icon changed from default nsis to bitcoin (master...patch-1) https://github.com/bitcoin/bitcoin/pull/24047
2372022-01-13T13:01:07  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2382022-01-13T13:01:32  *** bairen <bairen!~bairen@gateway/tor-sasl/bairen> has quit IRC (Remote host closed the connection)
2392022-01-13T13:01:54  *** bomb-on <bomb-on!~bomb-on@194.144.47.113> has joined #bitcoin-core-dev
2402022-01-13T13:02:24  *** bomb-on <bomb-on!~bomb-on@194.144.47.113> has quit IRC (Read error: Connection reset by peer)
2412022-01-13T13:02:32  *** bairen <bairen!~bairen@gateway/tor-sasl/bairen> has joined #bitcoin-core-dev
2422022-01-13T13:07:09  *** bomb-on <bomb-on!~bomb-on@194.144.47.113> has joined #bitcoin-core-dev
2432022-01-13T13:08:17  *** geyaeb2 <geyaeb2!~geyaeb@gateway/tor-sasl/geyaeb> has joined #bitcoin-core-dev
2442022-01-13T13:08:43  *** morcos_ <morcos_!~morcos@gateway/tor-sasl/morcos> has joined #bitcoin-core-dev
2452022-01-13T13:10:39  *** morcos <morcos!~morcos@gateway/tor-sasl/morcos> has quit IRC (Ping timeout: 276 seconds)
2462022-01-13T13:10:39  *** geyaeb <geyaeb!~geyaeb@gateway/tor-sasl/geyaeb> has quit IRC (Ping timeout: 276 seconds)
2472022-01-13T13:10:40  *** morcos_ is now known as morcos
2482022-01-13T13:14:06  *** gnaf_ <gnaf_!gnaf@gateway/vpn/protonvpn/gnaf> has joined #bitcoin-core-dev
2492022-01-13T13:15:49  *** dermoth <dermoth!~dermoth@user/dermoth> has quit IRC (Quit: Leaving)
2502022-01-13T13:19:38  *** gnaf_ <gnaf_!gnaf@gateway/vpn/protonvpn/gnaf> has quit IRC (Quit: Konversation terminated!)
2512022-01-13T13:22:33  *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Quit: = "")
2522022-01-13T13:25:06  *** bomb-on <bomb-on!~bomb-on@194.144.47.113> has quit IRC (Read error: Connection reset by peer)
2532022-01-13T13:28:16  *** bomb-on <bomb-on!~bomb-on@194.144.47.113> has joined #bitcoin-core-dev
2542022-01-13T13:29:41  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Remote host closed the connection)
2552022-01-13T13:30:07  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
2562022-01-13T13:34:31  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Ping timeout: 245 seconds)
2572022-01-13T13:38:02  *** salvatoshi <salvatoshi!~salvatosh@genymobile-2-6-86.fib.nerim.net> has joined #bitcoin-core-dev
2582022-01-13T14:00:09  *** drnet <drnet!~drnet@178.197.232.24> has joined #bitcoin-core-dev
2592022-01-13T14:07:58  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
2602022-01-13T14:08:08  *** Guyver2_ <Guyver2_!~Guyver@guyver2.xs4all.nl> has joined #bitcoin-core-dev
2612022-01-13T14:10:04  *** bomb-on <bomb-on!~bomb-on@194.144.47.113> has quit IRC (Quit: aллилѹіа!)
2622022-01-13T14:10:22  *** Guyver2 <Guyver2!~Guyver@guyver2.xs4all.nl> has quit IRC (Ping timeout: 250 seconds)
2632022-01-13T14:10:25  *** Guyver2_ is now known as Guyver2
2642022-01-13T14:19:05  *** da39a3ee5e6b4b0d <da39a3ee5e6b4b0d!~textual@2403:6200:8876:c04a:e083:f91a:e3b1:b08b> has joined #bitcoin-core-dev
2652022-01-13T14:28:13  *** da39a3ee5e6b4b0_ <da39a3ee5e6b4b0_!~textual@2403:6200:8876:c04a:6410:d0a3:c1e2:34d8> has joined #bitcoin-core-dev
2662022-01-13T14:30:57  *** da39a3ee5e6b4b0d <da39a3ee5e6b4b0d!~textual@2403:6200:8876:c04a:e083:f91a:e3b1:b08b> has quit IRC (Ping timeout: 240 seconds)
2672022-01-13T14:41:23  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Remote host closed the connection)
2682022-01-13T14:42:55  *** brunoerg <brunoerg!~brunoerg@187.183.47.88> has joined #bitcoin-core-dev
2692022-01-13T15:01:01  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2702022-01-13T15:01:02  <bitcoin-git> [bitcoin] MarcoFalke opened pull request #24059: Fix implicit-integer-sign-change in arith_uint256 (master...2201-int) https://github.com/bitcoin/bitcoin/pull/24059
2712022-01-13T15:01:03  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2722022-01-13T15:03:00  *** geyaeb3 <geyaeb3!~geyaeb@gateway/tor-sasl/geyaeb> has joined #bitcoin-core-dev
2732022-01-13T15:03:45  *** geyaeb2 <geyaeb2!~geyaeb@gateway/tor-sasl/geyaeb> has quit IRC (Ping timeout: 276 seconds)
2742022-01-13T15:06:22  *** Guyver2_ <Guyver2_!Guyver@guyver2.xs4all.nl> has joined #bitcoin-core-dev
2752022-01-13T15:09:23  *** Guyver2 <Guyver2!~Guyver@guyver2.xs4all.nl> has quit IRC (Ping timeout: 256 seconds)
2762022-01-13T15:09:23  *** Guyver2_ is now known as Guyver2
2772022-01-13T15:19:34  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has joined #bitcoin-core-dev
2782022-01-13T15:20:19  *** drnet <drnet!~drnet@178.197.232.24> has quit IRC (Ping timeout: 256 seconds)
2792022-01-13T15:24:53  *** arythmetic <arythmetic!~arythmeti@2607:fea8:85c1:db00:2565:e593:51c4:7af1> has joined #bitcoin-core-dev
2802022-01-13T15:30:05  *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2812022-01-13T15:32:57  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 240 seconds)
2822022-01-13T15:34:42  *** bomb-on <bomb-on!~bomb-on@194.144.47.113> has joined #bitcoin-core-dev
2832022-01-13T15:36:12  *** drnet <drnet!~drnet@178.197.232.24> has joined #bitcoin-core-dev
2842022-01-13T15:39:06  *** da39a3ee5e6b4b0_ <da39a3ee5e6b4b0_!~textual@2403:6200:8876:c04a:6410:d0a3:c1e2:34d8> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)
2852022-01-13T15:40:38  *** brunoerg <brunoerg!~brunoerg@187.183.47.88> has quit IRC (Remote host closed the connection)
2862022-01-13T15:40:45  *** bomb-on_ <bomb-on_!~bomb-on@213.220.120.43> has joined #bitcoin-core-dev
2872022-01-13T15:41:54  *** bomb-on <bomb-on!~bomb-on@194.144.47.113> has quit IRC (Read error: Connection reset by peer)
2882022-01-13T15:43:58  *** bomb-on_ <bomb-on_!~bomb-on@213.220.120.43> has quit IRC (Read error: Connection reset by peer)
2892022-01-13T15:45:49  *** bomb-on <bomb-on!~bomb-on@213.220.120.43> has joined #bitcoin-core-dev
2902022-01-13T15:46:49  *** bomb-on_ <bomb-on_!~bomb-on@194.144.47.113> has joined #bitcoin-core-dev
2912022-01-13T15:48:05  *** bomb-on <bomb-on!~bomb-on@213.220.120.43> has quit IRC (Read error: Connection reset by peer)
2922022-01-13T15:54:53  *** drnet <drnet!~drnet@178.197.232.24> has quit IRC (Ping timeout: 256 seconds)
2932022-01-13T15:56:45  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
2942022-01-13T16:01:34  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Ping timeout: 268 seconds)
2952022-01-13T16:20:30  *** grettke <grettke!~grettke@cpe-65-29-228-30.wi.res.rr.com> has joined #bitcoin-core-dev
2962022-01-13T16:26:30  *** drnet <drnet!~drnet@178.197.232.24> has joined #bitcoin-core-dev
2972022-01-13T16:30:19  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
2982022-01-13T16:31:43  *** promag <promag!~promag@188.250.84.129> has joined #bitcoin-core-dev
2992022-01-13T16:35:32  *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 250 seconds)
3002022-01-13T16:36:43  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3012022-01-13T16:45:51  *** jb55 <jb55!~jb55@user/jb55> has joined #bitcoin-core-dev
3022022-01-13T16:46:48  *** drnet <drnet!~drnet@178.197.232.24> has quit IRC (Ping timeout: 250 seconds)
3032022-01-13T16:49:57  *** jespada <jespada!~jespada@87.74.36.188> has quit IRC (Ping timeout: 240 seconds)
3042022-01-13T16:51:48  *** jespada <jespada!~jespada@87.74.36.188> has joined #bitcoin-core-dev
3052022-01-13T16:53:44  *** salvatoshi <salvatoshi!~salvatosh@genymobile-2-6-86.fib.nerim.net> has quit IRC (Ping timeout: 250 seconds)
3062022-01-13T17:06:15  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Remote host closed the connection)
3072022-01-13T17:08:50  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
3082022-01-13T17:10:48  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Remote host closed the connection)
3092022-01-13T17:11:33  *** RDK <RDK!~RDK@p200300db671eac80d64ce12aa1f4842d.dip0.t-ipconnect.de> has joined #bitcoin-core-dev
3102022-01-13T17:13:53  *** sz <sz!~sz@2601:642:4c04:a10:48b2:227a:9c59:1ae8> has joined #bitcoin-core-dev
3112022-01-13T17:16:06  *** bairen <bairen!~bairen@gateway/tor-sasl/bairen> has quit IRC (Remote host closed the connection)
3122022-01-13T17:16:37  *** bairen <bairen!~bairen@gateway/tor-sasl/bairen> has joined #bitcoin-core-dev
3132022-01-13T17:17:51  *** sz <sz!~sz@2601:642:4c04:a10:48b2:227a:9c59:1ae8> has quit IRC (Remote host closed the connection)
3142022-01-13T17:21:56  *** JimBer110 <JimBer110!~jimmy@83-233-247-129.cust.bredband2.com> has joined #bitcoin-core-dev
3152022-01-13T17:26:13  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
3162022-01-13T17:30:34  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Ping timeout: 250 seconds)
3172022-01-13T17:34:56  *** _andrewtoth_ <_andrewtoth_!~andrewtot@gateway/tor-sasl/andrewtoth> has joined #bitcoin-core-dev
3182022-01-13T17:35:41  *** _andrewtoth_ <_andrewtoth_!~andrewtot@gateway/tor-sasl/andrewtoth> has quit IRC (Remote host closed the connection)
3192022-01-13T17:36:01  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
3202022-01-13T17:36:01  <bitcoin-git> [bitcoin] laanwj pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/31db3dd874df...767ee2e3a108
3212022-01-13T17:36:01  <bitcoin-git> bitcoin/master 091ccc3 Perlover: The evhttp_connection_get_peer function from libevent changes the type of ...
3222022-01-13T17:36:01  <bitcoin-git> bitcoin/master c62d763 Perlover: Necessary improvements to make configure work without libevent installed
3232022-01-13T17:36:01  <bitcoin-git> bitcoin/master 767ee2e laanwj: Merge bitcoin/bitcoin#23607: rpc: Pass const char* to evhttp_connection_ge...
3242022-01-13T17:36:03  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3252022-01-13T17:36:18  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
3262022-01-13T17:36:18  <bitcoin-git> [bitcoin] laanwj merged pull request #23607: rpc: Pass const char* to evhttp_connection_get_peer for new libevent (master...patch-1) https://github.com/bitcoin/bitcoin/pull/23607
3272022-01-13T17:36:20  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3282022-01-13T17:37:48  *** andrewtoth_ <andrewtoth_!~andrewtot@gateway/tor-sasl/andrewtoth> has quit IRC (Ping timeout: 276 seconds)
3292022-01-13T17:37:54  *** saranshsharma <saranshsharma!~saranshsh@202.12.82.245> has joined #bitcoin-core-dev
3302022-01-13T17:38:55  *** saranshs_ <saranshs_!~saranshsh@202.12.82.245> has joined #bitcoin-core-dev
3312022-01-13T17:38:55  *** saranshsharma <saranshsharma!~saranshsh@202.12.82.245> has quit IRC (Read error: Connection reset by peer)
3322022-01-13T17:42:37  *** saranshs_ <saranshs_!~saranshsh@202.12.82.245> has quit IRC (Remote host closed the connection)
3332022-01-13T17:45:03  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
3342022-01-13T17:45:03  <bitcoin-git> [bitcoin] MarcoFalke pushed 5 commits to master: https://github.com/bitcoin/bitcoin/compare/767ee2e3a108...807169e10b4a
3352022-01-13T17:45:03  <bitcoin-git> bitcoin/master 2f79786 Sebastian Falbesoner: test: refactor: add constant for sequence number `SEQUENCE_FINAL`
3362022-01-13T17:45:03  <bitcoin-git> bitcoin/master f30041c Sebastian Falbesoner: test: create txs with current `nVersion` (2) by default
3372022-01-13T17:45:03  <bitcoin-git> bitcoin/master b24f6c6 Sebastian Falbesoner: test: MiniWallet: support default `from_node` for creating txs
3382022-01-13T17:45:05  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3392022-01-13T17:45:20  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
3402022-01-13T17:45:20  <bitcoin-git> [bitcoin] MarcoFalke merged pull request #24035: test: use MiniWallet for mempool_accept.py (master...202201-test-use_MiniWallet_for_mempool_accept_etc) https://github.com/bitcoin/bitcoin/pull/24035
3412022-01-13T17:45:21  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3422022-01-13T17:46:23  *** jarthur <jarthur!~jarthur@2603-8080-1540-002d-85fe-8f80-ea5f-426b.res6.spectrum.com> has joined #bitcoin-core-dev
3432022-01-13T17:50:13  *** Talkless <Talkless!~Talkless@mail.dargis.net> has joined #bitcoin-core-dev
3442022-01-13T17:52:51  <achow101> S3RK: that is correct. mapTxSpends maps all spends to the txids that contains the spend
3452022-01-13T17:53:18  <achow101> that is necessary in order to detect conflicting incomining txs
3462022-01-13T17:54:53  <achow101> should've caught that before #22929 was merged... this behavior needs some tests
3472022-01-13T17:54:57  <gribble> https://github.com/bitcoin/bitcoin/issues/22929 | wallet: Automatically add receiving destinations to the address book by S3RK · Pull Request #22929 · bitcoin/bitcoin · GitHub
3482022-01-13T17:57:39  *** bomb-on_ <bomb-on_!~bomb-on@194.144.47.113> has quit IRC (Quit: aллилѹіа!)
3492022-01-13T18:01:48  *** brunoerg <brunoerg!~brunoerg@187.183.47.88> has joined #bitcoin-core-dev
3502022-01-13T18:05:10  *** Aaronvan_ <Aaronvan_!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
3512022-01-13T18:06:21  *** brunoerg <brunoerg!~brunoerg@187.183.47.88> has quit IRC (Ping timeout: 256 seconds)
3522022-01-13T18:07:53  *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Ping timeout: 256 seconds)
3532022-01-13T18:09:57  *** bomb-on <bomb-on!~bomb-on@194.144.47.113> has joined #bitcoin-core-dev
3542022-01-13T18:11:18  *** RDK <RDK!~RDK@p200300db671eac80d64ce12aa1f4842d.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 250 seconds)
3552022-01-13T18:13:16  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has quit IRC (Remote host closed the connection)
3562022-01-13T18:13:41  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has joined #bitcoin-core-dev
3572022-01-13T18:13:43  *** outfox <outfox!~outfox@user/outfox> has quit IRC (Ping timeout: 256 seconds)
3582022-01-13T18:15:15  *** outfox <outfox!~outfox@user/outfox> has joined #bitcoin-core-dev
3592022-01-13T18:16:15  *** Nekorand <Nekorand!~Random@cm-188-171-200-176.telecable.es> has joined #bitcoin-core-dev
3602022-01-13T18:22:49  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
3612022-01-13T18:24:04  <jeremyrubin> achow101 if i see a long-chain in the bottom of the mempool, and a some output in that is paying me, does core wallet save those transactions for rebroadcast?
3622022-01-13T18:25:55  <achow101> jeremyrubin: I think it will only save the ones that have outputs for it
3632022-01-13T18:26:20  <achow101> it won't pick up any ancestors or descendants
3642022-01-13T18:26:34  <sipa> the solution of course is making the mempool do the rebroadcasting :)
3652022-01-13T18:26:59  <MarcoFalke> sipa: The mempool will drop the txs after two weeks
3662022-01-13T18:27:36  <jeremyrubin> i'm writing an email about this. we should save all ancestors (obviously?) because they're required to claim our money
3672022-01-13T18:28:04  <jeremyrubin> we should also save all descendants, if they are paying a higher feerate and serve as a CPFP
3682022-01-13T18:28:32  <jeremyrubin> it seems odd that we'd save the one we have outputs for but not the unconfirmed parents, that seems like a definite bug
3692022-01-13T18:28:56  <achow101> as we add more (unrelated) txs to the wallet, it gets slower
3702022-01-13T18:29:21  <achow101> if there are a lot of unconfirmed ancestors and descendants, once they do confirm, that's just going to be junk sitting in the wallet forever
3712022-01-13T18:29:25  <sipa> they could be stored in a separate set of transactions, independent from mapwallet
3722022-01-13T18:29:39  <sipa> from which confirmed/conflicted things can be pruned
3732022-01-13T18:29:42  <jeremyrubin> i think engineering concerns / DoS aside, it's clearly rational to save these
3742022-01-13T18:29:56  <sipa> but otherwise don't really participate in wallet reasoning
3752022-01-13T18:30:08  <sipa> i agree it makes sense to store them
3762022-01-13T18:30:12  <jeremyrubin> i just wanted to check on what existing behavior was
3772022-01-13T18:30:39  <jeremyrubin> when we go to spend and the txns exist in the mempool still, does coin-selection allow spending from unconfirmed account for CPFP cost for longchains?
3782022-01-13T18:30:51  <sipa> MarcoFalke: That's fair; the issue here isn't so much the rebroadcasting itself, but the forgetting?
3792022-01-13T18:30:52  <achow101> no
3802022-01-13T18:31:49  <jeremyrubin> so if you have a new wallet with 3 unconfirmeds that have different tx histories (e.g. 3 txs, 5 txs, 10txs) and you generate a spend what cost is used for those inputs?
3812022-01-13T18:31:53  <MarcoFalke> I guess the issue is both rebroadcasting and forgetting
3822022-01-13T18:31:54  <jeremyrubin> Just the satisfaction cost
3832022-01-13T18:32:02  <achow101> just the satisfaction cost
3842022-01-13T18:32:31  <jeremyrubin> kk, thanks
3852022-01-13T18:32:32  <achow101> iirc there's some consideration for whether we will exceed ancestor/descendant limits
3862022-01-13T18:32:42  <achow101> but only insofar as whether the utxo is available for selection
3872022-01-13T18:32:45  <sipa> seems reasonable to open an issue for it or so
3882022-01-13T18:32:57  <sipa> not sure if this is really ML material
3892022-01-13T18:33:14  <jeremyrubin> sipa hopefully im not being seen as spamming the ML
3902022-01-13T18:34:06  <sipa> i just don't see how this concerns the ML... it's an issue with Bitcoin Core's wallet, only affecting the users of that wallet
3912022-01-13T18:34:09  <achow101> i agree that's not really ML material
3922022-01-13T18:34:29  <jeremyrubin> well it's not just an issue for core
3932022-01-13T18:34:34  <jeremyrubin> for any rational wallet
3942022-01-13T18:34:54  <jeremyrubin> the reason for the post is that one of the critiques of CTV/congestion control is 'look at all the wallet software we'd have to have for it to work well', whereas i think most of the things are rational behaviors (CTV or no) that wallets would implement once mempool gets more backlogged
3952022-01-13T18:35:22  <jeremyrubin> so i'm just describing the lifetime of a payment from the perspective of a rational wallet user during congested mempool
3962022-01-13T18:35:43  <sipa> Do other wallets even do rebroadcasting?
3972022-01-13T18:35:52  <achow101> the problem is that there are a lot of rational behaviors that wallet's should implement, but those are all hard to implement
3982022-01-13T18:36:04  <achow101> nevermind the fact that the most basic things are already difficult to do
3992022-01-13T18:36:11  <jeremyrubin> hence the email is documenting
4002022-01-13T18:36:42  <jeremyrubin> these are also things that aren't you do x and y would be cheaper. these are you don't do X and your wallet will lose payments.
4012022-01-13T18:37:14  <sipa> well, in theory, sure
4022022-01-13T18:37:56  <sipa> but in practice, if the mempool forgets about an unconfirmed ancestor of yours, with default policy, i think it's very likely the transaction just isn't going to confirm at all, and will probably be RBFed anyway.
4032022-01-13T18:38:21  <jeremyrubin> the RBF might e.g. double spend you
4042022-01-13T18:38:39  <jeremyrubin> so it'd be rational for you to CPFP from your output to speed up the conf
4052022-01-13T18:38:54  <jeremyrubin> depending on the amt of funds received
4062022-01-13T18:39:04  <achow101> we never spend external unconfirmed utxos unless the user acknowledges that it is dangerous to do so
4072022-01-13T18:39:23  <jeremyrubin> spend-to-self if you can't piggyback an actualpayment
4082022-01-13T18:39:40  <sipa> is it even possible to do that (without raw transaction interface), achow101 ?
4092022-01-13T18:39:46  <jeremyrubin> achow101: that sounds mildly irrational. spend your bad money first, good money later.
4102022-01-13T18:39:56  <achow101> sipa: see include_unsafe
4112022-01-13T18:40:00  <sipa> minconf=0 will still only spend your own unconfirmed UTXOs.
4122022-01-13T18:40:02  <jeremyrubin> why would i spend money that has ~0% risk when i have something at 100% risk i can derisk by spending?
4132022-01-13T18:40:16  *** sebsp73 <sebsp73!~sebsp73@agrenoble-651-1-526-48.w90-42.abo.wanadoo.fr> has joined #bitcoin-core-dev
4142022-01-13T18:40:38  <achow101> jeremyrubin: huh? presumably you want your payment to go through
4152022-01-13T18:40:46  *** outfox <outfox!~outfox@user/outfox> has quit IRC (Ping timeout: 250 seconds)
4162022-01-13T18:40:53  <achow101> not potentially get stuck in limbo and maybe need an expert to fix the problem
4172022-01-13T18:42:43  *** outfox <outfox!~outfox@user/outfox> has joined #bitcoin-core-dev
4182022-01-13T18:43:21  <jeremyrubin> achow101: why would CPFP'ing an unconfirmed require an expert to fix it?
4192022-01-13T18:43:48  <achow101> if the unconfirmed gets rbf'd
4202022-01-13T18:44:35  <achow101> perhaps not need an expert, but results in a confusing situation for your average user
4212022-01-13T18:44:44  <jeremyrubin> it's a fair point.
4222022-01-13T18:45:02  <jeremyrubin> still, in this case, there are two outcomes: RBF still pays you, now your payment is dead
4232022-01-13T18:45:19  <jeremyrubin> if the RBF is still paying you, you can reissue the txn and save on CPFP amount
4242022-01-13T18:45:31  <achow101> yeah but the original still shows up as an unconfirmed transaction
4252022-01-13T18:45:43  <jeremyrubin> if the RBF isn't paying you, then you should CPFP even more so as not to lose a payment to you
4262022-01-13T18:45:57  <jeremyrubin> (glozow hi package relay)
4272022-01-13T18:47:13  <achow101> imo we shouldn't do anything that might cause a user to need to reissue a payment. they will feel like they are double paying
4282022-01-13T18:47:25  <jeremyrubin> (this is also a good point in favor of txn sponsors / fee accounts, which if your TX spend was inconvenient (e.g. requiring a multisig) that having the ability to add third party fees is great)
4292022-01-13T18:47:25  <achow101> or they may not understand that the original payment attempt is dead
4302022-01-13T18:47:48  <jeremyrubin> achow101 that seems like a UI problem, not a reason to deviate from rationality
4312022-01-13T18:48:25  <jeremyrubin> the rational behavior should be supported, and the UI should simplify what has happened and explain it clearly. Those are largely separate concerns
4322022-01-13T18:48:48  <jeremyrubin> much more frustrating would be the case where I see an unconfirmed and i get double spent
4332022-01-13T18:48:59  <achow101> that's not a ui problem, that's a problem with time being linear
4342022-01-13T18:49:09  <jeremyrubin> ...
4352022-01-13T18:49:16  <achow101> "I sent the payment 2 days ago, now you're telling me I need to send it again?"
4362022-01-13T18:49:19  <achow101> people have memories
4372022-01-13T18:50:04  <achow101> regardless of what the ui shows, people will remember that they tried to pay previously
4382022-01-13T18:50:11  <jeremyrubin> I would assume that much of this can be automated
4392022-01-13T18:50:34  <jeremyrubin> it's not you having to reissue the payment, the wallet can prompt you "this payment failed because X"
4402022-01-13T18:50:42  <jeremyrubin> (also it strikes me that APO fixes some of this...)
4412022-01-13T18:51:03  <jeremyrubin> and the prompt can give you the tx to sign again.
4422022-01-13T18:51:21  <jeremyrubin> (or maybe even do it without permission explicitly)
4432022-01-13T18:52:43  <jeremyrubin> in any case it is definitely good to think about the UI concerns about understanding why / if payments get made.
4442022-01-13T18:55:03  *** promag <promag!~promag@188.250.84.129> has quit IRC (Remote host closed the connection)
4452022-01-13T19:00:17  <laanwj> #startmeeting
4462022-01-13T19:00:18  <core-meetingbot`> Meeting started Thu Jan 13 19:00:17 2022 UTC.  The chair is laanwj. Information about MeetBot at https://bitcoin.jonasschnelli.ch/ircmeetings.
4472022-01-13T19:00:18  <core-meetingbot`> Available commands: action commands idea info link nick
4482022-01-13T19:00:34  <hebasto> hi
4492022-01-13T19:00:35  <laanwj> #bitcoin-core-dev Meeting: achow101 _aj_ amiti ariard 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 moneyball
4502022-01-13T19:00:37  <laanwj> morcos nehan NicolasDorier paveljanik petertodd phantomcircuit promag provoostenator ryanofsky sdaftuar sipa vasild
4512022-01-13T19:00:43  <achow101> hi
4522022-01-13T19:00:45  <michaelfolkson> hi
4532022-01-13T19:00:56  <cfields> hi
4542022-01-13T19:00:56  <laanwj> welcome to the weekly general bitcoin-core-dev meeting
4552022-01-13T19:01:00  <kvaciral[m]> hi
4562022-01-13T19:01:11  <b10c> hi
4572022-01-13T19:01:22  <provoostenator> hi
4582022-01-13T19:01:55  <laanwj> there have been no proposed meeting topics this week (this can be done using #proposedmeetingtopic <topic>), any last-minute ones?
4592022-01-13T19:02:06  <sipa> hi
4602022-01-13T19:03:57  <laanwj> #topic High priority for review
4612022-01-13T19:03:57  <core-meetingbot`> topic: High priority for review
4622022-01-13T19:04:01  <jonatack> hi
4632022-01-13T19:04:44  <laanwj> https://github.com/bitcoin/bitcoin/projects/8 has 8 blockers, no bugfixes, 1 chasing concept ACK at the moment
4642022-01-13T19:04:55  <laanwj> anything to add, remove, or that is ready for merge?
4652022-01-13T19:05:01  <MarcoFalke> can i haz #23629
4662022-01-13T19:05:02  <gribble> https://github.com/bitcoin/bitcoin/issues/23629 | refactor tests to fix ubsan suppressions by MarcoFalke · Pull Request #23629 · bitcoin/bitcoin · GitHub
4672022-01-13T19:05:32  <jonatack> #22932 has ACKs by hebasto and achow101 (thanks!), might need one more
4682022-01-13T19:05:35  <gribble> https://github.com/bitcoin/bitcoin/issues/22932 | Guard CBlockIndex::nStatus by cs_main, require GetBlockPos/GetUndoPos to hold cs_main by jonatack · Pull Request #22932 · bitcoin/bitcoin · GitHub
4692022-01-13T19:05:36  <_aj_> laanwj: #23508
4702022-01-13T19:05:37  <gribble> https://github.com/bitcoin/bitcoin/issues/23508 | Add getdeploymentinfo RPC by ajtowns · Pull Request #23508 · bitcoin/bitcoin · GitHub
4712022-01-13T19:06:27  <jeremyrubin> hi!
4722022-01-13T19:06:41  <laanwj> MarcoFalke _aj_: added
4732022-01-13T19:06:57  <laanwj> jonatack: good to know, will take a look
4742022-01-13T19:07:52  <jonatack> I've tried to diff-review #22702 after ACKing it a few months ago, but it requires a fresh re-review. Planning to do that.
4752022-01-13T19:07:54  <gribble> https://github.com/bitcoin/bitcoin/issues/22702 | Add allocator for node based containers by martinus · Pull Request #22702 · bitcoin/bitcoin · GitHub
4762022-01-13T19:08:13  <jonatack> laanwj: thanks
4772022-01-13T19:08:21  <jeremyrubin> #proposedmeetingtopic release processes / feature freezes / best practice & optionality w.r.t. BIP-119 for non-deployment code
4782022-01-13T19:08:26  <laanwj> it's a pretty tough PR to review, but would be good to have more eyes on it
4792022-01-13T19:09:11  <MarcoFalke> Maybe we should be holding back on risky stuff until after the branch off?
4802022-01-13T19:09:12  <jonatack> yes, agree, i need to go through it fully again
4812022-01-13T19:10:24  <laanwj> MarcoFalke: which one do you consider especially risky?
4822022-01-13T19:10:40  <MarcoFalke> The allocator stuff?
4832022-01-13T19:10:54  <MarcoFalke> (Not a expert on that, maybe it is not risky at all)
4842022-01-13T19:10:55  <jonatack> true
4852022-01-13T19:11:25  <laanwj> yes, ok, agree it's better to merge that at the beginning of a merge window instead of the end, but don't think it's done reviewing yet anyhow
4862022-01-13T19:11:51  <_aj_> we're ~four weeks from freeze, ~six weeks from branching?
4872022-01-13T19:12:03  <jeremyrubin> feb 15 feature freeze
4882022-01-13T19:12:08  <laanwj> _aj_: yep
4892022-01-13T19:12:21  <MarcoFalke> two weeks from translation soft freeze
4902022-01-13T19:13:17  <laanwj> #topic Release processes / feature freezes / etc (jeremyrubin)
4912022-01-13T19:13:17  <core-meetingbot`> topic: Release processes / feature freezes / etc (jeremyrubin)
4922022-01-13T19:13:37  <jeremyrubin> ok so for #21702
4932022-01-13T19:13:42  <gribble> https://github.com/bitcoin/bitcoin/issues/21702 | Implement BIP-119 Validation (CheckTemplateVerify) by JeremyRubin · Pull Request #21702 · bitcoin/bitcoin · GitHub
4942022-01-13T19:14:25  <jeremyrubin> i'm curious to know if there is a loss of "optionality" given usual precedent of merging non-activated code in a prior maj release that would motivate merging -- while still being reviewed / discussed for activation -- the CTV code
4952022-01-13T19:14:44  <jeremyrubin> if there is no loss of optionality in terms of normal release practices, it doesn't matter much
4962022-01-13T19:15:05  <jeremyrubin> (this was a discussion topic output from Tuesday's meeting)
4972022-01-13T19:15:41  <jeremyrubin> One of the considerations for doing it is e.g. the ease of backporting the feature to the last major version, for example.
4982022-01-13T19:15:52  <michaelfolkson> To state the obvious for observers there are many premature activation concerns on BIP 119 https://gist.github.com/michaelfolkson/352a503f4f9fc5de89af528d86a1b718
4992022-01-13T19:16:08  <provoostenator> I'm not sure about optionality,  but increasing complexity of consensus code - even in code paths that aren't hit - always carries some risk.
5002022-01-13T19:16:25  <michaelfolkson> I know Jeremy will keep his head in the sand regardless but for the sake of observers
5012022-01-13T19:17:15  *** bairen <bairen!~bairen@gateway/tor-sasl/bairen> has quit IRC (Ping timeout: 276 seconds)
5022022-01-13T19:17:23  <provoostenator> The patch is probably already as short as it gets, but you can always try to split of more stuff into seperate PR's if they have dual use.
5032022-01-13T19:18:04  <provoostenator> But after that I think rebase-purgatory is the place to be until there's broad consensus that people want this soft fork.
5042022-01-13T19:19:53  <jeremyrubin> provoostenator i think that's reasonable, I just want to ensure that "code wasn't in 0.2x" to contribute to a 6mo-1yr delay on a possible release timeline once that does exist, however it is to be measured (optionality)
5052022-01-13T19:20:01  <_aj_> backporting a small patch to older versions seems plausible for CTV compared to taproot or segwit too
5062022-01-13T19:20:16  <provoostenator> Backporting isn't necessarily easier; if you get some code in now and then have to dramatically change it later, including in backports, life isn't much easier.
5072022-01-13T19:20:43  *** bairen <bairen!~bairen@gateway/tor-sasl/bairen> has joined #bitcoin-core-dev
5082022-01-13T19:21:36  <provoostenator> You could even maintain a patch with test on earlier branch to demonstrate that it's indeed not a problem.
5092022-01-13T19:22:33  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has quit IRC (Ping timeout: 250 seconds)
5102022-01-13T19:23:34  <jeremyrubin> provoostenator that does seem doable I guess? once e.g. the split off happens I could rebase once onto the 0.23 and freeze that even if other branch needs updates
5112022-01-13T19:23:54  <provoostenator> I also tend to agree with your point above (before the meeting) that many changes you need for mempool and wallet handling are useful in general.
5122022-01-13T19:24:27  <provoostenator> jeremyrubin: at first glance that seems doable, but maybe a waste of time if nobody actually has that concern.
5132022-01-13T19:25:40  <provoostenator> And demonstrating CSV in a working and user friendly Core wallet might help increase excitement / decrease worries.
5142022-01-13T19:25:42  <jeremyrubin> i think the main negative impact (outside of bug/complexity) would be prematurely impacting the PrecomputedData code path, if it were merged now. It's not a huge overhead though, but it is something.
5152022-01-13T19:25:54  <provoostenator> * CTV
5162022-01-13T19:26:05  <jeremyrubin> One of the benefits of merging would be having a signet client with CTV validation
5172022-01-13T19:26:12  <jeremyrubin> that would aid testing
5182022-01-13T19:26:35  <provoostenator> I think Signet users can be expected to know how to compile though.
5192022-01-13T19:26:41  *** test_ <test_!flooded@gateway/vpn/protonvpn/flood/x-43489060> has joined #bitcoin-core-dev
5202022-01-13T19:26:49  <jeremyrubin> fair
5212022-01-13T19:27:10  <provoostenator> That would be a good use case for maintaining a release branch
5222022-01-13T19:27:28  <provoostenator> So people can test with stable release + patch, rather than master + patch.
5232022-01-13T19:27:40  <jeremyrubin> are any maintainers able to weigh in on what advocates of CTV should be doing/aiming for? your input is valauble here too
5242022-01-13T19:28:22  <jeremyrubin> if you don't want to talk about CTV in particular, can talk generally about what OP_FOOBAR should do in the future
5252022-01-13T19:28:43  <achow101> I agree with provoostenator
5262022-01-13T19:29:26  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has joined #bitcoin-core-dev
5272022-01-13T19:29:36  <jeremyrubin> what do we think about doing what provoostenator but actually doing a release build of 23.0+experimental? So then people can just grab a binary
5282022-01-13T19:29:52  <provoostenator> jeremyrubin: you can just do that
5292022-01-13T19:30:13  *** _flood <_flood!flooded@gateway/vpn/protonvpn/flood/x-43489060> has quit IRC (Ping timeout: 256 seconds)
5302022-01-13T19:30:19  <provoostenator> Should be -  if it isn't yet - a matter of maintaining a fork branch and some Guix tweaks
5312022-01-13T19:30:23  <jeremyrubin> sure, happy to. but if i'm the only signer i'd not advise people to run it
5322022-01-13T19:30:23  <_aj_> jeremyrubin: (i'd consider running out-of-tree code to mine ctv blocks on the real signet, though that would also mean figuring out how to make txs propogate, but there's a bunch of higher priority things on my todo list)
5332022-01-13T19:30:26  <provoostenator> So it'll even be reproducable
5342022-01-13T19:31:11  <jeremyrubin> _aj_: yeah, this is why when i looked into "can't i just make the signer on signet run the new code" it wasn't a workable option
5352022-01-13T19:31:22  *** test__ <test__!flooded@gateway/vpn/protonvpn/flood/x-43489060> has joined #bitcoin-core-dev
5362022-01-13T19:31:41  <provoostenator> I think it warrants a fresh signet,.
5372022-01-13T19:32:47  <_aj_> jeremyrubin: (eh, i've tried code in the past to combine p2p service bits with consensus versionbits so nodes running a new fork can talk to each other; it's just work)
5382022-01-13T19:34:01  *** test_ <test_!flooded@gateway/vpn/protonvpn/flood/x-43489060> has quit IRC (Ping timeout: 256 seconds)
5392022-01-13T19:34:18  *** promag <promag!~promag@188.250.84.129> has joined #bitcoin-core-dev
5402022-01-13T19:34:55  <jeremyrubin> _aj_: i'd be a bit out of my depth working on that and i don't want to impose on your time to do that; a new signet seems the simplest to make it happen. would be nice if could be done from the latest release without downloading a new thing, but that burden shouldn't be too large...
5412022-01-13T19:35:09  <provoostenator> Custom signet would also let you massively constrain block space there, which could be handy for testing.
5422022-01-13T19:35:59  <provoostenator> jeremyrubin: afaik you can point bitcoin.conf to arbirary signets
5432022-01-13T19:36:00  <_aj_> jeremyrubin: anyone trying to use a new consensus feature needs to be able to build their own wallet etc anyway, compiling their own bitcoind should be the least of their worries
5442022-01-13T19:36:22  <_aj_> provoostenator: (not if bitcoind doesn't support the opcode you're trying to test -- it won't be accepted into the mempool)
5452022-01-13T19:36:28  <jeremyrubin> _aj_: you can use sapio studio somewhat off the shelf right now
5462022-01-13T19:36:45  <jeremyrubin> but i guess that counts as "build" your own, less so "implement" your own
5472022-01-13T19:36:51  <provoostenator> _aj_: I'm assuming the signet is used with the custom branch or custom binary.
5482022-01-13T19:37:15  <_aj_> provoostenator: if it's a custom branch, you could add a new -chain=ctvsignet option i suppose
5492022-01-13T19:37:19  <provoostenator> But the patch itself won't be more complicated for using the custom signet.
5502022-01-13T19:39:34  *** promag <promag!~promag@188.250.84.129> has quit IRC (Remote host closed the connection)
5512022-01-13T19:39:47  *** promag <promag!~promag@188.250.84.129> has joined #bitcoin-core-dev
5522022-01-13T19:41:06  *** promag <promag!~promag@188.250.84.129> has quit IRC (Remote host closed the connection)
5532022-01-13T19:41:15  <laanwj> any other topics?
5542022-01-13T19:43:06  <laanwj> #endmeeting
5552022-01-13T19:43:07  <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
5562022-01-13T19:43:07  <core-meetingbot`> Meeting ended Thu Jan 13 19:43:06 2022 UTC.
5572022-01-13T19:43:07  <core-meetingbot`> Minutes:        https://bitcoin.jonasschnelli.ch/ircmeetings/logs/bitcoin-core-dev/2022/bitcoin-core-dev.2022-01-13-19.00.moin.txt
5582022-01-13T19:51:33  *** sebsp73 <sebsp73!~sebsp73@agrenoble-651-1-526-48.w90-42.abo.wanadoo.fr> has quit IRC (Quit: Client closed)
5592022-01-13T19:54:30  *** flooded <flooded!flooded@gateway/vpn/protonvpn/flood/x-43489060> has joined #bitcoin-core-dev
5602022-01-13T19:57:28  *** test__ <test__!flooded@gateway/vpn/protonvpn/flood/x-43489060> has quit IRC (Ping timeout: 250 seconds)
5612022-01-13T20:01:49  <luke-jr> jeremyrubin: maybe we need to focus more on encouraging people to sign more than Core mainline releases
5622022-01-13T20:02:31  <luke-jr> jeremyrubin: I'm still not 100% setup for Guix yet, but I will try to sign yours if you remind me
5632022-01-13T20:02:39  *** promag <promag!~promag@188.250.84.129> has joined #bitcoin-core-dev
5642022-01-13T20:03:04  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Remote host closed the connection)
5652022-01-13T20:04:28  <jeremyrubin> luke-jr: thanks. i am somewhat ambivalent about signed releases in the first place which is why i've not done it previously. but i dont think theres a better alternative presently :/
5662022-01-13T20:04:42  *** yanmaani <yanmaani!~yanmaani@gateway/tor-sasl/yanmaani> has quit IRC (Ping timeout: 276 seconds)
5672022-01-13T20:04:44  <jeremyrubin> "everyone should compile bitcoin by hand"
5682022-01-13T20:07:00  *** promag <promag!~promag@188.250.84.129> has quit IRC (Ping timeout: 250 seconds)
5692022-01-13T20:07:22  <luke-jr> certainly better than non-reproducible binaries :p
5702022-01-13T20:19:45  *** brunoerg <brunoerg!~brunoerg@187.183.47.88> has joined #bitcoin-core-dev
5712022-01-13T20:24:27  *** brunoerg <brunoerg!~brunoerg@187.183.47.88> has quit IRC (Ping timeout: 256 seconds)
5722022-01-13T20:34:38  <michaelfolkson> luke-jr: It depends what you think that signature represents. I'm curious actually. Let's say Jeremy releases a fork of Core with OP_CTV in it in an attempt to get it activated (I wouldn't recommend it but say he did)
5732022-01-13T20:35:46  <michaelfolkson> Would you want to review the code before signing? Would you want to agree with the consensus change? Would you want to agree that the consensus change had community consensus?
5742022-01-13T20:36:31  *** ___nick___ <___nick___!~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net> has quit IRC (Ping timeout: 256 seconds)
5752022-01-13T20:36:49  <michaelfolkson> It sounds like from the above you're willing to sign only on the condition that Jeremy signs yours and nothing else
5762022-01-13T20:37:15  *** Talkless <Talkless!~Talkless@mail.dargis.net> has quit IRC (Quit: Konversation terminated!)
5772022-01-13T20:38:10  <michaelfolkson> I guess it could be a bit web of trust-y. I know this came from Jeremy hence I'm willing to sign it
5782022-01-13T20:38:33  <michaelfolkson> (assuming you trust him of course)
5792022-01-13T20:40:16  *** pete_rizzo_33 <pete_rizzo_33!~pete_rizz@69.206.19.61> has joined #bitcoin-core-dev
5802022-01-13T20:40:23  <sipa> the guix attestations mean "this source code corresponds to this binary", and if it's for a named release "i agree that this indeed the released source code under that name"
5812022-01-13T20:40:25  <sipa> nothing more
5822022-01-13T20:40:48  *** FollowTheRabbit <FollowTheRabbit!~FollowThe@87-231-54.netrunf.cytanet.com.cy> has joined #bitcoin-core-dev
5832022-01-13T20:44:05  <michaelfolkson> sipa: Like cryptographically?! Or is that just implicitly understood?
5842022-01-13T20:44:35  <michaelfolkson> I guess I should look it up
5852022-01-13T20:44:43  <sipa> That's what attestations are. They attest that the software was correctly built.
5862022-01-13T20:45:18  <sipa> It would be very strange that it would mean "people should run X!" if there wasn't some sort of message signed that states that.
5872022-01-13T20:46:19  <michaelfolkson> But are you literally signing a statement like "this source code corresponds to this binary" or can you only sign if you've compiled and so its implicit?
5882022-01-13T20:46:41  <sipa> I don't understand your question.
5892022-01-13T20:47:05  <jeremyrubin> GUIX tooling can largely be automated to sign releases. Not a good assumption the code has actually been reviewed
5902022-01-13T20:47:16  <sipa> The attestation is a signature on a file that contains the hashes of the produced binaries, the source code tarball, and the file name.
5912022-01-13T20:47:44  <jeremyrubin> It might be good to layer a signature that says "this code is safe" or "I am running this personally, at least".
5922022-01-13T20:47:53  <sipa> It does not sign "I reviewed this code", or "I think people should run this code", or "This software will solve world hunger". If you want that, you can do that, but that's not what the attestations are about.
5932022-01-13T20:48:44  <michaelfolkson> Does it need to be generally understood (with communicated words) what that GUIX attestation represents? It sounds like yes it does
5942022-01-13T20:49:27  <michaelfolkson> I guess the only alternative would be a zero knowledge-y thing where you can literally only sign if you've generated same binary
5952022-01-13T20:49:56  *** flooded is now known as _flood
5962022-01-13T20:51:42  <sipa> That still doesn't prevent people from misinterpreting it as something else.
5972022-01-13T20:53:07  *** brunoerg <brunoerg!~brunoerg@187.183.47.88> has joined #bitcoin-core-dev
5982022-01-13T20:53:22  *** promag <promag!~promag@188.250.84.129> has joined #bitcoin-core-dev
5992022-01-13T20:53:23  <michaelfolkson> I guess but you'd point to the zero knowledge-y process that you followed in this speculative world where such a thing was possible
6002022-01-13T20:54:02  <sipa> I can also link to the GUIX process now.
6012022-01-13T20:54:25  <sipa> Doesn't mean people will read it or understand its implications.
6022022-01-13T20:57:12  <michaelfolkson> I guess. The more that is embedded in that signature it seems the better to me. And a process where it was only possible to sign through a ZK process would be even better
6032022-01-13T20:57:29  *** brunoerg <brunoerg!~brunoerg@187.183.47.88> has quit IRC (Ping timeout: 256 seconds)
6042022-01-13T20:57:33  <sipa> Nor does the process prevent people running it from attaching additional semantics to it (e.g. they might only do guix builds for code they think is safe to run, implicitly attaching a meaning of vouching for it).
6052022-01-13T20:57:59  <michaelfolkson> Other than just needing to verbally say "Here is a link to the GUIX process I followed"
6062022-01-13T20:58:09  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Remote host closed the connection)
6072022-01-13T20:58:13  <michaelfolkson> But ok, thanks!
6082022-01-13T20:58:18  <sipa> Whether that meaning is conveyed is purely a social issue.
6092022-01-13T20:58:38  <michaelfolkson> It could be embedded in the signature, that was my point
6102022-01-13T20:58:52  <michaelfolkson> So it becomes more of a math issue than a social issue
6112022-01-13T20:59:13  <sipa> I think you misunderstand what a ZK system can accomplish. If I copy your compiled binary and sign it, I achieve the same thing.
6122022-01-13T20:59:19  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
6132022-01-13T20:59:23  <sipa> Even if I didn't compile it myself.
6142022-01-13T20:59:38  <sipa> ZK systems protect secret data. There is nothing secret here.
6152022-01-13T20:59:54  *** JimBer110 <JimBer110!~jimmy@83-233-247-129.cust.bredband2.com> has quit IRC (Quit: Konversation terminated!)
6162022-01-13T21:01:32  *** dviola <dviola!~diego@187.39.23.21> has quit IRC (Quit: WeeChat 3.4)
6172022-01-13T21:03:47  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 250 seconds)
6182022-01-13T21:06:52  *** FollowTheRabbit <FollowTheRabbit!~FollowThe@87-231-54.netrunf.cytanet.com.cy> has quit IRC (Quit: Client closed)
6192022-01-13T21:07:42  *** lukedashjr <lukedashjr!~luke-jr@user/luke-jr> has joined #bitcoin-core-dev
6202022-01-13T21:07:55  *** yanmaani <yanmaani!~yanmaani@gateway/tor-sasl/yanmaani> has joined #bitcoin-core-dev
6212022-01-13T21:10:24  <lukedashjr> michaelfolkson: cryptography has no meaning at all, except what people understand it to mean
6222022-01-13T21:10:31  *** luke-jr <luke-jr!~luke-jr@user/luke-jr> has quit IRC (Ping timeout: 256 seconds)
6232022-01-13T21:11:07  *** lukedashjr is now known as luke-jr
6242022-01-13T21:11:36  <luke-jr> michaelfolkson: my Guix signatures explicitly clarify that I am using binary "substitutes" too
6252022-01-13T21:12:25  <luke-jr> and while I would certainly appreciate more builds of my releases, Jeremy included, I didn't include it as a condition of my doing so for his
6262022-01-13T21:14:26  <jeremyrubin> actually you can do some interesting things if you randomly sample data from a GUIX build on a challenge generated by the hash of your signing key and the files you're compiling, you could "prove" that you at least had access to a transcript of the build maybe... however, auditing that would require someone else to compile it and check the
6272022-01-13T21:14:27  <jeremyrubin> transcript over.
6282022-01-13T21:15:15  <sipa> Yeah. And also, only meaningful if you're sure nobody else shared their build transcripts.
6292022-01-13T21:16:07  <jeremyrubin> luke-jr: i would be more willing to do GUIX builds if I felt it were more clearly communicated that it just meant "I have a computer that ran this"
6302022-01-13T21:16:23  <jeremyrubin> maybe i can mitigate that by doing multiple guix builds and having a key-per-machine
6312022-01-13T21:16:39  <jeremyrubin> so it's clear the signature is jeremyrubin-build-machine-1, and not jeremyrubin
6322022-01-13T21:17:08  <sipa> I don't think that adds anything. The trust is derived from the person administering the machine.
6332022-01-13T21:17:57  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
6342022-01-13T21:19:11  <luke-jr> jeremyrubin: I mean, you can always use --sig-notation to add arbitrary disclaimers and such too
6352022-01-13T21:19:27  <jeremyrubin> sipa: i think it does? sure trust is from the administration of the machine, but if i can tell people how i set up jeremyrubin-machine-1 and maintain it, it makes more clear what they're trusting me for
6362022-01-13T21:21:03  <jeremyrubin> e.g., if i wanted to mitigate supply chain issues i might compile it on 5 different machines for myself *anyways*
6372022-01-13T21:22:25  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 256 seconds)
6382022-01-13T21:22:40  <jeremyrubin> provoostenator sipa achow101: i posted my 'transaction lifetime' post btw, thanks for the feedback earlier
6392022-01-13T21:22:54  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
6402022-01-13T21:23:30  <jeremyrubin> if you would like i can open GH issues for those topics separately for at least core to DTRT
6412022-01-13T21:25:53  *** pete_rizzo_33 <pete_rizzo_33!~pete_rizz@69.206.19.61> has quit IRC (Quit: Client closed)
6422022-01-13T21:42:39  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
6432022-01-13T21:47:06  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Ping timeout: 250 seconds)
6442022-01-13T22:11:13  *** lofiel <lofiel!~lofiel@user/lofiel> has joined #bitcoin-core-dev
6452022-01-13T22:18:21  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
6462022-01-13T22:22:51  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Ping timeout: 245 seconds)
6472022-01-13T22:25:20  <michaelfolkson> [21:10:24]  <lukedashjr> michaelfolkson: cryptography has no meaning at all, except what people understand it to mean
6482022-01-13T22:26:40  <michaelfolkson> No meaning at all is a bit strong. At the very least you are proving you own a private key. And if you sign a statement with a private key only you own you are indicating you support that statement
6492022-01-13T22:27:17  <sipa> I think what luke means is that the interpretation of that statement is up to humans, in this context.
6502022-01-13T22:27:34  <michaelfolkson> Right, ok
6512022-01-13T22:27:43  <sipa> It's a bit strong to generalize to all cryptography. In particularly, encryption doesn't generally suffer from such interpretation issues.
6522022-01-13T22:28:41  <sipa> Though I guess you can come up with scenarios where receiving a message that contains a certain decryption has a certain humam meaning too.
6532022-01-13T22:30:25  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 256 seconds)
6542022-01-13T22:43:19  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
6552022-01-13T22:44:47  *** Alina-ma- <Alina-ma-!~Alina-mal@37.252.83.224> has joined #bitcoin-core-dev
6562022-01-13T22:44:59  *** Alina-malina <Alina-malina!~Alina-mal@user/alina-malina> has quit IRC (Ping timeout: 256 seconds)
6572022-01-13T22:50:33  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has joined #bitcoin-core-dev
6582022-01-13T22:51:53  *** Alina-ma- <Alina-ma-!~Alina-mal@37.252.83.224> has quit IRC (Quit: !be back soon)
6592022-01-13T22:55:21  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:64d3:5ec4:6df9:8177> has quit IRC (Ping timeout: 268 seconds)
6602022-01-13T22:56:41  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has quit IRC (Ping timeout: 252 seconds)
6612022-01-13T22:57:49  *** Guyver2 <Guyver2!Guyver@guyver2.xs4all.nl> has quit IRC (Remote host closed the connection)
6622022-01-13T22:58:35  *** Nekorand <Nekorand!~Random@cm-188-171-200-176.telecable.es> has quit IRC (Ping timeout: 256 seconds)
6632022-01-13T23:02:31  <jeremyrubin> sipa: actually encyrption in particular does suffer from this, since in order to be a secure encryption all ciphertexts must be equally likely :p
6642022-01-13T23:02:43  <jeremyrubin> so the ciphertext must be completely meaningless :p
6652022-01-13T23:04:25  <sipa> That's not true. All that is required is that the attacker cannot learn anything that they do not already know, from the ciphertext, if they don't know the key
6662022-01-13T23:05:32  <sipa> Oh, the ciphertext!
6672022-01-13T23:06:29  <sipa> Well, that's still not true, because it only needs to hold for an attacker that does not have the key.
6682022-01-13T23:07:17  <sipa> And unless you're working with information theoretical security, the criterion isn't that all ciphertexts should be equally likely. Only that a computationally bounded attacker cannot distinguish it from random.
6692022-01-13T23:07:53  <jeremyrubin> equally likely up to a negligible based on your computational bound ;)
6702022-01-13T23:08:31  <jeremyrubin> but that is the textbook definition iirc.
6712022-01-13T23:09:02  <jeremyrubin> but you can't even know that you have 'the key'. e.g., there could be encryptions where you can make different keys decrypt to two different valid (containing a hash commit?) messages
6722022-01-13T23:10:03  <jeremyrubin> enc(k1, k2, m1, m2) = c s.t. dec(k1, c) = m1, dec(k2, c) = m2. (perhaps you could prove that's not possible, but it certainly seems something you could describe)
6732022-01-13T23:10:30  <jeremyrubin> 'deniable encryption'
6742022-01-13T23:10:49  <sipa> I don't think even that holds. In particular, for long messages with some mode AES256, if there are only two possible plaintexts, there are only 2^256 (keys) * 2^256 (IVs) * 2 (plaintexts) possible ciphertexts, but the ciphertext may be much longer than 513 bits.
6752022-01-13T23:11:18  <jeremyrubin> you're saying there exists an encryption where this property doesn't hold
6762022-01-13T23:11:24  <jeremyrubin> which is not a valid counter to
6772022-01-13T23:11:25  <sipa> But that can still be semantically secure.
6782022-01-13T23:11:41  <jeremyrubin> there may exist an encryption where this is possible
6792022-01-13T23:11:54  <jeremyrubin> https://en.wikipedia.org/wiki/Deniable_encryption
6802022-01-13T23:12:30  <sipa> I'm saying this example would still be considered secure, because the distribution is computationally indistinguishable from uniform, despite being very much nonuniform.
6812022-01-13T23:12:32  <jeremyrubin> in any case we're at a hugh level of pedantism for #bitcoin-core-dev, we could chat on wizards about it more
6822022-01-13T23:14:26  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has joined #bitcoin-core-dev
6832022-01-13T23:20:36  *** Alina-malina <Alina-malina!~Alina-mal@user/alina-malina> has joined #bitcoin-core-dev
6842022-01-13T23:35:39  *** mudsip <mudsip!~mudsip@user/mudsip> has joined #bitcoin-core-dev
6852022-01-13T23:43:04  *** brunoerg <brunoerg!~brunoerg@187.183.47.88> has joined #bitcoin-core-dev
6862022-01-13T23:47:34  *** brunoerg <brunoerg!~brunoerg@187.183.47.88> has quit IRC (Ping timeout: 250 seconds)
6872022-01-13T23:48:03  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 256 seconds)
6882022-01-13T23:50:26  *** promag <promag!~promag@188.250.84.129> has quit IRC (Remote host closed the connection)
6892022-01-13T23:58:57  *** jarthur <jarthur!~jarthur@2603-8080-1540-002d-85fe-8f80-ea5f-426b.res6.spectrum.com> has quit IRC (Ping timeout: 240 seconds)