12021-08-26T00:43:48 *** Ananta-shesha <Ananta-shesha!~pjetcetal@2.95.210.196> has quit IRC (Quit: EXIT)
22021-08-26T00:44:13 *** Ananta-shesha <Ananta-shesha!~pjetcetal@2.95.210.196> has joined #bitcoin-core-dev
32021-08-26T01:04:32 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
42021-08-26T01:04:32 <bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/e08770bed187...f0461314815e
52021-08-26T01:04:32 <bitcoin-git> bitcoin/master 0d9fdd3 aitorjs: test, doc: refer to the correct variable names in p2p_invalid_tx.py
62021-08-26T01:04:32 <bitcoin-git> bitcoin/master f046131 fanquake: Merge bitcoin/bitcoin#22797: test, doc: refer to the correct variable name...
72021-08-26T01:04:34 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
82021-08-26T01:04:44 <fanquake> achow101: just the boost change, and the backports PR
92021-08-26T01:04:47 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
102021-08-26T01:04:47 <bitcoin-git> [bitcoin] fanquake merged pull request #22797: test, doc: refer to the correct variable names in p2p_invalid_tx.py (master...master) https://github.com/bitcoin/bitcoin/pull/22797
112021-08-26T01:04:48 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
122021-08-26T01:05:02 <fanquake> Want to get those in today / tomorrow so we can get rc3 out
132021-08-26T01:05:42 <achow101> which boost change?
142021-08-26T01:05:47 *** b10c <b10c!uid500648@id-500648.charlton.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)
152021-08-26T01:06:03 <fanquake> #22713
162021-08-26T01:06:05 <gribble> https://github.com/bitcoin/bitcoin/issues/22713 | Fix build with Boost 1.77.0 by sizeofvoid · Pull Request #22713 · bitcoin/bitcoin · GitHub
172021-08-26T01:07:56 <achow101> there seems to be some discussion about i2p issues(? not really following it), are we intending to deal with that for 22.0?
182021-08-26T01:08:25 *** jarthur <jarthur!~jarthur@2603-8080-1540-002d-c17a-6f80-b4b6-4b45.res6.spectrum.com> has quit IRC (Ping timeout: 250 seconds)
192021-08-26T01:10:05 *** _cold is now known as cold
202021-08-26T01:10:45 <fanquake> I'm also not really following it. Will have to look at any PRs / issues today. However I'm also not super concerned if i2p support isn't perfect at release.
212021-08-26T01:10:53 <fanquake> There's been a long time to get any problems solved, and the last thing we want to be doing is making more last minute changes to networking code.
222021-08-26T01:15:47 *** ExEric3 <ExEric3!~exeric3@178.132.3.92> has quit IRC (Ping timeout: 250 seconds)
232021-08-26T01:28:51 *** AaronvanW <AaronvanW!~AaronvanW@2800:b20:1114:da9:bd58:7418:5113:ed77> has joined #bitcoin-core-dev
242021-08-26T01:30:40 *** earnestly <earnestly!~earnest@user/earnestly> has quit IRC (Ping timeout: 240 seconds)
252021-08-26T01:45:13 *** jarthur <jarthur!~jarthur@2603-8080-1540-002d-81dc-4f45-3881-6bd3.res6.spectrum.com> has joined #bitcoin-core-dev
262021-08-26T02:01:07 *** AaronvanW <AaronvanW!~AaronvanW@2800:b20:1114:da9:bd58:7418:5113:ed77> has quit IRC (Ping timeout: 240 seconds)
272021-08-26T02:04:22 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
282021-08-26T02:23:29 *** Yihen <Yihen!~textual@103.138.75.117> has joined #bitcoin-core-dev
292021-08-26T02:44:54 *** jarthur <jarthur!~jarthur@2603-8080-1540-002d-81dc-4f45-3881-6bd3.res6.spectrum.com> has quit IRC (Quit: jarthur)
302021-08-26T02:48:05 <kalle> Is it possible to set up #bitcoin-dev channel somehow? Would like to discuss BIP process and that channel would've probably been ideal, as it's not a core thing and #bitcoin is not focused on development.
312021-08-26T02:48:58 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Ping timeout: 244 seconds)
322021-08-26T02:49:11 <sipa> the channel aparently exists, but is invite only
332021-08-26T02:49:17 <sipa> i don't know how runs it
342021-08-26T02:49:24 *** jarthur <jarthur!~jarthur@2603-8080-1540-002d-81dc-4f45-3881-6bd3.res6.spectrum.com> has joined #bitcoin-core-dev
352021-08-26T02:51:51 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
362021-08-26T02:57:39 <kalle> Ahh, that's why I couldn't join it
372021-08-26T03:11:58 <midnight> This place has a namespace which project contacts can enforce.. so if you want it, it can be grabbed.
382021-08-26T03:14:03 <midnight> I think the idea was that #bitcoin-dev was killed thanks to rando jgarzik, so I guess they assumed it was toxic-- so they just put +f #bitcoin on it.
392021-08-26T03:14:38 <midnight> (i.e. there's nothing going on in there)
402021-08-26T03:15:19 <midnight> In the prior network I believe -bips- discussion had its own channels.
412021-08-26T03:16:10 <midnight> Obv. whatever you want to happen will just happen. Rub the lamp, genie pops out, presto.
422021-08-26T03:36:28 <Yihen> is there someone focuse on miniscript?
432021-08-26T03:36:57 <Yihen> is it a new script for bitcoin?
442021-08-26T03:37:52 <Yihen> does it need to compile to bitcoin OP_CODE script?
452021-08-26T03:44:56 <sipa> see http://bitcoin.sipa.be/miniscript
462021-08-26T03:52:38 <Yihen> yeahï¼ I have read it yeasterday. but I don't know how to use it? I see you have developed a compiier for miniscript written by c++. In my opinion, it is compile ploicy to miniscript. @sipa
472021-08-26T03:53:39 <Yihen> can i test it with daemon? if yes, can you give me some guide? thanks a lot.
482021-08-26T03:53:59 <Yihen> daemon ---> bitcoin daemon
492021-08-26T03:54:32 <sipa> there are several implementations in various stages of development, but it's best to treat it as a research project currently
502021-08-26T03:54:47 <sipa> it is not implemented in bitcoin core
512021-08-26T03:58:28 *** ExEric3 <ExEric3!~exeric3@178.132.3.92> has joined #bitcoin-core-dev
522021-08-26T03:59:45 *** vasild <vasild!~vd@user/vasild> has quit IRC (Ping timeout: 244 seconds)
532021-08-26T04:00:50 <Yihen> The script system is the engine of Bitcoin transactions, and I am very interested in miniscript.
542021-08-26T04:00:54 *** jarthur <jarthur!~jarthur@2603-8080-1540-002d-81dc-4f45-3881-6bd3.res6.spectrum.com> has quit IRC (Quit: jarthur)
552021-08-26T04:01:01 *** cmirror <cmirror!~cmirror@4.53.92.114> has quit IRC (Remote host closed the connection)
562021-08-26T04:01:04 *** AaronvanW <AaronvanW!~AaronvanW@2800:b20:1114:da9:bd58:7418:5113:ed77> has joined #bitcoin-core-dev
572021-08-26T04:01:08 *** cmirror <cmirror!~cmirror@4.53.92.114> has joined #bitcoin-core-dev
582021-08-26T04:21:39 *** VzxPLnHqr <VzxPLnHqr!VzxPLnHqr@gateway/vpn/protonvpn/vzxplnhqr> has quit IRC (Remote host closed the connection)
592021-08-26T04:21:59 *** VzxPLnHqr <VzxPLnHqr!VzxPLnHqr@gateway/vpn/protonvpn/vzxplnhqr> has joined #bitcoin-core-dev
602021-08-26T04:28:58 *** VzxPLnHqr <VzxPLnHqr!VzxPLnHqr@gateway/vpn/protonvpn/vzxplnhqr> has quit IRC (Remote host closed the connection)
612021-08-26T04:29:03 *** VzxPLnHqr_ <VzxPLnHqr_!VzxPLnHqr@gateway/vpn/protonvpn/vzxplnhqr> has joined #bitcoin-core-dev
622021-08-26T04:31:39 *** AaronvanW <AaronvanW!~AaronvanW@2800:b20:1114:da9:bd58:7418:5113:ed77> has quit IRC (Ping timeout: 250 seconds)
632021-08-26T04:35:00 *** belcher <belcher!~belcher@user/belcher> has quit IRC (Ping timeout: 250 seconds)
642021-08-26T04:36:23 *** vasild <vasild!~vd@user/vasild> has joined #bitcoin-core-dev
652021-08-26T04:48:02 *** belcher <belcher!~belcher@user/belcher> has joined #bitcoin-core-dev
662021-08-26T04:52:41 *** jarthur <jarthur!~jarthur@2603-8080-1540-002d-81dc-4f45-3881-6bd3.res6.spectrum.com> has joined #bitcoin-core-dev
672021-08-26T04:56:38 *** vasild <vasild!~vd@user/vasild> has quit IRC (*.net *.split)
682021-08-26T04:56:38 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (*.net *.split)
692021-08-26T04:56:38 *** ghost43_ <ghost43_!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (*.net *.split)
702021-08-26T04:56:38 *** SpellChecker <SpellChecker!~SpellChec@gateway/tor-sasl/spellchecker> has quit IRC (*.net *.split)
712021-08-26T04:56:38 *** hex17or <hex17or!~hex17or@gateway/tor-sasl/hex17or> has quit IRC (*.net *.split)
722021-08-26T04:56:38 *** yanmaani <yanmaani!~yanmaani@gateway/tor-sasl/yanmaani> has quit IRC (*.net *.split)
732021-08-26T04:56:38 *** vnogueira <vnogueira!~vnogueira@user/vnogueira> has quit IRC (*.net *.split)
742021-08-26T04:56:38 *** aechu <aechu!~major@gateway/tor-sasl/major> has quit IRC (*.net *.split)
752021-08-26T05:04:08 *** vnogueira <vnogueira!~vnogueira@user/vnogueira> has joined #bitcoin-core-dev
762021-08-26T05:04:14 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
772021-08-26T05:04:39 *** SpellChecker <SpellChecker!~SpellChec@gateway/tor-sasl/spellchecker> has joined #bitcoin-core-dev
782021-08-26T05:06:43 *** vasild <vasild!~vd@user/vasild> has joined #bitcoin-core-dev
792021-08-26T05:06:50 *** hex17or <hex17or!~hex17or@gateway/tor-sasl/hex17or> has joined #bitcoin-core-dev
802021-08-26T05:07:24 *** aechu <aechu!~major@gateway/tor-sasl/major> has joined #bitcoin-core-dev
812021-08-26T05:07:28 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
822021-08-26T05:07:36 *** yanmaani <yanmaani!~yanmaani@gateway/tor-sasl/yanmaani> has joined #bitcoin-core-dev
832021-08-26T05:09:49 *** VzxPLnHqr_ <VzxPLnHqr_!VzxPLnHqr@gateway/vpn/protonvpn/vzxplnhqr> has quit IRC (Ping timeout: 252 seconds)
842021-08-26T05:20:51 *** SpellChecker <SpellChecker!~SpellChec@gateway/tor-sasl/spellchecker> has quit IRC (Quit: bye)
852021-08-26T05:28:11 *** SpellChecker <SpellChecker!~SpellChec@gateway/tor-sasl/spellchecker> has joined #bitcoin-core-dev
862021-08-26T05:34:54 *** DeanGuss <DeanGuss!~dean@user/deanguss> has quit IRC (Ping timeout: 268 seconds)
872021-08-26T05:59:14 <kalle> midnight: I don't think there was a bips channel, and I feel like a non-core-focused dev channel would be nice to have, at least. Whoever the genie is, I propose we try restoring #bitcoin-dev. :)
882021-08-26T06:10:26 *** raj <raj!~raj_@103.77.139.233> has joined #bitcoin-core-dev
892021-08-26T06:11:29 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
902021-08-26T06:11:29 <bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/f0461314815e...84be9a89c1a4
912021-08-26T06:11:29 <bitcoin-git> bitcoin/master fa2547f MarcoFalke: fuzz: Avoid timeout in blockfilter fuzz target
922021-08-26T06:11:29 <bitcoin-git> bitcoin/master 84be9a8 MarcoFalke: Merge bitcoin/bitcoin#22755: fuzz: Avoid timeout in blockfilter fuzz targe...
932021-08-26T06:11:31 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
942021-08-26T06:11:45 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
952021-08-26T06:11:45 <bitcoin-git> [bitcoin] MarcoFalke merged pull request #22755: fuzz: Avoid timeout in blockfilter fuzz target (master...2108-fuzzBlockfilter) https://github.com/bitcoin/bitcoin/pull/22755
962021-08-26T06:11:46 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
972021-08-26T06:26:13 *** vysn <vysn!~vysn@user/vysn> has joined #bitcoin-core-dev
982021-08-26T06:29:41 *** AaronvanW <AaronvanW!~AaronvanW@2800:b20:1114:da9:bd58:7418:5113:ed77> has joined #bitcoin-core-dev
992021-08-26T06:38:21 *** bitdex_ <bitdex_!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
1002021-08-26T06:38:36 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Ping timeout: 276 seconds)
1012021-08-26T06:50:09 *** upekkha <upekkha!~Advanced@2a01:4f8:1c0c:49df::1> has quit IRC (Quit: upekkha)
1022021-08-26T06:55:07 *** upekkha <upekkha!~Advanced@2a01:4f8:1c0c:49df::1> has joined #bitcoin-core-dev
1032021-08-26T07:00:47 *** AaronvanW <AaronvanW!~AaronvanW@2800:b20:1114:da9:bd58:7418:5113:ed77> has quit IRC (Ping timeout: 240 seconds)
1042021-08-26T07:03:21 *** Guyver2 <Guyver2!Guyver@guyver2.xs4all.nl> has joined #bitcoin-core-dev
1052021-08-26T07:25:01 *** gleb7 <gleb7!~gleb@178.150.137.228> has quit IRC (Quit: Ping timeout (120 seconds))
1062021-08-26T07:25:22 *** gleb7 <gleb7!~gleb@178.150.137.228> has joined #bitcoin-core-dev
1072021-08-26T07:28:47 *** Kiminuo <Kiminuo!~Kiminuo@107.150.94.37> has joined #bitcoin-core-dev
1082021-08-26T07:41:10 *** smartin <smartin!~Icedove@88.135.18.171> has joined #bitcoin-core-dev
1092021-08-26T07:43:03 *** earnestly <earnestly!~earnest@user/earnestly> has joined #bitcoin-core-dev
1102021-08-26T08:01:20 *** prayank <prayank!~andr0irc@51.15.9.205> has joined #bitcoin-core-dev
1112021-08-26T08:03:00 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1122021-08-26T08:03:00 <bitcoin-git> [bitcoin] MarcoFalke pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/84be9a89c1a4...cea38b491f6a
1132021-08-26T08:03:00 <bitcoin-git> bitcoin/master aa5e7c9 Kiminuo: Fix typo in bitcoin-cli.cpp
1142021-08-26T08:03:00 <bitcoin-git> bitcoin/master 25de4e7 Kiminuo: Use `context.args` in `CWallet::Create` instead of `gArgs`.
1152021-08-26T08:03:00 <bitcoin-git> bitcoin/master c3c2132 Kiminuo: Use `context.args` in `src/wallet/load.cpp`.
1162021-08-26T08:03:02 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1172021-08-26T08:03:17 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1182021-08-26T08:03:17 <bitcoin-git> [bitcoin] MarcoFalke merged pull request #22183: Remove `gArgs` from `wallet.h` and `wallet.cpp` (master...feature/2021-06-07-wallet-n-gArgs-min) https://github.com/bitcoin/bitcoin/pull/22183
1192021-08-26T08:03:18 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1202021-08-26T08:06:11 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1212021-08-26T08:06:11 <bitcoin-git> [bitcoin] MarcoFalke pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/cea38b491f6a...718d9f2f7727
1222021-08-26T08:06:11 <bitcoin-git> bitcoin/master 0eca5eb Sebastian Falbesoner: contrib: refactor: introduce bitcoin-cli RPC call helper in getcoins.py
1232021-08-26T08:06:11 <bitcoin-git> bitcoin/master 8c203cf Sebastian Falbesoner: contrib: catch bitcoin-cli RPC call errors in getcoins.py
1242021-08-26T08:06:11 <bitcoin-git> bitcoin/master 42dbd90 Sebastian Falbesoner: contrib: return non-zero status if getcoins.py errors
1252021-08-26T08:06:13 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1262021-08-26T08:06:28 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1272021-08-26T08:06:28 <bitcoin-git> [bitcoin] MarcoFalke merged pull request #22660: contrib: catch bitcoin-cli RPC call errors in getcoins.py (master...202107-script-signet_getcoins_catch_rpc_errors) https://github.com/bitcoin/bitcoin/pull/22660
1282021-08-26T08:06:30 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1292021-08-26T08:10:39 *** Yihen <Yihen!~textual@103.138.75.117> has quit IRC (Remote host closed the connection)
1302021-08-26T08:13:21 *** kabaum <kabaum!~kabaum@h-46-59-13-35.A163.priv.bahnhof.se> has quit IRC (Ping timeout: 248 seconds)
1312021-08-26T08:21:18 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1322021-08-26T08:21:18 <bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/718d9f2f7727...3a62b8b77e7b
1332021-08-26T08:21:18 <bitcoin-git> bitcoin/master acb7aad Rafael Sadowski: Fix build with Boost 1.77.0
1342021-08-26T08:21:18 <bitcoin-git> bitcoin/master 3a62b8b fanquake: Merge bitcoin/bitcoin#22713: Fix build with Boost 1.77.0
1352021-08-26T08:21:20 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1362021-08-26T08:21:35 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1372021-08-26T08:21:35 <bitcoin-git> [bitcoin] fanquake merged pull request #22713: Fix build with Boost 1.77.0 (master...boost-1770) https://github.com/bitcoin/bitcoin/pull/22713
1382021-08-26T08:21:36 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1392021-08-26T08:26:20 *** kabaum <kabaum!~kabaum@h-46-59-13-35.A163.priv.bahnhof.se> has joined #bitcoin-core-dev
1402021-08-26T08:29:05 *** DeanGuss <DeanGuss!~dean@nonplayercharacter.me> has joined #bitcoin-core-dev
1412021-08-26T08:52:08 *** Henrik <Henrik!~textual@84.212.107.177> has joined #bitcoin-core-dev
1422021-08-26T08:53:33 *** shiza <shiza!~admin@ec2-52-208-131-13.eu-west-1.compute.amazonaws.com> has quit IRC (Quit: maintenance)
1432021-08-26T08:59:00 *** AaronvanW <AaronvanW!~AaronvanW@2800:b20:1114:da9:bd58:7418:5113:ed77> has joined #bitcoin-core-dev
1442021-08-26T09:13:20 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1452021-08-26T09:13:20 <bitcoin-git> [bitcoin] MarcoFalke pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/3a62b8b77e7b...0492b56e38c2
1462021-08-26T09:13:20 <bitcoin-git> bitcoin/master 646b388 Sebastian Falbesoner: test: refactor: use named args for block_submit in feature_nulldummy.py
1472021-08-26T09:13:20 <bitcoin-git> bitcoin/master 7720d4f Sebastian Falbesoner: test: fix failure in feature_nulldummy.py on single-core machines
1482021-08-26T09:13:20 <bitcoin-git> bitcoin/master 0492b56 MarcoFalke: Merge bitcoin/bitcoin#22738: test: fix failure in feature_nulldummy.py on ...
1492021-08-26T09:13:22 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1502021-08-26T09:13:37 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1512021-08-26T09:13:37 <bitcoin-git> [bitcoin] MarcoFalke merged pull request #22738: test: fix failure in feature_nulldummy.py on single-core machines (master...202108-test-fix_nulldummy_test_on_singlecore) https://github.com/bitcoin/bitcoin/pull/22738
1522021-08-26T09:13:38 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1532021-08-26T09:13:52 *** goatpig <goatpig!~goat@blocksettle-gw.cust.31173.se> has joined #bitcoin-core-dev
1542021-08-26T09:14:19 *** shiza <shiza!~admin@ec2-52-208-131-13.eu-west-1.compute.amazonaws.com> has joined #bitcoin-core-dev
1552021-08-26T09:21:45 *** hex17or <hex17or!~hex17or@gateway/tor-sasl/hex17or> has quit IRC (Ping timeout: 276 seconds)
1562021-08-26T09:24:36 *** prayank <prayank!~andr0irc@51.15.9.205> has quit IRC (Quit: irc thread exit)
1572021-08-26T09:27:05 *** vysn <vysn!~vysn@user/vysn> has quit IRC (Quit: WeeChat 3.2)
1582021-08-26T09:28:55 *** hex17or <hex17or!~hex17or@gateway/tor-sasl/hex17or> has joined #bitcoin-core-dev
1592021-08-26T09:31:24 *** AaronvanW <AaronvanW!~AaronvanW@2800:b20:1114:da9:bd58:7418:5113:ed77> has quit IRC (Ping timeout: 250 seconds)
1602021-08-26T09:33:39 *** Henrik <Henrik!~textual@84.212.107.177> has quit IRC (Quit: My MacBook Air has gone to sleep. ZZZzzzâ¦)
1612021-08-26T09:35:39 *** Yihen <Yihen!~textual@103.138.75.117> has joined #bitcoin-core-dev
1622021-08-26T09:37:44 *** Ananta-shesha <Ananta-shesha!~pjetcetal@2.95.210.196> has quit IRC (Remote host closed the connection)
1632021-08-26T09:43:28 *** Talkless <Talkless!~Talkless@mail.dargis.net> has joined #bitcoin-core-dev
1642021-08-26T09:58:26 *** lkqwejhhgasdjhgn <lkqwejhhgasdjhgn!~kljkljklk@p200300d46f389600bf6bab93e1f1735e.dip0.t-ipconnect.de> has joined #bitcoin-core-dev
1652021-08-26T10:16:36 *** JackH <JackH!~laptop@ppp-0-174.leed-a-2.dynamic.dsl.as9105.com> has joined #bitcoin-core-dev
1662021-08-26T10:38:29 *** NorrinRadd <NorrinRadd!~username@154.6.20.49> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzzâ¦)
1672021-08-26T10:40:06 <laanwj> is it time to do 22.0rc3 soon maybe
1682021-08-26T10:43:37 <fanquake> laanwj: yea. Need the Boost fix added to #22629, then I think we should just about cut an rc3
1692021-08-26T10:43:39 <gribble> https://github.com/bitcoin/bitcoin/issues/22629 | [22.x] rc3 backports by hebasto · Pull Request #22629 · bitcoin/bitcoin · GitHub
1702021-08-26T10:45:19 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1712021-08-26T10:45:19 <bitcoin-git> [bitcoin] laanwj pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/0492b56e38c2...7740ebcb0230
1722021-08-26T10:45:19 <bitcoin-git> bitcoin/master bebcf78 Jon Atack: Update i2p.md and tor.md regarding -onlynet config option
1732021-08-26T10:45:19 <bitcoin-git> bitcoin/master b87a9c4 Jon Atack: Improve doc/i2p.md regarding I2P router options/versions
1742021-08-26T10:45:19 <bitcoin-git> bitcoin/master 0175977 Jon Atack: Add I2P network SetReachable/IsReachable unit test assertions
1752021-08-26T10:45:21 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1762021-08-26T10:45:35 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
1772021-08-26T10:45:35 <bitcoin-git> [bitcoin] laanwj merged pull request #22648: doc, test: improve i2p/tor docs and i2p reachable unit tests (master...i2p-doc-updates-august-2021) https://github.com/bitcoin/bitcoin/pull/22648
1782021-08-26T10:45:36 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
1792021-08-26T10:45:54 <laanwj> that's one of the PRs jonatack still wants to add to #22629 ^^
1802021-08-26T10:45:58 <gribble> https://github.com/bitcoin/bitcoin/issues/22629 | [22.x] rc3 backports by hebasto · Pull Request #22629 · bitcoin/bitcoin · GitHub
1812021-08-26T10:46:32 <laanwj> i'm still too confused about onlynet logic to review #22651
1822021-08-26T10:46:35 <gribble> https://github.com/bitcoin/bitcoin/issues/22651 | tor: respect non-onion -onlynet= for outgoing Tor connections by vasild · Pull Request #22651 · bitcoin/bitcoin · GitHub
1832021-08-26T10:47:05 <fanquake> my understanding was that 22648 was only mergable if the other PR was also merged
1842021-08-26T10:47:26 <laanwj> oh no
1852021-08-26T10:47:36 <fanquake> confusing I know, as it should have just been based on top of it if that was the case
1862021-08-26T10:48:01 *** wired <wired!wired@gateway/vpn/protonvpn/wired> has joined #bitcoin-core-dev
1872021-08-26T10:48:41 <fanquake> Also why I wasn't overly concerned if either didn't make it into rc3, either as part of the current backport PR (which is getting large), or at all.
1882021-08-26T10:48:46 <laanwj> don't know if it was a good idea to couple it to that, the rest of the documentation changes looked sane
1892021-08-26T10:48:48 <wired> t is safe to say that the "Block Chain" is the "longest Proof-of-Work chain"?
1902021-08-26T10:49:06 <laanwj> i won't say anything about onlynet, i really don't know about onlynet
1912021-08-26T10:49:54 <wired> or my article just call it "TimeChain"?
1922021-08-26T10:50:02 <laanwj> wired: #bitcoin please
1932021-08-26T10:50:13 <wired> banned from there for asking this
1942021-08-26T10:50:17 <wired> so I asking here
1952021-08-26T10:50:26 <wired> you develop the software don't you?
1962021-08-26T10:50:26 <laanwj> then definitely don't repeat it here
1972021-08-26T10:50:31 <fanquake> wired: well the same will happen here. Your questions are off topic
1982021-08-26T10:50:41 <wired> can you talk to me about the "block chain" or "TimeChain"
1992021-08-26T10:50:43 <wired> ?
2002021-08-26T10:50:45 <laanwj> this is the development channel not bitcoin 101 channels
2012021-08-26T10:50:47 <laanwj> no
2022021-08-26T10:51:17 <wired> ohh yo you developing for who really? for the community or for Blockstream? no offense
2032021-08-26T10:52:21 <wired> I asking about "block chain" "timechain" and the "longest Proof-of-Work chain" and this is how you react, interesting
2042021-08-26T10:52:44 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2052021-08-26T10:52:44 <bitcoin-git> [bitcoin] klementtan opened pull request #22804: validation: GuessVerificationProgress returns 0 when no blocks downloaded (master...verification_progress_fix) https://github.com/bitcoin/bitcoin/pull/22804
2062021-08-26T10:52:45 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2072021-08-26T10:52:48 *** ChanServ sets mode: +o laanwj
2082021-08-26T10:52:51 <wired> so you're a Bitcoin developer?
2092021-08-26T10:52:59 *** laanwj sets mode: +b *!*@gateway/vpn/protonvpn/wired
2102021-08-26T10:53:02 *** wired was kicked by laanwj (wired)
2112021-08-26T10:53:08 *** ChanServ sets mode: -o laanwj
2122021-08-26T10:56:46 <laanwj> I think I'm starting to get #22647 and #22651, so it ends up with an onion proxy (despite not being specifiec explicitly) because of -listenonion, then because of that connecting to onions despite -onlynet, which should rule out connecting to networks not specified?
2132021-08-26T10:56:47 <gribble> https://github.com/bitcoin/bitcoin/issues/22647 | If both options "onion" and "proxy" are unset, no outbound Onion connections should be made · Issue #22647 · bitcoin/bitcoin · GitHub
2142021-08-26T10:56:49 <gribble> https://github.com/bitcoin/bitcoin/issues/22651 | tor: respect non-onion -onlynet= for outgoing Tor connections by vasild · Pull Request #22651 · bitcoin/bitcoin · GitHub
2152021-08-26T10:58:03 <laanwj> after all, onlynet specifies where outgoing connections should be made
2162021-08-26T10:59:30 <laanwj> but yes, the current backport PR is getting really large
2172021-08-26T11:01:33 <laanwj> though every individual backported PR in the set is fairly small
2182021-08-26T11:01:47 <laanwj> but it would be good to do a release some time
2192021-08-26T11:04:35 *** Guest90 <Guest90!~Guest90@218.212.21.21> has joined #bitcoin-core-dev
2202021-08-26T11:05:04 <fanquake> Yes, I think rc3 cut this week
2212021-08-26T11:08:56 *** klementtan <klementtan!~textual@218.212.21.21> has joined #bitcoin-core-dev
2222021-08-26T11:09:04 *** Guest90 <Guest90!~Guest90@218.212.21.21> has quit IRC (Client Quit)
2232021-08-26T11:23:53 <laanwj> I don't know if I'm making sense https://github.com/bitcoin/bitcoin/pull/22648/files#r696535966
2242021-08-26T11:24:15 <laanwj> in any case, yes, no need to make any rushed change here for rc3
2252021-08-26T11:27:38 <fanquake> laanwj: I'll take a look tomorrow for you
2262021-08-26T11:29:14 *** AaronvanW <AaronvanW!~AaronvanW@2800:b20:1114:da9:bd58:7418:5113:ed77> has joined #bitcoin-core-dev
2272021-08-26T11:30:27 <laanwj> fanquake: thank you!
2282021-08-26T11:31:15 *** aitorjs <aitorjs!~aitorjs@184.76.76.188.dynamic.jazztel.es> has joined #bitcoin-core-dev
2292021-08-26T11:31:30 <laanwj> I think we should properly think through what we want onlynet to do and implement (and test) that
2302021-08-26T11:32:07 <fanquake> I think there is a lot of scope to reduce the options there, and potentially the features we support. It seems to be very getting very convoluted / non-intuitive.
2312021-08-26T11:32:10 <laanwj> and what makes sense to users-not do for sake of expediency what is easiest to implement
2322021-08-26T11:32:38 <laanwj> right, deprecating some things completely might be an option too
2332021-08-26T11:34:06 <laanwj> there's user privacy at stake here it shouldn't be some dangerous maze of options
2342021-08-26T11:34:08 <fanquake> I'd be interested to know if / why some users might be using such networking setups. This also seems like something better solved (or at least moving that way) outside bitcoind, vs additional feature creep and back-compat / option complexity.
2352021-08-26T11:35:12 <fanquake> Having support for all of this built is ok, as long as we're not just giving foot-guns, or some sort of false sense of security to users who badly configure things.
2362021-08-26T11:51:10 *** aitorjs <aitorjs!~aitorjs@184.76.76.188.dynamic.jazztel.es> has quit IRC (Ping timeout: 240 seconds)
2372021-08-26T11:53:50 <hebasto> all of prs labeled "Needs backport (22.x)" have been processed
2382021-08-26T11:56:31 *** klementtan <klementtan!~textual@218.212.21.21> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzzâ¦)
2392021-08-26T11:56:58 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 246 seconds)
2402021-08-26T11:58:14 *** prayank <prayank!~andr0irc@51.158.144.32> has joined #bitcoin-core-dev
2412021-08-26T12:00:01 <laanwj> hebasto: great1
2422021-08-26T12:00:41 *** Guyver2 <Guyver2!Guyver@guyver2.xs4all.nl> has quit IRC (Quit: Going offline, see ya! (www.adiirc.com))
2432021-08-26T12:01:40 *** AaronvanW <AaronvanW!~AaronvanW@2800:b20:1114:da9:bd58:7418:5113:ed77> has quit IRC (Ping timeout: 240 seconds)
2442021-08-26T12:16:00 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2452021-08-26T12:18:01 <jonatack> was afk. it would be nice for https://github.com/bitcoin/bitcoin/pull/22648/commits/b87a9c4d to be backported into 22.0.
2462021-08-26T12:18:24 <jonatack> doc regarding I2P router options/versions
2472021-08-26T12:18:48 <jonatack> so as to not need to spend another half year pointing people to it
2482021-08-26T12:26:33 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2492021-08-26T12:26:33 <bitcoin-git> [bitcoin] laanwj pushed 16 commits to 22.x: https://github.com/bitcoin/bitcoin/compare/d3bd5410f64e...4a25e39624e2
2502021-08-26T12:26:33 <bitcoin-git> bitcoin/22.x e9d30fb Hennadii Stepanov: ci: Run fuzzer task for the master branch only
2512021-08-26T12:26:33 <bitcoin-git> bitcoin/22.x 57fce06 Anthony Towns: consensus/params: simplify ValidDeployment check to avoid gcc warning
2522021-08-26T12:26:33 <bitcoin-git> bitcoin/22.x e9b4487 Hennadii Stepanov: qt: Fix regression in "Encrypt Wallet" menu item
2532021-08-26T12:26:35 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2542021-08-26T12:26:50 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2552021-08-26T12:26:50 <bitcoin-git> [bitcoin] laanwj merged pull request #22629: [22.x] rc3 backports (22.x...210805-22.0-backport) https://github.com/bitcoin/bitcoin/pull/22629
2562021-08-26T12:26:51 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2572021-08-26T12:28:16 <hebasto> laanwj: just checked #22667, and it does not require update, and it is actually rtm
2582021-08-26T12:28:18 <gribble> https://github.com/bitcoin/bitcoin/issues/22667 | [22.x] qt: Pre-rc3 translations update by hebasto · Pull Request #22667 · bitcoin/bitcoin · GitHub
2592021-08-26T12:29:54 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2602021-08-26T12:29:54 <bitcoin-git> [bitcoin] laanwj pushed 2 commits to 22.x: https://github.com/bitcoin/bitcoin/compare/4a25e39624e2...99cd080db1ad
2612021-08-26T12:29:54 <bitcoin-git> bitcoin/22.x aa254a0 Hennadii Stepanov: qt: Pre-rc3 translations update
2622021-08-26T12:29:54 <bitcoin-git> bitcoin/22.x 99cd080 W. J. van der Laan: Merge bitcoin/bitcoin#22667: [22.x] qt: Pre-rc3 translations update
2632021-08-26T12:29:56 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2642021-08-26T12:33:18 <jonatack> fanquake: i hear from many users, can direct them to you if you're interested, let me know how best you'd like them to reach you
2652021-08-26T12:35:13 *** JackH <JackH!~laptop@ppp-0-174.leed-a-2.dynamic.dsl.as9105.com> has quit IRC (Ping timeout: 248 seconds)
2662021-08-26T12:35:25 <laanwj> hebasto: thanks for confirming
2672021-08-26T12:36:59 <fanquake> jonatack: why would they need to reach out to me directly? If there are problems, users should either be opening an issue on GH, and commenting on an existing one. Keeping discussing in DMs, or one-on-one interactions is not useful for ascertaining the scope of an issue, or creating any sort of public documentation.
2682021-08-26T12:37:29 <fanquake> My understand is that there are only a handful of i2p users in any case. There canât be too many, as itâs still an experimental, unreleased feature
2692021-08-26T12:37:58 <laanwj> jonatack: it would have been nice to have that PR in rc3, but it's too bad it's coupled to the onlynet change, I'm not sure about backporting it partially
2702021-08-26T12:38:17 <jonatack> fanquake: i'm doing what i can to help them. that's the only reason for the docs. there are maybe ~30 users who have set up I2P with bitcoin, but i've heard from many of them.
2712021-08-26T12:38:26 <laanwj> for now, it makes most sense to check the documentation on master with regard to i2p i guess
2722021-08-26T12:39:24 <jonatack> yes, my suggestion at this point was the commit about i2p routers. that's the most frequent question. along with onlynet.
2732021-08-26T12:39:25 <laanwj> but there's no harm in cherry-picking that PR either
2742021-08-26T12:39:36 <jonatack> (they are separate commits)
2752021-08-26T12:39:38 <laanwj> s/PR/commit
2762021-08-26T12:39:45 <jonatack> oh ok
2772021-08-26T12:39:52 <laanwj> I don't think I agree with the onlynet fix
2782021-08-26T12:41:34 <fanquake> jonatack: I still donât understand how having them reach out to me directly would be any use
2792021-08-26T12:43:47 <sipa> fanquake: i suspect jonatack means this as a means to show you people care aboit this
2802021-08-26T12:44:22 <laanwj> let's see if manual page generation behaves any more sane now
2812021-08-26T12:44:23 <jonatack> fanquake: that was in reply to "I'd be interested to know if / why some users might be using such networking setups" so you can discuss with them, if you like
2822021-08-26T12:44:39 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2832021-08-26T12:44:39 <bitcoin-git> [bitcoin] laanwj pushed 2 commits to 22.x: https://github.com/bitcoin/bitcoin/compare/99cd080db1ad...f95b655ba9ab
2842021-08-26T12:44:39 <bitcoin-git> bitcoin/22.x 59d4afc W. J. van der Laan: build: Bump version to 22.0rc3
2852021-08-26T12:44:39 <bitcoin-git> bitcoin/22.x f95b655 Jon Atack: Improve doc/i2p.md regarding I2P router options/versions
2862021-08-26T12:44:41 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
2872021-08-26T12:46:16 <fanquake> jonatack: sure. If users want to discuss that, Iâm happy for them to get in touch with me.
2882021-08-26T12:46:53 <jonatack> basically, people are looking for privacy and there's some confusion out there around the benefits and drawbacks of onlynet=onion. i'm seeing people starting with i2p with onlynet=i2p by default too.
2892021-08-26T12:48:07 <laanwj> ok in manual pages it now shows v22.0.0rc3 instead of v22.0rc2, hyphens still get nixed
2902021-08-26T12:49:46 *** bitdex_ <bitdex_!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Quit: = "")
2912021-08-26T12:50:50 <prayank> If we had wiki enabled in this repository, it could be used for privacy related docs. There is scope for lot of improvement but you need lot of patience to get any privacy related PR get merged (sometimes years).
2922021-08-26T12:52:51 <laanwj> the main problem (as I see it) is that how these options interact is incredibly complex, as well as under-tested in the functional tests, which makes reviewing changes to them scary
2932021-08-26T12:53:18 <laanwj> someone may be relying on some specific edge-case which then changes
2942021-08-26T12:53:21 <jonatack> (onlynet=onion seems overused from what i can tell. maybe in a few months onlynet=onion + onlynet=i2p could become interesting)
2952021-08-26T12:53:50 <jonatack> laanwj: agree
2962021-08-26T12:54:00 <laanwj> onlynet=onion is nice if you want to avoid using exit relays on tor
2972021-08-26T12:56:52 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
2982021-08-26T12:56:52 <bitcoin-git> [gui] hebasto merged pull request #403: refactor: Make paths to update Encryption and HD wallet statuses simpler (master...210811-hd) https://github.com/bitcoin-core/gui/pull/403
2992021-08-26T12:56:53 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3002021-08-26T12:56:57 <laanwj> i2p somewhat luckily doesn't have those
3012021-08-26T12:57:10 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
3022021-08-26T12:57:10 <bitcoin-git> [bitcoin] laanwj pushed 2 commits to 22.x: https://github.com/bitcoin/bitcoin/compare/f95b655ba9ab...86de56776aae
3032021-08-26T12:57:10 <bitcoin-git> bitcoin/22.x c1c79f4 W. J. van der Laan: doc: Stop nixing `-` in manual pages
3042021-08-26T12:57:10 <bitcoin-git> bitcoin/22.x 86de567 W. J. van der Laan: doc: Manual pages update for rc3
3052021-08-26T12:57:12 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3062021-08-26T12:57:27 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
3072021-08-26T12:57:27 <bitcoin-git> [bitcoin] hebasto pushed 5 commits to master: https://github.com/bitcoin/bitcoin/compare/7740ebcb0230...774a4f517cf6
3082021-08-26T12:57:27 <bitcoin-git> bitcoin/master 7d0d4c0 Hennadii Stepanov: qt: Add WalletFrame::currentWalletSet signal
3092021-08-26T12:57:27 <bitcoin-git> bitcoin/master 37dcf16 Hennadii Stepanov: qt, refactor: Emit WalletView::encryptionStatusChanged signal directly
3102021-08-26T12:57:27 <bitcoin-git> bitcoin/master fcdc8b0 Hennadii Stepanov: qt, refactor: Drop redundant signalling in WalletView::setWalletModel
3112021-08-26T12:57:29 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3122021-08-26T12:59:27 <laanwj> i think we're ready for tagging rc3
3132021-08-26T13:00:21 *** Guyver2 <Guyver2!Guyver@guyver2.xs4all.nl> has joined #bitcoin-core-dev
3142021-08-26T13:02:19 *** klementtan <klementtan!~textual@bb121-6-162-104.singnet.com.sg> has joined #bitcoin-core-dev
3152021-08-26T13:03:02 <hebasto> ^ agree
3162021-08-26T13:05:19 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
3172021-08-26T13:05:20 <bitcoin-git> [bitcoin] laanwj pushed tag v22.0rc3: https://github.com/bitcoin/bitcoin/compare/v22.0rc3
3182021-08-26T13:05:21 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3192021-08-26T13:05:42 <laanwj> ^^
3202021-08-26T13:07:39 <hebasto> \o/
3212021-08-26T13:10:01 <jonatack> prayank: not sure if you meant something else, but there is a wiki at https://github.com/bitcoin-core/bitcoin-devwiki/wiki
3222021-08-26T13:11:18 <laanwj> that said, it's probably not the best place for privacy advice for end users
3232021-08-26T13:12:19 <laanwj> although it can be convenient to edit documents (like release notes) there temporarily
3242021-08-26T13:16:08 <prayank> jonatack: Thanks for the link. I was about to ask if we could add docs section here for tor and i2p. Will also need write access for people who want to contribute. But laanwj doesn't think it's the best place to do it. Problem is right now people get privacy advice on Twitter, Reddit, Telegram, Stackexchange etc. Users with different levels of technical expertise.
3252021-08-26T13:19:14 <michaelfolkson> I think StackExchange is a good place for general privacy guidance. The Core docs document the Core software and how to use it, anything where there are differing perspectives and trade-offs to be discussed should probably be elsewhere
3262021-08-26T13:20:23 *** zenloading <zenloading!~zenloadin@user/zenloading> has joined #bitcoin-core-dev
3272021-08-26T13:21:17 <jonatack> that's true, the wiki is being used for repo project management. an article on your personal blog or website or (good point) on BitcoinStackExchange seems good, or https://en.bitcoin.it (still maintained?)
3282021-08-26T13:22:14 <laanwj> general privacy advice about using bitcoin spans much further than just using an overlay network, the most privacy-relevant in that regard is what you use to broadcast transactions
3292021-08-26T13:23:39 <michaelfolkson> jonatack: Oh yeah :facepalm: I completely forgot about belcher's awesome privacy wiki. https://en.bitcoin.it/wiki/Privacy
3302021-08-26T13:23:52 <laanwj> I think if you never broadcast your own transactions from your own node, how you connect is hardly privacy-sensitive at all, and overlay networks become more of a way of ensuring different connectivity to mitigate eclipse attacks
3312021-08-26T13:25:04 <michaelfolkson> jonatack: It might need updating for a few things since 2019 but this is most exhaustive resource on privacy I think
3322021-08-26T13:25:09 <jonatack> michaelfolkson: right! and last edited on 21 July 2021
3332021-08-26T13:25:19 <laanwj> (of course there are different perspectives, some people mean 'privacy' as in 'hiding that you're running a bitcoin node in the first place' which is... very difficult if impossible with overlay networks)
3342021-08-26T13:26:29 <laanwj> sure, your IP won't trivially show up in node lists, the sheer amount of data as well as timing patterns can give enough suspicion
3352021-08-26T13:29:53 <laanwj> but it might be *enough* privacy for some cases, always hard to judge
3362021-08-26T13:32:00 <prayank> Problem with Stackexchange and other places is you can write with more freedom and sometimes wrong things may not get noticed which in few years become a practice. Example: second paragraph in this comment by Greg Maxwell https://github.com/bitcoin/bitcoin/issues/17491#issuecomment-705485718
3372021-08-26T13:34:08 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
3382021-08-26T13:34:08 <bitcoin-git> [bitcoin] theStack opened pull request #22805: refactor: use CWallet const shared pointers in dump{privkey,wallet} (master...202108-refactor-const_correctness_for_further_dump_methods) https://github.com/bitcoin/bitcoin/pull/22805
3392021-08-26T13:34:10 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
3402021-08-26T13:35:47 *** klementtan <klementtan!~textual@bb121-6-162-104.singnet.com.sg> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzzâ¦)
3412021-08-26T13:36:16 <michaelfolkson> prayank: No panacea (every source has upsides and downsides) but maintaining a version of that very long (but good) privacy wiki in the Core docs is not a road we want to go down.
3422021-08-26T13:36:31 *** Guyver2 <Guyver2!Guyver@guyver2.xs4all.nl> has quit IRC (Quit: Going offline, see ya! (www.adiirc.com))
3432021-08-26T13:37:06 <muhblockchain> git (not github) sounds for me like the perfect place to organize any documents (for devs as well as users)
3442021-08-26T13:37:57 <michaelfolkson> prayank: Also I think belcher takes ownership of this privacy wiki as he wrote most of it in a way that he doesn't on some other non-privacy topics. Not many people know more about privacy than Chris
3452021-08-26T13:45:59 *** goatpig <goatpig!~goat@blocksettle-gw.cust.31173.se> has quit IRC (Quit: Konversation terminated!)
3462021-08-26T13:49:26 *** klementtan <klementtan!~textual@bb121-6-162-104.singnet.com.sg> has joined #bitcoin-core-dev
3472021-08-26T13:59:06 *** AaronvanW <AaronvanW!~AaronvanW@2800:b20:1114:da9:bd58:7418:5113:ed77> has joined #bitcoin-core-dev
3482021-08-26T14:04:22 <prayank> michaelfolkson: Agree that privacy wiki has lot of interesting things. I respect Chris Belcher for his contributions in improving Bitcoin Privacy. The docs I was talky about were only for Bitcoin Core. Mainly Tor, i2p, wallet etc. This privacy wiki also needs some updates: Dandelion should be removed, i2p needs to be added, lot of things related to Tor (you can write few pages on just `onlynet`). Anyways it's just a suggestion.
3492021-08-26T14:14:02 *** goatpig <goatpig!~goat@h-94-254-2-155.A498.priv.bahnhof.se> has joined #bitcoin-core-dev
3502021-08-26T14:20:56 <laanwj> from a more holistic point of view about "bitcoin privacy" i don't think something like onlynet contributes much
3512021-08-26T14:21:39 <laanwj> my initial point was to make the option behave sensibly, instead of writing diatribes about all its exceptions and strange cases
3522021-08-26T14:31:16 *** AaronvanW <AaronvanW!~AaronvanW@2800:b20:1114:da9:bd58:7418:5113:ed77> has quit IRC (Ping timeout: 250 seconds)
3532021-08-26T14:35:59 <prayank> There are lot of users who care about privacy and interested to know about trade-offs involved in using Tor with i2p and other combinations which needs `onlynet`
3542021-08-26T14:38:26 <laanwj> the way to make sure all outgoing connections go through a proxy has always been -proxy, this intentionally covers all networks
3552021-08-26T14:38:29 <prayank> Will they read right now? Maybe this https://bitcoin.stackexchange.com/questions/107060/tor-and-i2p-tradeoffs-in-bitcoin-core/ which I wrote based on some comments in different pull requests, asking some people on reddit, my own research etc.
3562021-08-26T14:38:51 <prayank> And I can't assure if everything mentioned is correct
3572021-08-26T14:39:53 <laanwj> the other thing to worry about is incoming connections, you either want to stop listening or P2P make sure you only listen on localhost (for a Tor hidden service)
3582021-08-26T14:39:59 <laanwj> that's it-
3592021-08-26T14:42:01 *** grettke <grettke!~grettke@cpe-65-29-228-30.wi.res.rr.com> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzzâ¦)
3602021-08-26T14:42:14 <jonatack> good points
3612021-08-26T14:42:17 <laanwj> that alone should be enough to run networking entirely through the proxy, if not, it's a serious bug
3622021-08-26T14:44:47 <laanwj> prayank: thanks for writing something up
3632021-08-26T14:48:41 *** smartin <smartin!~Icedove@88.135.18.171> has quit IRC (Quit: smartin)
3642021-08-26T14:48:54 <prayank> TBH I am not using i2p right now for mainnet. But experimenting a lot on testnet. There was a vulnerability in Tails long back and using two different complex things can always result in weird things which remain unnoticed for a long time. But it's good users have two options now: Tor and i2p
3652021-08-26T14:49:07 <prayank> Tails context: https://tor.stackexchange.com/a/6931/
3662021-08-26T14:52:40 *** AaronvanW <AaronvanW!~AaronvanW@2800:b20:1114:da9:bd58:7418:5113:ed77> has joined #bitcoin-core-dev
3672021-08-26T14:53:20 *** AaronvanW <AaronvanW!~AaronvanW@2800:b20:1114:da9:bd58:7418:5113:ed77> has quit IRC (Client Quit)
3682021-08-26T14:53:40 *** Guyver2 <Guyver2!Guyver@guyver2.xs4all.nl> has joined #bitcoin-core-dev
3692021-08-26T15:00:22 *** Kiminuo <Kiminuo!~Kiminuo@107.150.94.37> has quit IRC (Ping timeout: 246 seconds)
3702021-08-26T15:01:22 *** AaronvanW <AaronvanW!~AaronvanW@2800:b20:1114:da9:d0b0:437b:d458:5196> has joined #bitcoin-core-dev
3712021-08-26T15:19:04 *** klementtan <klementtan!~textual@bb121-6-162-104.singnet.com.sg> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzzâ¦)
3722021-08-26T15:26:12 *** jespada_ <jespada_!~jespada@90.254.245.194> has joined #bitcoin-core-dev
3732021-08-26T15:29:27 *** jespada <jespada!~jespada@90.254.245.194> has quit IRC (Ping timeout: 250 seconds)
3742021-08-26T15:34:23 *** prayank <prayank!~andr0irc@51.158.144.32> has quit IRC (Quit: irc thread exit)
3752021-08-26T15:36:33 *** gambpang <gambpang!~ishipman@207.181.230.156> has joined #bitcoin-core-dev
3762021-08-26T15:38:28 <michaelfolkson> prayank: Yeah comparing Tor and I2P is a good question. I don't know anything about I2P https://bitcoin.stackexchange.com/questions/107060/tor-and-i2p-tradeoffs-in-bitcoin-core/
3772021-08-26T15:39:31 <michaelfolkson> (as a protocol)
3782021-08-26T15:40:49 *** jespada_ <jespada_!~jespada@90.254.245.194> has quit IRC (Read error: Connection reset by peer)
3792021-08-26T15:41:07 *** jespada <jespada!~jespada@90.254.245.194> has joined #bitcoin-core-dev
3802021-08-26T15:41:38 <michaelfolkson> I2P is more robust and reliable (apparently) than Tor
3812021-08-26T15:42:22 *** NorrinRadd <NorrinRadd!~username@154.6.20.49> has joined #bitcoin-core-dev
3822021-08-26T15:42:55 *** JackH <JackH!~laptop@ppp-0-174.leed-a-2.dynamic.dsl.as9105.com> has joined #bitcoin-core-dev
3832021-08-26T15:51:41 *** lkqwejhhgasdjhgn <lkqwejhhgasdjhgn!~kljkljklk@p200300d46f389600bf6bab93e1f1735e.dip0.t-ipconnect.de> has quit IRC (Quit: Konversation terminated!)
3842021-08-26T16:08:30 *** gene <gene!~gene@gateway/tor-sasl/gene> has joined #bitcoin-core-dev
3852021-08-26T16:11:27 *** AaronvanW <AaronvanW!~AaronvanW@2800:b20:1114:da9:d0b0:437b:d458:5196> has quit IRC (Ping timeout: 240 seconds)
3862021-08-26T16:14:43 *** AaronvanW <AaronvanW!~AaronvanW@2800:b20:1114:da9:6d66:3de6:f0d7:8db8> has joined #bitcoin-core-dev
3872021-08-26T16:18:31 *** Guest97 <Guest97!~Guest97@194.107.179.197> has joined #bitcoin-core-dev
3882021-08-26T16:18:53 *** Guest97 <Guest97!~Guest97@194.107.179.197> has quit IRC (Client Quit)
3892021-08-26T16:26:38 <michaelfolkson> MarcoFalke: Re "I think long term there is no prospect that BIP 125 will be adhered to exactly" on #22665 why do you say that? Because you think BIP 125 is inferior to current Core code, because it would be too difficult to change in Core, because other implementations haven't implemented it etc?
3902021-08-26T16:26:41 <gribble> https://github.com/bitcoin/bitcoin/issues/22665 | policy/rbf: dont return "incorrect" replaceability status by darosior · Pull Request #22665 · bitcoin/bitcoin · GitHub
3912021-08-26T16:27:25 <sipa> michaelfolkson: i assume that MarcoFalke means that at some point just everything will be replaceable
3922021-08-26T16:28:05 <sipa> as BIP125/opt-in RBF in general are just gentlemen's agreements that are probably untenable in a rational market long-term
3932021-08-26T16:29:33 *** vysn <vysn!~vysn@user/vysn> has joined #bitcoin-core-dev
3942021-08-26T16:31:16 <michaelfolkson> sipa: ariard isn't sure that will land https://github.com/bitcoin/bitcoin/pull/22698#issuecomment-899886907 but MarcoFalke thinks it definitely will eventually?
3952021-08-26T16:38:25 <sipa> michaelfolkson: yes, sometimes people have different opinions about what will happen in the future
3962021-08-26T16:38:58 <michaelfolkson> sipa: Sure :) Just checking I understood the perspectives
3972021-08-26T16:44:57 *** copumpkin <copumpkin!~woohoo@user/copumpkin> has quit IRC (Read error: Connection reset by peer)
3982021-08-26T16:46:20 *** copumpkin <copumpkin!~woohoo@user/copumpkin> has joined #bitcoin-core-dev
3992021-08-26T16:47:13 *** copumpkin <copumpkin!~woohoo@user/copumpkin> has quit IRC (Read error: Connection reset by peer)
4002021-08-26T16:48:08 *** copumpkin <copumpkin!~woohoo@user/copumpkin> has joined #bitcoin-core-dev
4012021-08-26T16:56:47 <achow101> what about 0.21.2 final? Seems like there hasn't been any issues (although that may be due to no one testing?)
4022021-08-26T17:00:01 *** JackH <JackH!~laptop@ppp-0-174.leed-a-2.dynamic.dsl.as9105.com> has quit IRC (Ping timeout: 250 seconds)
4032021-08-26T17:06:24 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
4042021-08-26T17:06:24 <bitcoin-git> [bitcoin] kristapsk opened pull request #22807: RPC: Add universal options argument to listtransactions (master...listtransactions-options) https://github.com/bitcoin/bitcoin/pull/22807
4052021-08-26T17:06:25 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
4062021-08-26T17:13:38 <laanwj> achow101: sgtm
4072021-08-26T17:22:43 <hebasto> achow101: laanwj: it seems https://github.com/bitcoin/bitcoin/pull/22713 is required to be backported in 0.21
4082021-08-26T17:24:45 <achow101> I guess there's also #22784
4092021-08-26T17:24:45 <gribble> https://github.com/bitcoin/bitcoin/issues/22784 | combinerawtransaction fails to properly combine transactions containing taproot inputs · Issue #22784 · bitcoin/bitcoin · GitHub
4102021-08-26T17:27:06 *** grettke <grettke!~grettke@cpe-65-29-228-30.wi.res.rr.com> has joined #bitcoin-core-dev
4112021-08-26T17:32:56 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
4122021-08-26T17:32:56 <bitcoin-git> [bitcoin] hebasto opened pull request #22808: [0.21] 0.21.2rc2 backports (0.21...210826-0.21-backports) https://github.com/bitcoin/bitcoin/pull/22808
4132021-08-26T17:32:57 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
4142021-08-26T17:33:13 *** lightlike <lightlike!~lightlike@user/lightlike> has joined #bitcoin-core-dev
4152021-08-26T17:34:18 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
4162021-08-26T17:34:18 <bitcoin-git> [bitcoin] MarcoFalke opened pull request #22809: test: Check that non-signaling BIP125 tx can be replaced via parent (master...2108-testTxReplace) https://github.com/bitcoin/bitcoin/pull/22809
4172021-08-26T17:34:19 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
4182021-08-26T17:48:39 *** Aaronvan_ <Aaronvan_!~AaronvanW@190.86.109.168> has joined #bitcoin-core-dev
4192021-08-26T17:51:10 *** AaronvanW <AaronvanW!~AaronvanW@2800:b20:1114:da9:6d66:3de6:f0d7:8db8> has quit IRC (Ping timeout: 240 seconds)
4202021-08-26T18:01:17 *** Henrik <Henrik!~textual@84.212.107.177> has joined #bitcoin-core-dev
4212021-08-26T18:03:04 *** raj <raj!~raj_@103.77.139.233> has quit IRC (Quit: Leaving)
4222021-08-26T18:08:16 *** prayank <prayank!~andr0irc@51.15.0.88> has joined #bitcoin-core-dev
4232021-08-26T18:12:56 <prayank> Wrote a post about ONLYNET: https://prayank23.github.io/camouflage//blog/onlynet/
4242021-08-26T18:16:25 *** Henrik <Henrik!~textual@84.212.107.177> has quit IRC (Quit: My MacBook Air has gone to sleep. ZZZzzzâ¦)
4252021-08-26T18:24:56 *** prayank <prayank!~andr0irc@51.15.0.88> has quit IRC (Quit: irc thread exit)
4262021-08-26T18:28:46 *** zenloading <zenloading!~zenloadin@user/zenloading> has quit IRC (Quit: Leaving)
4272021-08-26T18:45:28 *** JohnnyD <JohnnyD!~JohnnyD@12.97.152.122> has joined #bitcoin-core-dev
4282021-08-26T19:00:08 <laanwj> #startmeeting
4292021-08-26T19:00:09 <core-meetingbot> Meeting started Thu Aug 26 19:00:08 2021 UTC. The chair is laanwj. Information about MeetBot at https://bitcoin.jonasschnelli.ch/ircmeetings.
4302021-08-26T19:00:09 <core-meetingbot> Available commands: action commands idea info link nick
4312021-08-26T19:00:16 <kvaciral[m]> hi
4322021-08-26T19:00:18 <larryruane> hi
4332021-08-26T19:00:19 <gene> hi
4342021-08-26T19:00:30 <hebasto> hi
4352021-08-26T19:00:38 <ariard__> hi
4362021-08-26T19:00:44 <jonatack> hi
4372021-08-26T19:00:52 <harding> hi
4382021-08-26T19:00:53 <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 lightlike luke-jr maaku marcofalke meshcollider michagogo moneyball morcos
4392021-08-26T19:00:55 <laanwj> nehan NicolasDorier paveljanik petertodd phantomcircuit promag provoostenator ryanofsky sdaftuar sipa vasild
4402021-08-26T19:01:01 <michaelfolkson> hi
4412021-08-26T19:01:12 <laanwj> no topics have been proposed using #proposedmeetingtopic this week
4422021-08-26T19:01:19 *** jarthur <jarthur!~jarthur@2603-8080-1540-002d-81dc-4f45-3881-6bd3.res6.spectrum.com> has quit IRC (Quit: jarthur)
4432021-08-26T19:01:21 <achow101> hi
4442021-08-26T19:01:24 <laanwj> any last minute topic proposals?
4452021-08-26T19:01:46 <laanwj> PSA: 22.0rc3 has been tagged today, please start your guix builders
4462021-08-26T19:02:10 <jarolrod> hi
4472021-08-26T19:02:59 <laanwj> a new 0.21.2 rc is also coming soon
4482021-08-26T19:03:25 <laanwj> #topic High priority for review
4492021-08-26T19:03:26 <core-meetingbot> topic: High priority for review
4502021-08-26T19:03:29 <jarolrod> time to bring out old reliable: gitian
4512021-08-26T19:03:56 <laanwj> https://github.com/bitcoin/bitcoin/projects/8 6 blockers, 2 chasing concept ACK currently
4522021-08-26T19:04:36 <ariard__> jamesob: happy to re-review #21526 tonight if you're around
4532021-08-26T19:04:36 <laanwj> jarolrod: right, branch <=0.21 will keep using gitian for builds
4542021-08-26T19:04:39 <gribble> https://github.com/bitcoin/bitcoin/issues/21526 | validation: UpdateTip/CheckBlockIndex assumeutxo support by jamesob · Pull Request #21526 · bitcoin/bitcoin · GitHub
4552021-08-26T19:06:22 <laanwj> anything to add/remove or that is almost ready for merge?
4562021-08-26T19:07:25 <laanwj> anything else to discuss? seems a short meeting today
4572021-08-26T19:07:30 <jonatack> don't hesitate to have a look at #22702 everyone, looks interesting, am running a node built with it
4582021-08-26T19:07:32 <gribble> https://github.com/bitcoin/bitcoin/issues/22702 | [WIP] Add allocator for node based containers by martinus · Pull Request #22702 · bitcoin/bitcoin · GitHub
4592021-08-26T19:07:56 <laanwj> jonatack: should we add it to high prio?
4602021-08-26T19:08:46 <jonatack> laanwj: i don't know but wanted to mention it
4612021-08-26T19:09:24 <michaelfolkson> Very cool review of Erlay from 0xB10C https://github.com/naumenkogs/txrelaysim/issues/8#issuecomment-903255752
4622021-08-26T19:09:51 <laanwj> jonatack: as it's still WIP, it probably should be on there, but I'll take a look
4632021-08-26T19:09:57 <laanwj> michaelfolkson: great!
4642021-08-26T19:11:27 <laanwj> #endmeeting
4652021-08-26T19:11:27 <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
4662021-08-26T19:11:27 <core-meetingbot> Meeting ended Thu Aug 26 19:11:27 2021 UTC.
4672021-08-26T19:11:27 <core-meetingbot> Minutes: https://bitcoin.jonasschnelli.ch/ircmeetings/logs/bitcoin-core-dev/2021/bitcoin-core-dev.2021-08-26-19.00.moin.txt
4682021-08-26T19:11:58 <jonatack> yes, it was WIP but the remaining hurdles seem to have been solved
4692021-08-26T19:12:42 <ariard__> michaelfolkson: re bip125, well i'm still aiming to propose full-rbf for 0.24, though there is no guarantee it will land, still have to reach out to more historical opponents to have them express an opinion
4702021-08-26T19:12:46 *** Talkless <Talkless!~Talkless@mail.dargis.net> has quit IRC (Quit: Konversation terminated!)
4712021-08-26T19:13:10 *** JohnnyD <JohnnyD!~JohnnyD@12.97.152.122> has quit IRC (Quit: Client closed)
4722021-08-26T19:14:00 <ariard__> michaelfolkson: note, there is also a discussion between matt and i on why it might be preferable to depracte replace-by-fee towards replace-by-feerate here :https://lightningdevkit.slack.com/archives/CTBLT3CAU/p1625786787422100
4732021-08-26T19:15:47 <michaelfolkson> ariard__: Cool, thanks. I'm guessing as you've described it as a CVE for Lightning you have a strong preference for it to be changed in the meantime
4742021-08-26T19:16:41 <michaelfolkson> ariard__: (to follow the BIP logic)
4752021-08-26T19:17:36 <michaelfolkson> I'm just trying to understand whether we should really care about this or not
4762021-08-26T19:19:40 <michaelfolkson> Others have said (and I agree) that it isn't a CVE for Core
4772021-08-26T19:22:02 <michaelfolkson> Going forward I think we need to take the BIPs more seriously. Different world when the BIP was originally written
4782021-08-26T19:23:42 <harding> michaelfolkson: I don't think anyone took BIP125 less than seriously when it was written.
4792021-08-26T19:25:07 *** gene <gene!~gene@gateway/tor-sasl/gene> has quit IRC (Quit: gene)
4802021-08-26T19:25:33 <harding> I don't even know what "take the BIPs more seriously" means.
4812021-08-26T19:28:08 *** Kiminuo <Kiminuo!~Kiminuo@107.150.94.38> has joined #bitcoin-core-dev
4822021-08-26T19:29:25 <michaelfolkson> harding: Right but Lightning didn't even exist. There wasn't these layer effect where something that seems minor on a lower level can be important for an upper level
4832021-08-26T19:32:27 *** prayank <prayank!~andr0irc@51.15.0.88> has joined #bitcoin-core-dev
4842021-08-26T19:34:40 *** jesseposner <jesseposner!~jesse@2601:647:0:89:69dd:83ee:ede:7268> has quit IRC (Ping timeout: 240 seconds)
4852021-08-26T19:36:27 <michaelfolkson> I guess if there are no policy BIPs ever again then it is less relevant. But I kinda think there should be. But the attitude of "the BIP gets overruled by whatever ended up in Core" shouldn't cut it in today's environment
4862021-08-26T19:37:18 <michaelfolkson> That seems the least and perhaps the most Core can do to help Lightning with this fuzzy policy guarantees problem
4872021-08-26T19:37:33 <harding> michaelfolkson: to nitpick a little, LN was first described several months before BIP125 was written, and there were two different types of payment channels available for use at that time (BlueMatt wrote the implementation of one; I was on the team that wrote a different implementation which had just gone into light production use). Certainly second layer protocols are much more important today than they were back then, but it's not like
4882021-08-26T19:37:34 <harding> people weren't thinking about them back then.
4892021-08-26T19:37:43 *** jesseposner <jesseposner!~jesse@2601:647:0:89:b867:e118:64da:aa80> has joined #bitcoin-core-dev
4902021-08-26T19:38:22 <michaelfolkson> Fair enough
4912021-08-26T19:38:40 <prayank> Implementation of a BIP with some differences should be fine. Problem was not documenting these differences which was fixed in https://github.com/bitcoin/bitcoin/pull/21946
4922021-08-26T19:39:00 <BlueMatt> If you're trying to imply, michaelfolkson, that somehow bitcoin core review process is "fine" with a bip text saying something different than the implementation, I dont think thats ever been the case. mistakes happen, things are missed in review, but, indeed, its always been a thing that if the bip text disagrees with the implementation one or both need to be fixed.
4932021-08-26T19:39:01 <harding> michaelfolkson: of course what's in an implementation should overrule what's in a BIP. BIPs are not laws, they're documentation.
4942021-08-26T19:39:18 <harding> michaelfolkson: implementations can do whatever they want.
4952021-08-26T19:39:28 <BlueMatt> which one depends on the situation, but I dont think anything here has changed in the past years, nor should it?
4962021-08-26T19:41:12 <michaelfolkson> BlueMatt: I'm not trying to imply that. But now we're in a situation where there is a difference between the BIP and the code what should be done?
4972021-08-26T19:41:36 <BlueMatt> we should look at the implementation, look at the BIP, decide which one makes more sense, and update the other one.
4982021-08-26T19:42:20 <michaelfolkson> I totally agree ^. But that surely involves Lightning implementations as it is more important for Lightning as it is Core
4992021-08-26T19:42:42 <sipa> FWIW, i disagree with changing the BIP - the number refers to the idea as it's written down, and changing it would only add confusion ("do you mean the old BIP125 approach or the new one?"); if we feel that this deserves a BIP in the first place, i think it'd need to be a new one
5002021-08-26T19:42:56 <harding> (I don't really care, but I'm slightly against changing old BIPs, though I wouldn't mind adding a note to the bottom about the issue.)
5012021-08-26T19:43:05 <BlueMatt> sure? And there's been some emails back and forth, though its not been a high priority for anyone, I believe.
5022021-08-26T19:43:15 <BlueMatt> sipa: sure, i suppose thats a process question
5032021-08-26T19:43:26 *** jarthur <jarthur!~jarthur@2603-8080-1540-002d-9d7c-c2fd-8741-43d9.res6.spectrum.com> has joined #bitcoin-core-dev
5042021-08-26T19:43:43 <sipa> i don't have an opinion on whether the implementation should be changed, or the documentation (whether that's a BIP, or just a writeup of the policy)
5052021-08-26T19:44:27 <sipa> just pointing out that the choice isn't changing the code or changing the BIP - there are other ways of changing the documentation that are less confusing
5062021-08-26T19:44:55 <michaelfolkson> If Lightning implementations don't care that much then just leave it to what the Core mempool devs want to do which seems to be just stripping out references to the BIP
5072021-08-26T19:45:23 <michaelfolkson> If Lightning implementations do really care then that should be factored in
5082021-08-26T19:45:32 <BlueMatt> i believe lightning stuff *strongly* prefers as loose a mempool policy as possible :p
5092021-08-26T19:45:52 <sipa> whatever happens, the implemented policy should be well-documented
5102021-08-26T19:45:56 <michaelfolkson> That's why I asked ariard about how strong his preference was for updating policy to match the BIP
5112021-08-26T19:46:08 <harding> Differing mempool policies was actually anticipated, BIP125 says: "A Bitcoin Wiki page has been created to help wallet authors track deployed mempool policies relating to transaction replacement." which links to https://en.bitcoin.it/wiki/Transaction_replacement
5122021-08-26T19:48:00 *** Aaronvan_ is now known as AaronvanW
5132021-08-26T19:52:17 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
5142021-08-26T19:52:17 <bitcoin-git> [gui] hebasto merged pull request #384: Add copy IP/Netmask action for banned peer (master...copy-subnet) https://github.com/bitcoin-core/gui/pull/384
5152021-08-26T19:52:18 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
5162021-08-26T19:52:39 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
5172021-08-26T19:52:39 <bitcoin-git> [bitcoin] hebasto pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/774a4f517cf6...b8d45a3c2015
5182021-08-26T19:52:39 <bitcoin-git> bitcoin/master ab1461d Shashwat: qt: Add copy IP/Netmask action for banned peer
5192021-08-26T19:52:39 <bitcoin-git> bitcoin/master b8d45a3 Hennadii Stepanov: Merge bitcoin-core/gui#384: Add copy IP/Netmask action for banned peer
5202021-08-26T19:52:41 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
5212021-08-26T20:00:59 *** prayank <prayank!~andr0irc@51.15.0.88> has quit IRC (Read error: Connection reset by peer)
5222021-08-26T20:10:00 *** Yihen <Yihen!~textual@103.138.75.117> has quit IRC (Remote host closed the connection)
5232021-08-26T20:34:25 *** bomb-on <bomb-on!~bomb-on@194.144.47.113> has joined #bitcoin-core-dev
5242021-08-26T20:35:13 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
5252021-08-26T20:49:17 *** Guyver2 <Guyver2!Guyver@guyver2.xs4all.nl> has quit IRC (Quit: Going offline, see ya! (www.adiirc.com))
5262021-08-26T20:51:25 *** Kiminuo <Kiminuo!~Kiminuo@107.150.94.38> has quit IRC (Ping timeout: 246 seconds)
5272021-08-26T20:53:03 *** AaronvanW <AaronvanW!~AaronvanW@190.86.109.168> has quit IRC (Remote host closed the connection)
5282021-08-26T20:54:39 *** aechu <aechu!~major@gateway/tor-sasl/major> has quit IRC (Ping timeout: 276 seconds)
5292021-08-26T20:56:12 *** aechu <aechu!~major@gateway/tor-sasl/major> has joined #bitcoin-core-dev
5302021-08-26T20:58:47 *** dongcarl4 <dongcarl4!~dongcarl@96.224.58.144> has joined #bitcoin-core-dev
5312021-08-26T21:00:37 *** niska` <niska`!~niska@static.38.6.217.95.clients.your-server.de> has joined #bitcoin-core-dev
5322021-08-26T21:01:43 *** dongcarl <dongcarl!~dongcarl@96.224.58.144> has quit IRC (Quit: Ping timeout (120 seconds))
5332021-08-26T21:01:43 *** niska <niska!~niska@static.38.6.217.95.clients.your-server.de> has quit IRC (Quit: Leaving)
5342021-08-26T21:01:44 *** dongcarl4 is now known as dongcarl
5352021-08-26T21:06:43 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Quit: Client closed)
5362021-08-26T21:17:27 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
5372021-08-26T21:17:27 <bitcoin-git> [bitcoin] hebasto closed pull request #22276: gui: update text to eliminate safety hazards (0.21...0.21) https://github.com/bitcoin/bitcoin/pull/22276
5382021-08-26T21:17:28 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
5392021-08-26T21:19:07 *** common <common!~common@096-033-221-075.res.spectrum.com> has joined #bitcoin-core-dev
5402021-08-26T21:23:37 *** AaronvanW <AaronvanW!~AaronvanW@190.86.109.168> has joined #bitcoin-core-dev
5412021-08-26T21:23:39 *** goatpig <goatpig!~goat@h-94-254-2-155.A498.priv.bahnhof.se> has quit IRC (Quit: Konversation terminated!)
5422021-08-26T21:35:38 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
5432021-08-26T21:35:38 <bitcoin-git> [bitcoin] hebasto opened pull request #22810: qt: Pre-0.21.2rc2 translations update (0.21...210826-0.21-tr) https://github.com/bitcoin/bitcoin/pull/22810
5442021-08-26T21:35:39 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
5452021-08-26T21:57:07 *** AaronvanW <AaronvanW!~AaronvanW@190.86.109.168> has quit IRC (Ping timeout: 240 seconds)
5462021-08-26T22:03:18 *** bomb-on <bomb-on!~bomb-on@194.144.47.113> has quit IRC (Quit: aллилѹÑа!)
5472021-08-26T22:06:30 *** earnestly <earnestly!~earnest@user/earnestly> has quit IRC (Read error: Connection reset by peer)
5482021-08-26T22:06:36 *** gleb7 <gleb7!~gleb@178.150.137.228> has quit IRC (Quit: Ping timeout (120 seconds))
5492021-08-26T22:06:58 *** gleb7 <gleb7!~gleb@178.150.137.228> has joined #bitcoin-core-dev
5502021-08-26T22:11:19 *** vysn <vysn!~vysn@user/vysn> has quit IRC (Remote host closed the connection)
5512021-08-26T22:22:55 *** Guest82 <Guest82!~Guest82@2603-8001-6f00-d491-8c90-5d1a-ea73-c04f.res6.spectrum.com> has joined #bitcoin-core-dev
5522021-08-26T22:23:21 *** Guest82 <Guest82!~Guest82@2603-8001-6f00-d491-8c90-5d1a-ea73-c04f.res6.spectrum.com> has quit IRC (Client Quit)
5532021-08-26T22:26:19 *** lightlike <lightlike!~lightlike@user/lightlike> has quit IRC (Ping timeout: 250 seconds)
5542021-08-26T22:34:58 <ariard__> michaelfolkson: i think it's preferable to well-document in the core code the divergences to the spec, instead of rewritting a new bip matching the code
5552021-08-26T22:35:10 <ariard__> and maybe add a small bottom note for the ln devs who aren't fluent in cpp
5562021-08-26T22:35:37 <ariard__> w.r.t to bip vs code, i think it's ultimately a case-by-case situation, weighting the implications
5572021-08-26T22:46:49 *** gleb7 <gleb7!~gleb@178.150.137.228> has quit IRC (Quit: Ping timeout (120 seconds))
5582021-08-26T22:47:10 *** gleb7 <gleb7!~gleb@178.150.137.228> has joined #bitcoin-core-dev
5592021-08-26T22:51:40 *** jesseposner <jesseposner!~jesse@2601:647:0:89:b867:e118:64da:aa80> has quit IRC (Ping timeout: 240 seconds)
5602021-08-26T22:54:49 *** biteskola <biteskola!~biteskola@184.76.76.188.dynamic.jazztel.es> has joined #bitcoin-core-dev
5612021-08-26T22:55:06 *** biteskola <biteskola!~biteskola@184.76.76.188.dynamic.jazztel.es> has quit IRC (Remote host closed the connection)
5622021-08-26T22:55:54 *** aitorjs <aitorjs!~aitorjs@184.76.76.188.dynamic.jazztel.es> has joined #bitcoin-core-dev
5632021-08-26T22:58:10 *** aitorjs <aitorjs!~aitorjs@184.76.76.188.dynamic.jazztel.es> has quit IRC (Client Quit)
5642021-08-26T23:01:01 *** jesseposner <jesseposner!~jesse@c-24-5-105-39.hsd1.ca.comcast.net> has joined #bitcoin-core-dev
5652021-08-26T23:01:40 *** AaronvanW <AaronvanW!~AaronvanW@190.86.109.168> has joined #bitcoin-core-dev
5662021-08-26T23:03:37 *** jesseposner_ <jesseposner_!~jesse@c-24-5-105-39.hsd1.ca.comcast.net> has joined #bitcoin-core-dev
5672021-08-26T23:05:37 *** jesseposner <jesseposner!~jesse@c-24-5-105-39.hsd1.ca.comcast.net> has quit IRC (Ping timeout: 248 seconds)
5682021-08-26T23:08:44 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
5692021-08-26T23:08:44 <bitcoin-git> [bitcoin] hebasto opened pull request #22811: build: Fix depends build system when working with subtargets (master...210826-subtarget) https://github.com/bitcoin/bitcoin/pull/22811
5702021-08-26T23:08:45 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
5712021-08-26T23:11:19 *** gambpang <gambpang!~ishipman@207.181.230.156> has quit IRC (Remote host closed the connection)
5722021-08-26T23:16:17 *** jesseposner_ <jesseposner_!~jesse@c-24-5-105-39.hsd1.ca.comcast.net> has quit IRC (Ping timeout: 248 seconds)
5732021-08-26T23:16:24 *** jarthur <jarthur!~jarthur@2603-8080-1540-002d-9d7c-c2fd-8741-43d9.res6.spectrum.com> has quit IRC (Quit: jarthur)
5742021-08-26T23:16:55 *** jesseposner <jesseposner!~jesse@c-24-5-105-39.hsd1.ca.comcast.net> has joined #bitcoin-core-dev
5752021-08-26T23:19:17 *** aitorjs <aitorjs!~aitorjs@184.76.76.188.dynamic.jazztel.es> has joined #bitcoin-core-dev
5762021-08-26T23:23:13 *** jesseposner <jesseposner!~jesse@c-24-5-105-39.hsd1.ca.comcast.net> has quit IRC (Ping timeout: 252 seconds)
5772021-08-26T23:24:24 *** jesseposner <jesseposner!~jesse@c-24-5-105-39.hsd1.ca.comcast.net> has joined #bitcoin-core-dev
5782021-08-26T23:25:51 *** jarthur <jarthur!~jarthur@2603-8080-1540-002d-7072-405b-f95f-69ad.res6.spectrum.com> has joined #bitcoin-core-dev
5792021-08-26T23:53:55 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
5802021-08-26T23:53:55 <bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/b8d45a3c2015...adccbb380b2e
5812021-08-26T23:53:55 <bitcoin-git> bitcoin/master faf7e48 MarcoFalke: Set regtest.BIP65Height = 111 to speed up tests
5822021-08-26T23:53:55 <bitcoin-git> bitcoin/master adccbb3 fanquake: Merge bitcoin/bitcoin#21862: test: Set regtest.BIP65Height = 111 to speed ...
5832021-08-26T23:53:57 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev
5842021-08-26T23:54:11 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has joined #bitcoin-core-dev
5852021-08-26T23:54:11 <bitcoin-git> [bitcoin] fanquake merged pull request #21862: test: Set regtest.BIP65Height = 111 to speed up tests (master...2105-testFasterBip65) https://github.com/bitcoin/bitcoin/pull/21862
5862021-08-26T23:54:12 *** bitcoin-git <bitcoin-git!~bitcoin-g@x0f.org> has left #bitcoin-core-dev