12021-01-28T00:02:54  *** spinza <spinza!~spin@102.132.245.16> has quit IRC (Quit: Coyote finally caught up with me...)
  22021-01-28T00:07:02  *** EagleTM <EagleTM!~EagleTM@unaffiliated/eagletm> has quit IRC (Ping timeout: 260 seconds)
  32021-01-28T00:09:37  *** spinza <spinza!~spin@102.132.245.16> has joined #bitcoin-core-dev
  42021-01-28T00:12:58  *** vadorovsky <vadorovsky!vadorovsky@gateway/shell/matrix.org/x-zjekpprcfisjgbfm> has joined #bitcoin-core-dev
  52021-01-28T00:12:59  *** robert_spigler <robert_spigler!robertspig@gateway/shell/matrix.org/x-jjtbjalneajouwbt> has joined #bitcoin-core-dev
  62021-01-28T00:12:59  *** icota[m] <icota[m]!icotamatri@gateway/shell/matrix.org/x-ecmdusibinvigata> has joined #bitcoin-core-dev
  72021-01-28T00:13:05  *** satwhale[m] <satwhale[m]!satwhalebi@gateway/shell/matrix.org/x-dytcfvbwxprbtvus> has joined #bitcoin-core-dev
  82021-01-28T00:13:05  *** suzziminer[m] <suzziminer[m]!suzziminer@gateway/shell/matrix.org/x-afhitfudsclrtywh> has joined #bitcoin-core-dev
  92021-01-28T00:13:05  *** marty[m]1 <marty[m]1!jmacawmatr@gateway/shell/matrix.org/x-zkfvjeudcxquukgf> has joined #bitcoin-core-dev
 102021-01-28T00:25:08  *** jonatack <jonatack!jon@gateway/vpn/airvpn/jonatack> has quit IRC (Ping timeout: 260 seconds)
 112021-01-28T00:28:50  *** prayank <prayank!~andr0irc@2402:8100:206a:1e47:f74d:e28e:ac6d:892f> has joined #bitcoin-core-dev
 122021-01-28T00:31:05  *** prayank <prayank!~andr0irc@2402:8100:206a:1e47:f74d:e28e:ac6d:892f> has quit IRC (Client Quit)
 132021-01-28T00:38:09  *** mattdrollette <mattdrollette!~mdrollett@cpe-70-123-125-237.tx.res.rr.com> has joined #bitcoin-core-dev
 142021-01-28T00:38:36  *** mdrollette <mdrollette!~mdrollett@cpe-70-123-125-237.tx.res.rr.com> has quit IRC (Ping timeout: 240 seconds)
 152021-01-28T00:40:58  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
 162021-01-28T00:40:59  <bitcoin-git> [bitcoin] meshcollider pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/d1ddead09a58...9deba2de764f
 172021-01-28T00:40:59  <bitcoin-git> bitcoin/master 647b81b Ivan Metlushko: wallet, rpc: add listdescriptors command
 182021-01-28T00:41:00  <bitcoin-git> bitcoin/master 9deba2d Samuel Dobson: Merge #20226: wallet, rpc: add listdescriptors command
 192021-01-28T00:41:01  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
 202021-01-28T00:41:48  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
 212021-01-28T00:41:49  <bitcoin-git> [bitcoin] meshcollider merged pull request #20226: wallet, rpc: add listdescriptors command (master...listdescriptors) https://github.com/bitcoin/bitcoin/pull/20226
 222021-01-28T00:41:49  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
 232021-01-28T00:44:18  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has quit IRC (Ping timeout: 268 seconds)
 242021-01-28T00:48:27  *** norisgOG <norisgOG!~norisgOG@91.193.7.40> has quit IRC (Read error: No route to host)
 252021-01-28T00:51:26  *** belcher <belcher!~belcher@unaffiliated/belcher> has quit IRC (Ping timeout: 240 seconds)
 262021-01-28T00:53:31  <dongcarl> In the meeting on the 14th, people asked jamesob and me to take a look at potential AssumeUTXO and chainman-deglobalization conflicts and if a certain merge order is preferable. Here is the result: https://github.com/bitcoin/bitcoin/pull/19806#issuecomment-768673523
 272021-01-28T00:53:48  <dongcarl> The conclusion was that the PRs are mergeable in any order without much pain if the last commit of the AssumeUTXO changes in #19806 is slightly modified
 282021-01-28T00:53:52  <gribble> https://github.com/bitcoin/bitcoin/issues/19806 | validation: UTXO snapshot activation by jamesob · Pull Request #19806 · bitcoin/bitcoin · GitHub
 292021-01-28T00:54:12  *** AaronvanW <AaronvanW!~AaronvanW@unaffiliated/aaronvanw> has quit IRC (Remote host closed the connection)
 302021-01-28T00:54:55  *** belcher <belcher!~belcher@unaffiliated/belcher> has joined #bitcoin-core-dev
 312021-01-28T01:02:46  <sipa> good to know
 322021-01-28T01:03:16  <dongcarl> :-)
 332021-01-28T01:06:05  *** justanotheruser <justanotheruser!~justanoth@unaffiliated/justanotheruser> has joined #bitcoin-core-dev
 342021-01-28T01:12:43  *** oozebrood <oozebrood!~oozebrood@mobile-166-177-184-1.mycingular.net> has quit IRC (Quit: Going offline, see ya! (www.adiirc.com))
 352021-01-28T01:16:02  *** stackingcore21_ <stackingcore21_!~stackingc@2604:a880:2:d0::1bda:1001> has quit IRC (Write error: Broken pipe)
 362021-01-28T01:16:02  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6981:7880::3> has quit IRC (Remote host closed the connection)
 372021-01-28T01:16:02  *** notmandatory <notmandatory!notmandato@2600:3c00::f03c:92ff:fe8e:dce6> has quit IRC (Quit: ZNC 1.7.2+deb3 - https://znc.in)
 382021-01-28T01:16:13  *** notmandatory <notmandatory!~notmandat@shindig.notmandatory.org> has joined #bitcoin-core-dev
 392021-01-28T01:16:27  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6981:7880::3> has joined #bitcoin-core-dev
 402021-01-28T01:16:38  *** stackingcore21 <stackingcore21!~stackingc@2604:a880:2:d0::1bda:1001> has joined #bitcoin-core-dev
 412021-01-28T01:24:49  *** jackk_ <jackk_!~jackk@205.178.111.134> has quit IRC (Quit: Going offline, see ya! (www.adiirc.com))
 422021-01-28T01:35:20  *** blueingress <blueingress!~pp_of_mm@197.1.197.35.bc.googleusercontent.com> has joined #bitcoin-core-dev
 432021-01-28T01:45:25  *** justanotheruser <justanotheruser!~justanoth@unaffiliated/justanotheruser> has quit IRC (Ping timeout: 240 seconds)
 442021-01-28T01:52:48  *** justanotheruser <justanotheruser!~justanoth@unaffiliated/justanotheruser> has joined #bitcoin-core-dev
 452021-01-28T02:00:00  *** spinza <spinza!~spin@102.132.245.16> has quit IRC (Quit: Coyote finally caught up with me...)
 462021-01-28T02:05:03  *** EagleTM <EagleTM!~EagleTM@unaffiliated/eagletm> has joined #bitcoin-core-dev
 472021-01-28T02:17:20  *** spinza <spinza!~spin@102.132.245.16> has joined #bitcoin-core-dev
 482021-01-28T02:19:48  *** Eagle[TM] <Eagle[TM]!~EagleTM@unaffiliated/eagletm> has joined #bitcoin-core-dev
 492021-01-28T02:21:15  *** notmandatory_ <notmandatory_!~notmandat@shindig.notmandatory.org> has joined #bitcoin-core-dev
 502021-01-28T02:21:41  *** rodarmor <rodarmor!sid210835@gateway/web/irccloud.com/x-moybmapnazyybsnq> has quit IRC (Ping timeout: 256 seconds)
 512021-01-28T02:21:41  *** EagleTM <EagleTM!~EagleTM@unaffiliated/eagletm> has quit IRC (Ping timeout: 256 seconds)
 522021-01-28T02:21:41  *** notmandatory <notmandatory!~notmandat@shindig.notmandatory.org> has quit IRC (Ping timeout: 256 seconds)
 532021-01-28T02:21:41  *** kexkey <kexkey!~kexkey@static-198-54-132-152.cust.tzulo.com> has quit IRC (Read error: Connection reset by peer)
 542021-01-28T02:21:41  *** mattdrollette <mattdrollette!~mdrollett@cpe-70-123-125-237.tx.res.rr.com> has quit IRC (Ping timeout: 256 seconds)
 552021-01-28T02:21:41  *** fanquake <fanquake!sid369002@gateway/web/irccloud.com/x-vaiqnaaqwdstxqrg> has quit IRC (Ping timeout: 256 seconds)
 562021-01-28T02:21:41  *** Jackielove4u <Jackielove4u!uid43977@gateway/web/irccloud.com/x-jdprefwyhgpusmtg> has quit IRC (Ping timeout: 256 seconds)
 572021-01-28T02:21:41  *** rodarmor <rodarmor!sid210835@gateway/web/irccloud.com/x-siorvfeetzzatiub> has joined #bitcoin-core-dev
 582021-01-28T02:21:47  *** fanquake_ <fanquake_!sid369002@gateway/web/irccloud.com/x-hooxevzeyzepxlxz> has joined #bitcoin-core-dev
 592021-01-28T02:21:58  *** mdrollette <mdrollette!~mdrollett@cpe-70-123-125-237.tx.res.rr.com> has joined #bitcoin-core-dev
 602021-01-28T02:22:07  *** copumpkin <copumpkin!~copumpkin@unaffiliated/copumpkin> has quit IRC (Ping timeout: 256 seconds)
 612021-01-28T02:22:22  *** az0re <az0re!~az0re@gateway/tor-sasl/az0re> has quit IRC (Remote host closed the connection)
 622021-01-28T02:22:36  *** Jackielove4u <Jackielove4u!uid43977@gateway/web/irccloud.com/x-sulwoxgyopxoqgnl> has joined #bitcoin-core-dev
 632021-01-28T02:23:59  *** copumpkin <copumpkin!~copumpkin@unaffiliated/copumpkin> has joined #bitcoin-core-dev
 642021-01-28T02:38:31  *** proofofkeags <proofofkeags!~proofofke@174-29-3-187.hlrn.qwest.net> has joined #bitcoin-core-dev
 652021-01-28T02:42:38  *** justanotheruser <justanotheruser!~justanoth@unaffiliated/justanotheruser> has quit IRC (Ping timeout: 264 seconds)
 662021-01-28T02:55:59  *** lukz40 <lukz40!~igloo@192.141.106.220> has joined #bitcoin-core-dev
 672021-01-28T03:03:39  *** lukz40 <lukz40!~igloo@192.141.106.220> has quit IRC (Ping timeout: 272 seconds)
 682021-01-28T03:16:53  *** sob3rkid <sob3rkid!de6ab109@222.106.177.9> has joined #bitcoin-core-dev
 692021-01-28T03:17:45  <sob3rkid> Hey guys
 702021-01-28T03:17:45  <sob3rkid> I have Ios,Android,and Nodejs SDK sources on Github that develpoers might be interested in testing.
 712021-01-28T03:17:46  <sob3rkid> We are currently developing a bundle of custodial and non-custodial assets and a combination of each functional layer into one.
 722021-01-28T03:17:46  <sob3rkid> I would like to share some sample codes for testing apps
 732021-01-28T03:17:47  <sob3rkid> would it be okay if I release the external link of the code on this IRC group?
 742021-01-28T03:17:47  <sob3rkid> These are useable open-sources for developers , people could use it if they like it after testing it :)
 752021-01-28T03:17:48  <sob3rkid> If you are kindly allow me to share this I would be really appreciated ,
 762021-01-28T03:17:48  <sob3rkid> or you could  personally message me.
 772021-01-28T03:17:49  <sob3rkid> thank you.
 782021-01-28T03:18:53  <sipa> sob3rkid: this channel is for development bitcoin core, a specific implementation of the bitcoin protocol
 792021-01-28T03:19:27  <sob3rkid> oh, I see, my bad  thank you :)
 802021-01-28T03:20:23  *** kexkey <kexkey!~kexkey@static-198-54-132-152.cust.tzulo.com> has joined #bitcoin-core-dev
 812021-01-28T03:20:37  *** sdaftuar <sdaftuar!~sdaftuar@gateway/tor-sasl/sdaftuar> has quit IRC (Remote host closed the connection)
 822021-01-28T03:20:56  *** yanmaani <yanmaani!~yanmaani@gateway/tor-sasl/yanmaani> has quit IRC (Ping timeout: 268 seconds)
 832021-01-28T03:21:01  *** sdaftuar <sdaftuar!~sdaftuar@gateway/tor-sasl/sdaftuar> has joined #bitcoin-core-dev
 842021-01-28T03:26:05  *** yanmaani <yanmaani!~yanmaani@gateway/tor-sasl/yanmaani> has joined #bitcoin-core-dev
 852021-01-28T03:27:46  *** az0re <az0re!~az0re@gateway/tor-sasl/az0re> has joined #bitcoin-core-dev
 862021-01-28T03:56:42  *** btc_thc <btc_thc!annalee@kosher.marriageiguana.com> has quit IRC (Quit: Buy Bitcoin)
 872021-01-28T04:00:12  *** btc_thc <btc_thc!annalee@kosher.marriageiguana.com> has joined #bitcoin-core-dev
 882021-01-28T04:03:37  *** andrewtoth <andrewtoth!~andrewtot@gateway/tor-sasl/andrewtoth> has quit IRC (Remote host closed the connection)
 892021-01-28T04:08:12  *** sob3rkid <sob3rkid!de6ab109@222.106.177.9> has quit IRC (Quit: Ping timeout (120 seconds))
 902021-01-28T04:15:41  *** AaronvanW <AaronvanW!~AaronvanW@unaffiliated/aaronvanw> has joined #bitcoin-core-dev
 912021-01-28T04:16:28  *** justanotheruser <justanotheruser!~justanoth@unaffiliated/justanotheruser> has joined #bitcoin-core-dev
 922021-01-28T04:46:56  *** AaronvanW <AaronvanW!~AaronvanW@unaffiliated/aaronvanw> has quit IRC (Ping timeout: 240 seconds)
 932021-01-28T05:00:32  *** jb55 <jb55!~jb55@gateway/tor-sasl/jb55> has quit IRC (Remote host closed the connection)
 942021-01-28T05:01:59  *** jb55 <jb55!~jb55@gateway/tor-sasl/jb55> has joined #bitcoin-core-dev
 952021-01-28T05:09:09  *** Tokamak <Tokamak!~Tokamak@204.141.172.64> has joined #bitcoin-core-dev
 962021-01-28T05:12:13  *** Tokamak_ <Tokamak_!~Tokamak@204.141.173.217> has quit IRC (Ping timeout: 272 seconds)
 972021-01-28T05:13:23  *** rpite <rpite!~rpite@47.187.219.52> has quit IRC (Quit: rpite)
 982021-01-28T05:13:45  *** Tokamak <Tokamak!~Tokamak@204.141.172.64> has quit IRC (Ping timeout: 240 seconds)
 992021-01-28T05:16:09  *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
