12026-02-19T00:20:51 *** moneyball_______ <moneyball_______!sid299869@id-299869.helmsley.irccloud.com> has quit IRC (Server closed connection)
22026-02-19T00:21:01 *** moneyball_______ <moneyball_______!sid299869@id-299869.helmsley.irccloud.com> has joined #bitcoin-core-dev
32026-02-19T00:30:51 *** glozow <glozow!sid453516@user/glozow> has quit IRC (Server closed connection)
42026-02-19T00:31:03 *** glozow <glozow!sid453516@user/glozow> has joined #bitcoin-core-dev
52026-02-19T00:36:11 *** johnny9dev <johnny9dev!johnny9dev@user/johnny9dev> has quit IRC (Server closed connection)
62026-02-19T00:36:23 *** johnny9dev <johnny9dev!johnny9dev@user/johnny9dev> has joined #bitcoin-core-dev
72026-02-19T00:36:35 <bitcoin-git> [bitcoin] achow101 pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/241ad5853bca...6d482b22de15
82026-02-19T00:36:35 <bitcoin-git> bitcoin/master 331a527 Pol Espinasa: wallet, rpc:remove settxfee and paytxfee
92026-02-19T00:36:35 <bitcoin-git> bitcoin/master 24f93c9 Pol Espinasa: release note
102026-02-19T00:36:35 <bitcoin-git> bitcoin/master 6d482b2 Ava Chow: Merge bitcoin/bitcoin#32138: wallet, rpc: remove settxfee and paytxfee
112026-02-19T00:36:37 <bitcoin-git> [bitcoin] achow101 merged pull request #32138: wallet, rpc: remove settxfee and paytxfee (master...deletesettxfee) https://github.com/bitcoin/bitcoin/pull/32138
122026-02-19T00:43:46 <bitcoin-git> [bitcoin] achow101 pushed 7 commits to master: https://github.com/bitcoin/bitcoin/compare/6d482b22de15...4933d1fbbada
132026-02-19T00:43:47 <bitcoin-git> bitcoin/master 634cd60 Fabian Jahr: build: Add embedded asmap data
142026-02-19T00:43:47 <bitcoin-git> bitcoin/master 6202b50 Fabian Jahr: build: Generate ip_asn.dat.h during build process
152026-02-19T00:43:47 <bitcoin-git> bitcoin/master 6244212 Fabian Jahr: init, net: Implement usage of binary-embedded asmap data
162026-02-19T00:43:49 <bitcoin-git> [bitcoin] achow101 merged pull request #28792: build: Embedded ASMap [3/3]: Build binary dump header file (master...2023-10-asmap-in-source) https://github.com/bitcoin/bitcoin/pull/28792
172026-02-19T01:18:00 <bitcoin-git> [bitcoin] achow101 opened pull request #34620: [28.x] backports and 28.4rc2 (28.x...28.4rc2-backports) https://github.com/bitcoin/bitcoin/pull/34620
182026-02-19T01:22:56 *** jerryf_ <jerryf_!~jerryf@user/jerryf> has joined #bitcoin-core-dev
192026-02-19T01:23:52 *** jerryf <jerryf!~jerryf@user/jerryf> has quit IRC (Remote host closed the connection)
202026-02-19T01:33:26 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
212026-02-19T01:33:57 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
222026-02-19T01:35:15 *** dzxzg <dzxzg!~dzxzg@user/dzxzg> has quit IRC (Remote host closed the connection)
232026-02-19T01:59:24 *** brunoerg <brunoerg!~brunoerg@179.87.178.96> has joined #bitcoin-core-dev
242026-02-19T02:05:38 *** brunoerg <brunoerg!~brunoerg@179.87.178.96> has quit IRC (Ping timeout: 268 seconds)
252026-02-19T02:12:07 *** adil <adil!~Thunderbi@2402:4000:b161:424b:cda5:fb6b:ca85:6168> has joined #bitcoin-core-dev
262026-02-19T02:18:03 *** hirish <hirish!~hirish@ip135.ip-37-59-81.eu> has quit IRC (Ping timeout: 265 seconds)
272026-02-19T02:23:12 *** hirish <hirish!~hirish@ip135.ip-37-59-81.eu> has joined #bitcoin-core-dev
282026-02-19T02:29:31 *** sedited <sedited!~drgrid@2a01:4f8:c013:ed0b::1> has quit IRC (Server closed connection)
292026-02-19T02:29:49 *** TheCharlatan <TheCharlatan!~drgrid@2a01:4f8:c013:ed0b::1> has joined #bitcoin-core-dev
302026-02-19T02:35:24 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
312026-02-19T02:35:50 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
322026-02-19T02:42:51 *** adil <adil!~Thunderbi@2402:4000:b161:424b:cda5:fb6b:ca85:6168> has quit IRC (Quit: adil)
332026-02-19T03:01:03 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
342026-02-19T03:01:26 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
352026-02-19T03:09:46 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 268 seconds)
362026-02-19T03:19:32 *** freedomcode <freedomcode!~reardenco@shrugged.reardencode.com> has quit IRC (Server closed connection)
372026-02-19T03:19:47 *** reardencode <reardencode!~reardenco@shrugged.reardencode.com> has joined #bitcoin-core-dev
382026-02-19T03:20:59 *** eragmus___ <eragmus___!sid136308@id-136308.tinside.irccloud.com> has quit IRC (Server closed connection)
392026-02-19T03:21:08 *** eragmus___ <eragmus___!sid136308@id-136308.tinside.irccloud.com> has joined #bitcoin-core-dev
402026-02-19T03:28:19 *** jesseposner <jesseposner!sid580595@user/jesseposner> has quit IRC (Server closed connection)
412026-02-19T03:28:31 *** jesseposner <jesseposner!sid580595@user/jesseposner> has joined #bitcoin-core-dev
422026-02-19T03:30:19 *** rodarmor <rodarmor!sid210835@id-210835.helmsley.irccloud.com> has quit IRC (Server closed connection)
432026-02-19T03:30:29 *** rodarmor <rodarmor!sid210835@id-210835.helmsley.irccloud.com> has joined #bitcoin-core-dev
442026-02-19T03:38:11 *** BlueMatt[m] <BlueMatt[m]!~bluematt@2620:6e:a000:ce11::d> has quit IRC (Server closed connection)
452026-02-19T03:38:30 *** BlueMatt[m] <BlueMatt[m]!~bluematt@2620:6e:a000:ce11::d> has joined #bitcoin-core-dev
462026-02-19T03:39:24 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
472026-02-19T03:43:39 *** stickies-v <stickies-v!sid544753@id-544753.uxbridge.irccloud.com> has quit IRC (Server closed connection)
482026-02-19T03:43:51 *** stickies-v <stickies-v!sid544753@id-544753.uxbridge.irccloud.com> has joined #bitcoin-core-dev
492026-02-19T03:48:13 <bitcoin-git> [qa-assets] sipa opened pull request #257: Add new clusterlin_{sfl,linearize} fuzz seeds (main...sfl_fuzz_add) https://github.com/bitcoin-core/qa-assets/pull/257
502026-02-19T04:03:28 *** johnny9dev <johnny9dev!johnny9dev@user/johnny9dev> has quit IRC (Quit: Connection closed for inactivity)
512026-02-19T04:07:28 *** svanstaa_ <svanstaa_!~quassel@dsl-217-25-166-173.pool.bitel.net> has joined #bitcoin-core-dev
522026-02-19T04:07:36 *** svanstaa <svanstaa!~quassel@dsl-94-229-148-119.pool.bitel.net> has quit IRC (Ping timeout: 264 seconds)
532026-02-19T04:12:11 *** Sjors[m]1 <Sjors[m]1!~provooste@2620:6e:a000:ce11::1f> has quit IRC (Server closed connection)
542026-02-19T04:12:27 *** Sjors[m]1 <Sjors[m]1!~provooste@2620:6e:a000:ce11::1f> has joined #bitcoin-core-dev
552026-02-19T05:01:02 *** cmirror <cmirror!~cmirror@4.53.92.114> has quit IRC (Remote host closed the connection)
562026-02-19T05:01:32 *** cmirror <cmirror!~cmirror@4.53.92.114> has joined #bitcoin-core-dev
572026-02-19T05:20:59 *** RubenSomsen <RubenSomsen!sid301948@user/rubensomsen> has quit IRC (Server closed connection)
582026-02-19T05:21:17 *** RubenSomsen <RubenSomsen!sid301948@user/rubensomsen> has joined #bitcoin-core-dev
592026-02-19T05:34:36 *** aleggg <aleggg!~aleggg@189.110.152.194> has quit IRC (Ping timeout: 264 seconds)
602026-02-19T05:34:54 *** aleggg <aleggg!~aleggg@189.110.152.194> has joined #bitcoin-core-dev
612026-02-19T05:42:19 *** elichai2 <elichai2!sid212594@id-212594.hampstead.irccloud.com> has quit IRC (Server closed connection)
622026-02-19T05:42:33 *** elichai2 <elichai2!sid212594@id-212594.hampstead.irccloud.com> has joined #bitcoin-core-dev
632026-02-19T06:02:25 *** upekkha <upekkha!~Advanced@2a01:4f8:1c0c:49df::1> has quit IRC ()
642026-02-19T06:02:38 *** upekkha <upekkha!~Advanced@2a01:4f8:1c0c:49df::1> has joined #bitcoin-core-dev
652026-02-19T06:21:25 *** drenalizea <drenalizea!uid740952@id-740952.hampstead.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)
662026-02-19T06:24:20 <bitcoin-git> [gui-qml] johnny9 opened pull request #503: Introduce Qml Test Bridge (qt6...test-bridge) https://github.com/bitcoin-core/gui-qml/pull/503
672026-02-19T06:43:56 *** darosior <darosior!~darosior@109.205.214.46> has quit IRC (Quit: Ping timeout (120 seconds))
682026-02-19T06:44:08 *** darosior <darosior!~darosior@109.205.214.46> has joined #bitcoin-core-dev
692026-02-19T06:52:07 <bitcoin-git> [qa-assets] maflcko merged pull request #257: Add new clusterlin_{sfl,linearize} fuzz seeds (main...sfl_fuzz_add) https://github.com/bitcoin-core/qa-assets/pull/257
702026-02-19T06:52:09 <bitcoin-git> [qa-assets] maflcko pushed 2 commits to main: https://github.com/bitcoin-core/qa-assets/compare/5203dc6f4109...195b736c7401
712026-02-19T06:52:10 <bitcoin-git> qa-assets/main f66d60f Pieter Wuille: Add new clusterlin_{sfl,linearize} fuzz seeds
722026-02-19T06:52:10 <bitcoin-git> qa-assets/main 195b736 maflcko: Merge pull request #257 from sipa/sfl_fuzz_add
732026-02-19T06:55:41 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
742026-02-19T06:56:02 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
752026-02-19T07:03:27 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Ping timeout: 252 seconds)
762026-02-19T07:03:31 *** meebey_ <meebey_!~meebey@nos.eu1.meebey.net> has quit IRC (Server closed connection)
772026-02-19T07:05:38 *** meebey <meebey!~meebey@nos.eu1.meebey.net> has joined #bitcoin-core-dev
782026-02-19T07:06:27 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
792026-02-19T07:09:28 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
802026-02-19T07:09:34 *** ghost43_ <ghost43_!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
812026-02-19T07:11:09 *** sliv3r__ <sliv3r__!~sliv3r__@user/sliv3r-:76883> has quit IRC (Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in)
822026-02-19T07:11:35 *** sliv3r__ <sliv3r__!~sliv3r__@user/sliv3r-:76883> has joined #bitcoin-core-dev
832026-02-19T07:36:11 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has quit IRC (Server closed connection)
842026-02-19T07:36:31 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has joined #bitcoin-core-dev
852026-02-19T07:54:39 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
862026-02-19T07:58:15 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Client Quit)
872026-02-19T08:04:38 *** timbo_xyz <timbo_xyz!~timbo@user/timbo-xyz:44979> has joined #bitcoin-core-dev
882026-02-19T08:11:57 *** sliv3r__- <sliv3r__-!~sliv3r__@user/sliv3r-:76883> has joined #bitcoin-core-dev
892026-02-19T08:12:24 *** sliv3r__ <sliv3r__!~sliv3r__@user/sliv3r-:76883> has quit IRC (Read error: Connection reset by peer)
902026-02-19T08:32:19 *** dlb76 <dlb76!~dlb76@user/dlb76> has quit IRC (Server closed connection)
912026-02-19T08:34:59 *** phantomcircuit_ <phantomcircuit_!~phantomci@2604:a880:1:20::f2:c001> has quit IRC (Server closed connection)
922026-02-19T08:35:16 *** phantomcircuit <phantomcircuit!~phantomci@192.241.205.97> has joined #bitcoin-core-dev
932026-02-19T08:35:29 *** dlb76 <dlb76!~dlb76@user/dlb76> has joined #bitcoin-core-dev
942026-02-19T08:44:32 *** JTL <JTL!~jtl@user/jtl> has quit IRC (Read error: Connection reset by peer)
952026-02-19T08:45:12 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
962026-02-19T08:45:22 *** JTL <JTL!~jtl@user/jtl> has joined #bitcoin-core-dev
972026-02-19T08:56:48 *** BUSY <BUSY!~BUSY@user/busy> has quit IRC (Ping timeout: 264 seconds)
982026-02-19T08:58:04 *** BUSY <BUSY!~BUSY@user/busy> has joined #bitcoin-core-dev
992026-02-19T09:01:18 *** Guyver2 <Guyver2!Guyver@77-174-98-73.fixed.kpn.net> has joined #bitcoin-core-dev
1002026-02-19T09:21:50 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Read error: Connection reset by peer)
1012026-02-19T09:21:59 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
1022026-02-19T09:35:32 *** jerryf_ <jerryf_!~jerryf@user/jerryf> has quit IRC (Remote host closed the connection)
1032026-02-19T09:35:49 *** jerryf <jerryf!~jerryf@user/jerryf> has joined #bitcoin-core-dev
1042026-02-19T10:19:20 <bitcoin-git> [bitcoin] fanquake pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/4933d1fbbada...8ee24d764a28
1052026-02-19T10:19:21 <bitcoin-git> bitcoin/master badcf1c fanquake: guix: fix typo in guix-codesign
1062026-02-19T10:19:21 <bitcoin-git> bitcoin/master 62e3785 fanquake: guix: don't export TZ twice
1072026-02-19T10:19:21 <bitcoin-git> bitcoin/master 8ee24d7 merge-script: Merge bitcoin/bitcoin#34604: guix: remove double export of `TZ`
1082026-02-19T10:19:22 <bitcoin-git> [bitcoin] fanquake merged pull request #34604: guix: remove double export of `TZ` (master...guix_cleanup) https://github.com/bitcoin/bitcoin/pull/34604
1092026-02-19T10:22:54 *** ghost43_ <ghost43_!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
1102026-02-19T10:23:14 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
1112026-02-19T10:37:41 <fjahr> #proposedmeetingtopic Embedded asmap release todos (e.g. https://github.com/bitcoin/bitcoin/pull/28792#discussion_r2826579455)
1122026-02-19T10:42:32 *** Guest41 <Guest41!~Guest41@2001:1c00:a107:500:2527:13a:ca22:b419> has joined #bitcoin-core-dev
1132026-02-19T10:44:51 *** cornfeedhobo <cornfeedhobo!~cornfeedh@user/cornfeedhobo> has quit IRC (Server closed connection)
1142026-02-19T10:46:12 *** Guest41 <Guest41!~Guest41@2001:1c00:a107:500:2527:13a:ca22:b419> has quit IRC (Client Quit)
1152026-02-19T10:51:26 *** cornfeedhobo <cornfeedhobo!~cornfeedh@user/cornfeedhobo> has joined #bitcoin-core-dev
1162026-02-19T11:00:51 *** otoburb <otoburb!~otoburb@user/otoburb> has quit IRC (Server closed connection)
1172026-02-19T11:01:08 *** otoburb <otoburb!~otoburb@user/otoburb> has joined #bitcoin-core-dev
1182026-02-19T11:24:50 *** Guyver2 <Guyver2!Guyver@77-174-98-73.fixed.kpn.net> has left #bitcoin-core-dev (Closing Window)
1192026-02-19T11:27:54 *** adil <adil!~Thunderbi@2402:4000:b161:424b:c8ac:bdf3:a30e:f965> has joined #bitcoin-core-dev
1202026-02-19T11:40:15 *** adil <adil!~Thunderbi@2402:4000:b161:424b:c8ac:bdf3:a30e:f965> has quit IRC (Quit: adil)
1212026-02-19T11:48:51 <l0rinc> sipa,andrewtoth: please see my measurements in https://github.com/bitcoin/bitcoin/pull/31132#issuecomment-3646563048 where I've compared dbcache 100-7000. There is some difference between dbcache=400 (03:56:25 for 900k blocks) and dbcache=2000 (03:33:51 for the same), but after that there isn't any measurable speedup - unless it's on network storage or hdd.
1222026-02-19T11:48:55 <l0rinc> But note that after the PR validation with 100 mb dbcache is still slightly faster than than master with 7 GB. Extracted a few other measurements from the PR to https://gist.github.com/l0rinc/a61db638f122ad4a4efd83f031980255
1232026-02-19T11:55:23 *** timbo_xyz <timbo_xyz!~timbo@user/timbo-xyz:44979> has quit IRC (Remote host closed the connection)
1242026-02-19T11:55:50 *** timbo_xyz <timbo_xyz!~timbo@user/timbo-xyz:44979> has joined #bitcoin-core-dev
1252026-02-19T11:57:42 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
1262026-02-19T11:58:04 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
1272026-02-19T12:01:55 *** brunoerg <brunoerg!~brunoerg@179.87.178.96> has joined #bitcoin-core-dev
1282026-02-19T12:13:29 *** brunoerg <brunoerg!~brunoerg@179.87.178.96> has quit IRC (Ping timeout: 260 seconds)
1292026-02-19T12:22:38 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
1302026-02-19T12:28:33 <bitcoin-git> [bitcoin] sedited pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/8ee24d764a28...5a8a427610ed
1312026-02-19T12:28:34 <bitcoin-git> bitcoin/master a099655 rkrux: scripted-diff: Update `DeriveType` enum values to mention ranged derivatio...
1322026-02-19T12:28:34 <bitcoin-git> bitcoin/master 5a8a427 merge-script: Merge bitcoin/bitcoin#32745: scripted-diff: Update DeriveType enum values ...
1332026-02-19T12:28:35 <bitcoin-git> [bitcoin] sedited merged pull request #32745: scripted-diff: Update DeriveType enum values to mention ranged derivations (master...derive-type) https://github.com/bitcoin/bitcoin/pull/32745
1342026-02-19T12:30:33 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
1352026-02-19T12:30:54 *** brunoerg <brunoerg!~brunoerg@179.87.178.96> has joined #bitcoin-core-dev
1362026-02-19T12:31:24 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Client Quit)
1372026-02-19T12:40:09 *** brunoerg <brunoerg!~brunoerg@179.87.178.96> has quit IRC (Ping timeout: 256 seconds)
1382026-02-19T12:41:51 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
1392026-02-19T12:54:14 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
1402026-02-19T12:54:34 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
1412026-02-19T13:05:10 *** TheCharlatan is now known as sedited
1422026-02-19T13:25:39 *** Anth0mk <Anth0mk!~Anth0mk@2a01:4f9:c012:2c3a::1> has quit IRC (Server closed connection)
1432026-02-19T13:25:55 *** Anth0mk <Anth0mk!~Anth0mk@static.120.6.27.37.clients.your-server.de> has joined #bitcoin-core-dev
1442026-02-19T13:45:54 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has joined #bitcoin-core-dev
1452026-02-19T13:48:13 *** brunoerg <brunoerg!~brunoerg@179.87.178.96> has joined #bitcoin-core-dev
1462026-02-19T13:53:05 *** brunoerg <brunoerg!~brunoerg@179.87.178.96> has quit IRC (Ping timeout: 265 seconds)
1472026-02-19T13:55:02 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
1482026-02-19T13:55:49 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
1492026-02-19T13:58:23 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has quit IRC (Quit: Client closed)
1502026-02-19T14:14:51 *** N4bu <N4bu!~Nabu@user/n4bu> has quit IRC (Server closed connection)
1512026-02-19T14:15:24 *** N4bu <N4bu!~Nabu@user/n4bu> has joined #bitcoin-core-dev
1522026-02-19T14:17:31 <bitcoin-git> [bitcoin] maflcko opened pull request #34622: test: assert_debug_log timeouts follow-up (master...2602-test-adl-follow-up) https://github.com/bitcoin/bitcoin/pull/34622
1532026-02-19T14:28:10 <bitcoin-git> [bitcoin] fanquake opened pull request #34623: Update secp256k1 subtree to latest master (master...secp256k1_subtree_update) https://github.com/bitcoin/bitcoin/pull/34623
1542026-02-19T14:28:49 *** andrewtoth_ <andrewtoth_!~andrewtot@gateway/tor-sasl/andrewtoth> has joined #bitcoin-core-dev
1552026-02-19T14:29:24 *** andrewtoth <andrewtoth!~andrewtot@gateway/tor-sasl/andrewtoth> has quit IRC (Remote host closed the connection)
1562026-02-19T14:38:05 *** timbo_xyz <timbo_xyz!~timbo@user/timbo-xyz:44979> has quit IRC (Quit: WeeChat 4.8.1)
1572026-02-19T14:41:37 *** apollodorus <apollodorus!~apollodor@94-226-216-172.access.telenet.be> has joined #bitcoin-core-dev
1582026-02-19T14:43:30 *** brunoerg <brunoerg!~brunoerg@2803:9810:48a1:8c08:f5c5:5e8c:68c5:a0c3> has joined #bitcoin-core-dev
1592026-02-19T14:47:45 *** brunoerg_ <brunoerg_!~brunoerg@179.87.176.178> has joined #bitcoin-core-dev
1602026-02-19T14:50:48 *** brunoer__ <brunoer__!~brunoerg@2803:9810:48a1:8c08:559c:36fa:b88e:7b7a> has joined #bitcoin-core-dev
1612026-02-19T14:51:09 *** brunoerg <brunoerg!~brunoerg@2803:9810:48a1:8c08:f5c5:5e8c:68c5:a0c3> has quit IRC (Ping timeout: 252 seconds)
1622026-02-19T14:53:52 *** brunoerg_ <brunoerg_!~brunoerg@179.87.176.178> has quit IRC (Ping timeout: 246 seconds)
1632026-02-19T14:55:14 <bitcoin-git> [bitcoin] HowHsu opened pull request #34625: cluster_linearize: add tests and benchmarks for chain and tree-shaped clusters (master...linearize-tests) https://github.com/bitcoin/bitcoin/pull/34625
1642026-02-19T15:09:55 *** brunoer__ <brunoer__!~brunoerg@2803:9810:48a1:8c08:559c:36fa:b88e:7b7a> has quit IRC (Remote host closed the connection)
1652026-02-19T15:10:31 *** brunoerg <brunoerg!~brunoerg@2803:9810:48a1:8c08:559c:36fa:b88e:7b7a> has joined #bitcoin-core-dev
1662026-02-19T15:18:40 *** brunoerg <brunoerg!~brunoerg@2803:9810:48a1:8c08:559c:36fa:b88e:7b7a> has quit IRC (Ping timeout: 245 seconds)
1672026-02-19T15:26:13 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has joined #bitcoin-core-dev
1682026-02-19T15:33:07 *** brunoerg <brunoerg!~brunoerg@2803:9810:48a1:8c08:559c:36fa:b88e:7b7a> has joined #bitcoin-core-dev
1692026-02-19T15:39:43 *** jurraca <jurraca!~jurraca@user/jurraca> has joined #bitcoin-core-dev
1702026-02-19T15:42:57 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
1712026-02-19T15:43:48 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
1722026-02-19T15:47:53 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has quit IRC (Ping timeout: 272 seconds)
1732026-02-19T15:47:53 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
1742026-02-19T15:48:52 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
1752026-02-19T15:50:29 *** Novo <Novo!~Novo@46.231.244.218> has joined #bitcoin-core-dev
1762026-02-19T15:55:08 *** sr_gi <sr_gi!~sr_gi@46.231.244.218> has joined #bitcoin-core-dev
1772026-02-19T15:57:34 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has joined #bitcoin-core-dev
1782026-02-19T15:58:18 *** dzxzg <dzxzg!~dzxzg@user/dzxzg> has joined #bitcoin-core-dev
1792026-02-19T15:59:25 *** Emc99 <Emc99!~Emc99@212.129.80.125> has joined #bitcoin-core-dev
1802026-02-19T16:00:00 *** maxedw_ is now known as maxedw
1812026-02-19T16:00:03 <fjahr> #startmeeting
1822026-02-19T16:00:03 <corebot> fjahr: Meeting started at 2026-02-19T16:00+0000
1832026-02-19T16:00:04 <corebot> fjahr: Current chairs: fjahr
1842026-02-19T16:00:05 <corebot> fjahr: Useful commands: #action #info #idea #link #topic #motion #vote #close #endmeeting
1852026-02-19T16:00:06 <corebot> fjahr: See also: https://hcoop-meetbot.readthedocs.io/en/stable/
1862026-02-19T16:00:07 <corebot> fjahr: Participants should now identify themselves with '#here' or with an alias like '#here FirstLast'
1872026-02-19T16:00:13 <dzxzg> hi
1882026-02-19T16:00:14 <maxedw> hi
1892026-02-19T16:00:17 <sr_gi> hi
1902026-02-19T16:00:17 <fjahr> #bitcoin-core-dev Meeting: abubakarsadiq achow101 _aj_ ajonas b10c brunoerg cfields darosior dergoegge dzxzg eugenesiegel fanquake fjahr furszy gleb glozow hebasto hodlinator instagibbs janb84 jarolrod jonatack josibake kanzure kevkevin laanwj LarryRuane lightlike l0rinc luke-jr maflcko marcofleon maxedw Murch pinheadmz provoostenator ryanofsky sdaftuar S3RK stickies-v sipa sliv3r__ sr_gi tdb3 theStack TheCharlatan vasild
1912026-02-19T16:00:18 <fjahr> willcl-ark
1922026-02-19T16:00:19 <sipa> hi
1932026-02-19T16:00:21 <brunoerg> hi
1942026-02-19T16:00:21 <dergoegge> hi
1952026-02-19T16:00:22 <eugenesiegel> hi
1962026-02-19T16:00:23 <theStack> hi
1972026-02-19T16:00:26 <marcofleon> hi
1982026-02-19T16:00:28 <jurraca> hi
1992026-02-19T16:00:31 <fjahr> There are two pre-proposed meeting topics this week. Any last minute ones to add?
2002026-02-19T16:00:31 <andrewtoth_> hi
2012026-02-19T16:00:32 <hebasto> hi
2022026-02-19T16:00:33 <furszy> hi
2032026-02-19T16:00:41 <fjahr> And I guess we will talk about feature freeze tomorrow briefly.
2042026-02-19T16:00:42 <stringintech> hi
2052026-02-19T16:00:47 <hodlinator> hi
2062026-02-19T16:01:12 <Novo> hi
2072026-02-19T16:01:31 <fjahr> Kicking off the WGs...
2082026-02-19T16:01:33 <fjahr> #topic Fuzzing WG Update (dergoegge)
2092026-02-19T16:01:59 <l0rinc> hi
2102026-02-19T16:02:04 <darosior> hi
2112026-02-19T16:02:04 <dergoegge> no update
2122026-02-19T16:02:05 <kanzure> hi
2132026-02-19T16:02:10 <yancy> hi
2142026-02-19T16:02:17 <fjahr> #topic Benchmarking WG Update (l0rinc, andrewtoth)
2152026-02-19T16:02:23 <l0rinc> Benchmarked the costmodel for #34138 on several different platforms
2162026-02-19T16:02:26 <corebot> https://github.com/bitcoin/bitcoin/issues/34138 | Cluster mempool: more accurate cost model for SFL by sipa · Pull Request #34138 · bitcoin/bitcoin · GitHub
2172026-02-19T16:02:43 <sipa> Hi!
2182026-02-19T16:02:52 <l0rinc> Had lots of reviews on the #34280 - thanks, keep them coming
2192026-02-19T16:02:53 <corebot> https://github.com/bitcoin/bitcoin/issues/34280 | Coins Cache Cleanup checklist · Issue #34280 · bitcoin/bitcoin · GitHub
2202026-02-19T16:02:57 <l0rinc> that's it from me - andrewtoth?
2212026-02-19T16:03:06 *** rkrux <rkrux!~rkrux@user/rkrux> has joined #bitcoin-core-dev
2222026-02-19T16:03:07 <andrewtoth_> Lots of great review on #34165, thank you! Had others do more benchmarking on #31132. Thanks!
2232026-02-19T16:03:09 <rkrux> hi
2242026-02-19T16:03:11 <corebot> https://github.com/bitcoin/bitcoin/issues/34165 | coins: don't mutate main cache when connecting block by andrewtoth · Pull Request #34165 · bitcoin/bitcoin · GitHub
2252026-02-19T16:03:14 <janb84> hi
2262026-02-19T16:03:14 <corebot> https://github.com/bitcoin/bitcoin/issues/31132 | validation: fetch block inputs on parallel threads 3x faster IBD by andrewtoth · Pull Request #31132 · bitcoin/bitcoin · GitHub
2272026-02-19T16:03:29 <pinheadmz> yo!
2282026-02-19T16:04:02 <fjahr> andrewtoth: anything else to add?
2292026-02-19T16:04:24 <andrewtoth_> that was it
2302026-02-19T16:04:28 <fjahr> #topic Silent Payments WG Update (Novo)
2312026-02-19T16:04:52 *** yonson <yonson!~yonson@wsip-70-166-87-132.sd.sd.cox.net> has quit IRC (Server closed connection)
2322026-02-19T16:04:52 <Novo> It's decided now that we will be limiting the max number of sp outputs in a tx
2332026-02-19T16:05:06 *** yonson <yonson!~yonson@2001:579:e320:bd:2575:23ba:a312:ba8> has joined #bitcoin-core-dev
2342026-02-19T16:05:18 <Novo> The current value is 1000. It is not part of the BIP yet and still being debated
2352026-02-19T16:05:32 <Novo> With this, we can solve the worst case scanning problem
2362026-02-19T16:05:43 *** johnny9dev <johnny9dev!johnny9dev@user/johnny9dev> has joined #bitcoin-core-dev
2372026-02-19T16:05:48 <Novo> I also experimented with a parallel scanning approach https://github.com/bitcoin-core/secp256k1/pull/1765#issuecomment-3907225436
2382026-02-19T16:06:18 <Novo> Works pretty well, but might require changes to the API
2392026-02-19T16:06:59 <Novo> In practice, users should not need to do this since worst case scanning time with a maximum of 1000Â outputs is in seconds
2402026-02-19T16:07:29 <Novo> Hence, there's not a lot of support to modify the API to support parallel scanning but we will see
2412026-02-19T16:07:42 <theStack> for the proposed K_max protocol change, I'm planning to open a BIP-352 PR today or tomorrow, with proper test vectors; no one has opposed the K_max=1000 suggestion, but different suggestions could still be made in that PR
2422026-02-19T16:07:56 <Novo> Nice theStack
2432026-02-19T16:08:17 <Novo> Nothing else to add
2442026-02-19T16:08:31 <fjahr> #topic Cluster Mempool WG Update (sdaftuar, sipa)
2452026-02-19T16:08:36 <sipa> We're getting very close with cluster mempool. #34023 was merged, and my last remaining PR is #34616 which I'd like to see in. There are a few more follow-ups like extra tests, RPC output, optimizations, and possible interaction with mining (to decide when to wake a waiting miners / cache blocks), but I think those aren't essential for feature freeze.
2462026-02-19T16:08:40 <corebot> https://github.com/bitcoin/bitcoin/issues/34023 | Optimized SFL cluster linearization by sipa · Pull Request #34023 · bitcoin/bitcoin · GitHub
2472026-02-19T16:08:41 <corebot> https://github.com/bitcoin/bitcoin/issues/34616 | Cluster mempool: SFL cost model (take 2) by sipa · Pull Request #34616 · bitcoin/bitcoin · GitHub
2482026-02-19T16:08:51 *** Novo <Novo!~Novo@46.231.244.218> has quit IRC (Quit: Client closed)
2492026-02-19T16:09:13 <sipa> That's it for me.
2502026-02-19T16:09:32 *** abubakarsadiq <abubakarsadiq!uid602234@id-602234.hampstead.irccloud.com> has joined #bitcoin-core-dev
2512026-02-19T16:09:56 <fjahr> Thanks, I didn't see kernel or net split...
2522026-02-19T16:10:24 <fjahr> #topic v31 feature freeze
2532026-02-19T16:10:56 <fjahr> Anything to be suggested to be added or removed? Anything making a push back necessary?
2542026-02-19T16:11:01 *** Bob <Bob!~Bob@1-164-64-230.dynamic-ip.hinet.net> has joined #bitcoin-core-dev
2552026-02-19T16:11:25 *** Bob is now known as Guest1152
2562026-02-19T16:11:25 *** Guest1152 <Guest1152!~Bob@1-164-64-230.dynamic-ip.hinet.net> has quit IRC (Client Quit)
2572026-02-19T16:11:39 <andrewtoth_> https://github.com/bitcoin/bitcoin/milestone/74
2582026-02-19T16:11:43 *** Bob2026 <Bob2026!~Bob2026@1-164-64-230.dynamic-ip.hinet.net> has joined #bitcoin-core-dev
2592026-02-19T16:12:03 <fjahr> andrewtoth: Thanks, I was just looking for it :)
2602026-02-19T16:13:30 <fjahr> It's still a pretty long list, I didn't have time to go through it yet. Any comments?
2612026-02-19T16:13:39 <fjahr> Otherwise, please review!
2622026-02-19T16:13:50 <fanquake> I don't think there's anything that would require pushing back. Things just need review. Plenty of double-ups where it's the bug report + PR both tagged.
2632026-02-19T16:14:00 <fanquake> Mostly bug reports for bugs introduced in this cycle.
2642026-02-19T16:14:35 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
2652026-02-19T16:14:53 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
2662026-02-19T16:15:02 <fjahr> #topic Bump default -dbcache setting? (sipa)
2672026-02-19T16:16:02 <sipa> Hi, I've been thinking about this for a while, and it seems to me that the default dbcache setting (450 MiB) is a bit outdated for most systems these days.
2682026-02-19T16:16:29 <l0rinc> let me repeat what I posted here a few hours ago: `sipa,andrewtoth: please see my measurements in https://github.com/bitcoin/bitcoin/pull/31132#issuecomment-3646563048 where I've compared dbcache 100-7000. There is some difference between dbcache=400 (03:56:25 for 900k blocks) and dbcache=2000 (03:33:51 for the same), but after that there isn't any measurable speedup - unless it's on network storage or hdd.`
2692026-02-19T16:16:33 <l0rinc> `But note that after the PR validation with 100 mb dbcache is still slightly faster than than master with 7 GB. Extracted a few other measurements from the PR to`
2702026-02-19T16:16:50 *** Guest80 <Guest80!~Guest80@173.38.117.69> has joined #bitcoin-core-dev
2712026-02-19T16:16:55 <darosior> It has been outdated, but with the current RAM prices, it's back to totally fine :p
2722026-02-19T16:17:00 <sipa> darosior: haha
2732026-02-19T16:17:04 <theStack> :D
2742026-02-19T16:17:35 <l0rinc> as andrewtoth mentioned yesterday #31132 modifies this assumption and even dbcache=100 will be faster than master
2752026-02-19T16:17:38 <corebot> https://github.com/bitcoin/bitcoin/issues/31132 | validation: fetch block inputs on parallel threads 3x faster IBD by andrewtoth · Pull Request #31132 · bitcoin/bitcoin · GitHub
2762026-02-19T16:17:41 <sipa> I understand that there are users who still run on minimal hardware, for which a default bump might not be appropriate, but still - I don't think there is really any problem with e.g. if you're on a 64-bit system and have say over 8 or 16 GiB of RAM, defaulting to 2 GiB dbcache
2772026-02-19T16:17:55 *** Guest80 <Guest80!~Guest80@173.38.117.69> has quit IRC (Client Quit)
2782026-02-19T16:17:59 <darosior> 1GiB should be totally fine in my opinion, but i defer my judgement to people that actively monitor that area (like Lorinc and Andrew who chimed in)
2792026-02-19T16:18:18 *** epicleafies <epicleafies!~epicleafi@2600:1700:3900:a0ef:ed53:622:e29c:6859> has joined #bitcoin-core-dev
2802026-02-19T16:18:27 <l0rinc> I can barely run an IBD on a node with 2 GB memory
2812026-02-19T16:18:50 <andrewtoth_> Yeah I think it would be a big speedup for network connected storage, which I think is the majority of nodes being run
2822026-02-19T16:18:54 <l0rinc> and after Andrew's parallelization change the difference won't be that big - can we postpone this decision after it lands?
2832026-02-19T16:18:56 <andrewtoth_> I'm more concerned about steady state than IBD. We don't periodically clear the cache anymore unless it grows too big. So, today users can run it for months/years and it won't exceed 450MB. If we update this default then maybe users who run their nodes on low memory systems and just set and forget will come back to an OOM crashed node after some months.
2842026-02-19T16:19:02 <darosior> Hasn't the expectation always been that people running on minimal hardware tweak their settings anyways? We have docs for this, and specs for minimal hardware must have been a lot lower a decade ago when we had the same default.
2852026-02-19T16:19:37 <sipa> l0rinc: my (largely unsubstantiated) guess is that there are settings (super slow spinning USB-connected disk) with very slow I/O, where even with parallel fetch, a large dbcache makes a big difference
2862026-02-19T16:19:59 <darosior> 2 GiB sounds good to me as a default too, for what it's worth.
2872026-02-19T16:20:07 <fjahr> It is also notable that this may be shared with the indexes if they are active
2882026-02-19T16:20:08 <Murch[m]> Itâs my impression that especially a lot of the low-powered devices are run by people that donât configureâ¦
2892026-02-19T16:20:16 <l0rinc> yes, as mentioned above, HDDs are definitely affected even after the parallel fetcher
2902026-02-19T16:20:35 <l0rinc> most people I talked to (including node providers) are afraid to change the defaults
2912026-02-19T16:20:38 *** afiore <afiore!~afiore@user/afiore> has quit IRC (Remote host closed the connection)
2922026-02-19T16:20:55 <pinheadmz> Murch[m] i wouldnt count on that, arent there plenty of SE questions about running on a Pi? suggested confs are easy to find
2932026-02-19T16:20:57 *** afiore <afiore!~afiore@user/afiore> has joined #bitcoin-core-dev
2942026-02-19T16:21:57 <darosior> Maybe a more conservative bump to 1GiB then?
2952026-02-19T16:22:02 <dzxzg> It would be nice if out-of-memory behavior was better before/along with raising the default, e.g. monitoring memory pressure / available memory and dynamically decreasing sizes of caches to avoid OOM
2962026-02-19T16:22:19 <l0rinc> it was changed a decade ago from 100 to 300: https://github.com/bitcoin/bitcoin/commit/32cab91278651d07a11132b7636dc3d21144e616#diff-d102b6032635ce90158c1e6e614f03b50e4449aa46ce23370da5387a658342fdR25-R27
2972026-02-19T16:22:37 <Murch[m]> Yeah, l0rinc, wasnât there something that limited the `dbcache` setting on basis of the RAM we had to 75% of the RAM?
2982026-02-19T16:22:50 <andrewtoth_> dzxzg: yeah, having something like #19873 would make this an easier discussion.
2992026-02-19T16:22:53 <corebot> https://github.com/bitcoin/bitcoin/issues/19873 | Flush dbcache early if system is under memory pressure by luke-jr · Pull Request #19873 · bitcoin/bitcoin · GitHub
3002026-02-19T16:22:56 <_aj_> l0rinc's graph suggested 1GB would get most of the benefit, i thought
3012026-02-19T16:23:05 <l0rinc> yes, we have a warning now if the dbcache is too high compared to the total ram
3022026-02-19T16:23:41 <l0rinc> I could get behind that if we separated dbcache during and after IBD (which we partially do already by stealing the mempool memory)
3032026-02-19T16:24:13 <sipa> fwiw, i'm motivated by seeing people complain about days-long syncs - which usually is a sign there is more wrong than just dbcache, but it keeps reminding me that i think 450 MiB is silly today
3042026-02-19T16:24:46 <Murch[m]> Well, it is plenty in the steady state at the chaintipâ¦
3052026-02-19T16:24:55 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
3062026-02-19T16:24:57 <sipa> yeah, this is just about IBD
3072026-02-19T16:24:57 <hodlinator> couldn't it be a sign of trying to fit the UTXO set in the -dbcache and running into swapping issues?
3082026-02-19T16:25:07 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
3092026-02-19T16:25:12 <hodlinator> ...due to running out of RAM
3102026-02-19T16:25:45 <sipa> hodlinator: not in the recent example (#34601) i think, but yes
3112026-02-19T16:25:46 <corebot> https://github.com/bitcoin/bitcoin/issues/34601 | bitcoind sync gets very, very slow on Augst 2023 in btc chain (maybe 2/3 progressed or something like that) · Issue #34601 · bitcoin/bitcoin · GitHub
3122026-02-19T16:25:49 <Murch[m]> Yeah, I heard that malarkey a few times, too, that people thought dbcache has to be bigger than the UTXO set. But we should catch that with the warning, right?
3132026-02-19T16:26:12 <l0rinc> it could, that's why we have the new warning now - and why I opened #34606
3142026-02-19T16:26:14 <corebot> https://github.com/bitcoin/bitcoin/issues/34606 | [RFC] common: warn on high swap usage by l0rinc · Pull Request #34606 · bitcoin/bitcoin · GitHub
3152026-02-19T16:26:15 <andrewtoth_> l0rinc: agreed, switching to lower dbcache after IBD would make this safer
3162026-02-19T16:26:33 <hodlinator> yes, it should warn, provided the user runs a newer version.
3172026-02-19T16:26:46 <andrewtoth_> bumping to 2GB during IBD on 64 bit systems then lowering to current default after IBD would be great
3182026-02-19T16:26:47 *** rkrux <rkrux!~rkrux@user/rkrux> has quit IRC (Quit: Client closed)
3192026-02-19T16:27:09 <jonatack> hi
3202026-02-19T16:27:19 <darosior> andrewtoth_: why safer? More optimal maybe, but i don't see how a larger dbcache makes things less safe at tip.
3212026-02-19T16:27:21 <_aj_> good grief, the utxo set via usb2?
3222026-02-19T16:27:23 <sipa> andrewtoth_: that seems weird to me, if you have enough memory for one, why not use it all the time?
3232026-02-19T16:27:24 <l0rinc> I don't mind pushing a PR that creates a 2 gb default for anything having e.g. 8 gb total memory and reverting to 450 after IBD
3242026-02-19T16:27:50 <sipa> if the concern is OOMing later, we can try a preallocation run - just fill the dbcache once at startup and wipe it
3252026-02-19T16:27:58 <l0rinc> but even 2 GB is too high for a 4 GB machine
3262026-02-19T16:28:18 <Murch[m]> sipa: People run all sorts of other stuff on their Bitcoin boxes now, but most of it only after IBD. So they might have more RAM for bitcoind before IBD is finished
3272026-02-19T16:28:40 <sipa> yeah fair
3282026-02-19T16:28:47 <andrewtoth_> what Murch said
3292026-02-19T16:28:50 <darosior> I see
3302026-02-19T16:28:56 <darosior> Would everyone be happy with a 1GiB default? That's already more than twice as better as today, and could mitigate the concerns raised here?
3312026-02-19T16:28:58 <dzxzg> It would be good to know connection times at the tip as a function of dbcache size
3322026-02-19T16:29:30 <l0rinc> I have regular OOMs on 2GB and 4GB boxes ... everything seems fine and after a while something triggers an OOM even with the safety nets. These are so close to the limit by default
3332026-02-19T16:29:32 <darosior> s/twice as better/twice better/ oui oui baguette
3342026-02-19T16:30:02 <andrewtoth_> dzxzg: I am trying to measure that for #31132. With default dbcache today the cache is not flushed for about 3 weeks. So it's a long thing to measure.
3352026-02-19T16:30:05 <corebot> https://github.com/bitcoin/bitcoin/issues/31132 | validation: fetch block inputs on parallel threads 3x faster IBD by andrewtoth · Pull Request #31132 · bitcoin/bitcoin · GitHub
3362026-02-19T16:30:11 <Murch[m]> 1 GB seems like an improvement. It would be great if we could do something conditionally on how much RAM the system has
3372026-02-19T16:30:12 <darosior> l0rinc: by this token we will never be able to bump defaults ever again, because someone will still have a 4GiB box somewhere a decade from now
3382026-02-19T16:30:41 <darosior> We have configuration for a reason, defaults should represent the vast majority of users, not the lowest common denominator possible?
3392026-02-19T16:31:15 <fjahr> 1 GB sounds like a good compromise to me, again, also keep in mind this may be shared with the indexes
3402026-02-19T16:31:22 <lightlike> is the suggested bump meant to go into v31 still?
3412026-02-19T16:31:23 <sipa> i also like the idea of having presets, like are you running in a very resource-constrained system, or a giant machine? which could control things like dbcache, mempool size, network buffers, connection counts, ...
3422026-02-19T16:31:35 <_aj_> pruning
3432026-02-19T16:31:46 <sipa> which may be more interesting for config-averse people to choose than manually tweaking values
3442026-02-19T16:31:51 <Murch[m]> sipa: That sounds interesting.
3452026-02-19T16:31:54 <darosior> sipa: makes sense.
3462026-02-19T16:32:03 <l0rinc> I'm all for e/acc, it's just something I see on the lower-end devices - I would go for 100 if lower than 2 GB, 400 if lower than 4 GB and 1 GB if higher
3472026-02-19T16:32:20 <sipa> #8437 :p
3482026-02-19T16:32:21 <corebot> https://github.com/bitcoin/bitcoin/issues/8437 | Separate resource usage profiles · Issue #8437 · bitcoin/bitcoin · GitHub
3492026-02-19T16:32:52 <andrewtoth_> l0rinc: I think you need to configure to get it to run on 2GB at all, right?
3502026-02-19T16:33:04 <_aj_> would just providing example three configs be a good/easy way of doing that?
3512026-02-19T16:33:10 <l0rinc> yes, that already needs a -dbcache=100
3522026-02-19T16:33:12 <dzxzg> I think it's confusing to have to tweak the size of each of bitcoind's memory pools individually, instead of setting a single resource usage target
3532026-02-19T16:33:15 <Murch[m]> Maybe we can reconsider that in light of itâs 10th anniversary coming up ^^
3542026-02-19T16:33:25 <sipa> (its)
3552026-02-19T16:33:47 <andrewtoth_> I think 1GB would be an improvement. Put it front and center in the release notes.
3562026-02-19T16:34:04 <darosior> yay
3572026-02-19T16:34:18 <sipa> 100 / 400 / 1000 depending on ram size makes sense to me
3582026-02-19T16:34:25 <Murch[m]> In before âBitcoin Core hates Raspberry Pi users!â
3592026-02-19T16:34:27 <Murch[m]> :p
3602026-02-19T16:34:31 <andrewtoth_> lol
3612026-02-19T16:34:32 <sipa> yes, i mean for 31.0
3622026-02-19T16:34:53 <andrewtoth_> sipa, l0rinc: yes, 100/400/1000
3632026-02-19T16:35:00 <Murch[m]> sipa: I thought that it was not available on all systems or smth
3642026-02-19T16:35:02 <l0rinc> "Put it front and center in the release notes" - clarifying that this isn't because we want more spam :p
3652026-02-19T16:35:12 <Murch[m]> As in, we donât know in Bitcoin Core how much the system has?
3662026-02-19T16:35:32 <sipa> Murch[m]: we always know if we're on 32-bit vs 64-bit, unsure about accessing ram size on every OS
3672026-02-19T16:36:09 <jonatack> presets changing multiple config options as a user-friendly suggestion sounds good indeed
3682026-02-19T16:36:16 <_aj_> it's only going to be linux/bsd that have low memory though?
3692026-02-19T16:36:44 <sipa> _aj_: i'd guess that many people run on old windows boxes
3702026-02-19T16:36:46 <jonatack> if feasible, avoiding too much devilry in the details
3712026-02-19T16:37:03 <l0rinc> we have access to total memory, introduced in https://github.com/bitcoin/bitcoin/pull/33333/changes#diff-248c2f4789084c026a9c5a8e718cc117b9d32ffb91a09f541ae1abc0eef7e6f6R114-R123
3722026-02-19T16:37:34 <Murch[m]> well then, default based on available RAM sounds like a great idea!
3732026-02-19T16:38:19 <sipa> ok i think we can conclude this topic and discuss on a PR if someone(?) creates one
3742026-02-19T16:38:23 <darosior> Murch[m]: doesn't that contradict your previous point that it's going to make the process OOM if the user runs anything else besides bitcoind?,,
3752026-02-19T16:38:34 <yancy> availble ram or total system ram?
3762026-02-19T16:38:41 <darosior> sipa: +1
3772026-02-19T16:38:48 <fjahr> Yeah, let's continue
3782026-02-19T16:38:50 <fjahr> #topic Embedded asmap release todos (e.g. https://github.com/bitcoin/bitcoin/pull/28792#discussion_r2826579455) (fjahr)
3792026-02-19T16:38:51 <l0rinc> I'll push a PR for that today, thanks for the feedback. To be clear, should we revert to a lower value after IBD or should we choose values that make sense regardless (excluding the barrowed mempool 300 MB)?
3802026-02-19T16:39:00 <fjahr> I didnât have time to prepare anything for this but since it came up and might be relevant for the wider group, I thought I would make everyone aware of the ideas in the comment thread there.
3812026-02-19T16:39:08 <fjahr> tldr; the ideas are: moving the asmap-data repo into bitcoin-core org, letting participants of the collaborative runs sign their results and transcript with the necessary script and place for sharing, sharing the raw data before processing, notifying users of an older asmap data (potentially only after default).
3822026-02-19T16:39:12 <darosior> l0rinc: in my opinion this should be a separate improvement.
3832026-02-19T16:39:16 <fjahr> Note that these ideas are in addition to the suggested process already described here: https://github.com/bitcoin/bitcoin/blob/master/doc/asmap-data.md
3842026-02-19T16:39:23 <fjahr> Anything that people would like to add or comment on there? I will collect and track them in the asmap issue.
3852026-02-19T16:40:16 <sipa> moving asmap-data to bitcoin-core org makes sense, as does having some kind of attestation process for collaborative asmap creation participants, effectively signing off on "i ran kartograf with these settings at this point in time, and obtained this"
3862026-02-19T16:41:02 *** stringintech <stringintech!~stringint@user/stringintech> has quit IRC (Remote host closed the connection)
3872026-02-19T16:41:23 <Murch[m]> darosior: That was meant to be a point why 1 GB might be too big, when a box has only 4 GB
3882026-02-19T16:41:54 <Murch[m]> But if we generally pick defaults based on RAM, weâd probably do something smaller for a 4 GB box?
3892026-02-19T16:42:18 *** Emc37 <Emc37!~Emc99@212.129.76.158> has joined #bitcoin-core-dev
3902026-02-19T16:42:22 <l0rinc> I'll add a PR for that and we can discuss there, thanks for the feedback!
3912026-02-19T16:42:28 <Murch[m]> Sorry, can talk more later. Different topic now.
3922026-02-19T16:43:12 <fjahr> Ok, I guess the RAM question is still more exciting than this question. Still feel free to comment here or in the links later if you have opinion.
3932026-02-19T16:43:14 <fjahr> Anything else to discuss?
3942026-02-19T16:43:39 <andrewtoth_> fjahr congrats on getting asmap merged!
3952026-02-19T16:43:50 <darosior> Are people interested in picking back up the GUI topic from last week. I didn't attend but reading the backlog it doesn't seem like much was decided.
3962026-02-19T16:43:58 <Murch[m]> I havenât looked much into it, but if weâre shipping the ASMAP default, putting the attestation into the Bitcoin Core org makes sense
3972026-02-19T16:43:59 <fjahr> andrewtoth: thank you :)
3982026-02-19T16:44:29 <darosior> I guess i didn't see hebasto nor achow and we'd need them to discuss GUI stuff..
3992026-02-19T16:44:47 <hebasto> darosior: hi
4002026-02-19T16:44:50 <fjahr> Murch: default on is for the future but the process should keep that in mind already I think
4012026-02-19T16:44:51 <darosior> oh hi
4022026-02-19T16:45:19 <bitcoin-git> [bitcoin] sedited pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/5a8a427610ed...910bd1c964b6
4032026-02-19T16:45:19 <bitcoin-git> bitcoin/master fac3eca MarcoFalke: rpc: Properly parse -rpcworkqueue/-rpcthreads
4042026-02-19T16:45:21 <bitcoin-git> [bitcoin] sedited merged pull request #34582: rpc: Properly parse -rpcworkqueue/-rpcthreads (master...2602-int-arg) https://github.com/bitcoin/bitcoin/pull/34582
4052026-02-19T16:45:51 <darosior> hebasto: anything to add, following up on last week's discussion? What should be the way forward?
4062026-02-19T16:46:09 *** Emc99 <Emc99!~Emc99@212.129.80.125> has quit IRC (Ping timeout: 272 seconds)
4072026-02-19T16:46:16 *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has joined #bitcoin-core-dev
4082026-02-19T16:46:29 <fjahr> I think the outcome was we should wait with a final decision until we meet in person?
4092026-02-19T16:47:12 <fjahr> Seems like people are exploring options, like will's vibe code rpc experiment
4102026-02-19T16:47:12 <darosior> It does not seem like any of the discussion we've had in person have ever made this move forward.
4112026-02-19T16:47:16 <fanquake> It'd be good to know about #33684 (given the Qs there, or maybe have a dedicated issue). There doesn't seem to be an answer to where new features should be added? Seems like something we should know, to unblock progress/prevent wasted work/have any clarity.
4122026-02-19T16:47:18 <corebot> https://github.com/bitcoin/bitcoin/issues/33684 | Async Payjoin · Issue #33684 · bitcoin/bitcoin · GitHub
4132026-02-19T16:47:30 <hebasto> fanquake posted a detailed plan that allows us bring more gui-only deps into the release process -- https://github.com/bitcoin/bitcoin/issues/29914#issuecomment-3921585808
4142026-02-19T16:48:10 <johnny9dev> I did some work as well since last week to get everything for gui-qml in a PR or merged so all work from last year is in the default branch for it. I have also given hebasto a feature comparison summary
4152026-02-19T16:48:20 <hebasto> ^ this
4162026-02-19T16:48:22 <fjahr> darosior: is that a problem with the topic or meeting in person?
4172026-02-19T16:48:31 <darosior> :)
4182026-02-19T16:48:47 <fanquake> johnny9dev: so you're working on something that is going to whotely replace the current widgets gui right?
4192026-02-19T16:49:03 <fanquake> *wholely
4202026-02-19T16:49:12 <johnny9dev> I think so.
4212026-02-19T16:49:12 <sipa> wholly?
4222026-02-19T16:49:14 <darosior> So is the plan to replace the QT widget GUI with the QML GUI?
4232026-02-19T16:49:32 <darosior> Would this be IPC based?
4242026-02-19T16:49:38 <hebasto> not now
4252026-02-19T16:49:42 <fjahr> I think having some time to think about it and explore options is good, I haven't had time to look into it more because of getting stuff done for feature freeze
4262026-02-19T16:49:43 <johnny9dev> last year I wouldnt have agreed to such a think but today with the tools we have. i might
4272026-02-19T16:50:27 <fanquake> johnny9dev: great, can we get a writeup or similar, that explains the architecture, dependencies needed, how are we going to decouple it from the current code, etc
4282026-02-19T16:50:40 <sedited> darosior's delving post was also discussed here, which at least gives a taste of what gui users might think of it https://stacker.news/items/1436922
4292026-02-19T16:50:51 <fjahr> Maybe a way to encourage this would be to let people note down where they currently stand in a table similar to what we had on controversial issues in the past? Does that sound interesting?
4302026-02-19T16:50:51 <johnny9dev> yeah, I will work towards that and get some help from hebasto as well
4312026-02-19T16:50:54 <fanquake> I guess this means that currently, nothing is being added to the gui, until qml ships?
4322026-02-19T16:51:08 <hebasto> correct
4332026-02-19T16:51:17 <hebasto> once the release process is safe regarding more gui deps, we will be able to switch to qml
4342026-02-19T16:51:25 <darosior> sedited: oh, i hadn't seen that, thanks.
4352026-02-19T16:51:46 <fanquake> It's not just the release process. i.e the whole subtree thing needs to be fixed/
4362026-02-19T16:52:06 <dzxzg> given that the timeline for qml is not bounded, does it make sense to stop adding features to qtwidgets?
4372026-02-19T16:52:15 <hebasto> subtree is minor issue, I have a wip branch
4382026-02-19T16:52:35 <fanquake> and process separation?
4392026-02-19T16:52:40 <hebasto> dzxzg: it is de-facto
4402026-02-19T16:52:59 <hebasto> process separation is a next step
4412026-02-19T16:53:09 <dzxzg> hebasto: To make sure I understand, you mean that as a fact, no one is adding features to qtwidgets today?
4422026-02-19T16:53:13 <fanquake> I take it nothing is blocked on designers now either?
4432026-02-19T16:53:35 <hebasto> right
4442026-02-19T16:53:56 <Murch[m]> interesting thread, sedited
4452026-02-19T16:54:20 <hebasto> dzxzg: noone is actively reviewing already suggested features
4462026-02-19T16:54:33 <darosior> What's the status of the QML GUI, as in, in your branch johnny9dev? My understanding was that it was still under heavy development, but is it now close to feature complete?
4472026-02-19T16:54:55 <hebasto> feature comparison tables will be available shortly
4482026-02-19T16:55:06 <dzxzg> hebasto: That makes sense, I would just oppose it as a matter of policy, e.g. if people do start showing up and reviewing gui PR's, I don't think they should be rejected on the basis of the qtwidgets gui being replaced with qml,
4492026-02-19T16:55:27 <hebasto> dzxzg: sure
4502026-02-19T16:56:03 *** nervana21 <nervana21!~nervana21@69.206.165.174> has joined #bitcoin-core-dev
4512026-02-19T16:56:09 <darosior> dzxzg: Is adding new features to the GUI even a goal? My understanding was that its main purpose was backward compatibility to support existing users, but that if you wanted a neat GUI with all the new features, other projects already do it better, and are a more appropriate place for further development.
4522026-02-19T16:56:20 <johnny9dev> there is work to do for sure. working towards understanding how close at the moment.
4532026-02-19T16:56:54 <fjahr> 3 minutes left...
4542026-02-19T16:57:05 <sipa> darosior: people might not agree on what the goal is
4552026-02-19T16:57:09 <dzxzg> darosior: I mean it may not be a goal for you
4562026-02-19T16:57:40 <pinheadmz> darosior personally, if the gui had harwarde wallet support i would never need another bitcoin program, i want that for myself ;-)
4572026-02-19T16:57:53 <sipa> we could agree on explicit goals, but that doesn't align well with the notion of not telling people what they should work on
4582026-02-19T16:57:59 <darosior> it's not like it does not come with its own externalities
4592026-02-19T16:58:03 <pinheadmz> so i guess that feature should go in QML then ?
4602026-02-19T16:58:04 <fanquake> sipa: ideally we can agree on goals like, not wasting developers time, by not having any clarity around what the project is doing
4612026-02-19T16:58:28 <fanquake> i.e: someone shows up implementing a new gui feature, unaware that nothing is going to be added to the current gui, or they should have added it to qml
4622026-02-19T16:58:29 <fjahr> johnny9dev: If we continue with the qml gui as originally planned I think it would be good to make a plan for attracting new contributors in a more serious manner as well
4632026-02-19T16:58:31 <sipa> fanquake: agreed, but i think it's more a matter of setting expectations than strictly deciding what is being worked on
4642026-02-19T16:58:31 <darosior> If it was a separate program in a separate project, i agree, if people are interested in doing stuff, good for them, good for their users. But the reality is not so.
4652026-02-19T16:59:02 <fanquake> given that qml has taken 5 years, and not shipped, seems like a good time to try clarify some of these things
4662026-02-19T16:59:38 <dzxzg> it kind of seems like shooting oneself in the foot to stop all qtwidgets gui development in the hope that someday it's replaced by qml, if you dislike the gui you may not see it that way since it perpetuates the present problems with the gui
4672026-02-19T16:59:41 <hebasto> again, with https://github.com/bitcoin/bitcoin/issues/29914#issuecomment-3921585808, I can see now a straight path for switching to qml
4682026-02-19T17:00:00 <fjahr> I guess we can continue the conversation next week :)
4692026-02-19T17:00:04 <fjahr> #endmeeting
4702026-02-19T17:00:05 <corebot> fjahr: Meeting ended at 2026-02-19T17:00+0000
4712026-02-19T17:00:06 <corebot> fjahr: Raw log: https://achow101.com/ircmeetings/2026/bitcoin-core-dev.2026-02-19_16_00.log.json
4722026-02-19T17:00:07 <corebot> fjahr: Formatted log: https://achow101.com/ircmeetings/2026/bitcoin-core-dev.2026-02-19_16_00.log.html
4732026-02-19T17:00:08 <corebot> fjahr: Minutes: https://achow101.com/ircmeetings/2026/bitcoin-core-dev.2026-02-19_16_00.html
4742026-02-19T17:00:11 <Murch[m]> Itâs always right before something is done that people get disenchanted? :p
4752026-02-19T17:00:19 <fanquake> hebasto: I hope qml wasn't waiting 5 years for me to leave that comment
4762026-02-19T17:00:35 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has quit IRC (Quit: Client closed)
4772026-02-19T17:00:39 <sipa> my point is mostly a response to dzxzg... if some group of people were hypothetically to show up and start working on, and reviewing and testing qtwidgets stuff, then i don't see the problem with those being merged... but getting clarity on whether such a group or not exists matters, and may inform people to not take on such projects if there isn't
4782026-02-19T17:00:49 <fanquake> (I think splitting up the release builds is also tangentially, given it would already be useful, regardless of wether we are switching gui backends)
4792026-02-19T17:01:05 *** Emc37 <Emc37!~Emc99@212.129.76.158> has quit IRC (Quit: Client closed)
4802026-02-19T17:01:08 *** nervana21 <nervana21!~nervana21@69.206.165.174> has quit IRC (Quit: Client closed)
4812026-02-19T17:01:21 *** nervana21 <nervana21!~nervana21@69.206.165.174> has joined #bitcoin-core-dev
4822026-02-19T17:01:23 *** Bob2026 <Bob2026!~Bob2026@1-164-64-230.dynamic-ip.hinet.net> has quit IRC (Quit: Client closed)
4832026-02-19T17:01:24 <sipa> (lunchtime)
4842026-02-19T17:01:37 *** jurraca <jurraca!~jurraca@user/jurraca> has quit IRC (Quit: leaving)
4852026-02-19T17:01:41 *** SakshiKasat18 <SakshiKasat18!~SakshiKas@203.92.58.30> has joined #bitcoin-core-dev
4862026-02-19T17:01:41 <hebasto> fanquake: yes, but it is always someone expresses an idea crystal clearly
4872026-02-19T17:03:32 *** sr_gi <sr_gi!~sr_gi@46.231.244.218> has quit IRC (Quit: Client closed)
4882026-02-19T17:05:57 <bitcoin-git> [bitcoin] fanquake opened pull request #34627: guix: use a temporary file over sponge, drop moreutils (master...replace_sponge) https://github.com/bitcoin/bitcoin/pull/34627
4892026-02-19T17:05:58 <bitcoin-git> [bitcoin] sedited pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/910bd1c964b6...097c18239b58
4902026-02-19T17:05:59 <bitcoin-git> bitcoin/master 9f2b338 Hennadii Stepanov: subprocess: Fix `-Wunused-private-field` for `Popen` class on Windows
4912026-02-19T17:05:59 <bitcoin-git> bitcoin/master 1b36bf0 Hennadii Stepanov: subprocess: Fix `-Wunused-private-field` for `Child` class on Windows
4922026-02-19T17:05:59 <bitcoin-git> bitcoin/master 097c182 merge-script: Merge bitcoin/bitcoin#34385: subprocess: Fix `-Wunused-private-field` when...
4932026-02-19T17:06:01 <bitcoin-git> [bitcoin] sedited merged pull request #34385: subprocess: Fix `-Wunused-private-field` when building with clang-cl on Windows (master...260122-clangcl-unsused) https://github.com/bitcoin/bitcoin/pull/34385
4942026-02-19T17:09:48 *** epicleafies <epicleafies!~epicleafi@2600:1700:3900:a0ef:ed53:622:e29c:6859> has quit IRC (Quit: Client closed)
4952026-02-19T17:10:41 *** cfields <cfields!~cfields@user/cfields> has joined #bitcoin-core-dev
4962026-02-19T17:12:33 *** nervana21 <nervana21!~nervana21@69.206.165.174> has quit IRC (Quit: Client closed)
4972026-02-19T17:13:26 <cfields> grr, my ircd was acting up for today's meeting :(
4982026-02-19T17:13:33 <cfields> will read the log
4992026-02-19T17:18:34 *** dzxzg <dzxzg!~dzxzg@user/dzxzg> has quit IRC ()
5002026-02-19T17:24:38 <johnny9dev> fjahr: re: recruiting new devs. I actually might have a new dev that is interested in helping get the qml gui feature complete so working on onboarding him now. I'm hopeful about this aspect of the project
5012026-02-19T17:25:48 <jarolrod> I will be helping with review on the qml side, and can help attract new contribs
5022026-02-19T17:27:06 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has joined #bitcoin-core-dev
5032026-02-19T17:30:56 <cfields> johnny9dev: (I missed the meeting, catching up now) what interface does the qml interface use to communicate with Core?
5042026-02-19T17:31:40 <hebasto> cfields: internal
5052026-02-19T17:32:38 <cfields> is there a branch I can take a look at? I'd be interested in seeing what it would take to do it over IPC.
5062026-02-19T17:33:07 <hebasto> https://github.com/bitcoin-core/gui-qml
5072026-02-19T17:33:39 <hebasto> the default branch is `qt6`
5082026-02-19T17:33:42 <jarolrod> ^ the qt6 branch
5092026-02-19T17:33:57 <cfields> thanks
5102026-02-19T17:35:57 *** SakshiKasat18 <SakshiKasat18!~SakshiKas@203.92.58.30> has quit IRC (Quit: Client closed)
5112026-02-19T17:41:01 <cfields> any chance someone has hacked up depends packages for the additional dependencies?
5122026-02-19T17:41:38 <hebasto> cfields: elaborate pls
5132026-02-19T17:42:49 <cfields> hebasto: is there a branchs somewhere that adds the depends changes necessary for (for ex) qtquick?
5142026-02-19T17:43:17 <hebasto> I have one, but it's outdated now
5152026-02-19T17:43:32 <cfields> ok, no worries
5162026-02-19T17:44:35 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
5172026-02-19T17:52:12 *** adys <adys!~adys@user/adys> has joined #bitcoin-core-dev
5182026-02-19T17:52:55 *** adys0 <adys0!~adys@user/adys> has quit IRC (Read error: Connection reset by peer)
5192026-02-19T18:00:59 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
5202026-02-19T18:09:29 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
5212026-02-19T18:09:56 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
5222026-02-19T18:20:50 <darosior> wow, some high quality comments on that stackernews thread..
5232026-02-19T18:24:41 <achow101> sipa: such a group may concretely exist
5242026-02-19T18:32:40 *** dzxzg <dzxzg!~dzxzg@user/dzxzg> has joined #bitcoin-core-dev
5252026-02-19T18:38:54 *** mudsip <mudsip!~mudsip@user/mudsip> has joined #bitcoin-core-dev
5262026-02-19T18:44:25 <pinheadmz> darosior yes how did the public find out that intelligence agencies are hiring people who hate bitcoin to do all the core development?
5272026-02-19T18:44:54 <pinheadmz> (/s) -- just in case justin_shocknet follows IRC logs
5282026-02-19T18:52:13 *** mudsip <mudsip!~mudsip@user/mudsip> has quit IRC ()
5292026-02-19T19:00:32 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has quit IRC (Quit: Client closed)
5302026-02-19T19:02:58 *** nervana21 <nervana21!~nervana21@103.251.27.90> has joined #bitcoin-core-dev
5312026-02-19T19:31:57 <bitcoin-git> [bitcoin] sedited pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/097c18239b58...37e449dcc72c
5322026-02-19T19:31:58 <bitcoin-git> bitcoin/master e0463b4 Sjors Provoost: rpc: add coinbase_tx field to getblock
5332026-02-19T19:31:58 <bitcoin-git> bitcoin/master 37e449d merge-script: Merge bitcoin/bitcoin#34512: rpc: add coinbase_tx field to getblock
5342026-02-19T19:31:59 <bitcoin-git> [bitcoin] sedited merged pull request #34512: rpc: add coinbase_tx field to getblock (master...2026/02/getblockfields) https://github.com/bitcoin/bitcoin/pull/34512
5352026-02-19T19:32:10 *** Chris_Stewart_5 <Chris_Stewart_5!~Chris_Ste@155.2.191.235> has joined #bitcoin-core-dev
5362026-02-19T19:41:52 <bitcoin-git> [bitcoin] achow101 pushed 6 commits to master: https://github.com/bitcoin/bitcoin/compare/37e449dcc72c...d0998cbe348e
5372026-02-19T19:41:54 <bitcoin-git> bitcoin/master b54dedc ismaelsadeeq: fees: reduce `MIN_BUCKET_FEERATE` to 100
5382026-02-19T19:41:54 <bitcoin-git> bitcoin/master fc4fbda ismaelsadeeq: fees: bump fees file version
5392026-02-19T19:41:54 <bitcoin-git> bitcoin/master 243e48c ismaelsadeeq: fees: delete unused dummy field
5402026-02-19T19:41:54 <bitcoin-git> [bitcoin] achow101 merged pull request #33199: fees: enable `CBlockPolicyEstimator` return sub 1 sat/vb fee rate estimates (master...08-2025-low-fee-rate-estimate) https://github.com/bitcoin/bitcoin/pull/33199
5412026-02-19T20:08:24 *** stringintech <stringintech!~stringint@user/stringintech> has joined #bitcoin-core-dev
5422026-02-19T20:34:30 *** thelounge855 <thelounge855!~thelounge@i59F45E30.versanet.de> has joined #bitcoin-core-dev
5432026-02-19T20:34:51 *** thelounge855 <thelounge855!~thelounge@i59F45E30.versanet.de> has left #bitcoin-core-dev
5442026-02-19T20:41:26 <bitcoin-git> [bitcoin] achow101 pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/d0998cbe348e...02c83fef8431
5452026-02-19T20:41:27 <bitcoin-git> bitcoin/master 59d24bd furszy: threadpool: make Submit return Expected instead of throwing
5462026-02-19T20:41:27 <bitcoin-git> bitcoin/master 726b366 furszy: http: properly respond to HTTP request during shutdown
5472026-02-19T20:41:27 <bitcoin-git> bitcoin/master 02c83fe Ava Chow: Merge bitcoin/bitcoin#34577: http: fix submission during shutdown race
5482026-02-19T20:41:28 <bitcoin-git> [bitcoin] achow101 merged pull request #34577: http: fix submission during shutdown race (master...2026_http_submission_error) https://github.com/bitcoin/bitcoin/pull/34577
5492026-02-19T20:49:31 *** Guest85 <Guest85!~Guest85@159.192.34.56> has joined #bitcoin-core-dev
5502026-02-19T20:52:55 *** mudsip <mudsip!~mudsip@user/mudsip> has joined #bitcoin-core-dev
5512026-02-19T20:55:41 *** Guest85 <Guest85!~Guest85@159.192.34.56> has quit IRC (Ping timeout: 272 seconds)
5522026-02-19T21:03:49 *** mudsip <mudsip!~mudsip@user/mudsip> has quit IRC ()
5532026-02-19T21:11:05 *** brunoerg <brunoerg!~brunoerg@2803:9810:48a1:8c08:559c:36fa:b88e:7b7a> has quit IRC (Remote host closed the connection)
5542026-02-19T21:19:08 <bitcoin-git> [bitcoin] sedited pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/02c83fef8431...739f75c0980e
5552026-02-19T21:19:09 <bitcoin-git> bitcoin/master 7e52b1b LÅrinc: fuzz: call `EmplaceCoinInternalDANGER` as well in `SimulationTest`
5562026-02-19T21:19:09 <bitcoin-git> bitcoin/master b413491 Pieter Wuille: coins: Keep track of number of dirty entries in `CCoinsViewCache`
5572026-02-19T21:19:09 <bitcoin-git> bitcoin/master afb1bc1 Pieter Wuille: validation: Use dirty entry count in flush warnings and disk space checks
5582026-02-19T21:19:10 <bitcoin-git> [bitcoin] sedited merged pull request #33512: coins: use dirty entry count for flush warnings and disk space checks (master...l0rinc/warn-dirty-coin-coint) https://github.com/bitcoin/bitcoin/pull/33512
5592026-02-19T21:42:23 <bitcoin-git> [bitcoin] achow101 pushed 8 commits to master: https://github.com/bitcoin/bitcoin/compare/739f75c0980e...c808dfbbdcea
5602026-02-19T21:42:24 <bitcoin-git> bitcoin/master 573bb54 Andrew Toth: net: Store recipient node address in private broadcast
5612026-02-19T21:42:24 <bitcoin-git> bitcoin/master 5e64982 Andrew Toth: net: Add PrivateBroadcast::GetBroadcastInfo
5622026-02-19T21:42:24 <bitcoin-git> bitcoin/master 996f20c Andrew Toth: rpc: Add getprivatebroadcastinfo
5632026-02-19T21:42:25 <bitcoin-git> [bitcoin] achow101 merged pull request #34329: rpc,net: Add private broadcast RPCs (master...private_broadcast_rpcs) https://github.com/bitcoin/bitcoin/pull/34329
5642026-02-19T22:09:13 *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has quit IRC (Quit: Leaving)
5652026-02-19T22:13:30 *** jerryf <jerryf!~jerryf@user/jerryf> has quit IRC (Remote host closed the connection)
5662026-02-19T22:14:02 *** jerryf <jerryf!~jerryf@user/jerryf> has joined #bitcoin-core-dev
5672026-02-19T22:15:04 <l0rinc> can we add #34389 to v31? It fixes some logging inconsistencies
5682026-02-19T22:15:06 <corebot> https://github.com/bitcoin/bitcoin/issues/34389 | net/log: standardize peer+addr log formatting via `LogPeer` by l0rinc · Pull Request #34389 · bitcoin/bitcoin · GitHub
5692026-02-19T22:52:31 *** aleggg <aleggg!~aleggg@189.110.152.194> has quit IRC (Ping timeout: 264 seconds)
5702026-02-19T22:53:27 *** aleggg <aleggg!~aleggg@177.102.158.185> has joined #bitcoin-core-dev
5712026-02-19T23:25:20 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has quit IRC (Remote host closed the connection)
5722026-02-19T23:27:02 *** cotsuka <cotsuka!~cotsuka@user/cotsuka> has joined #bitcoin-core-dev
5732026-02-19T23:50:18 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
5742026-02-19T23:50:39 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev