12022-03-17T00:13:06  <luke-jr> hebasto: why strikeout https://github.com/bitcoin/bitcoin/pull/24521#issuecomment-1064867120 ?
  22022-03-17T00:17:45  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has quit IRC (Ping timeout: 268 seconds)
  32022-03-17T00:30:39  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
  42022-03-17T00:30:39  <bitcoin-git> [bitcoin] ajtowns closed pull request #24563: wallet: Don't override sighash specified in PSBT (master...202203-fillpsbt) https://github.com/bitcoin/bitcoin/pull/24563
  52022-03-17T00:30:39  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
  62022-03-17T00:37:45  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has joined #bitcoin-core-dev
  72022-03-17T00:38:15  *** shesek <shesek!~shesek@user/shesek> has quit IRC (Remote host closed the connection)
  82022-03-17T00:38:40  *** shesek <shesek!~shesek@user/shesek> has joined #bitcoin-core-dev
  92022-03-17T00:41:36  *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Remote host closed the connection)
 102022-03-17T00:49:15  *** shesek <shesek!~shesek@user/shesek> has quit IRC (Remote host closed the connection)
 112022-03-17T00:49:40  *** shesek <shesek!~shesek@user/shesek> has joined #bitcoin-core-dev
 122022-03-17T01:08:16  *** shesek <shesek!~shesek@user/shesek> has quit IRC (Remote host closed the connection)
 132022-03-17T01:08:40  *** shesek <shesek!~shesek@user/shesek> has joined #bitcoin-core-dev
 142022-03-17T01:12:09  *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
 152022-03-17T01:12:57  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has quit IRC (Ping timeout: 252 seconds)
 162022-03-17T01:16:36  *** geyaeb <geyaeb!~geyaeb@gateway/tor-sasl/geyaeb> has quit IRC (Ping timeout: 240 seconds)
 172022-03-17T01:18:50  *** geyaeb <geyaeb!~geyaeb@gateway/tor-sasl/geyaeb> has joined #bitcoin-core-dev
 182022-03-17T01:22:30  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
 192022-03-17T01:23:55  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
 202022-03-17T01:37:01  *** B_1o1 <B_1o1!~B_1o1@> has quit IRC (Ping timeout: 240 seconds)
 212022-03-17T01:45:15  *** shesek <shesek!~shesek@user/shesek> has quit IRC (Remote host closed the connection)
 222022-03-17T01:45:41  *** shesek <shesek!~shesek@user/shesek> has joined #bitcoin-core-dev
 232022-03-17T01:45:47  *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Ping timeout: 256 seconds)
 242022-03-17T01:56:32  *** grettke <grettke!~grettke@cpe-65-29-228-30.wi.res.rr.com> has joined #bitcoin-core-dev
 252022-03-17T01:58:36  *** BUSY <BUSY!~BUSY@user/busy> has quit IRC (Read error: Connection reset by peer)
 262022-03-17T02:04:46  *** shesek <shesek!~shesek@user/shesek> has quit IRC (Remote host closed the connection)
 272022-03-17T02:05:10  *** shesek <shesek!~shesek@user/shesek> has joined #bitcoin-core-dev
 282022-03-17T02:08:54  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
 292022-03-17T02:08:54  <bitcoin-git> [bitcoin] ajtowns opened pull request #24595: WIP remove g_versionbitscache global (master...202202-cchainparams-chainstatemanager) https://github.com/bitcoin/bitcoin/pull/24595
 302022-03-17T02:08:54  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
 312022-03-17T02:09:23  *** vysn <vysn!~vysn@user/vysn> has joined #bitcoin-core-dev
 322022-03-17T02:13:18  *** BUSY <BUSY!~BUSY@user/busy> has joined #bitcoin-core-dev
 332022-03-17T02:13:39  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
 342022-03-17T02:13:58  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
 352022-03-17T02:30:16  *** shesek <shesek!~shesek@user/shesek> has quit IRC (Remote host closed the connection)
 362022-03-17T02:30:40  *** shesek <shesek!~shesek@user/shesek> has joined #bitcoin-core-dev
 372022-03-17T02:59:38  *** Cory <Cory!~Cory@user/pasha> has quit IRC (Ping timeout: 250 seconds)
 382022-03-17T03:00:30  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
 392022-03-17T03:00:44  *** Cory <Cory!~Cory@user/pasha> has joined #bitcoin-core-dev
 402022-03-17T03:00:44  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
 412022-03-17T03:00:46  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
 422022-03-17T03:01:17  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
 432022-03-17T03:06:01  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:bda3:424f:951c:38ed> has quit IRC (Ping timeout: 256 seconds)
 442022-03-17T03:07:33  *** brunoerg <brunoerg!~brunoerg@> has joined #bitcoin-core-dev
 452022-03-17T03:10:37  *** jarthur <jarthur!~jarthur@2603-8080-1540-002d-c00d-0011-9495-6b87.res6.spectrum.com> has quit IRC (Ping timeout: 240 seconds)
 462022-03-17T03:11:42  *** jarthur <jarthur!~jarthur@2603-8080-1540-002d-95ed-c4ac-7eb1-dc6f.res6.spectrum.com> has joined #bitcoin-core-dev
 472022-03-17T03:14:44  *** grettke <grettke!~grettke@cpe-65-29-228-30.wi.res.rr.com> has quit IRC (Quit: Textual IRC Client: www.textualapp.com)
 482022-03-17T03:16:56  *** grettke <grettke!~grettke@cpe-65-29-228-30.wi.res.rr.com> has joined #bitcoin-core-dev
 492022-03-17T03:25:45  *** ronoaldo <ronoaldo!~ronoaldo@> has quit IRC (Quit: Konversation terminated!)
 502022-03-17T03:31:03  *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
 512022-03-17T03:31:46  *** shesek <shesek!~shesek@user/shesek> has quit IRC (Remote host closed the connection)
 522022-03-17T03:32:11  *** shesek <shesek!~shesek@user/shesek> has joined #bitcoin-core-dev
 532022-03-17T03:34:18  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 252 seconds)
 542022-03-17T03:43:11  *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
 552022-03-17T03:59:38  *** grettke <grettke!~grettke@cpe-65-29-228-30.wi.res.rr.com> has quit IRC (Quit: Textual IRC Client: www.textualapp.com)
 562022-03-17T04:01:01  *** cmirror <cmirror!~cmirror@> has quit IRC (Remote host closed the connection)
 572022-03-17T04:01:16  *** cmirror <cmirror!~cmirror@> has joined #bitcoin-core-dev
 582022-03-17T04:06:15  *** shesek <shesek!~shesek@user/shesek> has quit IRC (Remote host closed the connection)
 592022-03-17T04:06:43  *** shesek <shesek!~shesek@user/shesek> has joined #bitcoin-core-dev
 602022-03-17T04:10:36  *** brunoerg <brunoerg!~brunoerg@> has quit IRC (Ping timeout: 240 seconds)
 612022-03-17T04:11:38  *** morcos_ <morcos_!~morcos@gateway/tor-sasl/morcos> has joined #bitcoin-core-dev
 622022-03-17T04:12:36  *** morcos <morcos!~morcos@gateway/tor-sasl/morcos> has quit IRC (Ping timeout: 240 seconds)
 632022-03-17T04:12:36  *** morcos_ is now known as morcos
 642022-03-17T04:13:02  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:bda3:424f:951c:38ed> has joined #bitcoin-core-dev
 652022-03-17T04:16:32  *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Ping timeout: 240 seconds)
 662022-03-17T04:31:58  *** mikehu44 <mikehu44!~quassel@gateway/vpn/pia/mikehu44-jc> has joined #bitcoin-core-dev
 672022-03-17T05:05:37  *** mikehu44 <mikehu44!~quassel@gateway/vpn/pia/mikehu44-jc> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
 682022-03-17T05:17:21  *** hashfunc569 <hashfunc569!~user@2601:5c0:c280:7090:78e9:5f82:1899:8c96> has joined #bitcoin-core-dev
 692022-03-17T05:24:46  *** shesek <shesek!~shesek@user/shesek> has quit IRC (Remote host closed the connection)
 702022-03-17T05:25:15  *** shesek <shesek!~shesek@user/shesek> has joined #bitcoin-core-dev
 712022-03-17T05:33:39  <hebasto> luke-jr: it is not about boost in depends, but about boost installed via homebrew
 722022-03-17T05:36:01  *** mikehu44 <mikehu44!~quassel@> has joined #bitcoin-core-dev
 732022-03-17T05:36:15  *** mikehu44 <mikehu44!~quassel@> has quit IRC (Client Quit)
 742022-03-17T05:36:45  *** grettke <grettke!~grettke@cpe-65-29-228-30.wi.res.rr.com> has joined #bitcoin-core-dev
 752022-03-17T05:48:12  *** lucasdcf <lucasdcf!~lucasdcf@201-26-23-125.dsl.telesp.net.br> has quit IRC (Ping timeout: 250 seconds)
 762022-03-17T06:06:07  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has quit IRC (Remote host closed the connection)
 772022-03-17T06:06:25  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has joined #bitcoin-core-dev
 782022-03-17T06:07:17  *** sudoforge <sudoforge!~sudoforge@wireguard/tunneler/sudoforge> has quit IRC (Ping timeout: 240 seconds)
 792022-03-17T06:12:36  *** grettke <grettke!~grettke@cpe-65-29-228-30.wi.res.rr.com> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)
 802022-03-17T06:13:12  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
 812022-03-17T06:13:12  <bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/d6cb4e8ff0d0...74f8c551e9ba
 822022-03-17T06:13:12  <bitcoin-git> bitcoin/master 12cc020 Sebastian Falbesoner: contrib: fix signet miner (sighash mismatch)
 832022-03-17T06:13:12  <bitcoin-git> bitcoin/master 74f8c55 MarcoFalke: Merge bitcoin/bitcoin#24553: contrib: fix signet miner (sighash mismatch)
 842022-03-17T06:13:12  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
 852022-03-17T06:13:28  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
 862022-03-17T06:13:28  <bitcoin-git> [bitcoin] MarcoFalke merged pull request #24553: contrib: fix signet miner (sighash mismatch) (master...202203-contrib-fix_signet_miner_sighash_mismatch) https://github.com/bitcoin/bitcoin/pull/24553
 872022-03-17T06:13:28  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
 882022-03-17T06:14:04  *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
 892022-03-17T06:18:39  *** ifeanyi <ifeanyi!~ifeanyi@> has joined #bitcoin-core-dev
 902022-03-17T06:19:04  *** morcos <morcos!~morcos@gateway/tor-sasl/morcos> has quit IRC (Remote host closed the connection)
 912022-03-17T06:19:21  *** morcos <morcos!~morcos@gateway/tor-sasl/morcos> has joined #bitcoin-core-dev
 922022-03-17T06:22:11  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
 932022-03-17T06:22:11  <bitcoin-git> [bitcoin] hebasto pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/74f8c551e9ba...aece56624941
 942022-03-17T06:22:11  <bitcoin-git> bitcoin/master 026b5b4 Sjors Provoost: move-only: helper function to present PSBT
 952022-03-17T06:22:11  <bitcoin-git> bitcoin/master 4b5a6cd Sjors Provoost: refactor: helper function signWithExternalSigner()
 962022-03-17T06:22:11  <bitcoin-git> bitcoin/master 2efdfb8 Sjors Provoost: gui: restore Send for external signer
 972022-03-17T06:22:11  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
 982022-03-17T06:22:27  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
 992022-03-17T06:22:27  <bitcoin-git> [gui] hebasto merged pull request #555: Restore Send button when using external signer (master...2022/02/send_button) https://github.com/bitcoin-core/gui/pull/555