1002021-01-28T05:17:26  *** kpyke <kpyke!~kpyke@185.204.1.185> has quit IRC (Remote host closed the connection)
1012021-01-28T05:28:16  *** Tokamak <Tokamak!~Tokamak@204.141.172.64> has joined #bitcoin-core-dev
1022021-01-28T05:37:17  *** belcher_ <belcher_!~belcher@unaffiliated/belcher> has joined #bitcoin-core-dev
1032021-01-28T05:40:43  *** belcher <belcher!~belcher@unaffiliated/belcher> has quit IRC (Ping timeout: 272 seconds)
1042021-01-28T05:51:03  *** dermoth_ <dermoth_!~dermoth@unaffiliated/dermoth> has joined #bitcoin-core-dev
1052021-01-28T05:51:03  *** dermoth <dermoth!~dermoth@unaffiliated/dermoth> has quit IRC (Disconnected by services)
1062021-01-28T05:51:21  *** dermoth_ is now known as dermoth
1072021-01-28T05:57:25  *** oozebrood <oozebrood!~oozebrood@2603-6080-b202-d300-5cc4-8fdf-67e1-67d9.res6.spectrum.com> has joined #bitcoin-core-dev
1082021-01-28T05:57:50  <jamesob> dongcarl: thanks for the write-up! Will be revising the assumeutxo PR shortly
1092021-01-28T05:59:37  *** oozebrood <oozebrood!~oozebrood@2603-6080-b202-d300-5cc4-8fdf-67e1-67d9.res6.spectrum.com> has quit IRC (Client Quit)
1102021-01-28T06:00:10  *** oozebrood <oozebrood!~oozebrood@2603-6080-b202-d300-5cc4-8fdf-67e1-67d9.res6.spectrum.com> has joined #bitcoin-core-dev
1112021-01-28T06:25:20  *** blueingress <blueingress!~pp_of_mm@197.1.197.35.bc.googleusercontent.com> has quit IRC (Ping timeout: 256 seconds)
1122021-01-28T06:32:36  *** Tokamak <Tokamak!~Tokamak@204.141.172.64> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)
1132021-01-28T06:44:31  *** AaronvanW <AaronvanW!~AaronvanW@unaffiliated/aaronvanw> has joined #bitcoin-core-dev
1142021-01-28T06:48:35  *** ajonas_ <ajonas_!sid385278@gateway/web/irccloud.com/x-bgtpgwlcfpuidlxj> has joined #bitcoin-core-dev
1152021-01-28T06:48:52  *** contrapumpkin <contrapumpkin!~copumpkin@unaffiliated/copumpkin> has joined #bitcoin-core-dev
1162021-01-28T06:49:29  *** ajonas <ajonas!sid385278@gateway/web/irccloud.com/x-afwpuvrnyrfhxzoe> has quit IRC (Ping timeout: 256 seconds)
1172021-01-28T06:49:29  *** nckx <nckx!~nckx@tobias.gr> has quit IRC (Ping timeout: 256 seconds)
1182021-01-28T06:49:29  *** kexkey <kexkey!~kexkey@static-198-54-132-152.cust.tzulo.com> has quit IRC (Read error: Connection reset by peer)
1192021-01-28T06:49:35  *** rodarmor <rodarmor!sid210835@gateway/web/irccloud.com/x-siorvfeetzzatiub> has quit IRC (Ping timeout: 256 seconds)
1202021-01-28T06:50:10  *** nckx <nckx!~nckx@tobias.gr> has joined #bitcoin-core-dev
1212021-01-28T06:50:36  *** rodarmor <rodarmor!sid210835@gateway/web/irccloud.com/x-hmtybbdpgwdrfqgt> has joined #bitcoin-core-dev
1222021-01-28T06:50:43  *** dermoth <dermoth!~dermoth@unaffiliated/dermoth> has quit IRC (Ping timeout: 256 seconds)
1232021-01-28T06:50:43  *** copumpkin <copumpkin!~copumpkin@unaffiliated/copumpkin> has quit IRC (Ping timeout: 256 seconds)
1242021-01-28T06:51:01  *** dermoth <dermoth!~dermoth@unaffiliated/dermoth> has joined #bitcoin-core-dev
1252021-01-28T07:17:45  *** AaronvanW <AaronvanW!~AaronvanW@unaffiliated/aaronvanw> has quit IRC (Ping timeout: 240 seconds)
1262021-01-28T07:45:56  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1272021-01-28T07:45:56  <bitcoin-git> [bitcoin] fctorial opened pull request #21020: Add check for gnu sed inplace replace (master...gnu_sed) https://github.com/bitcoin/bitcoin/pull/21020
1282021-01-28T07:45:57  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1292021-01-28T07:53:06  *** rpite <rpite!~rpite@47.187.219.52> has joined #bitcoin-core-dev
1302021-01-28T07:54:00  *** rpite <rpite!~rpite@47.187.219.52> has quit IRC (Client Quit)
1312021-01-28T07:54:56  *** rpite <rpite!~rpite@47.187.219.52> has joined #bitcoin-core-dev
1322021-01-28T07:57:19  *** ghost43_ <ghost43_!~daer@gateway/tor-sasl/daer> has joined #bitcoin-core-dev
1332021-01-28T07:59:03  *** ghost43 <ghost43!~daer@gateway/tor-sasl/daer> has quit IRC (Ping timeout: 268 seconds)
1342021-01-28T08:05:42  *** TallTim <TallTim!~TallTim@184-83-248-206-dynamic.midco.net> has quit IRC (Ping timeout: 246 seconds)
1352021-01-28T08:06:52  *** TallTim <TallTim!~TallTim@184-83-248-206-dynamic.midco.net> has joined #bitcoin-core-dev
1362021-01-28T08:12:49  *** Kiminuo <Kiminuo!~mix@193.9.112.92> has joined #bitcoin-core-dev
1372021-01-28T08:31:45  *** awesome_doge <awesome_doge!awesome-do@gateway/shell/matrix.org/x-qdjwmwfycxpyunqp> has joined #bitcoin-core-dev
1382021-01-28T09:05:15  <jonasschnelli> meshcollider: I think you should also add the GUI to your push mirrors when merging stuff
1392021-01-28T09:06:14  <jonasschnelli> ^ --- ithubmerge.pushmirrors=git@github.com:bitcoin-core/gui.git
1402021-01-28T09:06:16  <jonasschnelli> +g
1412021-01-28T09:08:05  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1422021-01-28T09:08:05  <bitcoin-git> [gui] jonasschnelli merged pull request #177: Use "fusion" style on macOS Big Sur with old Qt (master...210107-style) https://github.com/bitcoin-core/gui/pull/177
1432021-01-28T09:08:06  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1442021-01-28T09:08:25  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1452021-01-28T09:08:25  <bitcoin-git> [bitcoin] jonasschnelli pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/9deba2de764f...02b01651c562
1462021-01-28T09:08:26  <bitcoin-git> bitcoin/master 4e1154d Hennadii Stepanov: qt: Use "fusion" style on macOS Big Sur with old Qt
1472021-01-28T09:08:27  <bitcoin-git> bitcoin/master 02b0165 Jonas Schnelli: Merge bitcoin-core/gui#177: Use "fusion" style on macOS Big Sur with old Q...
1482021-01-28T09:08:28  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1492021-01-28T09:12:49  *** lntvdls <lntvdls!~manrtre@37.160.148.8> has joined #bitcoin-core-dev
1502021-01-28T09:14:08  *** worc3131 <worc3131!~quassel@2a02:c7f:dcc4:6500:217b:6c7a:eac3:3be9> has quit IRC (Ping timeout: 268 seconds)
1512021-01-28T09:14:59  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1522021-01-28T09:14:59  <bitcoin-git> [gui] jonasschnelli merged pull request #72: util: Log static plugins meta data and used style (master...200812-log) https://github.com/bitcoin-core/gui/pull/72
1532021-01-28T09:15:00  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1542021-01-28T09:15:01  *** lntvdls <lntvdls!~manrtre@37.160.148.8> has quit IRC (Client Quit)
1552021-01-28T09:15:23  *** AaronvanW <AaronvanW!~AaronvanW@unaffiliated/aaronvanw> has joined #bitcoin-core-dev
1562021-01-28T09:15:44  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1572021-01-28T09:15:44  <bitcoin-git> [bitcoin] jonasschnelli pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/02b01651c562...759518354377
1582021-01-28T09:15:44  <bitcoin-git> bitcoin/master 957895c Hennadii Stepanov: util: Log static plugins meta data and style
1592021-01-28T09:15:45  <bitcoin-git> bitcoin/master 7595183 Jonas Schnelli: Merge bitcoin-core/gui#72: util: Log static plugins meta data and used sty...
1602021-01-28T09:15:46  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1612021-01-28T09:17:23  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1622021-01-28T09:17:24  <bitcoin-git> [bitcoin] jonasschnelli pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/759518354377...68692d33c6c5
1632021-01-28T09:17:24  <bitcoin-git> bitcoin/master b695148 Hennadii Stepanov: qt: Add flags to prevent a "What's This" button on Windows OS
1642021-01-28T09:17:25  <bitcoin-git> bitcoin/master ac7ccd6 Hennadii Stepanov: scripted-diff: Remove unused "What's This" button in dialogs on Windows
1652021-01-28T09:17:26  <bitcoin-git> bitcoin/master 68692d3 Jonas Schnelli: Merge bitcoin-core/gui#85: Remove unused "What's This" button in dialogs o...
1662021-01-28T09:17:27  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1672021-01-28T09:17:43  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1682021-01-28T09:17:43  <bitcoin-git> [gui] jonasschnelli merged pull request #85: Remove unused "What's This" button in dialogs on Windows OS (master...200907-whatsit) https://github.com/bitcoin-core/gui/pull/85
1692021-01-28T09:17:48  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1702021-01-28T09:31:21  *** bosch-0 <bosch-0!74cee4cc@116.206.228.204> has joined #bitcoin-core-dev
1712021-01-28T09:32:31  *** setpill <setpill!~setpill@unaffiliated/setpill> has joined #bitcoin-core-dev
1722021-01-28T09:47:21  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has joined #bitcoin-core-dev
1732021-01-28T09:48:05  *** AaronvanW <AaronvanW!~AaronvanW@unaffiliated/aaronvanw> has quit IRC (Ping timeout: 256 seconds)
1742021-01-28T09:49:21  *** bosch-0 <bosch-0!74cee4cc@116.206.228.204> has quit IRC (Ping timeout: 248 seconds)
1752021-01-28T09:58:29  *** luke-jr <luke-jr!~luke-jr@unaffiliated/luke-jr> has quit IRC (Quit: ZNC - http://znc.sourceforge.net)
1762021-01-28T09:58:53  *** luke-jr <luke-jr!~luke-jr@unaffiliated/luke-jr> has joined #bitcoin-core-dev
1772021-01-28T10:12:57  *** prayank <prayank!~andr0irc@2402:8100:206d:256b:72d2:6ce4:d87a:6e2> has joined #bitcoin-core-dev
1782021-01-28T10:16:04  <prayank> https://consensus-health.torproject.org/
1792021-01-28T10:16:29  <prayank> https://github.com/bitcoin/bitcoin/pull/20757#issuecomment-766906173
1802021-01-28T10:24:00  *** AaronvanW <AaronvanW!~AaronvanW@unaffiliated/aaronvanw> has joined #bitcoin-core-dev
1812021-01-28T10:26:38  *** vasild <vasild!~vd@gateway/tor-sasl/vasild> has quit IRC (Disconnected by services)
1822021-01-28T10:26:39  *** vasild_ <vasild_!~vd@gateway/tor-sasl/vasild> has joined #bitcoin-core-dev
1832021-01-28T10:26:39  *** vasild_ is now known as vasild
1842021-01-28T10:30:34  *** lntvdls <lntvdls!~manrtre@37.160.148.8> has joined #bitcoin-core-dev
1852021-01-28T10:30:47  *** lntvdls <lntvdls!~manrtre@37.160.148.8> has quit IRC (Client Quit)
1862021-01-28T10:47:10  <jnewbery> It's actually impossible to load the hidden review comments in #20749. Whenever I hit the "Load more..." button it instantly fails. Looking at network capture I'm getting a 400 bad request when trying to load the extra comments.
1872021-01-28T10:47:12  <gribble> https://github.com/bitcoin/bitcoin/issues/20749 | [Bundle 1/n] Prune g_chainman usage related to ::LookupBlockIndex by dongcarl · Pull Request #20749 · bitcoin/bitcoin · GitHub
1882021-01-28T10:47:24  <jnewbery> github is quickly becoming unusable to do serious review
1892021-01-28T10:52:10  *** owowo <owowo!~ovovo@2a02:20c8:4124::2e> has joined #bitcoin-core-dev
1902021-01-28T10:52:26  *** ovovo <ovovo!~ovovo@unaffiliated/ovovo> has quit IRC (Ping timeout: 240 seconds)
1912021-01-28T10:55:27  <wumpus> prayank: https://github.com/bitcoin/bitcoin/pull/20757#issuecomment-768969585  nope nope nope nope nope
1922021-01-28T10:56:16  <wumpus> jnewbery: that's been my experience as well
1932021-01-28T10:56:53  <fanquake_> wumpus: lol. yea we certainly aren't about to start a Tor fork..
1942021-01-28T10:56:56  <wumpus> jnewbery: it's starting to look like the API is the only way to use github anymore, the website adds less and less
1952021-01-28T10:57:35  <wumpus> (this is really bad for a mostly web based product)
1962021-01-28T10:57:58  <wumpus> fanquake_: right eh
1972021-01-28T10:58:42  <fanquake_> jnewbery: I reported a similar issue to GitHub on the 30th of October last year. It got a reply a week later, which was basically "can't reproduce"
1982021-01-28T11:01:23  <fanquake_> Can anyone else confirm that hitting load more in #20749 doesn't work ?
1992021-01-28T11:01:25  <gribble> https://github.com/bitcoin/bitcoin/issues/20749 | [Bundle 1/n] Prune g_chainman usage related to ::LookupBlockIndex by dongcarl · Pull Request #20749 · bitcoin/bitcoin · GitHub
2002021-01-28T11:01:32  *** dgenr8 <dgenr8!~dgenr8@unaffiliated/dgenr8> has quit IRC (Ping timeout: 260 seconds)
2012021-01-28T11:03:04  <wumpus> prayank: to be clear i would be happy if someone picked up Dandelion again, and was able to resolve the DoS issues, it has a limited an realistic enough scope, transaction broadcast
2022021-01-28T11:04:40  <wumpus> fanquake_: same now
2032021-01-28T11:04:49  <jnewbery> jonatack: thanks for the gh cli tip. Do you know if there's any way to also load the inline code review comments?
2042021-01-28T11:04:51  <wumpus> i was able to load them yesterday
2052021-01-28T11:05:01  <fanquake_> wumpus: great. Just wanted to triple check before posting heh
2062021-01-28T11:05:10  <jnewbery> I'm just seeing the top level PR review comments
2072021-01-28T11:05:21  <fanquake_> https://imgur.com/a/bOerpMG
2082021-01-28T11:06:01  <fanquake_> https://0bin.net/paste/bEEMvISZ#hKXweSD5iGIyBFzjBvgF+EfugKkx9QM8ZARoHzUGh4M
2092021-01-28T11:06:06  *** belcher_ is now known as belcher
2102021-01-28T11:06:47  <jnewbery> fanquake_: yep - that's exactly my experience
2112021-01-28T11:07:36  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2122021-01-28T11:07:36  <bitcoin-git> [bitcoin] MarcoFalke reopened pull request #21012: ci: Fuzz with integer sanitizer (master...2101-fuzzIntSan) https://github.com/bitcoin/bitcoin/pull/21012
2132021-01-28T11:07:37  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2142021-01-28T11:08:16  <prayank> wumpus: I was trying to experiment with Dandelion and had few issues. Will try again this week and write about all the issues. One basic question was answered by 0xb10c on SE:  https://bitcoin.stackexchange.com/questions/99602/dumpmempool-and-loadmempool-in-src-validation-cpp
2152021-01-28T11:08:21  *** dgenr8 <dgenr8!~dgenr8@unaffiliated/dgenr8> has joined #bitcoin-core-dev
2162021-01-28T11:13:40  <wumpus> it's possible to access (https://docs.github.com/en/rest/reference/pulls#list-review-comments-in-a-repository) and even create (https://docs.github.com/en/rest/reference/pulls#create-a-review-for-a-pull-request) inline comments through the github API, the line numbers and such are available, but i checked the cli tool's docs and i can't find anything related to that
2172021-01-28T11:13:46  *** darosior <darosior!~darosior@194.36.189.246> has quit IRC (Read error: Connection reset by peer)
2182021-01-28T11:14:06  *** darosior <darosior!~darosior@194.36.189.246> has joined #bitcoin-core-dev
2192021-01-28T11:15:06  <wumpus> e.g. https://cli.github.com/manual/gh_pr_review   has nothing about specific places in the code, but might be missing someting
2202021-01-28T11:16:41  <wumpus> https://github.com/cli/cli/issues/359 "Fine Grained Code Review Support"
2212021-01-28T11:17:10  *** rpite <rpite!~rpite@47.187.219.52> has quit IRC (Quit: rpite)
2222021-01-28T11:18:33  *** Griffin72Vanderv <Griffin72Vanderv!~Griffin72@static.57.1.216.95.clients.your-server.de> has joined #bitcoin-core-dev
2232021-01-28T11:21:03  <wumpus> so: currently no—it seems to less of an implementation issue but more of a matter of failing to agree on what would be a usable command line interface to this
2242021-01-28T11:25:28  <wumpus> prayank: i keep being surprised how actually-helpful the bitcoin stackexchange is
2252021-01-28T11:27:41  <prayank> wumpus: Not sure if I should comment on this but it's been helpful sometimes and for few things I had to ask questions on r/bitcoin and other places.
2262021-01-28T11:28:42  <michaelfolkson> prayank: I think you forget about the questions you get answered and just focus on those that don't. Never going to get close to 100 percent success rate
2272021-01-28T11:29:13  <prayank> lol maybe
2282021-01-28T11:29:40  <michaelfolkson> Given it is completely voluntary it is very impressive the people that dedicate time to it
2292021-01-28T11:30:05  *** Griffin72Vanderv <Griffin72Vanderv!~Griffin72@static.57.1.216.95.clients.your-server.de> has quit IRC (Ping timeout: 256 seconds)
2302021-01-28T11:30:49  <wumpus> prayank: then i see a reddit thread and am shocked how full of distractive trolls and nonsense it is, though it definitely has it's good threads too, but the stack exchange is just so serious and people seem to really take their time to type explanations and such that are on-point
2312021-01-28T11:32:30  <wumpus> michaelfolkson: exactly
2322021-01-28T11:33:01  <prayank> wumpus: Agree both have their own positives. Maybe I am just overthinking about few issues and hate the options available to "close" questions on Stackexchange.
2332021-01-28T11:33:58  <michaelfolkson> If you didn't have the moderator features you'd get the Reddit style "full of distractive trolls and nonsense"
2342021-01-28T11:34:37  <michaelfolkson> Moderation is never perfect but it is generally pretty high quality imo
2352021-01-28T11:34:49  <wumpus> michaelfolkson: it's kind of defined by that, yes
2362021-01-28T11:37:36  <wumpus> prayank: anyhow yeah if you write down what the specific issues are (and what you're trying to do) others might be able to help you out, fwiw there are a fair bit of dandelion-specific threads on the stack exchange too
2372021-01-28T11:38:08  <wumpus> you're far from the only person looking into this
2382021-01-28T11:39:03  <wumpus> https://bitcoin.stackexchange.com/questions/81503/what-is-the-tradeoff-between-privacy-and-implementation-complexity-of-dandelion must be the most famous one
2392021-01-28T11:41:51  <michaelfolkson> While you're here prayank, you just need to ACK the head commit, not ACK each individual commit
2402021-01-28T11:42:00  <michaelfolkson> https://jonatack.github.io/articles/how-to-review-pull-requests-in-bitcoin-core
2412021-01-28T11:42:23  <prayank> wumpus: I found only one thing that explains the risks involved in Dandelion on SE: https://bitcoin.stackexchange.com/a/81504/ My issues are mainly related to implementation of the this commit: https://github.com/dandelion-org/bitcoin/commit/d043e36bbe9249a78cf751c80b8d876b7d9f07ea in present code's master branch because lot of things have changed since 2018
2422021-01-28T11:42:59  <michaelfolkson> Referring to this btw https://github.com/bitcoin/bitcoin/pull/20757#issuecomment-768192425
2432021-01-28T11:43:02  <wumpus> oh yes, rebasing the work on recent source code is going to be a challenge in itself
2442021-01-28T11:44:09  *** prayank <prayank!~andr0irc@2402:8100:206d:256b:72d2:6ce4:d87a:6e2> has quit IRC (Quit: AndroIRC - Android IRC Client ( http://www.androirc.com ))
2452021-01-28T11:44:29  *** prayank <prayank!~andr0irc@2402:8100:206d:256b:72d2:6ce4:d87a:6e2> has joined #bitcoin-core-dev
2462021-01-28T11:45:19  <wumpus> i think to do that you need to first understand every change, then see how it applies to master, git's source-context-based suggestions quickly become completely useless
2472021-01-28T11:45:42  <prayank> michaelfolkson: Thanks. I had seen someone doing ACKs on individual commits so thought we can do it.
2482021-01-28T11:46:29  <michaelfolkson> I guess if you only review one commit (or a subset of commits) then you could refer to them. But if you review all of them just ACK that head commit
2492021-01-28T11:46:35  <wumpus> you *can* ACK invidual commits, but that's generally if you have a special reason to
2502021-01-28T11:46:37  <wumpus> right
2512021-01-28T11:47:24  <prayank> wumpus: Yes. Trying to understand every change and there are lot of changes.
2522021-01-28T11:47:54  <wumpus> prayank: maybe as first pass, try to sort out which are the most important ones :)
2532021-01-28T11:48:28  *** prayank <prayank!~andr0irc@2402:8100:206d:256b:72d2:6ce4:d87a:6e2> has quit IRC (Client Quit)
2542021-01-28T11:48:56  <wumpus> there's alwasys ancillary things like refactors that were needed at the time to bring things into posistion which might no longer be needed, or needed completely differently
2552021-01-28T11:48:58  *** prayank <prayank!~andr0irc@2402:8100:206d:256b:72d2:6ce4:d87a:6e2> has joined #bitcoin-core-dev
2562021-01-28T11:49:22  <prayank> Thanks. Will try and share the progress in few days.
2572021-01-28T11:49:28  <wumpus> ok!
2582021-01-28T11:50:19  *** prayank <prayank!~andr0irc@2402:8100:206d:256b:72d2:6ce4:d87a:6e2> has quit IRC (Remote host closed the connection)
2592021-01-28T12:27:06  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2602021-01-28T12:27:07  <bitcoin-git> [bitcoin] chrismaddern opened pull request #21021: Seems like time... (master...patch-1) https://github.com/bitcoin/bitcoin/pull/21021
2612021-01-28T12:27:07  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2622021-01-28T12:34:23  *** dviola <dviola!~diego@unaffiliated/dviola> has quit IRC (Quit: WeeChat 3.0)
2632021-01-28T12:39:21  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2642021-01-28T12:39:22  <bitcoin-git> [bitcoin] fanquake closed pull request #21021: Seems like time... (master...patch-1) https://github.com/bitcoin/bitcoin/pull/21021
2652021-01-28T12:39:22  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2662021-01-28T12:39:34  *** rpite <rpite!~rpite@47.187.219.52> has joined #bitcoin-core-dev
2672021-01-28T12:43:46  *** nejon <nejon!sid38993@gateway/web/irccloud.com/x-qfvqhbthsevgepbp> has joined #bitcoin-core-dev
2682021-01-28T12:47:02  *** bosch-0 <bosch-0!74cee4f4@116.206.228.244> has joined #bitcoin-core-dev
2692021-01-28T12:52:26  *** rpite <rpite!~rpite@47.187.219.52> has quit IRC (Quit: rpite)
2702021-01-28T12:53:41  *** rpite <rpite!~rpite@47.187.219.52> has joined #bitcoin-core-dev
2712021-01-28T12:58:05  *** Guyver2 <Guyver2!Guyver@guyver2.xs4all.nl> has joined #bitcoin-core-dev
2722021-01-28T12:58:34  *** jespada <jespada!~jespada@90.254.242.138> has quit IRC (Ping timeout: 265 seconds)
2732021-01-28T13:02:11  *** jespada <jespada!~jespada@90.254.242.138> has joined #bitcoin-core-dev
2742021-01-28T13:18:03  *** setpill <setpill!~setpill@unaffiliated/setpill> has quit IRC (Quit: o/)
2752021-01-28T13:33:59  *** Kiminuo <Kiminuo!~mix@193.9.112.92> has quit IRC (Read error: Connection reset by peer)
2762021-01-28T13:34:51  *** livestradamus <livestradamus!~quassel@unaffiliated/livestradamus> has quit IRC (Quit: I'm out.)
2772021-01-28T13:35:16  *** livestradamus <livestradamus!~quassel@unaffiliated/livestradamus> has joined #bitcoin-core-dev
2782021-01-28T13:40:14  *** justanotheruser <justanotheruser!~justanoth@unaffiliated/justanotheruser> has quit IRC (Ping timeout: 264 seconds)
2792021-01-28T13:42:56  *** Guyver2_ <Guyver2_!Guyver@guyver2.xs4all.nl> has joined #bitcoin-core-dev
2802021-01-28T13:44:49  *** darosior4 <darosior4!~darosior@194.36.189.246> has joined #bitcoin-core-dev
2812021-01-28T13:45:55  *** darosior <darosior!~darosior@194.36.189.246> has quit IRC (Read error: Connection reset by peer)
2822021-01-28T13:46:05  *** Guyver2 <Guyver2!Guyver@guyver2.xs4all.nl> has quit IRC (Ping timeout: 256 seconds)
2832021-01-28T13:54:09  *** jonatack <jonatack!~jon@88.124.242.136> has joined #bitcoin-core-dev
2842021-01-28T13:54:42  *** jonatack <jonatack!~jon@88.124.242.136> has quit IRC (Client Quit)
2852021-01-28T14:10:14  *** Guyver2_ <Guyver2_!Guyver@guyver2.xs4all.nl> has quit IRC (Ping timeout: 264 seconds)
2862021-01-28T14:10:16  *** Guyver2__ <Guyver2__!Guyver@guyver2.xs4all.nl> has joined #bitcoin-core-dev
2872021-01-28T14:14:46  *** luke-jr <luke-jr!~luke-jr@unaffiliated/luke-jr> has quit IRC (Excess Flood)
2882021-01-28T14:15:34  *** setpill <setpill!~setpill@unaffiliated/setpill> has joined #bitcoin-core-dev
2892021-01-28T14:16:05  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2902021-01-28T14:16:06  <bitcoin-git> [bitcoin] MarcoFalke pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/68692d33c6c5...4d5eaf7a90bc
2912021-01-28T14:16:06  <bitcoin-git> bitcoin/master fa99e33 MarcoFalke: fuzz: move-only FillNode implementation to cpp file
2922021-01-28T14:16:08  <bitcoin-git> bitcoin/master fad3d76 MarcoFalke: fuzz: Avoid initializing version to less than MIN_PEER_PROTO_VERSION
2932021-01-28T14:16:08  <bitcoin-git> bitcoin/master 4d5eaf7 MarcoFalke: Merge #20995: fuzz: Avoid initializing version to less than MIN_PEER_PROTO...
2942021-01-28T14:16:09  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2952021-01-28T14:16:25  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2962021-01-28T14:16:25  <bitcoin-git> [bitcoin] MarcoFalke merged pull request #20995: fuzz: Avoid initializing version to less than MIN_PEER_PROTO_VERSION (master...2101-fuzzVersion0) https://github.com/bitcoin/bitcoin/pull/20995
2972021-01-28T14:16:26  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2982021-01-28T14:16:43  *** luke-jr <luke-jr!~luke-jr@unaffiliated/luke-jr> has joined #bitcoin-core-dev
2992021-01-28T14:25:10  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
3002021-01-28T14:25:10  <bitcoin-git> [bitcoin] fanquake opened pull request #21022: [Not for merge] pthread sanity check (master...broken_shared_mutex_sanity_check) https://github.com/bitcoin/bitcoin/pull/21022
3012021-01-28T14:25:11  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3022021-01-28T14:27:12  *** bosch-0 <bosch-0!74cee4f4@116.206.228.244> has quit IRC (Quit: Ping timeout (120 seconds))
3032021-01-28T14:28:18  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
3042021-01-28T14:28:18  <bitcoin-git> [bitcoin] MarcoFalke opened pull request #21023: fuzz: Disable shuffle when merge=1 (master...2101-fuzzMerge) https://github.com/bitcoin/bitcoin/pull/21023
3052021-01-28T14:28:19  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3062021-01-28T14:42:25  *** jackk_ <jackk_!~jackk@205.178.111.134> has joined #bitcoin-core-dev
3072021-01-28T14:43:45  *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Quit: = "")
3082021-01-28T14:53:18  *** gribble <gribble!~gribble@unaffiliated/nanotube/bot/gribble> has quit IRC (Remote host closed the connection)
3092021-01-28T14:58:30  *** gribble <gribble!~gribble@unaffiliated/nanotube/bot/gribble> has joined #bitcoin-core-dev
3102021-01-28T15:06:37  *** queip <queip!~queip@unaffiliated/rezurus> has quit IRC (Ping timeout: 256 seconds)
3112021-01-28T15:12:31  *** jackk_ <jackk_!~jackk@205.178.111.134> has quit IRC (Quit: Going offline, see ya! (www.adiirc.com))
3122021-01-28T15:16:44  *** justanotheruser <justanotheruser!~justanoth@unaffiliated/justanotheruser> has joined #bitcoin-core-dev
3132021-01-28T15:17:13  *** cltrbreak_MAD2 <cltrbreak_MAD2!~ctrlbreak@159.2.165.130> has joined #bitcoin-core-dev
3142021-01-28T15:19:28  *** queip <queip!~queip@unaffiliated/rezurus> has joined #bitcoin-core-dev
3152021-01-28T15:20:26  *** ctrlbreak_MAD <ctrlbreak_MAD!~ctrlbreak@159.2.165.130> has quit IRC (Ping timeout: 264 seconds)
3162021-01-28T15:46:27  *** darosior4 is now known as darosior
3172021-01-28T16:02:34  *** jonatack <jonatack!~jon@88.124.242.136> has joined #bitcoin-core-dev
3182021-01-28T16:07:11  *** jonatack <jonatack!~jon@88.124.242.136> has quit IRC (Ping timeout: 246 seconds)
3192021-01-28T16:07:36  *** jonatack <jonatack!jon@gateway/vpn/airvpn/jonatack> has joined #bitcoin-core-dev
3202021-01-28T16:10:32  *** jonatack <jonatack!jon@gateway/vpn/airvpn/jonatack> has quit IRC (Client Quit)
3212021-01-28T16:12:39  *** GankMove <GankMove!~GankMove@dsl-lprbng11-54f88d-13.dhcp.inet.fi> has joined #bitcoin-core-dev
3222021-01-28T16:13:56  *** jonatack <jonatack!~jon@88.124.242.136> has joined #bitcoin-core-dev
3232021-01-28T16:19:26  *** jonatack <jonatack!~jon@88.124.242.136> has quit IRC (Ping timeout: 240 seconds)
3242021-01-28T16:19:53  *** jonatack <jonatack!jon@gateway/vpn/airvpn/jonatack> has joined #bitcoin-core-dev
3252021-01-28T16:26:36  *** GankMove <GankMove!~GankMove@unaffiliated/gankmove> has quit IRC (Quit: GankMove)
3262021-01-28T16:27:58  *** GankMove <GankMove!~GankMove@unaffiliated/gankmove> has joined #bitcoin-core-dev
3272021-01-28T16:36:00  *** Guyver2__ is now known as Guyver2
3282021-01-28T16:37:41  *** fanquake_ <fanquake_!sid369002@gateway/web/irccloud.com/x-hooxevzeyzepxlxz> has quit IRC (Read error: Connection reset by peer)
3292021-01-28T16:38:03  *** fanquake_ <fanquake_!sid369002@gateway/web/irccloud.com/x-pllzngnlrrqggqyd> has joined #bitcoin-core-dev
3302021-01-28T16:44:57  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
3312021-01-28T16:44:57  <bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/4d5eaf7a90bc...6ba2ffd28b6b
3322021-01-28T16:44:58  <bitcoin-git> bitcoin/master 624091b setpill: Fix docker args conditional
3332021-01-28T16:44:58  <bitcoin-git> bitcoin/master 6ba2ffd MarcoFalke: Merge #21004: contrib: Fix docker args conditional in gitian-build
3342021-01-28T16:45:00  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3352021-01-28T16:45:17  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
3362021-01-28T16:45:17  <bitcoin-git> [bitcoin] MarcoFalke merged pull request #21004: contrib: Fix docker args conditional in gitian-build (master...improve-gitian-build-py) https://github.com/bitcoin/bitcoin/pull/21004
3372021-01-28T16:45:18  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3382021-01-28T16:48:13  <MarcoFalke> #proposedmeetingtopic 0.20.2
3392021-01-28T16:49:32  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
3402021-01-28T16:49:32  <bitcoin-git> [bitcoin] MarcoFalke opened pull request #21024: appveyor: image: Previous Visual Studio 2019 (master...2101-ciAppveyorPrev) https://github.com/bitcoin/bitcoin/pull/21024
3412021-01-28T16:49:33  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3422021-01-28T16:55:39  <dongcarl> Anyone experimented with Radicle yet and have a bitcoin-core radicle ID?
3432021-01-28T17:04:01  <wumpus> dongcarl: yes, let me see
3442021-01-28T17:04:33  <wumpus> dongcarl: rad:git:hwd1yreyfmyg5my7kskrsc5r33h5jr9anra9635hpncfs9f1wsk1eaf8f9w
3452021-01-28T17:04:45  <wumpus> let me start my node too
3462021-01-28T17:05:52  <dongcarl> I see it!
3472021-01-28T17:08:33  *** rpite <rpite!~rpite@47.187.219.52> has quit IRC (Quit: rpite)
3482021-01-28T17:08:55  *** rpite <rpite!~rpite@47.187.219.52> has joined #bitcoin-core-dev
3492021-01-28T17:09:32  <dongcarl> Workflow seems quite different... I don't even see issues or PRs...
3502021-01-28T17:13:18  <vasild> All bugs have been fixed and Bitcoin Core has no issues!
3512021-01-28T17:13:55  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
3522021-01-28T17:13:55  <bitcoin-git> [bitcoin] MarcoFalke closed pull request #21024: appveyor: image: Previous Visual Studio 2019 (master...2101-ciAppveyorPrev) https://github.com/bitcoin/bitcoin/pull/21024
3532021-01-28T17:13:56  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3542021-01-28T17:14:49  <MarcoFalke> dongcarl: I think we still need some kind of centralized entity
3552021-01-28T17:15:20  <MarcoFalke> I can't imagine our workflow when half the devs don't see half the pull requests
3562021-01-28T17:15:47  <MarcoFalke> (You can only see the ones you "follow", according to the docs, haven't tried myself)
3572021-01-28T17:17:15  <dongcarl> Right, that is the current behaviour but I can see how they can introduce "remote rebroadcasting" to solve this. Surely other projects will want the same thing.
3582021-01-28T17:18:56  <luke-jr> MarcoFalke: at least half the devs already ignore half the PRs I suspect :P
3592021-01-28T17:19:11  <MarcoFalke> Also, radicle doesn't work with the normal browser
3602021-01-28T17:19:16  <luke-jr> but yes, it's probably important new devs get visibility
3612021-01-28T17:19:19  <MarcoFalke> you need to download their own software to browse
3622021-01-28T17:20:26  <MarcoFalke> luke-jr: Most new devs remove the word "experimental", so it would be good if no one could see those anymore. Though, rarely someone has an actual bug fix.
3632021-01-28T17:20:30  <MarcoFalke> Same goes for issues
3642021-01-28T17:21:35  <wumpus> dongcarl: the mirror should update every 15 minutes
3652021-01-28T17:22:09  <wumpus> dongcarl: issues and PRs haven't been implemented in the frontend yet, unfortunately, this kind of limits its usefulness at the moment
3662021-01-28T17:22:16  <dongcarl> Oh of course right now it's full of problems and is in alpha, I'm just thinking about a list of things still missing from radicle that perhaps can be advocated for.
3672021-01-28T17:22:44  <luke-jr> MarcoFalke: :/
3682021-01-28T17:25:44  *** Tokamak <Tokamak!~Tokamak@204.141.173.217> has joined #bitcoin-core-dev
3692021-01-28T17:48:55  *** contrapumpkin is now known as copumpkin
3702021-01-28T17:52:15  *** copumpkin <copumpkin!~copumpkin@unaffiliated/copumpkin> has quit IRC (Quit: Bye!)
3712021-01-28T17:52:54  *** copumpkin <copumpkin!~copumpkin@unaffiliated/copumpkin> has joined #bitcoin-core-dev
3722021-01-28T17:53:04  *** dviola <dviola!~diego@unaffiliated/dviola> has joined #bitcoin-core-dev
3732021-01-28T17:55:03  *** setpill <setpill!~setpill@unaffiliated/setpill> has quit IRC (Quit: o/)
3742021-01-28T18:10:35  *** justanotheruser <justanotheruser!~justanoth@unaffiliated/justanotheruser> has quit IRC (Ping timeout: 272 seconds)
3752021-01-28T18:12:45  *** Talkless <Talkless!~Talkless@mail.dargis.net> has joined #bitcoin-core-dev
3762021-01-28T18:14:47  *** promag_ <promag_!~promag@188.250.84.129> has joined #bitcoin-core-dev
3772021-01-28T18:14:47  *** promag <promag!~promag@188.250.84.129> has quit IRC (Read error: Connection reset by peer)
3782021-01-28T18:24:04  *** jessepos_ <jessepos_!~jp@2601:645:200:162f:3c9a:cd45:284b:ebea> has quit IRC (Quit: Textual IRC Client: www.textualapp.com)
3792021-01-28T18:24:27  *** jesseposner <jesseposner!~jp@2601:645:200:162f:3c9a:cd45:284b:ebea> has joined #bitcoin-core-dev
3802021-01-28T18:25:47  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
3812021-01-28T18:25:47  <bitcoin-git> [bitcoin] laanwj pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/6ba2ffd28b6b...80e16cadd56c
3822021-01-28T18:25:48  <bitcoin-git> bitcoin/master faf8356 MarcoFalke: rpc: [refactor] Use concise C++11 code in CRPCConvertTable constructor
3832021-01-28T18:25:48  <bitcoin-git> bitcoin/master fa92912 MarcoFalke: rpc: Use RPCHelpMan for check-rpc-mappings linter
3842021-01-28T18:25:49  <bitcoin-git> bitcoin/master fa04f9b MarcoFalke: rpc: Remove duplicate name and argNames from CRPCCommand
3852021-01-28T18:25:50  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3862021-01-28T18:26:07  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
3872021-01-28T18:26:07  <bitcoin-git> [bitcoin] laanwj merged pull request #20012: rpc: Remove duplicate name and argNames from CRPCCommand (master...2009-rpcCheckMapping) https://github.com/bitcoin/bitcoin/pull/20012
3882021-01-28T18:26:08  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3892021-01-28T18:31:26  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
3902021-01-28T18:31:26  <bitcoin-git> [bitcoin] dongcarl opened pull request #21025: validation: Guard the active_chainstate with cs_main (master...2021-01-chainman-activechainstate-locking) https://github.com/bitcoin/bitcoin/pull/21025
3912021-01-28T18:31:27  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3922021-01-28T18:38:02  *** luke-jr <luke-jr!~luke-jr@unaffiliated/luke-jr> has quit IRC (Ping timeout: 256 seconds)
3932021-01-28T18:38:28  *** luke-jr <luke-jr!~luke-jr@unaffiliated/luke-jr> has joined #bitcoin-core-dev
3942021-01-28T18:46:34  *** rpite <rpite!~rpite@47.187.219.52> has quit IRC (Ping timeout: 265 seconds)
3952021-01-28T19:00:39  <wumpus> #startmeeting
3962021-01-28T19:00:49  <jonasschnelli> hi
3972021-01-28T19:00:52  <sipa> hi
3982021-01-28T19:00:58  <warren> hi
3992021-01-28T19:01:01  <dongcarl> hi
4002021-01-28T19:01:01  <achow101> hi
4012021-01-28T19:01:02  <hebasto> h
4022021-01-28T19:01:02  <wumpus> #bitcoin-core-dev Meeting: achow101 aj amiti ariard bluematt cfields Chris_Stewart_5 digi_james dongcarl elichai2 emilengler fanquake fjahr gleb glozow gmaxwell gwillen hebasto instagibbs jamesob jb55 jeremyrubin jl2012 jnewbery jonasschnelli jonatack jtimon kallewoof kanzure kvaciral lightlike luke-jr maaku marcofalke meshcollider michagogo moneyball morcos nehan NicolasDorier paveljanik
4032021-01-28T19:01:04  <wumpus> petertodd phantomcircuit promag provoostenator ryanofsky sdaftuar sipa vasild wumpus
4042021-01-28T19:01:24  <warren> I have a short suggested topic, can mention later when there's an opening.
4052021-01-28T19:01:31  <ariard> hi
4062021-01-28T19:01:32  <fjahr> hi
4072021-01-28T19:01:37  <sipa> i like how wumpus doesn't even forget to call wumpus to the meeting
4082021-01-28T19:01:39  <wumpus> no proposed meeting topics in http://gnusha.org/bitcoin-core-dev/proposedmeetingtopics.txt
4092021-01-28T19:01:54  <michaelfolkson> hi
4102021-01-28T19:01:57  <wumpus> sipa: hah!
4112021-01-28T19:02:01  <jonasschnelli> heh
4122021-01-28T19:02:12  <jnewbery> hi
4132021-01-28T19:02:52  <wumpus> warren: do let us know so that we can announce it?
4142021-01-28T19:03:18  *** sdaftuar <sdaftuar!~sdaftuar@gateway/tor-sasl/sdaftuar> has quit IRC (Remote host closed the connection)
4152021-01-28T19:03:20  <wumpus> #topic High priority for review
4162021-01-28T19:03:45  *** sdaftuar <sdaftuar!~sdaftuar@gateway/tor-sasl/sdaftuar> has joined #bitcoin-core-dev
4172021-01-28T19:03:48  <ariard> may we get #19160 as a priority (multiprocess) ?
4182021-01-28T19:03:50  <gribble> https://github.com/bitcoin/bitcoin/issues/19160 | multiprocess: Add basic spawn and IPC support by ryanofsky · Pull Request #19160 · bitcoin/bitcoin · GitHub
4192021-01-28T19:03:50  <wumpus> https://github.com/bitcoin/bitcoin/projects/8   11 blockers, 1 bugfix, 2 chasing concept ACK
4202021-01-28T19:03:58  <emzy> hi
4212021-01-28T19:04:14  <ariard> it sounds finally to attract reviewers :)
4222021-01-28T19:04:21  <warren> Suggested Topic: A bit concerning to me is Fedora is again approaching possible packaging and distribution of Bitcoin Core. While the openssl-based risk is now eliminated, I now intend to package Guix for Fedora and use that to make binary identical builds. I think I can handle the Fedora specific parts of this. But Guix for Bitcoin Core releases is still missing a few parts of what Gitian used to do?
4232021-01-28T19:04:26  <aj> hi-ish (laggy)
4242021-01-28T19:04:50  <jonatack> hi
4252021-01-28T19:04:59  <wumpus> ariard: added
4262021-01-28T19:05:05  <ariard> thanks!
4272021-01-28T19:05:28  <wumpus> 12 blockers now! anything to add/remove or that's ready for merge?
4282021-01-28T19:05:42  <michaelfolkson> Your #19820 is still chasing Concept ACK ariard. Keep it there or remove?
4292021-01-28T19:05:43  <gribble> https://github.com/bitcoin/bitcoin/issues/19820 | Transactions propagation design goals · Issue #19820 · bitcoin/bitcoin · GitHub
4302021-01-28T19:06:08  <ariard> michaelfolkson: it's not really consuming review time...
4312021-01-28T19:06:13  <jonatack> wumpus: can rm #20391
4322021-01-28T19:06:16  <gribble> https://github.com/bitcoin/bitcoin/issues/20391 | wallet: introduce setfeerate (an improved settxfee, in sat/vB) by jonatack · Pull Request #20391 · bitcoin/bitcoin · GitHub
4332021-01-28T19:06:34  <wumpus> jonatack: done
4342021-01-28T19:06:48  <jonatack> thanks (being on the blockers list doesn't attract review)
4352021-01-28T19:07:11  <michaelfolkson> ariard: Ok. I hope to drive it forward a tiny bit at some point.
4362021-01-28T19:07:29  <ariard> michaelfolkson: I'll try to transfer in the wiki soon and trakc all related works in this area
4372021-01-28T19:07:31  <wumpus> jonatack: it helps for some PRs, though not all for sure
4382021-01-28T19:08:37  <michaelfolkson> ariard: I think everyone would give it a Concept ACK but needs more than that ;)
4392021-01-28T19:09:07  <wumpus> I didn't look into that one myself because honestly not sure about the logistics of adding another global fee setting command, it seems like something ideally set per transaction
4402021-01-28T19:09:57  <jonatack> wumpus: it's part of a larger roadmap to migrate to sat/vB
4412021-01-28T19:10:53  <jonatack> we can't deprecate the feeRate options in BTC/kB as long as settxfee and estimatesmartfee are only in BTC/kB
4422021-01-28T19:11:00  <wumpus> jonatack: yes it's not specific to your PR, I generally agree with that roadmap, just something I've had a differing opinion about for a long time
4432021-01-28T19:11:01  <jonatack> but that's ok, no worries
4442021-01-28T19:11:50  <wumpus> anything else to discuss in regard to high prio?
4452021-01-28T19:11:52  <aj> re 19160, it needs rebase? also is there any roadmap for libmultiprocessing, it's out of tree, but seems pretty bitcoin specific? has it really been reviewed much?
4462021-01-28T19:12:42  <dongcarl>  #21025 is potentially a pre-req for safely doing 2 other high-prios, but happy to table that till later
4472021-01-28T19:12:43  <gribble> https://github.com/bitcoin/bitcoin/issues/21025 | validation: Guard the active_chainstate with cs_main by dongcarl · Pull Request #21025 · bitcoin/bitcoin · GitHub
4482021-01-28T19:12:52  <ariard> aj: it needs rebase since 12 min...
4492021-01-28T19:12:55  <jonatack> wumpus: the idea is to make hidden/soft-deprecate settxfee and estimatesmartfee in favor of new setfeerate and estimatefeerate rpcs
4502021-01-28T19:13:03  <wumpus> jonatack: also, introducing a new command with a new name to introduce a new unit , might be a bit overkill
4512021-01-28T19:13:06  <ariard> but yeah libmultiprocess should be moved under bitcoin-core
4522021-01-28T19:13:09  <wumpus> jonatack: okay
4532021-01-28T19:13:10  <ariard> at least
4542021-01-28T19:13:33  <wumpus> jonatack: I do agree the new names are better
4552021-01-28T19:13:36  <jonatack> wumpus: i don't see a choice, but TBH i'm happy to close and move on to other things
4562021-01-28T19:13:45  <jonatack> leave the migration to someone else
4572021-01-28T19:13:52  <ariard> and yes I had a look on libmultiprocess but ofc needs more review
4582021-01-28T19:14:01  <jonatack> we need review more than PRs to review
4592021-01-28T19:14:14  <wumpus> jonatack: well don't let it up to me, it's just my opinion, I'm not going to get in the way
4602021-01-28T19:14:47  <wumpus> ariard: if it needs more review, adding it to high prio for review makes sense :)
4612021-01-28T19:15:19  <wumpus> jonatack: what does achow101 think about it?
4622021-01-28T19:15:23  *** Eagle[TM] <Eagle[TM]!~EagleTM@unaffiliated/eagletm> has quit IRC (Ping timeout: 256 seconds)
4632021-01-28T19:15:30  <sipa> jonatack: i think it's really the only convenient option to get an RPC with sat/vB units, so seems fine to me
4642021-01-28T19:15:40  <jonatack> achow101 wrote that they should all be in sat/vB
4652021-01-28T19:16:25  <wumpus> ok ,good
4662021-01-28T19:16:32  <jonatack> sipa: ok. anyway, no rush. we have lots to do.
4672021-01-28T19:16:38  <sipa> this is true
4682021-01-28T19:16:49  <wumpus> absolutely
4692021-01-28T19:16:59  <wumpus> not many topics for this meeting though, let's go to warren 's
4702021-01-28T19:17:07  <luke-jr> jonatack: I wouldn't close it tho
4712021-01-28T19:17:14  <wumpus> #topic Fedora packaging (warren)
4722021-01-28T19:17:21  <warren> A bit concerning to me is Fedora is again approaching possible packaging and distribution of Bitcoin Core. While the openssl-based risk is now eliminated, I now intend to package Guix for Fedora and use that to make binary identical builds. I think I can handle the Fedora specific parts of this. But Guix for Bitcoin Core releases is still missing a few parts of what Gitian used to do?
4732021-01-28T19:17:25  <warren> I will not be able to stop them from distributing not-deterministic Bitcoin Core for much longer.
4742021-01-28T19:17:30  <warren> Maybe TODO List?
4752021-01-28T19:17:30  <warren> 1) Bitcoin Core switch to Guix for release builds (when possible ... Guix is missing some of the architectures?) I believe we want a replacement for what Gitian used to do including exporting a particular tag from git, naming and versioning the output tarballs, anything else?
4762021-01-28T19:17:37  <warren> 2) Guix to additionally output .deb and .rpm packages that contain the same binary as the tarball.
4772021-01-28T19:17:37  <warren> 3) Debian Unstable now ships Guix. Warren is working on figuring out a way to package Guix so it would be acceptable for Fedora where it would be capable of building the above for Fedora/CentOS direct distribution.
4782021-01-28T19:18:18  <luke-jr> warren: distro packages *shouldn't* be identical to release binaries, but deterministic certainly does seem desirable
4792021-01-28T19:18:34  <luke-jr> warren: the problems with distro pkgs were discussed at the last meeting regarding Debian (which has chosen to ignore them)
4802021-01-28T19:18:35  <dongcarl> Status update on Guix from me: all architectures are packaged, codesigning is the main remaining task
4812021-01-28T19:18:52  <warren> luke-jr: Fedora can't do deterministic with its own build system anytime soon, using Guix there and here is the achievable goal in the short-term.
4822021-01-28T19:18:59  <achow101> dongcarl: codesigning is easy now
4832021-01-28T19:19:03  <warren> dongcarl: *all*? amazing!
4842021-01-28T19:19:11  <luke-jr> warren: sure, that's fine - but they should dynamic link to most libraries
4852021-01-28T19:19:19  <achow101> codesigning is also unreltaed to linux distros
4862021-01-28T19:19:29  <dongcarl> right
4872021-01-28T19:19:46  <warren> luke-jr: I believe that's an opinion not shared by most others?
4882021-01-28T19:19:51  *** virtu <virtu!~virtu@gateway/tor-sasl/virtu> has quit IRC (Ping timeout: 268 seconds)
4892021-01-28T19:19:58  <luke-jr> warren: dunno, if not, they're wrong ;)
4902021-01-28T19:20:23  <luke-jr> LevelDB is the one exception that might justify static linking
4912021-01-28T19:20:25  <wumpus> i'm for 100% static release binaries
4922021-01-28T19:20:34  <luke-jr> (in distro packages)
4932021-01-28T19:20:45  <warren> dongcarl: so this soon to be process eliminates gitian? is there something to handle naming and versioning outputs like gitian used to do?
4942021-01-28T19:21:02  <luke-jr> warren: it can't eliminate gitian..
4952021-01-28T19:21:04  <dongcarl> warren: The output naming scheme is exactly Gitian's
4962021-01-28T19:21:10  <warren> dongcarl: can this work entirely offline with provided pre-cached downloads? That's one of the requirements of Fedora's build system
4972021-01-28T19:21:14  <luke-jr> Guix requires a trusted bootstrap
4982021-01-28T19:21:24  *** virtu <virtu!~virtu@gateway/tor-sasl/virtu> has joined #bitcoin-core-dev
4992021-01-28T19:21:37  <sipa> luke-jr: you trust the system you're building on, no?
5002021-01-28T19:22:02  <luke-jr> sipa: yes, but Guix wants me to trust <random third party binaries>
5012021-01-28T19:22:19  <dongcarl> luke-jr: Is gitian different?
5022021-01-28T19:22:28  <MarcoFalke> luke-jr: Just use a vm
5032021-01-28T19:22:36  <luke-jr> dongcarl: gitian runs all untrusted bins in a VM
5042021-01-28T19:22:36  <wumpus> guix is an improvement to gitian in that regard, that's all
5052021-01-28T19:22:40  <luke-jr> MarcoFalke: that's what gitian is for ;)
5062021-01-28T19:22:42  <wumpus> you can run guix in a vm
5072021-01-28T19:22:48  <luke-jr> Guix *within* gitian is an improvement
5082021-01-28T19:22:49  <wumpus> you can run guix in gitian even
5092021-01-28T19:22:51  <wumpus> :-)
5102021-01-28T19:22:53  <luke-jr> Guix *without* gitian is a regression
5112021-01-28T19:23:01  <wumpus> well that's entirely up to you
5122021-01-28T19:23:08  <wumpus> guix doesn't care what you run it in
5132021-01-28T19:23:10  <wumpus> that's thepoint
5142021-01-28T19:23:13  <warren> dongcarl: can this new glorious gitianless future work entirely offline with provided pre-cached downloads? That's one of the requirements of Fedora's build system
5152021-01-28T19:23:13  <MarcoFalke> luke-jr: You are free to use guix in gitian, but you can't force everyone else to do the same
5162021-01-28T19:23:25  <warren> MarcoFalke: +1
5172021-01-28T19:24:04  <achow101> I agree with luke-jr for a different reason. I think gitian is an easier way to onboard new gitian builders, and existing gitian builders don't need to change anything for guix. So we should still have gitian descriptors that do the guix builds. People who want guix locally can do that too. It should all be the same.
5182021-01-28T19:24:07  <dongcarl> warren: Yes, I believe it's designed to do so. I will double-check
5192021-01-28T19:24:25  <warren> achow101: that's fine
5202021-01-28T19:24:39  <sipa> achow101: yeah, i'd expect we'll just change the gitian descriptors to be thin wrappers around guix
5212021-01-28T19:24:44  <sipa> but no reason they can't remain
5222021-01-28T19:24:45  <warren> if people find it more convenient to use it that way
5232021-01-28T19:24:55  <luke-jr> sipa: +1
5242021-01-28T19:24:59  <wumpus> mind that gitian is effectively unmaintained
5252021-01-28T19:25:02  <MarcoFalke> achow101: guix is included in debian, so it will be in Ubuntu soon. I don't see how another wrapper makes things easier
5262021-01-28T19:25:29  <achow101> MarcoFalke: I already have gitian setup and can't be bothered to figure out gitian :p
5272021-01-28T19:25:39  <achow101> * figure out guix
5282021-01-28T19:25:47  <luke-jr> MarcoFalke: we should not be asking people to run third-party binaries on their system to build releases
5292021-01-28T19:26:04  <MarcoFalke> luke-jr: Then they should be using a vm
5302021-01-28T19:26:06  <wumpus> and it has some long-running issues, like the inability to upgrade base images leading to very long setup+build times
5312021-01-28T19:26:10  <luke-jr> MarcoFalke: yes
5322021-01-28T19:26:32  <MarcoFalke> luke-jr: The gitian guide starts by telling people how to install the vm, so nothing changes
5332021-01-28T19:26:32  <luke-jr> wumpus: gitian's last merge was only a month ago, hardly unmaintained..
5342021-01-28T19:26:33  <dongcarl> Is the main benefit here just a convenience script for running guix in a VM, or that people are used to the Gitian workflow?
5352021-01-28T19:26:40  <wumpus> then again, i'm tired of this discussion every time, if you want to use gitian then do...
5362021-01-28T19:27:08  <wumpus> i don't think it should be the default recommendation or 'a good way to onboard new builders'
5372021-01-28T19:27:15  <sipa> gitian does a few things that guix doesn't, i assume (like the creation of assert files, signing, verifying them)?
5382021-01-28T19:27:21  <wumpus> just make guix easy to use please
5392021-01-28T19:27:33  <wumpus> sipa: there is no reason why the guix wrapper couldn't do that
5402021-01-28T19:27:41  <sipa> wumpus: of course
5412021-01-28T19:27:52  <dongcarl> making guix easy to use is very much my goal
5422021-01-28T19:28:03  <wumpus> generating assert files is quite easy, signing them is done by gnupg
5432021-01-28T19:28:08  <wumpus> dongcarl: right!
5442021-01-28T19:28:35  <wumpus> and verifying them can be done without gitian now, e.g. see the gitian-verify.py script in maintainer-tools
5452021-01-28T19:28:41  <sipa> ok!
5462021-01-28T19:28:42  <warren> luke-jr: you can bootstrap guix yourself, why are you calling it untrusted?
5472021-01-28T19:28:50  <luke-jr> warren: no, I cannot
5482021-01-28T19:28:56  <luke-jr> warren: I spent hours trying and couldn't get anywhere
5492021-01-28T19:29:02  <MarcoFalke> warren: What is the policy for packages that are EOL? What is the policy for packages that went from fedora->stream->rhel?
5502021-01-28T19:29:08  <wumpus> I mean the whole point is that guix relies on a smaller trusted base than gitian
5512021-01-28T19:29:32  <warren> MarcoFalke: i need to ask what is possible from Fedora Engineering Steering Committee. I have a few things in mind like:
5522021-01-28T19:29:33  <aj> MarcoFalke: bitcoin's not going in stream/rhel, surely
5532021-01-28T19:29:36  <wumpus> gitian installs an *ubuntu* VM, it has lots of cruft
5542021-01-28T19:29:59  <luke-jr> wumpus: Guix is a smaller trusted base than Ubuntu, but larger than gitian for the host end
5552021-01-28T19:30:00  <warren> 1) Before a distro goes EOL the bitcoincore package is replaced with a final update that removes the binary.
5562021-01-28T19:30:27  <warren> 2) Build system CI could verify that the binary is reproducible and matches some URL upstream.
5572021-01-28T19:30:36  <wumpus> luke-jr: otoh if the guix trusted base is compromised so will the bitcoin core binaries
5582021-01-28T19:30:42  <luke-jr> warren: how about automatic upgrades and softforks? both deploying and not deploying the softfork are problematic without user consent
5592021-01-28T19:30:45  <sipa> wumpus: i think luke-jr's concern is about the risk that guix is malicious and say install malware in his host system; not about trusting the result of the build
5602021-01-28T19:30:49  <wumpus> luke-jr: it's kind of important
5612021-01-28T19:30:55  <wumpus> same for ubuntu right now, btw
5622021-01-28T19:30:56  <MarcoFalke> aj: shoudn't or can't?
5632021-01-28T19:30:58  * dongcarl is here but is a bit overwhelmed by the convo
5642021-01-28T19:31:09  <warren> luke-jr: why are you blindly trusting Ubuntu right now?
5652021-01-28T19:31:19  <wumpus> one compromised package in ubuntu and our binaries can be compromised
5662021-01-28T19:31:26  <aj> MarcoFalke: won't / isn't a rhel priority so doesn't make sense?
5672021-01-28T19:31:27  <wumpus> this is kind of scary
5682021-01-28T19:31:27  * warren hands dongcarl a calming Tribble.
5692021-01-28T19:31:35  <luke-jr> wumpus: yes, but we already have that problem
5702021-01-28T19:31:40  * sipa googles Tribble
5712021-01-28T19:31:52  <wumpus> luke-jr: it is mitigated by guix
5722021-01-28T19:31:55  <luke-jr> (with Ubuntu)
5732021-01-28T19:31:58  <MarcoFalke> aj: Oh, I assumed they just take all packages from fedora
5742021-01-28T19:32:36  <wumpus> because guix has a smaller trusted base, sure, it still has some binaries for bootstrapping, n one really solved the trusting-trust attacks yet, we can only slowly improve things
5752021-01-28T19:32:47  <luke-jr> wumpus: the ideal solution would be a way to bootstrap Guix without the third-party binary blobs
5762021-01-28T19:32:58  <warren> luke-jr does have a legitimate question about automatic upgrades. It is upstream's policy to not force users into automatic upgrades. If you install a distro package you opt-in to that.
5772021-01-28T19:33:00  <wumpus> luke-jr: i'm sure that's possible
5782021-01-28T19:33:21  <warren> There is a way however for users to opt-out of automatic distro upgrades.
5792021-01-28T19:33:23  <wumpus> guix is fully open source right? why couldn't you bootstrap it from an existing system?
5802021-01-28T19:33:37  <wumpus> givn that you have compilers and such of course
5812021-01-28T19:33:43  *** luke-jr <luke-jr!~luke-jr@unaffiliated/luke-jr> has quit IRC (Quit: ZNC - http://znc.sourceforge.net)
5822021-01-28T19:33:53  <warren> well that's one way to win the debate
5832021-01-28T19:33:55  <achow101> wumpus: from my experience, there are some usability hurdles that can make setting up guix really frustrating
5842021-01-28T19:34:12  <wumpus> achow101: well then we need to solve them
5852021-01-28T19:34:13  <aj> warren: nah, he got too close to telling the truth, so the powers that be deplatformed him
5862021-01-28T19:34:25  <wumpus> i don't see why that's an argument in favor of wrapping guix in ubuntu forever
5872021-01-28T19:34:32  <sipa> it isn't
5882021-01-28T19:34:34  <warren> achow101: people downloading a guix VM is no worse than people blindly trusting Ubuntu in current gitian.
5892021-01-28T19:34:54  <dongcarl> I'm happy to solve all of the usability problems in setting up Guix, that was an explicit goal from the beginning. To make it easier to use.
5902021-01-28T19:35:00  <sipa> yay.
5912021-01-28T19:35:13  <aj> dongcarl: <3
5922021-01-28T19:35:38  <dongcarl> Bootstrapping Guix from source is not the most user-friendly, but the UX problems are being solved, and the recent debian packaging outlines a for-sure way to bootstrap it from a system
5932021-01-28T19:35:42  <MarcoFalke> warren: Also, who would maintain the fedora package?
5942021-01-28T19:35:43  <warren> There is a way however for users to opt-out of automatic distro upgrades. The .rpm distributed by bitcoincore.org would be identical to the package distributed by Fedora except the Epoch number is higher. That way the Fedora package will never be seen as "newer". It retains the property desired by Bitcoin Core project that nobody is forced into automatic upgrades.
5952021-01-28T19:36:05  <warren> MarcoFalke: me, and everyone, because I intend it to be identical to bitcoincore.org's guix generated .rpm
5962021-01-28T19:36:15  *** luke-jr <luke-jr!~luke-jr@unaffiliated/luke-jr> has joined #bitcoin-core-dev
5972021-01-28T19:36:17  <wumpus> fwiw gitian is also not the most user friendly, it helps that there's guides for it everywhere now, but it took ages for people to start using it
5982021-01-28T19:36:45  <dongcarl> I'm sure that the debian packaging rules/formula can be ported to other distros, such as Gentoo, so that people on those distros can stay within their trusted base and boostrap Guix
5992021-01-28T19:36:46  <sipa> i don't even invoke anything gitian related directly, all within perhaps several layers of wrapper scripts
6002021-01-28T19:37:33  <wumpus> in a way it's just a matter of getting used to a new way of working, i don't think we need to wait for guix to be 100% user friendly all over the board until we can start using it for release builds
6012021-01-28T19:38:03  *** luke-jr <luke-jr!~luke-jr@unaffiliated/luke-jr> has quit IRC (Excess Flood)
6022021-01-28T19:38:08  <jonatack> this ^
6032021-01-28T19:38:08  <warren> gitian is already not user friendly, it's been mostly broken for me for a few years now.
6042021-01-28T19:38:23  <sipa> agree
6052021-01-28T19:38:27  <wumpus> warren: exactly my point, gitian was never easy to use or set up
6062021-01-28T19:38:30  <achow101> true
6072021-01-28T19:38:54  <dongcarl> I am also happy to offer my time to 1. Help anyone with their setup 2. Document UX hiccups 3. Fix them so that others don't experience them
6082021-01-28T19:38:55  <wumpus> it's just fairly well documented now, that will happen for guix too i'm sure when we start using it
6092021-01-28T19:39:00  <MarcoFalke> Are we aiming to ship guix packages for the next release?
6102021-01-28T19:39:05  <warren> If people want easy to use guix they can download a VM. That isn't worse than the current blind trust on Ubuntu used within gitian.
6112021-01-28T19:39:22  <wumpus> warren: at least you have more flexibility in what VM then!
6122021-01-28T19:39:44  <sipa> dongcarl: how realistic do you think it is to replace all release binaries for 22.0 with guix-built ones?
6132021-01-28T19:39:52  <wumpus> it doesn't need to be ubuntu anymore, can be debian, or even a guix-as-a-distro VM
6142021-01-28T19:40:17  <jonatack> warren: we've onboarded a dozen or so new gitian signers the past 6 months, by (a) making it a bit easier to get started and (b) communicating a bit more about doing it to people
6152021-01-28T19:40:31  <jonatack> i'm sure can do the same with guix
6162021-01-28T19:40:48  <dongcarl> sipa, MarcoFalke: The missing steps before we ship 22 with guix are: codesigning, assert-file tooling, UX/non-UX debugging and testing
6172021-01-28T19:40:51  <warren> How difficult are the remaining things needed to switch to guix/
6182021-01-28T19:40:52  <warren> ?
6192021-01-28T19:41:14  <MarcoFalke> dongcarl: Would those be easier if the gitian setup was used?
6202021-01-28T19:41:28  <dongcarl> I don't expect codesigning and assert-file tooling to be too difficult, but I don't want to make any promises w/re UX/non-UX debugging and testing
6212021-01-28T19:41:34  <MarcoFalke> I.e. replace the gitian build script with a guix build script, but still call gitian
6222021-01-28T19:41:55  <dongcarl> MarcoFalke: No, I believe using the gitian setup will probably be much more difficult
6232021-01-28T19:42:03  <warren> dongcarl: fedora builds have things neat thing where .rpm contains stripped binaries, but unstripped go into an optional -debuginfo package. gdb is smart enough to look at the debuginfo if you debug. Does guix have anything like that?
6242021-01-28T19:42:09  <dongcarl> s/much more/a bit/
6252021-01-28T19:42:24  <wumpus> there's still 4.5 months left before the 22.0 feature freeze
6262021-01-28T19:42:48  <warren> Could we do a practice release using guix of 0.21?
6272021-01-28T19:42:52  <MarcoFalke> If we switch, I'd prefer to do it at least two months before freeze
6282021-01-28T19:43:09  <warren> 0.21.x
6292021-01-28T19:43:19  *** luke-jr <luke-jr!~luke-jr@unaffiliated/luke-jr> has joined #bitcoin-core-dev
6302021-01-28T19:43:21  <sipa> dongcarl: what do you mean with "UX/non-UX debugging" ?
6312021-01-28T19:43:21  <wumpus> nack on wrapping guix in gitian, i really don't want to do a build like that
6322021-01-28T19:43:27  <warren> wumpus: +1
6332021-01-28T19:43:41  <wumpus> this almost doubles the trusted base
6342021-01-28T19:44:11  <dongcarl> Okay, I've been deep in the libbitcoin_kernel work as of late. But let me reload my stack, explore the scope, and get back to you all with my rough timeline expectations next week. Does that sound alright?
6352021-01-28T19:44:14  *** pinheadmz <pinheadmz!~pinheadmz@pool-71-105-114-182.nycmny.fios.verizon.net> has quit IRC (Quit: pinheadmz)
6362021-01-28T19:44:21  <wumpus> dongcarl: thanks!
6372021-01-28T19:44:37  <warren> How difficult is it to write the remaining tooling needed to switch releases to guix? If we don't know the answer right now can we have a TODO list by next meeting?
6382021-01-28T19:44:50  *** ghost43_ <ghost43_!~daer@gateway/tor-sasl/daer> has quit IRC (Remote host closed the connection)
6392021-01-28T19:45:07  *** ghost43 <ghost43!~daer@gateway/tor-sasl/daer> has joined #bitcoin-core-dev
6402021-01-28T19:45:34  <wumpus> how can we help?
6412021-01-28T19:45:39  <dongcarl> sipa: UX debugging would be going through the process to see which parts are non-intuitive and hard to use. non-UX debugging would entail testing the build output result more thoroughly
6422021-01-28T19:46:12  <warren> dongcarl: isn't that the same problem we have with the gitian release process?
6432021-01-28T19:46:16  <warren> not a new problem
6442021-01-28T19:46:19  <sipa> dongcarl: i'd expect the former can be alleviated by just writing documentation
6452021-01-28T19:46:36  <sipa> and perhaps in later steps make it more user friendly, so less needs to be documented
6462021-01-28T19:46:36  <MarcoFalke> do we need any assert-file tooling?
6472021-01-28T19:46:47  * dongcarl furiously typing
6482021-01-28T19:46:56  <MarcoFalke> As I understand the assert-file will list the installed ubuntu packages, but we no longer use that
6492021-01-28T19:47:13  <wumpus> what would a guix assert file even look like? just a list of hashes of the release files? or would you want to include more?
6502021-01-28T19:47:25  <wumpus> MarcoFalke: right, that
6512021-01-28T19:47:36  <achow101> shoudl the assert file even try to look like gitian's?
6522021-01-28T19:47:49  <wumpus> achow101: no reason it needs to
6532021-01-28T19:47:56  <MarcoFalke> so a sha256sum with a wildcard would generate the "assert file"?
6542021-01-28T19:47:57  <achow101> I would expect the guix assert file would be everything installed in guix
6552021-01-28T19:48:00  <sipa> if it's not guix-in-gitian, i see no reason why the assert file needs to be anything similar
6562021-01-28T19:48:04  <dongcarl> You're right, it doesn't need to.
6572021-01-28T19:48:13  <wumpus> it's fine with me if the assert file loks like SHA256SUMS.asc
6582021-01-28T19:48:30  * luke-jr kicks ISP
6592021-01-28T19:48:34  <sipa> it's nice if it also commits to the exact source code it was built from
6602021-01-28T19:48:56  <dongcarl> Here's the way fanquake and I have been verifying our outputs: https://github.com/bitcoin/bitcoin/pull/17920#issuecomment-765109583
6612021-01-28T19:48:57  <wumpus> sipa: true!
6622021-01-28T19:49:14  <dongcarl> Literally a one-liner
6632021-01-28T19:49:17  <wumpus> ideally it could commit to the inputs as well as the outputs
6642021-01-28T19:49:34  <dongcarl> Since that one-liner includes src/bitcoin-f1694757ddbc.tar.gz, it does commit to the bitcoin source
6652021-01-28T19:49:37  <luke-jr> it would be nice if as a result from this, we can dump everyone's signatures into the SHA256SUMS.asc file on the website
6662021-01-28T19:49:53  <MarcoFalke> dongcarl: Is the commit included when building tags?
6672021-01-28T19:50:15  <dongcarl> MarcoFalke: Sorry, not entirely sure what you mean here
6682021-01-28T19:50:26  <wumpus> luke-jr: that was my thinking as well
6692021-01-28T19:50:39  <dongcarl> luke-jr: That would be nice! I'll make a note of that
6702021-01-28T19:50:46  <MarcoFalke> when building a tag, the archive looks like `bitcoin-22.0.tar.gz`, not `bitcoin-fffffff.targ.gz`
6712021-01-28T19:51:01  <wumpus> everyone would be signing the same data so you could combine the signatures
6722021-01-28T19:51:13  <luke-jr> I wrote a blog post about verifying gitian sigs - it was way more complex than I'd like
6732021-01-28T19:51:30  <dongcarl> MarcoFalke: Yes, I believe I made sure of that some time ago, will re-check for you!
6742021-01-28T19:51:59  <wumpus> luke-jr: have you seen https://github.com/bitcoin-core/bitcoin-maintainer-tools#gitian-verify ? it makes things much easier
6752021-01-28T19:52:10  <wumpus> (e.g. tabulates the result)
6762021-01-28T19:52:29  <luke-jr> wumpus: that assumes the end user already has it ;)
6772021-01-28T19:52:39  <MarcoFalke> Though, since guix only works from git, including the commit hash in the "assert file" shouldn't be too hard
6782021-01-28T19:52:45  <wumpus> luke-jr: already has what?
6792021-01-28T19:52:57  <luke-jr> wumpus: a trusted Bitcoin Core source repo
6802021-01-28T19:53:28  <luke-jr> or rather, the maintainer tools repo
6812021-01-28T19:53:42  <wumpus> well okay sure, if you want to do it all manually
6822021-01-28T19:53:47  <wumpus> that's definitely a lot of work
6832021-01-28T19:53:57  <luke-jr> wget https://luke.dashjr.org/programs/bitcoin/files/bitcoind/0.21.0/SHA256SUMS.asc && gpg --verify SHA256SUMS.asc
6842021-01-28T19:53:59  <luke-jr> is a lot less
6852021-01-28T19:54:15  <luke-jr> (sha256sum -c too I guess)
6862021-01-28T19:54:46  <wumpus> i mean, sure, but that still assumes someone has all the gpg keys received and installed, but yeah
6872021-01-28T19:55:11  <wumpus> any other topics?
6882021-01-28T19:55:13  <warren> Question ... since 0.22 is months away could we aim to do a practice release on 0.21.x?
6892021-01-28T19:55:23  <luke-jr> WOT issues are unavoidable and not going away XD
6902021-01-28T19:55:45  <wumpus> warren: i would prefer to start using guix only in a major release
6912021-01-28T19:55:46  <MarcoFalke> wumpus: My topic was 0.20.2 :)
6922021-01-28T19:56:05  <warren> wumpus: not official for 0.21.x, but in parallel
6932021-01-28T19:56:19  <sipa> warren: or just master?
6942021-01-28T19:56:21  <warren> wumpus: partly because I need it to calm down the Fedora packagers
6952021-01-28T19:56:22  <MarcoFalke> warren: I think we can also practice on master
6962021-01-28T19:56:23  <sipa> why backport?
6972021-01-28T19:56:24  <wumpus> it's too big a change to backport, and besides, it needs the more extensive rc cycle of a major release
6982021-01-28T19:56:37  <warren> hmm
6992021-01-28T19:56:42  <wumpus> yes, practicing can be done fine on master
7002021-01-28T19:56:54  <warren> I'll live with that.
7012021-01-28T19:56:58  <sipa> or, on the guix PR branch, as long as it's not merged
7022021-01-28T19:56:59  <dongcarl> I'd be happy to practice with anyone and take notes :-)
7032021-01-28T19:57:02  <wumpus> #topic 0.20.2 (MarcoFalke)
7042021-01-28T19:57:14  <MarcoFalke> Basically asking if anything is left to do there
7052021-01-28T19:57:30  <MarcoFalke> and whether to do an rc and upload binaries
7062021-01-28T19:57:31  <wumpus> no idea, haven't kept track
7072021-01-28T19:58:44  <MarcoFalke> the rc1 was never released?
7082021-01-28T19:58:46  <luke-jr> MarcoFalke: I did end up finding a bug in the 0.19 bump
7092021-01-28T19:58:56  <luke-jr> sorry I missed the rcs
7102021-01-28T19:59:03  <MarcoFalke> luke-jr: huh?
7112021-01-28T19:59:12  * luke-jr digs it out to see if it's relevant to 0.20
7122021-01-28T19:59:45  <wumpus> I think it would be good if someone took over the back-releases from me, i do not have the capacity to handle that, definitely not so many at the same time
7132021-01-28T20:00:03  <luke-jr> I thought MarcoFalke was?
7142021-01-28T20:00:20  <MarcoFalke> I create the backports
7152021-01-28T20:00:22  <wumpus> yes, he effectively does
7162021-01-28T20:00:29  <wumpus> already
7172021-01-28T20:00:40  <MarcoFalke> Haven't run any of the release stuff scripts
7182021-01-28T20:00:43  <luke-jr> MarcoFalke: aha, it was a libevent dep for just bitcoin-tx builds
7192021-01-28T20:01:09  <luke-jr> I think it was fixed before 0.20
7202021-01-28T20:01:40  <luke-jr> so n/a for 0.20.2, and 0.19 will probably be dead before there's a chance to do another
7212021-01-28T20:02:47  *** Talkless <Talkless!~Talkless@mail.dargis.net> has quit IRC (Quit: Konversation terminated!)
7222021-01-28T20:02:52  <wumpus> #endmeeting
7232021-01-28T20:02:55  <MarcoFalke> luke-jr: 0.19 won't get any gitian binaries published, as I understood it
7242021-01-28T20:03:11  <luke-jr> ? this is when building from source
7252021-01-28T20:03:46  <wumpus> feel free to open a PR against the 0.19 branch to fix it then
7262021-01-28T20:08:20  <sipa> luke-jr: can i have a BIP number for bip-bech32m? (there are a few other things in the bips repo that want your attention too, i think)
7272021-01-28T20:08:59  *** justanotheruser <justanotheruser!~justanoth@unaffiliated/justanotheruser> has joined #bitcoin-core-dev
7282021-01-28T20:11:53  *** mfi_ <mfi_!~matthias@p200300df3f0f7db963081d59f40a9781.dip0.t-ipconnect.de> has joined #bitcoin-core-dev
7292021-01-28T20:12:19  <luke-jr> sipa: I guess use 350
7302021-01-28T20:13:08  <sipa> luke-jr: thanks!
7312021-01-28T20:21:09  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
7322021-01-28T20:21:09  <bitcoin-git> [bitcoin] laanwj opened pull request #21026: doc: Document use of make-tag script to make tags (master...2021-01-make-tag) https://github.com/bitcoin/bitcoin/pull/21026
7332021-01-28T20:21:10  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
7342021-01-28T20:24:15  <wumpus> ^^ might be useful if anyone else is to have a go at making releases
7352021-01-28T20:33:11  <achow101> is it possible to remove a task from CScheduler or maybe pause one?
7362021-01-28T20:36:35  <wumpus> doesn't seem like it
7372021-01-28T20:40:03  <sipsorcery> MarcoFalke: Did you change anything on the appveyor config? Or did one job just magically work again?
7382021-01-28T20:51:06  <dongcarl> For those following along the assumeutxo/chainman-deglobalizing work, please take a look at this very short PR which aims to remove the m_active_chainstate r/w footgun: #21025
7392021-01-28T20:51:07  <gribble> https://github.com/bitcoin/bitcoin/issues/21025 | validation: Guard the active_chainstate with cs_main by dongcarl · Pull Request #21025 · bitcoin/bitcoin · GitHub
7402021-01-28T20:52:10  <dongcarl> This is a prerequisite to having both work be safe, and I hope is simple enough to get in relatively quickly to unblock the two high-prio PRs
7412021-01-28T20:52:20  *** luke-jr <luke-jr!~luke-jr@unaffiliated/luke-jr> has quit IRC (Quit: ZNC - http://znc.sourceforge.net)
7422021-01-28T20:52:45  *** luke-jr <luke-jr!~luke-jr@unaffiliated/luke-jr> has joined #bitcoin-core-dev
7432021-01-28T20:52:47  *** mfi_ <mfi_!~matthias@p200300df3f0f7db963081d59f40a9781.dip0.t-ipconnect.de> has quit IRC (Quit: Leaving)
7442021-01-28T21:25:00  <luke-jr> MarcoFalke: can you please upstream https://github.com/bitcoin-core/univalue/pull/24 ?
7452021-01-28T21:29:27  <wumpus> dongcarl: thanks for working in that
7462021-01-28T21:29:30  <wumpus> on*
7472021-01-28T21:29:57  <dongcarl> :-)
7482021-01-28T21:37:22  *** Guyver2 <Guyver2!Guyver@guyver2.xs4all.nl> has quit IRC (Quit: Going offline, see ya! (www.adiirc.com))
7492021-01-28T21:44:16  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
7502021-01-28T21:44:17  <bitcoin-git> [bitcoin] laanwj pushed 5 commits to master: https://github.com/bitcoin/bitcoin/compare/80e16cadd56c...6a726cb534ed
7512021-01-28T21:44:17  <bitcoin-git> bitcoin/master 798bc0b Luke Dashjr: Support glibc-back-compat on 64-bit POWER
7522021-01-28T21:44:18  <bitcoin-git> bitcoin/master 63fc2b1 Luke Dashjr: gitian: Properly quote arguments in wrappers
7532021-01-28T21:44:18  <bitcoin-git> bitcoin/master 00f67c8 Luke Dashjr: gitian-linux: Build binaries for 64-bit POWER
7542021-01-28T21:44:19  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
7552021-01-28T21:44:36  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
7562021-01-28T21:44:37  <bitcoin-git> [bitcoin] laanwj merged pull request #20963: gitian-linux: Build binaries for 64-bit POWER (continued) (master...2021-01-power) https://github.com/bitcoin/bitcoin/pull/20963
7572021-01-28T21:44:48  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
7582021-01-28T21:45:30  <sipa> POWER, unlimited POWER!
7592021-01-28T21:49:22  * warren imagines beard stroking.
7602021-01-28T21:49:39  *** EagleTM <EagleTM!~EagleTM@unaffiliated/eagletm> has joined #bitcoin-core-dev
7612021-01-28T21:55:25  *** Tokamak <Tokamak!~Tokamak@204.141.173.217> has quit IRC (Ping timeout: 246 seconds)
7622021-01-28T21:58:48  *** Tokamak <Tokamak!~Tokamak@204.141.173.217> has joined #bitcoin-core-dev
7632021-01-28T22:11:04  <wumpus> hehe "64-bit POWER" sounds a bit like some cheesy early AMD64 commercial
7642021-01-28T22:12:09  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has quit IRC ()
7652021-01-28T22:15:54  <sipa> brings back memories of nintendo64
7662021-01-28T22:16:20  <sipa> where a "64" suffix was used in way too many places
7672021-01-28T22:16:20  <luke-jr> was that POWER?
7682021-01-28T22:16:27  <sipa> MIPS, i think
7692021-01-28T22:16:32  <luke-jr> 64-bit MIPS?
7702021-01-28T22:16:37  <luke-jr> does that even exist?
7712021-01-28T22:17:56  <sipa> apparently it did in 1996
7722021-01-28T22:23:55  *** justanotheruser <justanotheruser!~justanoth@unaffiliated/justanotheruser> has quit IRC (Ping timeout: 272 seconds)
7732021-01-28T22:26:39  *** vasild <vasild!~vd@gateway/tor-sasl/vasild> has quit IRC (Disconnected by services)
7742021-01-28T22:26:40  *** vasild_ <vasild_!~vd@gateway/tor-sasl/vasild> has joined #bitcoin-core-dev
7752021-01-28T22:26:40  *** vasild_ is now known as vasild
7762021-01-28T22:29:32  *** jackk_ <jackk_!~jackk@205.178.111.134> has joined #bitcoin-core-dev
7772021-01-28T23:02:46  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has joined #bitcoin-core-dev
7782021-01-28T23:14:44  <wumpus> IIRC nintendo64 didn't have an actual 64 bit processor, but two 32 bit ones
7792021-01-28T23:15:59  <phantomcircuit> wumpus, it was a hybrid, there were 64bit instructions
7802021-01-28T23:16:03  <phantomcircuit> iirc they were not useful
7812021-01-28T23:16:30  <wumpus> okay
7822021-01-28T23:17:47  <phantomcircuit> wumpus, no im wrong it's a true 64bit cpu but with a 32bit system bus... so nobody used the 64bit operations
7832021-01-28T23:19:01  <wumpus> i was confused with a different console then, i'm fairly sure the trick i mentioned was used somewhere
7842021-01-28T23:24:43  *** proofofkeags <proofofkeags!~proofofke@174-29-3-187.hlrn.qwest.net> has quit IRC (Remote host closed the connection)
7852021-01-28T23:33:38  *** luke-jr <luke-jr!~luke-jr@unaffiliated/luke-jr> has quit IRC (Quit: ZNC - http://znc.sourceforge.net)
7862021-01-28T23:34:30  *** rc_423 <rc_423!~r_423@cpe-75-185-100-189.cinci.res.rr.com> has quit IRC (Remote host closed the connection)
7872021-01-28T23:35:17  *** rc_423 <rc_423!~r_423@cpe-75-185-100-189.cinci.res.rr.com> has joined #bitcoin-core-dev
7882021-01-28T23:35:34  *** luke-jr <luke-jr!~luke-jr@unaffiliated/luke-jr> has joined #bitcoin-core-dev
7892021-01-28T23:35:52  *** elichai2 <elichai2!sid212594@gateway/web/irccloud.com/x-dcgzhmutntdsthom> has quit IRC (Ping timeout: 246 seconds)
7902021-01-28T23:36:04  *** rc_423 <rc_423!~r_423@cpe-75-185-100-189.cinci.res.rr.com> has quit IRC (Remote host closed the connection)
7912021-01-28T23:36:22  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
7922021-01-28T23:36:22  <bitcoin-git> [gui] jonatack opened pull request #201: gui: ensure inbound block relay peers have relevant services (master...inbound-block-relay) https://github.com/bitcoin-core/gui/pull/201
7932021-01-28T23:36:23  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
7942021-01-28T23:36:37  *** rc_423 <rc_423!~r_423@cpe-75-185-100-189.cinci.res.rr.com> has joined #bitcoin-core-dev
7952021-01-28T23:37:03  *** wangchun <wangchun!uid444603@gateway/web/irccloud.com/x-noqhzlwzyglfgrtn> has quit IRC (Ping timeout: 265 seconds)
7962021-01-28T23:37:05  *** wangchun_ <wangchun_!uid444603@gateway/web/irccloud.com/x-clwiemgrswhavjfu> has joined #bitcoin-core-dev
7972021-01-28T23:37:06  *** felixweis_ <felixweis_!sid154231@gateway/web/irccloud.com/x-xnoihktppjcorqez> has joined #bitcoin-core-dev
7982021-01-28T23:37:08  *** wallet42____ <wallet42____!sid154231@gateway/web/irccloud.com/x-lqwrexozzfjzdwgt> has joined #bitcoin-core-dev
7992021-01-28T23:37:15  *** jakesyl_ <jakesyl_!sid56879@gateway/web/irccloud.com/x-cdljmnidcybkxqei> has joined #bitcoin-core-dev
8002021-01-28T23:37:33  *** jakesyl <jakesyl!sid56879@gateway/web/irccloud.com/x-ovsgclsmhkkkcxht> has quit IRC (Ping timeout: 260 seconds)
8012021-01-28T23:37:42  *** jakesyl_ is now known as jakesyl
8022021-01-28T23:37:50  *** elichai2 <elichai2!sid212594@gateway/web/irccloud.com/x-djjbiuznzxhrxocp> has joined #bitcoin-core-dev
8032021-01-28T23:38:08  *** wallet42___ <wallet42___!sid154231@gateway/web/irccloud.com/x-cyqjwvcpwnemivxk> has quit IRC (Ping timeout: 260 seconds)
8042021-01-28T23:38:09  *** felixweis <felixweis!sid154231@gateway/web/irccloud.com/x-smefinmvkaltzcwo> has quit IRC (Ping timeout: 260 seconds)
8052021-01-28T23:38:17  *** felixweis_ is now known as felixweis
8062021-01-28T23:45:51  *** jackk_ <jackk_!~jackk@205.178.111.134> has quit IRC (Quit: Going offline, see ya! (www.adiirc.com))
8072021-01-28T23:53:26  *** hebasto <hebasto!sid449604@gateway/web/irccloud.com/x-wksdajxeaaviknor> has quit IRC (Ping timeout: 264 seconds)
8082021-01-28T23:54:36  *** hebasto <hebasto!sid449604@gateway/web/irccloud.com/x-eahswtbwpdytwihi> has joined #bitcoin-core-dev
8092021-01-28T23:56:29  *** rc_423 <rc_423!~r_423@cpe-75-185-100-189.cinci.res.rr.com> has quit IRC (Remote host closed the connection)
8102021-01-28T23:57:05  *** rc_423 <rc_423!~r_423@cpe-75-185-100-189.cinci.res.rr.com> has joined #bitcoin-core-dev