1002022-03-17T06:22:27  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1012022-03-17T06:23:04  *** morcos <morcos!~morcos@gateway/tor-sasl/morcos> has quit IRC (Client Quit)
1022022-03-17T06:23:33  *** morcos <morcos!~morcos@gateway/tor-sasl/morcos> has joined #bitcoin-core-dev
1032022-03-17T06:25:35  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
1042022-03-17T06:26:35  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1052022-03-17T06:26:35  <bitcoin-git> [bitcoin] MarcoFalke pushed 8 commits to master: https://github.com/bitcoin/bitcoin/compare/aece56624941...601bfc417d1f
1062022-03-17T06:26:35  <bitcoin-git> bitcoin/master 5be9ee3 Anthony Towns: refactor: more const annotations for uses of CBlockIndex*
1072022-03-17T06:26:35  <bitcoin-git> bitcoin/master 3bbb6fe Carl Dong: style-only: Various blockstorage.cpp cleanups
1082022-03-17T06:26:35  <bitcoin-git> bitcoin/master 42e56d9 Carl Dong: style-only: No need for std::pair for vSortedByHeight
1092022-03-17T06:26:35  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1102022-03-17T06:26:51  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1112022-03-17T06:26:51  <bitcoin-git> [bitcoin] MarcoFalke merged pull request #24515: Only load BlockMan in BlockMan member functions  (master...2022-03-kirby-p2.5) https://github.com/bitcoin/bitcoin/pull/24515
1122022-03-17T06:26:51  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1132022-03-17T06:27:12  *** ifeanyi <ifeanyi!~ifeanyi@> has quit IRC (Ping timeout: 250 seconds)
1142022-03-17T06:27:31  *** ifeanyi <ifeanyi!~ifeanyi@> has joined #bitcoin-core-dev
1152022-03-17T06:28:20  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
1162022-03-17T06:29:08  *** morcos <morcos!~morcos@gateway/tor-sasl/morcos> has quit IRC (Remote host closed the connection)
1172022-03-17T06:29:24  *** morcos <morcos!~morcos@gateway/tor-sasl/morcos> has joined #bitcoin-core-dev
1182022-03-17T06:30:15  *** shesek <shesek!~shesek@user/shesek> has quit IRC (Remote host closed the connection)
1192022-03-17T06:30:43  *** shesek <shesek!~shesek@user/shesek> has joined #bitcoin-core-dev
1202022-03-17T06:33:31  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1212022-03-17T06:33:31  <bitcoin-git> [bitcoin] hebasto opened pull request #24596: [23.x] GUI backport (23.x...220317-23.x-backport) https://github.com/bitcoin/bitcoin/pull/24596
1222022-03-17T06:33:31  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1232022-03-17T06:41:48  *** gnaf <gnaf!~gnaf@195-154-105-157.rev.poneytelecom.eu> has quit IRC (Read error: Connection reset by peer)
1242022-03-17T06:46:42  *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Ping timeout: 250 seconds)
1252022-03-17T06:52:14  *** szkl <szkl!uid110435@id-110435.uxbridge.irccloud.com> has joined #bitcoin-core-dev
1262022-03-17T06:57:45  *** grettke <grettke!~grettke@cpe-65-29-228-30.wi.res.rr.com> has joined #bitcoin-core-dev
1272022-03-17T07:06:57  *** hashfunc569 <hashfunc569!~user@2601:5c0:c280:7090:78e9:5f82:1899:8c96> has quit IRC (Ping timeout: 240 seconds)
1282022-03-17T07:10:30  *** jarthur <jarthur!~jarthur@2603-8080-1540-002d-95ed-c4ac-7eb1-dc6f.res6.spectrum.com> has quit IRC (Quit: jarthur)
1292022-03-17T07:29:44  *** shesek <shesek!~shesek@user/shesek> has quit IRC (Remote host closed the connection)
1302022-03-17T07:29:46  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1312022-03-17T07:29:46  <bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/601bfc417d1f...bf2c0fb2a264
1322022-03-17T07:29:46  <bitcoin-git> bitcoin/master f59bee3 Anthony Towns: fuzz: execute each file in dir without fuzz engine
1332022-03-17T07:29:46  <bitcoin-git> bitcoin/master bf2c0fb MarcoFalke: Merge bitcoin/bitcoin#24472: fuzz: execute each file in dir without fuzz e...
1342022-03-17T07:29:46  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1352022-03-17T07:30:02  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1362022-03-17T07:30:02  <bitcoin-git> [bitcoin] MarcoFalke merged pull request #24472: fuzz: execute each file in dir without fuzz engine (master...202203-phuzztesting) https://github.com/bitcoin/bitcoin/pull/24472
1372022-03-17T07:30:02  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1382022-03-17T07:30:10  *** shesek <shesek!~shesek@user/shesek> has joined #bitcoin-core-dev
1392022-03-17T07:36:58  *** jouke <jouke!~jouke@140-100-128-083.dynamic.caiway.nl> has quit IRC (Ping timeout: 250 seconds)
1402022-03-17T07:45:34  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1412022-03-17T07:49:17  *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 240 seconds)
1422022-03-17T07:56:44  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1432022-03-17T07:56:44  <bitcoin-git> [bitcoin] hebasto opened pull request #24597: doc, guix: Include `arm64-apple-darwin` into codesigned archs (master...220317-docs) https://github.com/bitcoin/bitcoin/pull/24597
1442022-03-17T07:56:44  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1452022-03-17T08:02:01  *** Alexthek1d <Alexthek1d!~Alexthek1@p5b3ae941.dip0.t-ipconnect.de> has joined #bitcoin-core-dev
1462022-03-17T08:04:44  <Alexthek1d> Hello,
1472022-03-17T08:04:45  <Alexthek1d> if you download the full node with bitcoin-core and i choose an external hard drive as target for the node:
1482022-03-17T08:05:02  <Alexthek1d> Does bitcoin-core copy the data temporarily to the drive of the OS first (so "caching") or in memory/RAM and then to the external hdd?
1492022-03-17T08:05:21  <Alexthek1d> (I ask because i do not want too many write operations on my OS drive)
1502022-03-17T08:06:01  <sipa> It will only use the drive/directory you select.
1512022-03-17T08:08:52  <Alexthek1d> sipa, thank you :)
1522022-03-17T08:15:39  *** ifeanyi <ifeanyi!~ifeanyi@> has quit IRC (Ping timeout: 256 seconds)
1532022-03-17T08:16:06  *** NorrinRadd <NorrinRadd!~username@> has joined #bitcoin-core-dev
1542022-03-17T08:21:45  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
1552022-03-17T08:22:01  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
1562022-03-17T08:23:15  *** shesek <shesek!~shesek@user/shesek> has quit IRC (Remote host closed the connection)
1572022-03-17T08:23:40  *** shesek <shesek!~shesek@user/shesek> has joined #bitcoin-core-dev
1582022-03-17T08:26:36  *** NorrinRadd <NorrinRadd!~username@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)
1592022-03-17T08:28:14  *** b10c <b10c!~quassel@user/b10c> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
1602022-03-17T08:28:36  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
1612022-03-17T08:28:52  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
1622022-03-17T08:32:15  *** b10c <b10c!~quassel@static.> has joined #bitcoin-core-dev
1632022-03-17T08:36:02  <Alexthek1d> sipa, does it use RAM as cache?
1642022-03-17T08:37:14  <laanwj> please take general usage questions to #bitcoin
1652022-03-17T08:38:31  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1662022-03-17T08:38:31  <bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/bf2c0fb2a264...8435d7f11a89
1672022-03-17T08:38:31  <bitcoin-git> bitcoin/master 1f4801b Hennadii Stepanov: doc, guix: Include arm64-apple-darwin into codesigned archs
1682022-03-17T08:38:31  <bitcoin-git> bitcoin/master 8435d7f fanquake: Merge bitcoin/bitcoin#24597: doc, guix: Include `arm64-apple-darwin` into ...
1692022-03-17T08:38:31  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1702022-03-17T08:38:48  *** Guyver2 <Guyver2!~Guyver@guyver2.xs4all.nl> has joined #bitcoin-core-dev
1712022-03-17T08:38:48  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1722022-03-17T08:38:48  <bitcoin-git> [bitcoin] fanquake merged pull request #24597: doc, guix: Include `arm64-apple-darwin` into codesigned archs (master...220317-docs) https://github.com/bitcoin/bitcoin/pull/24597
1732022-03-17T08:38:56  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1742022-03-17T08:41:41  <Alexthek1d> laanwj, okay
1752022-03-17T08:43:52  *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
1762022-03-17T08:48:21  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1772022-03-17T08:48:21  <bitcoin-git> [bitcoin] laanwj merged pull request #24593: [23.x] macOS / build backports (23.x...more_macos_backports_rc3) https://github.com/bitcoin/bitcoin/pull/24593
1782022-03-17T08:48:21  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1792022-03-17T08:52:14  *** shesek <shesek!~shesek@user/shesek> has quit IRC (Remote host closed the connection)
1802022-03-17T08:52:41  *** shesek <shesek!~shesek@user/shesek> has joined #bitcoin-core-dev
1812022-03-17T08:58:31  *** szkl <szkl!uid110435@id-110435.uxbridge.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)
1822022-03-17T08:59:48  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1832022-03-17T08:59:49  <bitcoin-git> [bitcoin] prusnak opened pull request #24598: Add *.xip to .gitignore (master...gitignore-xip) https://github.com/bitcoin/bitcoin/pull/24598
1842022-03-17T08:59:49  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1852022-03-17T09:00:31  *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Quit: = "")
1862022-03-17T09:09:43  *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
1872022-03-17T09:13:01  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 268 seconds)
1882022-03-17T09:14:12  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has joined #bitcoin-core-dev
1892022-03-17T09:21:25  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has quit IRC ()
1902022-03-17T09:31:39  *** rex4539 <rex4539!~rex4539@gateway/tor-sasl/rex4539> has joined #bitcoin-core-dev
1912022-03-17T09:37:15  *** mikehu44 <mikehu44!~quassel@gateway/vpn/pia/mikehu44-jc> has joined #bitcoin-core-dev
1922022-03-17T10:04:34  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1932022-03-17T10:04:34  <bitcoin-git> [bitcoin] fanquake opened pull request #24599: guix: remove mingw-w64 std::filesystem workaround (master...remove_newlib_workaround) https://github.com/bitcoin/bitcoin/pull/24599
1942022-03-17T10:04:42  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1952022-03-17T10:07:50  *** jouke <jouke!~jouke@92-111-70-106.static.v4.ziggozakelijk.nl> has joined #bitcoin-core-dev
1962022-03-17T10:18:36  *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Ping timeout: 250 seconds)
1972022-03-17T10:20:08  *** Alexthek1d1977 <Alexthek1d1977!~Alexthek1@p5b3ae399.dip0.t-ipconnect.de> has joined #bitcoin-core-dev
1982022-03-17T10:20:12  *** Alexthek1d <Alexthek1d!~Alexthek1@p5b3ae941.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 252 seconds)
1992022-03-17T10:23:37  *** mudsip <mudsip!~mudsip@user/mudsip> has joined #bitcoin-core-dev
2002022-03-17T10:25:11  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has quit IRC (Remote host closed the connection)
2012022-03-17T10:25:31  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has joined #bitcoin-core-dev
2022022-03-17T10:29:35  *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
2032022-03-17T10:42:45  *** mudsip <mudsip!~mudsip@user/mudsip> has quit IRC ()
2042022-03-17T11:05:18  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:bda3:424f:951c:38ed> has quit IRC (Ping timeout: 252 seconds)
2052022-03-17T11:07:26  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2062022-03-17T11:07:27  <bitcoin-git> [bitcoin] fanquake opened pull request #24600: doc: mention that BDB is for the legacy wallet in build-freebsd.md (master...freebsd_legacy_descriptor_switch) https://github.com/bitcoin/bitcoin/pull/24600
2072022-03-17T11:07:27  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2082022-03-17T11:11:08  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2092022-03-17T11:11:09  <bitcoin-git> [bitcoin] josibake opened pull request #24601: ci: add ci/scratch dir to .gitignore (master...add-ci-scratch-gitignore) https://github.com/bitcoin/bitcoin/pull/24601
2102022-03-17T11:11:09  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2112022-03-17T11:19:35  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:bda3:424f:951c:38ed> has joined #bitcoin-core-dev
2122022-03-17T11:21:52  *** jonatack <jonatack!jonatack@user/jonatack> has quit IRC (Ping timeout: 250 seconds)
2132022-03-17T11:23:00  *** jouke <jouke!~jouke@92-111-70-106.static.v4.ziggozakelijk.nl> has quit IRC (Ping timeout: 240 seconds)
2142022-03-17T11:26:41  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
2152022-03-17T11:26:57  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
2162022-03-17T11:32:21  *** jouke <jouke!~jouke@92-111-70-106.static.v4.ziggozakelijk.nl> has joined #bitcoin-core-dev
2172022-03-17T11:39:45  *** shesek <shesek!~shesek@user/shesek> has quit IRC (Remote host closed the connection)
2182022-03-17T11:40:02  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2192022-03-17T11:40:02  <bitcoin-git> [bitcoin] mzumsande opened pull request #24602: fuzz: add target for coinselection algorithms (master...202203_fuzz_coinselection) https://github.com/bitcoin/bitcoin/pull/24602
2202022-03-17T11:40:02  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2212022-03-17T11:40:11  *** shesek <shesek!~shesek@user/shesek> has joined #bitcoin-core-dev
2222022-03-17T11:47:48  *** jouke <jouke!~jouke@92-111-70-106.static.v4.ziggozakelijk.nl> has quit IRC (Ping timeout: 240 seconds)
2232022-03-17T11:54:56  *** lucasdcf <lucasdcf!~lucasdcf@2804:431:c7d8:f893:e8fc:29f0:7723:741e> has joined #bitcoin-core-dev
2242022-03-17T11:55:37  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:bda3:424f:951c:38ed> has quit IRC (Ping timeout: 240 seconds)
2252022-03-17T11:55:48  *** ronoaldo <ronoaldo!~ronoaldo@> has joined #bitcoin-core-dev
2262022-03-17T12:04:31  *** jouke <jouke!~jouke@92-111-70-106.static.v4.ziggozakelijk.nl> has joined #bitcoin-core-dev
2272022-03-17T12:08:39  <stickies-v> #proposedmeetingtopic important changes in 23.0 to cover in the new RC Testing Guide (see https://github.com/bitcoin-core/bitcoin-devwiki/wiki/22.0-Release-Candidate-Testing-Guide)
2282022-03-17T12:14:44  *** An0rak <An0rak!An0rak@user/an0rak> has quit IRC (Remote host closed the connection)
2292022-03-17T12:18:39  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has joined #bitcoin-core-dev
2302022-03-17T12:24:33  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
2312022-03-17T12:24:50  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
2322022-03-17T12:27:15  *** gnaf <gnaf!~gnaf@51-15-187-53.rev.poneytelecom.eu> has joined #bitcoin-core-dev
2332022-03-17T12:35:36  *** gnaf <gnaf!~gnaf@51-15-187-53.rev.poneytelecom.eu> has quit IRC (Quit: Konversation terminated!)
2342022-03-17T12:41:24  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2352022-03-17T12:41:24  <bitcoin-git> [bitcoin] fanquake opened pull request #24603: macdeploy: remove unused detached-sig-apply.sh (master...unused_detached_sig_apply) https://github.com/bitcoin/bitcoin/pull/24603
2362022-03-17T12:41:24  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2372022-03-17T12:45:48  *** arythmetic <arythmetic!~arythmeti@> has joined #bitcoin-core-dev
2382022-03-17T12:47:42  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
2392022-03-17T12:47:58  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
2402022-03-17T13:00:35  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
2412022-03-17T13:00:52  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
2422022-03-17T13:09:06  *** Guyver2 <Guyver2!~Guyver@guyver2.xs4all.nl> has quit IRC (Quit: Going offline, see ya! (www.adiirc.com))
2432022-03-17T13:11:45  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
2442022-03-17T13:13:52  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2452022-03-17T13:13:52  <bitcoin-git> [bitcoin] fanquake opened pull request #24604: build: fix copypasta in OpenBSD C{XX} flags (master...openbsd_copy_pasta) https://github.com/bitcoin/bitcoin/pull/24604
2462022-03-17T13:13:52  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2472022-03-17T13:15:01  *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 240 seconds)
2482022-03-17T13:15:23  *** goatpig <goatpig!~goat@ec2-13-48-246-2.eu-north-1.compute.amazonaws.com> has joined #bitcoin-core-dev
2492022-03-17T13:15:25  *** goatpig_ <goatpig_!~goat@h-94-254-2-155.A498.priv.bahnhof.se> has quit IRC (Ping timeout: 250 seconds)
2502022-03-17T13:24:12  *** mikehu44 <mikehu44!~quassel@gateway/vpn/pia/mikehu44-jc> has quit IRC (Ping timeout: 240 seconds)
2512022-03-17T13:33:21  *** lucasdcf <lucasdcf!~lucasdcf@2804:431:c7d8:f893:e8fc:29f0:7723:741e> has quit IRC (Read error: Connection reset by peer)
2522022-03-17T13:33:44  *** lucasdcf <lucasdcf!~lucasdcf@2804:431:c7d8:f893:e8fc:29f0:7723:741e> has joined #bitcoin-core-dev
2532022-03-17T13:39:27  *** Guest64 <Guest64!~Guest64@dynamic-acs-24-101-67-242.zoominternet.net> has joined #bitcoin-core-dev
2542022-03-17T13:40:17  *** Guest64 <Guest64!~Guest64@dynamic-acs-24-101-67-242.zoominternet.net> has quit IRC (Client Quit)
2552022-03-17T13:44:48  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has quit IRC (Remote host closed the connection)
2562022-03-17T13:45:30  *** mikehu44 <mikehu44!~quassel@gateway/vpn/pia/mikehu44-jc> has joined #bitcoin-core-dev
2572022-03-17T13:47:02  *** goatpig <goatpig!~goat@ec2-13-48-246-2.eu-north-1.compute.amazonaws.com> has quit IRC (Ping timeout: 250 seconds)
2582022-03-17T13:47:14  *** goatpig <goatpig!~goat@h-94-254-2-155.A498.priv.bahnhof.se> has joined #bitcoin-core-dev
2592022-03-17T13:49:57  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has joined #bitcoin-core-dev
2602022-03-17T13:54:24  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has quit IRC (Ping timeout: 250 seconds)
2612022-03-17T13:56:01  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has joined #bitcoin-core-dev
2622022-03-17T13:59:43  *** szkl <szkl!uid110435@id-110435.uxbridge.irccloud.com> has joined #bitcoin-core-dev
2632022-03-17T14:00:12  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has quit IRC (Ping timeout: 240 seconds)
2642022-03-17T14:02:05  *** sudoforge <sudoforge!~sudoforge@wireguard/tunneler/sudoforge> has joined #bitcoin-core-dev
2652022-03-17T14:06:35  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
2662022-03-17T14:06:57  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
2672022-03-17T14:07:53  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
2682022-03-17T14:07:59  *** ghost43_ <ghost43_!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
2692022-03-17T14:08:32  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has joined #bitcoin-core-dev
2702022-03-17T14:24:07  *** Guyver2 <Guyver2!~Guyver@guyver2.xs4all.nl> has joined #bitcoin-core-dev
2712022-03-17T14:45:25  *** Willtech <Willtech!~Willtech@user/Willtech> has joined #bitcoin-core-dev
2722022-03-17T14:56:51  *** Willtech <Willtech!~Willtech@user/Willtech> has quit IRC (Quit: Willtech)
2732022-03-17T14:57:30  *** Willtech <Willtech!~Willtech@user/Willtech> has joined #bitcoin-core-dev
2742022-03-17T14:57:50  *** Willtech is now known as NOD32Admin
2752022-03-17T15:09:18  <MarcoFalke> I can't force push to github anymore
2762022-03-17T15:09:36  <MarcoFalke>  ! [remote rejected]       2203-designated_init-🛍 -> 2203-designated_init-🛍 (Internal Server Error)
2772022-03-17T15:09:49  *** mikehu44 <mikehu44!~quassel@gateway/vpn/pia/mikehu44-jc> has quit IRC (Ping timeout: 250 seconds)
2782022-03-17T15:10:03  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has quit IRC (Ping timeout: 252 seconds)
2792022-03-17T15:11:00  <stick> MarcoFalke: github outage
2802022-03-17T15:11:25  <stick> regular push does not work either from here
2812022-03-17T15:11:36  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has joined #bitcoin-core-dev
2822022-03-17T15:12:06  <stick> https://www.githubstatus.com
2832022-03-17T15:13:35  *** ghost43_ <ghost43_!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
2842022-03-17T15:14:23  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
2852022-03-17T15:16:03  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has quit IRC (Ping timeout: 250 seconds)
2862022-03-17T15:16:29  *** bomb-on <bomb-on!~bomb-on@user/bomb-on> has joined #bitcoin-core-dev
2872022-03-17T15:21:57  <MarcoFalke> tea time, I guess
2882022-03-17T15:22:13  <fanquake> knock off time
2892022-03-17T15:22:29  *** brunoerg <brunoerg!~brunoerg@> has joined #bitcoin-core-dev
2902022-03-17T15:22:33  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
2912022-03-17T15:23:22  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
2922022-03-17T15:24:31  <achow101> bah, can't comment either :(
2932022-03-17T15:26:37  *** brunoerg <brunoerg!~brunoerg@> has quit IRC (Ping timeout: 240 seconds)
2942022-03-17T15:28:33  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has joined #bitcoin-core-dev
2952022-03-17T15:33:09  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has quit IRC (Ping timeout: 252 seconds)
2962022-03-17T15:34:38  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has joined #bitcoin-core-dev
2972022-03-17T15:39:46  <Earnest> achow101: Will descriptor wallets ever work with sethdseed and the ability to dump the (WIF) seed?
2982022-03-17T15:39:54  <achow101> Earnest: no
2992022-03-17T15:40:48  <Earnest> That is a feature I wanted to use but it seems to be going away now, I'll have to reconsider this
3002022-03-17T15:41:14  <sipa> You can dump the descriptor(s), though.
3012022-03-17T15:41:37  <Earnest> Yeah, I noted that and the recent change to dump the tprv as well
3022022-03-17T15:41:49  <achow101> #23417 may allow for exporting the master private key however
3032022-03-17T15:41:51  <gribble> https://github.com/bitcoin/bitcoin/issues/23417 | wallet, spkm: Move key management from DescriptorScriptPubKeyMan to wallet level KeyManager by achow101 · Pull Request #23417 · bitcoin/bitcoin · GitHub
3042022-03-17T15:42:22  <Earnest> But that's not nearly as useful as seeds, including any inactiveseeds
3052022-03-17T15:42:58  <achow101> but with descriptor wallets, we want to be explicit about what is being imported and watched for, rather than inferring
3062022-03-17T15:43:05  <Earnest> I quite like the idea of having my public/private keys being derived from a password/phrase, considerations for security withstanding
3072022-03-17T15:43:31  <Earnest> So that I don't have to entirely rely on the robustness of computers
3082022-03-17T15:43:52  <Earnest> (Much like curiosity, they rebooted it 7 times a day, just in case its state became corrupted)
3092022-03-17T15:43:55  <achow101> key's are not useful if you don't know what scripts, and seeds are not useful without derivation paths
3102022-03-17T15:44:01  <sipa> you can print a descriptor to paper or so as well
3112022-03-17T15:44:08  <Earnest> achow101: This is a fair point, yeah
3122022-03-17T15:44:19  <achow101> descriptors does not preclude containing bip39 mnemonics or other methods of deriving keys as KEY expressions
3132022-03-17T15:44:26  <Earnest> Oh yeah, the new wallets are much nicer in that respect
3142022-03-17T15:44:35  <Earnest> achow101: Yes, that's what I'm getting at
3152022-03-17T15:44:50  <Earnest> (Doesn't have to be necessarily seed words though)
3162022-03-17T15:45:15  *** lucasdcf <lucasdcf!~lucasdcf@2804:431:c7d8:f893:e8fc:29f0:7723:741e> has quit IRC (Ping timeout: 252 seconds)
3172022-03-17T15:46:23  <Earnest> If you don't mind, thanks for answering so far, but listdescriptors on a new wallet will output 4 of them, and seems they're all the same but with different derivation paths and checksums.  As the tpub/tprv is the same for all of them, how would you import that tprv in such a way to recover them all instead of just one?
3182022-03-17T15:46:42  <Earnest> Hm, actually I can probably answer that myself
3192022-03-17T15:46:59  <sipa> you don't import tprvs; you import the whole descriptor
3202022-03-17T15:47:14  <Earnest> Yeah, I just remembered that heh
3212022-03-17T15:50:05  <Earnest> achow101: 23417 seems nice yeah
3222022-03-17T15:56:21  *** jouke <jouke!~jouke@92-111-70-106.static.v4.ziggozakelijk.nl> has quit IRC (Ping timeout: 256 seconds)
3232022-03-17T16:09:19  *** szkl <szkl!uid110435@id-110435.uxbridge.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)
3242022-03-17T16:14:30  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
3252022-03-17T16:15:21  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
3262022-03-17T16:19:49  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has quit IRC (Ping timeout: 240 seconds)
3272022-03-17T16:22:11  *** NOD32Admin <NOD32Admin!~Willtech@user/Willtech> has quit IRC (Quit: NOD32Admin)
3282022-03-17T16:22:50  *** NOD32Admin <NOD32Admin!~Willtech@user/Willtech> has joined #bitcoin-core-dev
3292022-03-17T16:28:33  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
3302022-03-17T16:29:22  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
3312022-03-17T16:32:31  *** NOD32Admin <NOD32Admin!~Willtech@user/Willtech> has quit IRC (Quit: NOD32Admin)
3322022-03-17T16:33:10  *** NOD32Admin <NOD32Admin!~Willtech@user/Willtech> has joined #bitcoin-core-dev
3332022-03-17T16:33:50  *** lucasdcf <lucasdcf!~lucasdcf@201-26-23-125.dsl.telesp.net.br> has joined #bitcoin-core-dev
3342022-03-17T16:38:03  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has quit IRC (Ping timeout: 252 seconds)
3352022-03-17T16:42:34  *** vysn <vysn!~vysn@user/vysn> has quit IRC (Ping timeout: 268 seconds)
3362022-03-17T16:44:31  *** brunoerg <brunoerg!~brunoerg@> has joined #bitcoin-core-dev
3372022-03-17T17:06:31  *** Alexthek1d1977 <Alexthek1d1977!~Alexthek1@p5b3ae399.dip0.t-ipconnect.de> has quit IRC (Quit: Leaving)
3382022-03-17T17:12:34  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
3392022-03-17T17:12:52  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
3402022-03-17T17:12:57  *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
3412022-03-17T17:15:49  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 240 seconds)
3422022-03-17T17:20:29  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
3432022-03-17T17:21:18  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
3442022-03-17T17:35:03  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has joined #bitcoin-core-dev
3452022-03-17T17:35:28  *** NorrinRadd <NorrinRadd!~username@> has joined #bitcoin-core-dev
3462022-03-17T17:40:10  *** NorrinRadd <NorrinRadd!~username@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)
3472022-03-17T17:41:18  *** Flow <Flow!~none@gentoo/developer/flow> has quit IRC (Ping timeout: 252 seconds)
3482022-03-17T17:49:43  *** Flow <Flow!~none@gentoo/developer/flow> has joined #bitcoin-core-dev
3492022-03-17T18:05:44  *** NOD32Admin <NOD32Admin!~Willtech@user/Willtech> has quit IRC (Read error: Connection reset by peer)
3502022-03-17T18:05:48  *** brunoerg <brunoerg!~brunoerg@> has quit IRC (Remote host closed the connection)
3512022-03-17T18:06:21  *** NOD32Admin <NOD32Admin!~Willtech@user/Willtech> has joined #bitcoin-core-dev
3522022-03-17T18:06:34  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
3532022-03-17T18:07:36  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
3542022-03-17T18:08:33  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
3552022-03-17T18:09:17  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
3562022-03-17T18:10:58  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has joined #bitcoin-core-dev
3572022-03-17T18:15:12  *** jouke <jouke!~jouke@> has joined #bitcoin-core-dev
3582022-03-17T18:17:01  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has quit IRC (Ping timeout: 250 seconds)
3592022-03-17T18:19:17  *** shesek <shesek!~shesek@user/shesek> has quit IRC (Remote host closed the connection)
3602022-03-17T18:23:43  *** brunoerg <brunoerg!~brunoerg@> has joined #bitcoin-core-dev
3612022-03-17T18:25:39  *** Talkless <Talkless!~Talkless@mail.dargis.net> has joined #bitcoin-core-dev
3622022-03-17T18:26:03  *** NOD32Admin <NOD32Admin!~Willtech@user/Willtech> has quit IRC (Quit: NOD32Admin)
3632022-03-17T18:26:42  *** NOD32Admin <NOD32Admin!~Willtech@user/Willtech> has joined #bitcoin-core-dev
3642022-03-17T18:46:41  *** ifeanyi <ifeanyi!~ifeanyi@> has joined #bitcoin-core-dev
3652022-03-17T18:46:55  *** jonatack <jonatack!jonatack@user/jonatack> has joined #bitcoin-core-dev
3662022-03-17T18:53:12  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
3672022-03-17T18:53:12  <bitcoin-git> [bitcoin] MarcoFalke opened pull request #24605: 2203 mini 🐧 (master...2203-mini-🐧) https://github.com/bitcoin/bitcoin/pull/24605
3682022-03-17T18:53:12  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3692022-03-17T18:55:25  *** gnaf <gnaf!~gnaf@51-15-187-53.rev.poneytelecom.eu> has joined #bitcoin-core-dev
3702022-03-17T19:00:09  <laanwj> #startmeeting
3712022-03-17T19:00:10  <core-meetingbot`> Meeting started Thu Mar 17 19:00:09 2022 UTC.  The chair is laanwj. Information about MeetBot at https://bitcoin.jonasschnelli.ch/ircmeetings.
3722022-03-17T19:00:10  <core-meetingbot`> Available commands: action commands idea info link nick
3732022-03-17T19:00:13  <achow101> hi
3742022-03-17T19:00:17  <stickies-v> hi
3752022-03-17T19:00:43  <hebasto> hi
3762022-03-17T19:00:55  <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
3772022-03-17T19:00:56  <laanwj> morcos nehan NicolasDorier paveljanik petertodd phantomcircuit promag provoostenator ryanofsky sdaftuar sipa vasild
3782022-03-17T19:01:03  <provoostenator> hi
3792022-03-17T19:01:23  <cfields_> hi
3802022-03-17T19:01:24  <laanwj> welcome to the weekly bitcoin-core-dev general meeting
3812022-03-17T19:01:28  <dongcarl> hi
3822022-03-17T19:02:09  <laanwj> there has been one proposed topic: important changes in 23.0 to cover in the new RC Testing Guide (stickies-v)
3832022-03-17T19:02:14  <MarcoFalke> #proposedmeetingtopic Adjusted time offset warning
3842022-03-17T19:02:15  <laanwj> any last minute additional ones?
3852022-03-17T19:02:32  <laanwj> MarcoFalke: ok
3862022-03-17T19:03:02  <michaelfolkson> hi
3872022-03-17T19:03:30  <laanwj> #topic High priority for review
3882022-03-17T19:03:30  <core-meetingbot`> topic: High priority for review
3892022-03-17T19:03:37  <laanwj> let's start with high prio as usual
3902022-03-17T19:04:03  <laanwj> https://github.com/bitcoin/bitcoin/projects/8  at the moment there's 8 blockers, 1 chasing concept ACK
3912022-03-17T19:04:21  <laanwj> anything to add/remove, or that's almost ready for merge?
3922022-03-17T19:04:39  <laanwj> #24058 was added outside the meeting last week
3932022-03-17T19:04:42  <gribble> https://github.com/bitcoin/bitcoin/issues/24058 | BIP-322 basic support by kallewoof · Pull Request #24058 · bitcoin/bitcoin · GitHub
3942022-03-17T19:04:55  <MarcoFalke> #23595 for me pls
3952022-03-17T19:04:55  <gribble> https://github.com/bitcoin/bitcoin/issues/23595 | util: Add ParseHex () helper by MarcoFalke · Pull Request #23595 · bitcoin/bitcoin · GitHub
3962022-03-17T19:05:37  *** Flow <Flow!~none@gentoo/developer/flow> has quit IRC (Ping timeout: 240 seconds)
3972022-03-17T19:06:05  <laanwj> MarcoFalke: added
3982022-03-17T19:06:20  *** brunoerg <brunoerg!~brunoerg@> has quit IRC (Remote host closed the connection)
3992022-03-17T19:06:29  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
4002022-03-17T19:06:42  <MarcoFalke> dank
4012022-03-17T19:06:45  <jonatack> hi
4022022-03-17T19:06:52  <luke-jr> maybe add #22693 for me
4032022-03-17T19:06:53  <gribble> https://github.com/bitcoin/bitcoin/issues/22693 | RPC/Wallet: Add "use_txids" to output of getaddressinfo by luke-jr · Pull Request #22693 · bitcoin/bitcoin · GitHub
4042022-03-17T19:07:18  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
4052022-03-17T19:07:23  <laanwj> luke-jr: added
4062022-03-17T19:07:29  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
4072022-03-17T19:07:36  <luke-jr> ty
4082022-03-17T19:07:42  <jonatack> may i please add #24555 (targets backport to v23)
4092022-03-17T19:07:44  <gribble> https://github.com/bitcoin/bitcoin/issues/24555 | doc: create initial doc/cjdns.md for CJDNS how-to documentation by jonatack · Pull Request #24555 · bitcoin/bitcoin · GitHub
4102022-03-17T19:08:12  <jeremyrubin> hi
4112022-03-17T19:08:28  <laanwj> jonatack: done
4122022-03-17T19:08:37  <jonatack> laanwj: thank you
4132022-03-17T19:08:59  *** brunoerg <brunoerg!~brunoerg@> has joined #bitcoin-core-dev
4142022-03-17T19:10:01  <laanwj> i guess that was it for high prio, let's move to next topic
4152022-03-17T19:10:13  <laanwj> #topic Important changes in 23.0 to cover in the new RC Testing Guide (stickies-v)
4162022-03-17T19:10:14  <core-meetingbot`> topic: Important changes in 23.0 to cover in the new RC Testing Guide (stickies-v)
4172022-03-17T19:10:29  <stickies-v> Context: I've started working on updating the 23.0 RC Testing Guide, and I'd like to get some early feedback on which changes are considered important and useful to test since we don't have too much until release date.
4182022-03-17T19:10:40  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
4192022-03-17T19:10:42  <stickies-v> From the release notes (https://github.com/bitcoin-core/bitcoin-devwiki/wiki/23.0-Release-Notes-draft), I've selected the 5 changes I think most worthwhile to test, and 1 extra if I have time to get to it. I'd very much appreciate feedback on if you think anything else should really be included, and if maybe something can be omitted.
4202022-03-17T19:10:56  <stickies-v> The changes I've selected are (in random order, summarized from release notes):
4212022-03-17T19:10:57  <luke-jr> stickies-v: release dates are not firm; it's ready when it's ready
4222022-03-17T19:11:24  <stickies-v> 1. The strong preference for only connecting to peers that listen the standard port 8333 has been removed.  (#23542)
4232022-03-17T19:11:29  *** brunoerg <brunoerg!~brunoerg@> has quit IRC (Remote host closed the connection)
4242022-03-17T19:11:29  <stickies-v> 2. Descriptor wallets are now the default wallet type. Newly created wallets will use descriptors unless descriptors=false is set during createwallet.
4252022-03-17T19:11:30  <gribble> https://github.com/bitcoin/bitcoin/issues/23542 | net: open p2p connections to nodes that listen on non-default ports by vasild · Pull Request #23542 · bitcoin/bitcoin · GitHub
4262022-03-17T19:11:35  <stickies-v> 3. The validateaddress RPC now returns an error_locations array for invalid addresses, with the indices of invalid character locations in the address (if known). (#16807)
4272022-03-17T19:11:38  <gribble> https://github.com/bitcoin/bitcoin/issues/16807 | Let validateaddress locate error in Bech32 address by meshcollider · Pull Request #16807 · bitcoin/bitcoin · GitHub
4282022-03-17T19:11:39  <stickies-v> 4. The getblock RPC command and /rest/block/ REST endpoint now support verbosity level 3 containing transaction inputs' prevout information.
4292022-03-17T19:11:43  <stickies-v> 5. Information on soft fork status has been moved from getblockchaininfo to the new getdeploymentinfo RPC which allows querying soft fork status at any block, rather than just at the chain tip. (#23508)
4302022-03-17T19:11:49  <gribble> https://github.com/bitcoin/bitcoin/issues/23508 | Add getdeploymentinfo RPC by ajtowns · Pull Request #23508 · bitcoin/bitcoin · GitHub
4312022-03-17T19:12:02  <laanwj> i don't think 1 is straightforward to test
4322022-03-17T19:12:02  <stickies-v> The additional change if I get to it in time is:
4332022-03-17T19:12:02  <stickies-v> 6. A bitcoind node will only rumour addresses to inbound peers after they've sent an ADDR, ADDRV2, or GETADDR message. (#21528)
4342022-03-17T19:12:09  <gribble> https://github.com/bitcoin/bitcoin/issues/21528 | [p2p] Reduce addr blackholes by amitiuttarwar · Pull Request #21528 · bitcoin/bitcoin · GitHub
4352022-03-17T19:12:31  <laanwj> because nothing will really give you non-8333 ports frequently yet (e.g. the DNS seeds strongly prefer 8333)
4362022-03-17T19:12:34  <luke-jr> laanwj: well, testers can at least verify they have 8 peers that look randomish?
4372022-03-17T19:12:45  *** jouke <jouke!~jouke@> has quit IRC (Ping timeout: 256 seconds)
4382022-03-17T19:12:58  <michaelfolkson> And 2 isn't new for this release. Not sure if that should be a focus?
4392022-03-17T19:13:01  <laanwj> sure, you can test that you still get usable peers
4402022-03-17T19:13:15  <hebasto> owners of Apple M1 could test native arm64 binaries
4412022-03-17T19:13:23  <laanwj> hebasto: yes, that's a good one
4422022-03-17T19:13:32  <luke-jr> and they don't get deleted :P
4432022-03-17T19:13:42  <hebasto> indeed
4442022-03-17T19:13:49  <stickies-v> hebasto: thanks I'll include that
4452022-03-17T19:14:05  <laanwj> stickies-v: thanks for working on this btw
4462022-03-17T19:14:06  <jonatack> stickies: would be nice to test bitcoind over CJDNS, including IBD with -onlynet=cjdns and dns seeds
4472022-03-17T19:14:40  *** Flow <Flow!~none@gentoo/developer/flow> has joined #bitcoin-core-dev
4482022-03-17T19:15:30  <stickies-v> jonatack: cool, will add that too
4492022-03-17T19:16:05  <jonatack> stickies-v:  great
4502022-03-17T19:16:13  <stickies-v> I was thinking the non-default port could be tested on regtest, since it does seem like quite an important change for the network going forward?
4512022-03-17T19:16:38  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has joined #bitcoin-core-dev
4522022-03-17T19:17:51  <stickies-v> achow101: what do you think about michaelfolkson's comment regarding descriptor wallet becoming default not being important to include in the testing as it's not a new change?
4532022-03-17T19:18:02  <jonatack> stickies-v: you might be able to easily recycle the I2P testing in the last release testing, and link to doc/cjdns.md in #24555
4542022-03-17T19:18:04  <gribble> https://github.com/bitcoin/bitcoin/issues/24555 | doc: create initial doc/cjdns.md for CJDNS how-to documentation by jonatack · Pull Request #24555 · bitcoin/bitcoin · GitHub
4552022-03-17T19:18:15  <laanwj> i don't think port preference ever plays a role on regtest, as all connections are manual
4562022-03-17T19:18:28  <luke-jr> were there any major changes to descriptor wallets between 21/22.x and 23.x?
4572022-03-17T19:18:33  <luke-jr> besides adding Taproot
4582022-03-17T19:18:56  <jonatack> (e.g. convert the I2P testing section for v22 to CJDNS)
4592022-03-17T19:19:08  <stickies-v> hmm okay didn't know that, will reconsider 1. then and leave it out if I don't find any good way to test efficiently
4602022-03-17T19:19:14  <achow101> stickies-v: I don't feel strongly either way. frankly, it's such a small change that there isn't much that could go wrong
4612022-03-17T19:19:17  <laanwj> but if you consider it like that, all functional tests test non-default ports, as they pseudo-randomly assign ports
4622022-03-17T19:20:15  <MarcoFalke> I think the most important testing is of the parts that everyone assumes *not* to be changed.
4632022-03-17T19:20:52  <luke-jr> true
4642022-03-17T19:21:02  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has quit IRC (Ping timeout: 240 seconds)
4652022-03-17T19:21:04  <MarcoFalke> Surely, it is important that new features are tested, but even more importantly everything else shouldn't break
4662022-03-17T19:21:04  <jonatack> 3, 4, and 5 may be well-tested already (if I'm not mistaken), not sure if there is much value in people checking those
4672022-03-17T19:21:08  <laanwj> also testing it with third-party programs is always interesting (i guess e.g. joinmarket, c-lightning are covered)
4682022-03-17T19:21:09  <lightlike> I think it should work to addpeeradress a couple of fantasy addresses with default/non default ports and take statistics what it tries to connect to.
4692022-03-17T19:22:04  <luke-jr> new features are probably more tested already too
4702022-03-17T19:22:10  <MarcoFalke> Jup, any business or third party software should have a test suite to check that their use of Bitcoin Core doesn't break with an upgrade
4712022-03-17T19:22:28  <stickies-v> MarcoFalke: that's a good point but I'm not sure if that's something we can make actionable in this testing guide?
4722022-03-17T19:22:48  *** brunoerg <brunoerg!~brunoerg@> has joined #bitcoin-core-dev
4732022-03-17T19:22:52  <stickies-v> I think it's more of an intro get people familiar with testing and with what's changing
4742022-03-17T19:22:56  <laanwj> right, the testing guide is more about giving peopel specific focus what they could test, if it's just "what you are doing already" it's short
4752022-03-17T19:24:17  <stickies-v> alright thank you for the ideas everyone, I'll look into all of these suggestions and revert next week with a draft of the guide
4762022-03-17T19:24:29  <michaelfolkson> Ok makes sense. Leave it up to your judgment then stickies-v :)
4772022-03-17T19:24:30  <jonatack> right, the reason i mention the cjdns testing is also that there are more moving parts, platforms, cases and possible issues that may not have been seen yet
4782022-03-17T19:24:31  <laanwj> thanks!
4792022-03-17T19:24:40  <laanwj> let's move to next topic
4802022-03-17T19:24:45  <laanwj> #topic Adjusted time offset warning (MarcoFalke)
4812022-03-17T19:24:45  <core-meetingbot`> topic: Adjusted time offset warning (MarcoFalke)
4822022-03-17T19:25:07  <MarcoFalke> So while the adjusted time was improved over the last couple of years, it still has some shortcomings
4832022-03-17T19:25:14  *** An0rak <An0rak!An0rak@user/an0rak> has joined #bitcoin-core-dev
4842022-03-17T19:25:18  <laanwj> i've always felt really uncomfortable with the time adjustment code
4852022-03-17T19:25:31  <laanwj> can't we just like phase it out
4862022-03-17T19:25:45  <MarcoFalke> Just to mention a few: (1) non-monotonic (2) adjusted by peers ...
4872022-03-17T19:26:04  <MarcoFalke> So I was thinking to simply remove it and replace it with a stronger warning mechanism
4882022-03-17T19:26:27  <laanwj> adjusted by peers based on unauthenticated cleartext data, based on strange criteria which we're too scared to touch
4892022-03-17T19:26:36  <laanwj> ack
4902022-03-17T19:26:47  <luke-jr> sounds like a good idea IMO
4912022-03-17T19:26:57  *** brunoerg <brunoerg!~brunoerg@> has quit IRC (Ping timeout: 240 seconds)
4922022-03-17T19:27:01  <MarcoFalke> The question is how to warn?
4932022-03-17T19:27:12  <laanwj> isn't there a warnings field on some RPC call
4942022-03-17T19:27:13  <lightlike> what would that "stronger warning mechanism" look like?
4952022-03-17T19:27:20  <luke-jr> laanwj: GUI can probably use improvement
4962022-03-17T19:27:23  <MarcoFalke> We can't warn at startup, as only the local system time is available
4972022-03-17T19:27:38  <luke-jr> maybe the sync overlay could be a good place for it
4982022-03-17T19:28:11  <MarcoFalke> I think the GUI is already good. There will be a orange warning, very hard to miss
4992022-03-17T19:28:50  <laanwj> yes that seems fine to use
5002022-03-17T19:28:55  <MarcoFalke> (For reference there is a long thread at #4521 with cross-links)
5012022-03-17T19:28:56  <gribble> https://github.com/bitcoin/bitcoin/issues/4521 | AddTimeData will never update nTimeOffset past 199 samples · Issue #4521 · bitcoin/bitcoin · GitHub
5022022-03-17T19:28:57  <laanwj> it doesn't have to be at startup
5032022-03-17T19:29:23  <laanwj> warnings can be added at any time (it is, or was, used for some other network conditions too)
5042022-03-17T19:29:26  <MarcoFalke> So one option I was thinking about was to just shut down the node. Does that seem too agressive?
5052022-03-17T19:29:33  <laanwj> way too aggressive
5062022-03-17T19:29:47  <laanwj> just log a message and make it available on a RPC call
5072022-03-17T19:29:56  <laanwj> like we've always done for warnings
5082022-03-17T19:30:19  <MarcoFalke> It seems unlikely the user will ping the RPC regularly to get the warning
5092022-03-17T19:30:22  <laanwj> making it possible for peers to shut down your node by flooding you with massaged time values is even worse than we have now
5102022-03-17T19:30:30  <laanwj> for fact, they do
5112022-03-17T19:30:48  <luke-jr> maybe safe mode wasn't a terrible idea
5122022-03-17T19:30:49  <laanwj> or at least used to when warnings were more common i don't know nowadays
5132022-03-17T19:31:02  <MarcoFalke> ok, good point
5142022-03-17T19:31:22  *** JesseBarton <JesseBarton!~JesseBart@ip72-203-188-10.tu.ok.cox.net> has quit IRC (Quit: Client closed)
5152022-03-17T19:31:25  <luke-jr> laanwj: otoh, if all your peers are, maybe you want new peers..
5162022-03-17T19:31:27  <MarcoFalke> luke-jr: I don't think there is a need to shut down the wallet? I think this mostly affects the mining code
5172022-03-17T19:31:45  <luke-jr> MarcoFalke: I would expect miners to be monitoring the node state closely
5182022-03-17T19:32:12  <laanwj> i think it would be valid to strip out the time adjustment system completely, just leave it up to the user's responsibility to have their time correct, like other software does
5192022-03-17T19:32:14  <MarcoFalke> So my other idea was to throw an exception in getblocktemplate. Does that seem too agressive?
5202022-03-17T19:32:22  <laanwj> having a warning is nice but i don't see it as cirical
5212022-03-17T19:32:47  <laanwj> not sure why this would need a more aggressive mechanism than other warnings
5222022-03-17T19:32:57  <luke-jr> MarcoFalke: also, miners are likely to internally only have peers with their own nodes
5232022-03-17T19:33:14  <luke-jr> so throwing in GBT won't be helpful IMO
5242022-03-17T19:33:21  <jeremyrubin> could also have something like walletnotify where we call a script to get the time
5252022-03-17T19:34:05  <jeremyrubin> that would make it possible for pluggin in an arbiitrary time source if users don't want their system time
5262022-03-17T19:34:09  <laanwj> come on, it's 2022, computers tend to have correct system time these days
5272022-03-17T19:34:26  <luke-jr> jeremyrubin: idk why we would support not using system time
5282022-03-17T19:34:45  <laanwj> if you want to mess aroudn with the time for whatever reason there's faketime and even time namespaces in newer linux kernels
5292022-03-17T19:34:48  <MarcoFalke> ok, I mean I am fine just removing it. I just wanted to see if there is something we could do better
5302022-03-17T19:34:52  <luke-jr> laanwj: exactly
5312022-03-17T19:35:34  <luke-jr> we have mockable time too
5322022-03-17T19:35:41  <jeremyrubin> i just mean that if you want behavior for "my peers think the time is different" you could let that be configured as a script callback
5332022-03-17T19:35:42  <MarcoFalke> luke-jr: Not for main-net
5342022-03-17T19:35:50  <laanwj> MarcoFalke: so i would say the proposal to change it to a warning is fine, for now, it can always be fully removed later if we want, but i don't think it needs a more aggressive mechanism
5352022-03-17T19:36:06  <luke-jr> MarcoFalke: could be trivially enabled if desired
5362022-03-17T19:36:09  <MarcoFalke> laanwj: I think a warning already exists
5372022-03-17T19:36:19  <MarcoFalke> I can add a new dedicated RPC for it, too
5382022-03-17T19:36:26  <laanwj> not sure a dedicated RPC would be better
5392022-03-17T19:36:37  <jeremyrubin> (you can also crontab and parse the log for the warning, which is fine)
5402022-03-17T19:36:38  <laanwj> things like warnings are better grouped, so people don't have to listen for everything separately
5412022-03-17T19:36:47  <MarcoFalke> I guess a dedicated RPC would make jeremyrubin also happy
5422022-03-17T19:37:14  <laanwj> don't we have the time delta in RPC already somewhere
5432022-03-17T19:37:27  <MarcoFalke> getpeerinfo, maybe?
5442022-03-17T19:37:46  <MarcoFalke> At least the GUI shows it in the peers tab
5452022-03-17T19:37:48  * jeremyrubin ponders the nature of happiness 
5462022-03-17T19:38:19  <jeremyrubin> i will say that a good portion of nodes might be running on centralized time servers
5472022-03-17T19:38:52  <laanwj> i think it's ok to make the information available, dont' think a new RPC is worth it
5482022-03-17T19:38:54  <jeremyrubin> so this might be giving someone somewhere the "brick all the nodes" key
5492022-03-17T19:39:01  <jonatack> getpeerinfo has a timeoffset field in seconds
5502022-03-17T19:39:03  <jeremyrubin> but i don't think it's the biggest deal
5512022-03-17T19:39:11  <laanwj> it's not like the time adjustment scheme really protected against that
5522022-03-17T19:39:39  <luke-jr> jeremyrubin: … someone who can centrally control your server's time, can probably just shut off the power too
5532022-03-17T19:39:40  <laanwj> if you can sabotage a centralized timeserver sure you could mess up things for a bit until people figure it out
5542022-03-17T19:40:09  <jeremyrubin>  luke-jr: i would expect apple can change my laptops time, but i don't think they can shut my power off
5552022-03-17T19:40:23  <laanwj> they could probably delete all software from your system at least
5562022-03-17T19:40:35  <luke-jr> that seems naive, but I understand - thought you meant VPS with a shared kernel
5572022-03-17T19:40:44  <MarcoFalke> adjusted time really only protects against a 30 or 60 minute offset (DST/time zone) for at most half a year
5582022-03-17T19:41:40  <laanwj> in any case, if you're serious about mitigating attacks on timeservers i'd guess that has a much bigger scope than bitcoin
5592022-03-17T19:41:58  <laanwj> like, run your own atomic clock and adjust your system time to it
5602022-03-17T19:42:39  <MarcoFalke> adjust your system time to Bitcoin (timechain) MTP
5612022-03-17T19:43:06  <laanwj> btw, ntp also allows for only very small on the fly changes
5622022-03-17T19:43:09  <MarcoFalke> (obviously don't do that)
5632022-03-17T19:43:20  <laanwj> it's not like your ntp server can suddenly warp you back hours or days
5642022-03-17T19:44:28  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has joined #bitcoin-core-dev
5652022-03-17T19:45:06  <luke-jr> MarcoFalke: might not be terrible tbh
5662022-03-17T19:45:12  <luke-jr> if you have a working monotonic clock
5672022-03-17T19:45:23  <laanwj> at boot up it will probably accept any time, especially on embedded systems without a RTC, but that's also easiest to detect
5682022-03-17T19:45:37  <MarcoFalke> luke-jr: You might miss blocks if MTP is lagging too much
5692022-03-17T19:46:53  <laanwj> it's also hardly a 'brick all the nodes' key if you have to wait for all servers running nodes to reboot first :)
5702022-03-17T19:47:39  <Earnest> monotonic vs bootime might be worth considering as monotonic clocks tend to stop when systems sleep afaiui
5712022-03-17T19:48:06  <luke-jr> MarcoFalke: well, you'd have to do MTP + 30 minutes at least. a bit of buffer would help handle stuff like this.
5722022-03-17T19:48:11  *** ifeanyi <ifeanyi!~ifeanyi@> has quit IRC (Ping timeout: 250 seconds)
5732022-03-17T19:48:21  <Earnest> Ah, nevermind https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d6ed449afdb38f89a7b38ec50e367559e1b8f71f
5742022-03-17T19:48:53  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has quit IRC (Ping timeout: 252 seconds)
5752022-03-17T19:48:56  <luke-jr> laanwj: modern systems constantly sync their clocks over NTP, not just at boot
5762022-03-17T19:48:58  <laanwj> Earnest: monotonic clocks are only used for measuring time intervals, so that's fine, usually
5772022-03-17T19:49:05  <luke-jr> though maybe only within some limited drift
5782022-03-17T19:49:09  <laanwj> luke-jr: yes, but only minimal adjustments
5792022-03-17T19:49:50  <laanwj> at least that's how linux ntpd works, i have no idea about other OSes
5802022-03-17T19:50:20  <luke-jr> lots of people use systemd OS now :p
5812022-03-17T19:50:38  *** brunoerg <brunoerg!~brunoerg@> has joined #bitcoin-core-dev
5822022-03-17T19:50:55  <luke-jr> (it ate ntpd)
5832022-03-17T19:51:23  <jonatack> getnetworkinfo has a timeoffset field that is our GetTimeOffset() result, IIUC,  as opposed to the offset for each peer in getpeerinfo
5842022-03-17T19:51:25  <Earnest> As systemd-timesyncd which is sntpd implementation
5852022-03-17T19:51:42  <laanwj> i mean, with all the complications and exceptions it's not realistic as an attack on bitcoin, that's all i was trying to say
5862022-03-17T19:52:14  <laanwj> jonatack: nice, so that too already exists
5872022-03-17T19:53:27  <luke-jr> maybe getblocktemplate should throw if there's a known better-except-for-time-just-barely block?
5882022-03-17T19:53:41  <luke-jr> seems more likely to cause than solve problems tho
5892022-03-17T19:54:14  <MarcoFalke> luke-jr: How often did that happen in the last 10 years?
5902022-03-17T19:54:19  *** Guest28 <Guest28!~Guest28@> has joined #bitcoin-core-dev
5912022-03-17T19:54:26  <luke-jr> MarcoFalke: no clue
5922022-03-17T19:54:43  <jonatack> (and only outbound peers offsets contribute to our timedata samples to make it harder for peers to tamper with our adjusted time... src/net_processing.cpp::2761)
5932022-03-17T19:54:55  *** brunoerg <brunoerg!~brunoerg@> has quit IRC (Ping timeout: 256 seconds)
5942022-03-17T19:54:56  <luke-jr> kinda doubt miners would risk getting so close to the time cutoff
5952022-03-17T19:55:00  <Guest28> stickies-v: 1 can be tested for non default ports, you just need to look for nodes that are using such ports. There are different ways to do it.
5962022-03-17T19:56:32  <laanwj> right i would be surprised if miners weren't already really careful about having correct time on their machines, to rule that out as a reason to miss a block reward
5972022-03-17T19:56:37  *** Guest28 <Guest28!~Guest28@> has quit IRC (Client Quit)
5982022-03-17T19:56:42  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has joined #bitcoin-core-dev
5992022-03-17T19:57:48  <laanwj> any well-meaning protective mechanism added on top might just get in the way in case of some edge case
6002022-03-17T19:58:26  <MarcoFalke> Even if one miner is back by 1h and another one forward by 1h, it shouldn't lead to any issues
6012022-03-17T19:58:37  <MarcoFalke> Only if the difference is more than 2h
6022022-03-17T19:58:42  <laanwj> sure
6032022-03-17T19:59:32  <MarcoFalke> Well, thanks everyone for the input!
6042022-03-17T20:00:25  <laanwj> it's time to close the meeting
6052022-03-17T20:00:28  <laanwj> #endmeeting
6062022-03-17T20:00:28  <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
6072022-03-17T20:00:28  <core-meetingbot`> Meeting ended Thu Mar 17 20:00:27 2022 UTC.
6082022-03-17T20:00:28  <core-meetingbot`> Minutes:        https://bitcoin.jonasschnelli.ch/ircmeetings/logs/bitcoin-core-dev/2022/bitcoin-core-dev.2022-03-17-19.00.moin.txt
6092022-03-17T20:04:12  <jonatack> I wonder how many people adjust the -maxtimeadjustment config option (default 70 minutes) on their nodes and with what values
6102022-03-17T20:04:32  <jonatack> miners, maybe?
6112022-03-17T20:05:46  <dongcarl> Hi all I just set up https://github.com/bitcoin/bitcoin/projects/18 to keep track of all the libbitcoinkernel PRs
6122022-03-17T20:06:31  <laanwj> dongcarl: awesome!
6132022-03-17T20:06:41  <dongcarl> One question: there are a few PRs which others have opened that will help make future work in libbitcoinkernel easier, can I add an "Relevant External PRs" column to keep track of those?
6142022-03-17T20:06:55  <jonatack> seems to be some good discussion of -maxtimeadjustment tradeoffs in #7573
6152022-03-17T20:06:57  <gribble> https://github.com/bitcoin/bitcoin/issues/7573 | P2P: add maxtimeadjustment command line option by mruddy · Pull Request #7573 · bitcoin/bitcoin · GitHub
6162022-03-17T20:07:28  <jonatack> dongcarl: nice / sgtm
6172022-03-17T20:07:47  <laanwj> i disabled time adjustment entirely for a while but i don't think i'm still bothering in my current configs
6182022-03-17T20:08:23  <laanwj> dongcarl: yes, feel free to organize the project board as is useful for you
6192022-03-17T20:08:41  *** An0rak <An0rak!An0rak@user/an0rak> has quit IRC ()
6202022-03-17T20:09:04  <dongcarl> Also, I'm a bit confused as to what the conclusion of the timedata conversation was above, will we remove it?
6212022-03-17T20:09:49  <laanwj> dongcarl: i don't think there was a conclusion
6222022-03-17T20:10:24  <dongcarl> Okay got it. Will operate under the assumption that we're not imminently removing it then
6232022-03-17T20:10:27  <jeremyrubin> one option we didn't discuss (i think?) is that we can phase it out by continuing to send out our time messages but not reading them... that way we don't let old nodes who rely on these time broadcasts get attacked
6242022-03-17T20:10:59  <jeremyrubin> so it can be a thing where we'll happily tell anyone our time, but not care about others time
6252022-03-17T20:13:15  <laanwj> i don't think there is any proposal to remove the time from version messages?
6262022-03-17T20:13:56  *** Talkless <Talkless!~Talkless@mail.dargis.net> has quit IRC (Quit: Konversation terminated!)
6272022-03-17T20:14:13  <laanwj> well i think i heard it mentioned as a fingerprinting vector once, but it's definitely not the same proposal as stopping doing time adjustment
6282022-03-17T20:16:29  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
6292022-03-17T20:16:29  <bitcoin-git> [bitcoin] MarcoFalke pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/8435d7f11a89...e09cf64c4828
6302022-03-17T20:16:29  <bitcoin-git> bitcoin/master bf84677 fanquake: doc: cleanup wallet docs in build-osx.md
6312022-03-17T20:16:29  <bitcoin-git> bitcoin/master 57f3f5c fanquake: doc: s/Compiler/Dependency in dependencies.md
6322022-03-17T20:16:29  <bitcoin-git> bitcoin/master e09cf64 MarcoFalke: Merge bitcoin/bitcoin#24585: doc: mention that BDB is for the legacy walle...
6332022-03-17T20:16:29  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
6342022-03-17T20:16:45  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
6352022-03-17T20:16:45  <bitcoin-git> [bitcoin] MarcoFalke merged pull request #24585: doc: mention that BDB is for the legacy wallet in build-osx.md (master...build_osx_descriptor_legacy_switch) https://github.com/bitcoin/bitcoin/pull/24585
6362022-03-17T20:16:45  *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
6372022-03-17T20:16:51  <jonatack> hm, maybe a first step (if people think it's an improvement) would be to change the default -maxtimeadjustment
6382022-03-17T20:16:59  <laanwj> it'd be a BIP level change; mind that the version message was always the only time adjustment input, there is no 'time message'
6392022-03-17T20:17:19  <MarcoFalke> We can save that for the cleanup-version-msg-bip
6402022-03-17T20:17:25  <laanwj> yes
6412022-03-17T20:17:33  <MarcoFalke> Pretty sure there is other stuff in the version message that needs to be removed
6422022-03-17T20:17:41  <laanwj> correct
6432022-03-17T20:18:34  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
6442022-03-17T20:19:20  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
6452022-03-17T20:19:34  <lightlike> just noting that with 23.0, we don't use any timestamps from inbound peers anymore (#23631) - that should help with some concerns at least.
6462022-03-17T20:19:35  <gribble> https://github.com/bitcoin/bitcoin/issues/23631 | p2p: Dont use timestamps from inbound peers for Adjusted Time by mzumsande · Pull Request #23631 · bitcoin/bitcoin · GitHub
6472022-03-17T20:19:55  <laanwj> that said, system time in seconds is a pretty lousy fingerprinting vector, and besides, it's also part of many lower level network packets already, so removing it from the bitcoin protocol doesn't do that much to prevent it being used
6482022-03-17T20:21:20  <jonatack> lightlike: yes, mentioned that during the meeting (https://www.erisian.com.au/bitcoin-core-dev/log-2022-03-17.html#l-592)
6492022-03-17T20:21:26  <laanwj> (this is where centralization of time actually helps for privacy i guess :-)
6502022-03-17T20:24:22  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has quit IRC (Read error: Connection reset by peer)
6512022-03-17T20:24:24  <MarcoFalke> lightlike: jonatack: right, that makes it harder to attack adjusted time, but it retains the issues of adjusted time that are present even in the absence of attacks
6522022-03-17T20:24:26  <jonatack> jeremyrubin: setting the default -maxtimeadjustment to 0 would take care of that, I guess
6532022-03-17T20:25:27  <jonatack> and users could opt in to allowing peers to adjust the timedata
6542022-03-17T20:25:34  <laanwj> so that would imply anyone would voluntarily want to enable it
6552022-03-17T20:26:01  <laanwj> but it definitely would be the most straightforward change, sure
6562022-03-17T20:28:05  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has joined #bitcoin-core-dev
6572022-03-17T20:35:31  *** hashfunc569 <hashfunc569!~user@2601:5c0:c280:7090:78e9:5f82:1899:8c96> has joined #bitcoin-core-dev
6582022-03-17T20:39:49  *** Guest28 <Guest28!~Guest28@> has joined #bitcoin-core-dev
6592022-03-17T20:40:42  <Guest28> Hi, I would like to know if there is some upcoming privacy method to Bitcoin Core. Even something basic like PayJoin would be nice. Thx!
6602022-03-17T20:41:13  <jonatack> yes, i don't know. people seemed to want it on by default in the discussion in #7573. perhaps things have changed as you mentioned earlier above.
6612022-03-17T20:41:15  <gribble> https://github.com/bitcoin/bitcoin/issues/7573 | P2P: add maxtimeadjustment command line option by mruddy · Pull Request #7573 · bitcoin/bitcoin · GitHub
6622022-03-17T20:42:18  <jonatack> Guest28: see https://github.com/bitcoin-core/bitcoin-devwiki/wiki/23.0-Release-Notes-draft
6632022-03-17T20:42:55  <Guest28> jonatack ok, thx! ;)
6642022-03-17T20:45:44  <Guest28> jonatack I don't find any information related to transaction privacy there
6652022-03-17T20:45:54  <jonatack> hm, cjdns isn't in the release notes
6662022-03-17T20:46:17  <Guest28> (I mean blockchain privacy, not Tor related features)
6672022-03-17T20:46:59  <jonatack> Guest28: there may be some items still missing from the release notes draft, but IIRC not a change like you are looking for in v23
6682022-03-17T20:49:02  <Guest28> jonatack ok! Is there any chance the upcoming Mimblewimble solution on extension blocks on Litecoin will come to Bitcoin Core? :)
6692022-03-17T20:50:38  <Guest28> All risks are contained to the extension block and increases capacity as MW transactions are very small. People could have their savings in the main block (public) and use the extension block for their expenses.
6702022-03-17T20:51:29  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
6712022-03-17T20:52:13  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
6722022-03-17T20:54:36  <laanwj> this channel is for implementation issues, the mailing list or #bitcoin-wizards would be a better place to discuss proposed consensus changes
6732022-03-17T20:55:41  <Guest28> laanwj ok, I will ask there, thx! :)
6742022-03-17T20:56:22  <laanwj> jonatack: yes, not sure how much changed in opinions there since 2016, i've always been uncomfortable with the node time adjustment system as it is (also clear from my replies there), but not everyone shares that sentiment obviously
6752022-03-17T20:57:23  *** An0rak <An0rak!An0rak@user/an0rak> has joined #bitcoin-core-dev
6762022-03-17T20:57:38  *** An0rak <An0rak!An0rak@user/an0rak> has left #bitcoin-core-dev
6772022-03-17T20:58:08  *** An0rak <An0rak!An0rak@user/an0rak> has joined #bitcoin-core-dev
6782022-03-17T21:00:02  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has quit IRC (Ping timeout: 240 seconds)
6792022-03-17T21:01:33  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
6802022-03-17T21:02:14  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
6812022-03-17T21:02:17  *** brunoerg <brunoerg!~brunoerg@> has joined #bitcoin-core-dev
6822022-03-17T21:11:54  <jeremyrubin> jonatack: that seems right
6832022-03-17T21:13:20  *** Guest58 <Guest58!~Guest58@> has joined #bitcoin-core-dev
6842022-03-17T21:13:50  *** Guest28 <Guest28!~Guest28@> has quit IRC (Quit: byee)
6852022-03-17T21:14:08  <Guest58> jonatack: cjdns isnt a network focused on privacy: a) it is not shared in their goals or wp on github: https://github.com/cjdelisle/cjdns/blob/master/doc/projectGoals.md
6862022-03-17T21:14:10  <Guest58> b) testimonials prove its not a priority c) encryption is not always privacy
6872022-03-17T21:14:16  <Guest58> Its tring to solve different problems and using ipv6.
6882022-03-17T21:14:23  <Guest58> *trying
6892022-03-17T21:14:44  *** Guest58 <Guest58!~Guest58@> has quit IRC (Client Quit)
6902022-03-17T21:16:23  <laanwj> no, cjdns is not a privacy network, this is well-known, its usecase is for mesh networks, I2P and Tor are supported privacy overlay networks
6912022-03-17T21:18:57  <laanwj> besides, mind that privacy requires a large anonimity set so if that's your goal, using something more obscure than Tor or maybe I2P could end up making you less instead of more private
6922022-03-17T21:25:42  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
6932022-03-17T21:26:19  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
6942022-03-17T21:30:56  *** An0rak <An0rak!An0rak@user/an0rak> has quit IRC ()
6952022-03-17T21:35:55  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has joined #bitcoin-core-dev
6962022-03-17T21:39:27  *** Kaizen_K_ <Kaizen_K_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 252 seconds)
6972022-03-17T21:40:12  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745> has quit IRC (Ping timeout: 240 seconds)
6982022-03-17T21:49:30  *** Guyver2 <Guyver2!~Guyver@guyver2.xs4all.nl> has quit IRC (Quit: Going offline, see ya! (www.adiirc.com))
6992022-03-17T22:01:01  *** Kaizen_Kintsugi_ <Kaizen_Kintsugi_!~Kaizen_Ki@node-1w7jr9yi65te3r2qcrdmyaiye.ipv6.telus.net> has joined #bitcoin-core-dev
7002022-03-17T22:07:31  *** brunoerg <brunoerg!~brunoerg@> has quit IRC (Ping timeout: 256 seconds)
7012022-03-17T22:15:11  *** morcos <morcos!~morcos@gateway/tor-sasl/morcos> has quit IRC (Remote host closed the connection)
7022022-03-17T22:15:32  *** morcos <morcos!~morcos@gateway/tor-sasl/morcos> has joined #bitcoin-core-dev
7032022-03-17T22:17:32  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
7042022-03-17T22:18:20  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
7052022-03-17T22:26:32  *** hashfunc569 <hashfunc569!~user@2601:5c0:c280:7090:78e9:5f82:1899:8c96> has quit IRC (Ping timeout: 240 seconds)
7062022-03-17T22:28:06  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has joined #bitcoin-core-dev
7072022-03-17T22:30:39  *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
7082022-03-17T22:47:26  <jonatack> Guest58: yes sorry, I noticed that cjdns isn't in the release notes draft but didn't intend to suggest that it was an answer to your question.
7092022-03-17T22:59:10  *** Guest7843 <Guest7843!~Guest78@> has joined #bitcoin-core-dev
7102022-03-17T22:59:57  <Guest7843> jonatack: it wasnt me. we can select our own nick in webchat using this url: https://web.libera.chat/#bitcoin-core-dev and GuestN can be anyone. N depends if its available imo. Guest99 at 00:00 UTC wont me same as Guest99 at 00:30 most of the times.
7112022-03-17T23:01:08  *** Guest7843 <Guest7843!~Guest78@> has quit IRC (Client Quit)
7122022-03-17T23:02:08  *** vasild <vasild!~vd@user/vasild> has quit IRC (Remote host closed the connection)
7132022-03-17T23:02:19  *** vasild <vasild!~vd@user/vasild> has joined #bitcoin-core-dev
7142022-03-17T23:03:35  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
7152022-03-17T23:03:57  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
7162022-03-17T23:07:35  *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Remote host closed the connection)
7172022-03-17T23:11:42  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
7182022-03-17T23:12:02  *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
7192022-03-17T23:17:18  *** lucasdcf <lucasdcf!~lucasdcf@201-26-23-125.dsl.telesp.net.br> has quit IRC (Ping timeout: 250 seconds)
7202022-03-17T23:23:19  *** Guest63 <Guest63!~Guest63@> has joined #bitcoin-core-dev
7212022-03-17T23:24:11  *** Guest63 <Guest63!~Guest63@> has quit IRC (Client Quit)
7222022-03-17T23:31:43  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has quit IRC (Ping timeout: 256 seconds)
7232022-03-17T23:33:35  *** brunoerg <brunoerg!~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3> has joined #bitcoin-core-dev
7242022-03-17T23:35:09  *** szkl <szkl!uid110435@id-110435.uxbridge.irccloud.com> has joined #bitcoin-core-dev
7252022-03-17T23:38:06  *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
7262022-03-17T23:41:00  *** sipsorcery <sipsorcery!~sipsorcer@2a02:8084:6180:500::12b> has quit IRC (Ping timeout: 252 seconds)
7272022-03-17T23:47:36  *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Ping timeout: 240 seconds)
7282022-03-17T23:54:38  *** geyaeb <geyaeb!~geyaeb@gateway/tor-sasl/geyaeb> has quit IRC (Remote host closed the connection)
7292022-03-17T23:57:17  *** mudsip <mudsip!~mudsip@user/mudsip> has joined #bitcoin-core-dev
7302022-03-17T23:58:37  *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev