12025-12-11T00:33:29 *** tarotfied <tarotfied!~tarotfied@user/tarotfied> has joined #bitcoin-core-dev
22025-12-11T03:25:35 <bitcoin-git> [bitcoin] ajtowns opened pull request #34049: rpc: Disallow captures in RPCMethodImpl (master...202512-rpcimpl-noref) https://github.com/bitcoin/bitcoin/pull/34049
32025-12-11T03:57:37 *** durandal_ <durandal_!~durandal@94.196.64.38.threembb.co.uk> has quit IRC (Ping timeout: 264 seconds)
42025-12-11T05:01:33 *** cmirror <cmirror!~cmirror@4.53.92.114> has joined #bitcoin-core-dev
52025-12-11T05:15:38 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
62025-12-11T06:09:00 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
72025-12-11T06:13:11 *** durandal_ <durandal_!~durandal@188.30.83.6.threembb.co.uk> has joined #bitcoin-core-dev
82025-12-11T06:14:28 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
92025-12-11T06:30:49 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Remote host closed the connection)
102025-12-11T06:32:01 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
112025-12-11T06:37:18 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
122025-12-11T06:38:48 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
132025-12-11T06:43:20 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Ping timeout: 240 seconds)
142025-12-11T07:03:07 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Ping timeout: 252 seconds)
152025-12-11T07:07:12 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
162025-12-11T07:12:18 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
172025-12-11T07:16:00 *** Holz <Holz!~Holz@user/Holz> has joined #bitcoin-core-dev
182025-12-11T07:57:51 *** FirefoxDeHuk <FirefoxDeHuk!~FirefoxDe@user/FirefoxDeHuk> has joined #bitcoin-core-dev
192025-12-11T07:57:54 *** adys39 <adys39!~adys@149.106.235.56> has joined #bitcoin-core-dev
202025-12-11T08:04:15 *** adys3 <adys3!~adys@149.106.235.56> has quit IRC (Read error: Connection reset by peer)
212025-12-11T08:04:16 *** brunoerg_ <brunoerg_!~brunoerg@179.191.241.122> has quit IRC (Ping timeout: 240 seconds)
222025-12-11T08:06:59 *** FirefoxDeHuk <FirefoxDeHuk!~FirefoxDe@user/FirefoxDeHuk> has quit IRC (Quit: Client closed)
232025-12-11T08:09:54 *** brunoerg <brunoerg!~brunoerg@2804:1600:11d:2c00:bd9a:81a:c79:392e> has joined #bitcoin-core-dev
242025-12-11T08:17:07 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Ping timeout: 264 seconds)
252025-12-11T08:27:49 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
262025-12-11T08:28:09 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
272025-12-11T08:32:32 *** f321x <f321x!~f321x@user/f321x> has joined #bitcoin-core-dev
282025-12-11T08:33:40 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
292025-12-11T08:33:48 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
302025-12-11T08:33:57 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
312025-12-11T08:38:23 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Ping timeout: 256 seconds)
322025-12-11T08:45:16 *** TallTim_ <TallTim_!~talltim@24-124-35-28-dynamic.midco.net> has joined #bitcoin-core-dev
332025-12-11T08:46:59 *** TallTim <TallTim!~talltim@24-124-35-28-dynamic.midco.net> has quit IRC (Ping timeout: 260 seconds)
342025-12-11T08:53:33 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
352025-12-11T09:14:01 *** bomb-on <bomb-on!~bomb-on@user/bomb-on> has joined #bitcoin-core-dev
362025-12-11T09:20:02 *** jerryf <jerryf!~jerryf@user/jerryf> has quit IRC (Remote host closed the connection)
372025-12-11T09:20:25 *** jerryf <jerryf!~jerryf@user/jerryf> has joined #bitcoin-core-dev
382025-12-11T09:27:43 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
392025-12-11T09:27:57 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
402025-12-11T09:37:53 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
412025-12-11T09:38:15 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
422025-12-11T09:56:59 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Ping timeout: 260 seconds)
432025-12-11T09:57:39 *** f321x <f321x!~f321x@user/f321x> has quit IRC (Ping timeout: 252 seconds)
442025-12-11T10:00:49 *** f321x <f321x!~f321x@user/f321x> has joined #bitcoin-core-dev
452025-12-11T10:07:55 *** f321x <f321x!~f321x@user/f321x> has quit IRC (Ping timeout: 252 seconds)
462025-12-11T10:27:35 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
472025-12-11T10:32:34 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Ping timeout: 260 seconds)
482025-12-11T10:35:48 *** f321x <f321x!~f321x@user/f321x> has joined #bitcoin-core-dev
492025-12-11T10:36:27 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
502025-12-11T10:45:19 *** f321x <f321x!~f321x@user/f321x> has quit IRC (Ping timeout: 252 seconds)
512025-12-11T10:52:33 *** f321x <f321x!~f321x@user/f321x> has joined #bitcoin-core-dev
522025-12-11T11:09:16 *** Guest07 <Guest07!~Guest07@182.63.52.14> has joined #bitcoin-core-dev
532025-12-11T11:13:55 *** f321x <f321x!~f321x@user/f321x> has quit IRC (Ping timeout: 252 seconds)
542025-12-11T11:19:22 *** Guest07 <Guest07!~Guest07@182.63.52.14> has quit IRC (Quit: Client closed)
552025-12-11T11:41:17 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
562025-12-11T11:50:25 *** f321x <f321x!~f321x@user/f321x> has joined #bitcoin-core-dev
572025-12-11T11:50:48 <bitcoin-git> [bitcoin] l0rinc opened pull request #34050: fuzz: exercise `ComputeMerkleRoot` without `mutated` parameter (master...l0rinc/merkle-merkle-root-without-mutated) https://github.com/bitcoin/bitcoin/pull/34050
582025-12-11T13:20:09 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
592025-12-11T13:20:35 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
602025-12-11T13:53:42 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
612025-12-11T14:00:28 *** TallTim_ is now known as TallTim
622025-12-11T14:06:12 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
632025-12-11T14:10:57 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 244 seconds)
642025-12-11T14:11:53 *** conman <conman!~con@180-150-21-3.b49615.mel.static.aussiebb.net> has quit IRC (Ping timeout: 246 seconds)
652025-12-11T14:11:53 *** cman <cman!~con@180-150-21-3.b49615.mel.static.aussiebb.net> has joined #bitcoin-core-dev
662025-12-11T14:25:49 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
672025-12-11T14:32:45 *** CryptoBuilder <CryptoBuilder!~CryptoBui@2800:e2:5b00:fc2:959e:cd04:4605:6b6c> has joined #bitcoin-core-dev
682025-12-11T14:40:18 *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has joined #bitcoin-core-dev
692025-12-11T14:40:44 *** flooded <flooded!~flooded@149.102.226.249> has joined #bitcoin-core-dev
702025-12-11T15:02:14 *** Novo <Novo!uid605808@id-605808.lymington.irccloud.com> has joined #bitcoin-core-dev
712025-12-11T15:06:18 *** Novo18 <Novo18!~Novo@129.18.197.162> has joined #bitcoin-core-dev
722025-12-11T15:06:21 *** Novo <Novo!uid605808@id-605808.lymington.irccloud.com> has quit IRC (Client Quit)
732025-12-11T15:07:37 *** Novo18 <Novo18!~Novo@129.18.197.162> has quit IRC (Client Quit)
742025-12-11T15:07:59 *** Novo <Novo!~Novo@129.18.197.162> has joined #bitcoin-core-dev
752025-12-11T15:11:17 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Quit: = "")
762025-12-11T15:11:44 *** Guyver2 <Guyver2!Guyver@77-174-98-73.fixed.kpn.net> has joined #bitcoin-core-dev
772025-12-11T15:22:40 *** CryptoBuilder <CryptoBuilder!~CryptoBui@2800:e2:5b00:fc2:959e:cd04:4605:6b6c> has quit IRC (Quit: Client closed)
782025-12-11T15:34:32 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
792025-12-11T15:44:06 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has joined #bitcoin-core-dev
802025-12-11T15:46:18 *** andrewtoth <andrewtoth!~andrewtot@gateway/tor-sasl/andrewtoth> has joined #bitcoin-core-dev
812025-12-11T15:54:27 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Ping timeout: 250 seconds)
822025-12-11T15:56:14 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
832025-12-11T15:59:33 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has quit IRC (Quit: Client closed)
842025-12-11T16:00:10 <stickies-v> #startmeeting
852025-12-11T16:00:10 <corebot> stickies-v: Meeting started at 2025-12-11T16:00+0000
862025-12-11T16:00:11 <corebot> stickies-v: Current chairs: stickies-v
872025-12-11T16:00:12 <corebot> stickies-v: Useful commands: #action #info #idea #link #topic #motion #vote #close #endmeeting
882025-12-11T16:00:13 <corebot> stickies-v: See also: https://hcoop-meetbot.readthedocs.io/en/stable/
892025-12-11T16:00:14 <corebot> stickies-v: Participants should now identify themselves with '#here' or with an alias like '#here FirstLast'
902025-12-11T16:00:20 <stickies-v> #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 sr_gi tdb3 theStack TheCharlatan vasild
912025-12-11T16:00:20 <stickies-v> willcl-ark
922025-12-11T16:00:23 <l0rinc> hi
932025-12-11T16:00:25 <hodlinator> hi
942025-12-11T16:00:26 <cfields> hi
952025-12-11T16:00:31 <kevkevin> hi
962025-12-11T16:00:36 <andrewtoth> hi
972025-12-11T16:00:38 <pinheadmz> hi
982025-12-11T16:00:42 <stringintech> hi
992025-12-11T16:00:49 <darosior> hi
1002025-12-11T16:00:50 <yancy> hi
1012025-12-11T16:01:06 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has joined #bitcoin-core-dev
1022025-12-11T16:01:19 <stickies-v> There are no pre-proposed meeting topics this week. Any last minute ones to add?
1032025-12-11T16:01:20 <Novo> hi
1042025-12-11T16:01:26 <eugenesiegel> hi
1052025-12-11T16:01:37 <sipa> hi
1062025-12-11T16:01:50 <pinheadmz> #proposedmeetingtopic https://github.com/libevent/libevent/issues/1812
1072025-12-11T16:01:50 <corebot> pinheadmz: Unknown command: #proposedmeetingtopic
1082025-12-11T16:01:55 <pinheadmz> #lastminute
1092025-12-11T16:01:55 <corebot> pinheadmz: Unknown command: #lastminute
1102025-12-11T16:02:03 <stickies-v> thx, will add it to the list!
1112025-12-11T16:02:14 <stickies-v> #topic Fuzzing WG Update (dergoegge)
1122025-12-11T16:02:21 <b10c> hi
1132025-12-11T16:02:33 <dergoegge> no update, but i'll commit to an update next week
1142025-12-11T16:02:49 <stickies-v> high hopes
1152025-12-11T16:02:54 <stickies-v> #topic Kernel WG Update (sedited)
1162025-12-11T16:03:41 <jonatack> hi
1172025-12-11T16:04:29 <stickies-v> not sure if sedited is here, so i'l do somehting impromptu
1182025-12-11T16:04:32 *** andrewtoth <andrewtoth!~andrewtot@gateway/tor-sasl/andrewtoth> has quit IRC (Remote host closed the connection)
1192025-12-11T16:04:56 <stickies-v> stringintech has been doing a lot of work on extending the language bindings test suite, latest PR in https://github.com/stringintech/kernel-bindings-tests/pull/11
1202025-12-11T16:05:15 <stickies-v> i've been doing a lot of work on separating node and kernel logging, will open an RFC issue by tomorrow
1212025-12-11T16:05:52 *** andrewtoth <andrewtoth!~andrewtot@gateway/tor-sasl/andrewtoth> has joined #bitcoin-core-dev
1222025-12-11T16:06:19 <stickies-v> bunch of open PRs to look at too, for overview see https://github.com/orgs/bitcoin/projects/3
1232025-12-11T16:06:39 <stickies-v> #topic Benchmarking WG Update (l0rinc, andrewtoth)
1242025-12-11T16:06:45 <l0rinc> #30442 and #33602 were just merged - thanks for the reviews!
1252025-12-11T16:06:50 <corebot> l0rinc: Error: That URL raised <HTTP Error 503: Service Unavailable>
1262025-12-11T16:06:52 <corebot> l0rinc: Error: That URL raised <HTTP Error 503: Service Unavailable>
1272025-12-11T16:07:02 <l0rinc> #30442 and #33602
1282025-12-11T16:07:06 <corebot> https://github.com/bitcoin/bitcoin/issues/30442 | precalculate SipHash constant salt XORs by l0rinc · Pull Request #30442 · bitcoin/bitcoin · GitHub
1292025-12-11T16:07:15 <corebot> https://github.com/bitcoin/bitcoin/issues/33602 | [IBD] coins: reduce lookups in dbcache layer propagation by l0rinc · Pull Request #33602 · bitcoin/bitcoin · GitHub
1302025-12-11T16:07:18 <stickies-v> looks like corebot needs even more of a tuneup than ibd
1312025-12-11T16:07:23 <l0rinc> andrewtoth rebased #31132 after the above changes and added new test cases. We also had our first Umbrel measurement: a full sync finished in 6.5 hours (31% faster than master) B-)
1322025-12-11T16:07:28 <corebot> l0rinc: Error: That URL raised <HTTP Error 503: Service Unavailable>
1332025-12-11T16:07:41 <l0rinc> stickies-v lol, indeed
1342025-12-11T16:07:41 <cfields> Nice!
1352025-12-11T16:07:50 <l0rinc> We are also making good progress reviewing #33657. Roman is very responsive, and once the remaining Windows test inconsistencies are fixed, I expect it to be ready for review (and merge) soon.
1362025-12-11T16:07:50 <kevkevin> #31132
1372025-12-11T16:07:58 <corebot> l0rinc: Error: That URL raised <Connection timed out.>
1382025-12-11T16:07:59 <dergoegge> what are the specs on the umbrel machine?
1392025-12-11T16:08:04 <corebot> https://github.com/bitcoin/bitcoin/issues/31132 | validation: fetch block inputs on parallel threads >40% faster IBD by andrewtoth · Pull Request #31132 · bitcoin/bitcoin · GitHub
1402025-12-11T16:08:29 <l0rinc> dergoegge `reindex-chainstate | 923319 blocks | dbcache 450 | umbrel | x86_64 | Intel(R) N150 | 4 cores | 15Gi RAM | ext4 | SSD`
1412025-12-11T16:08:35 <fjahr> hi
1422025-12-11T16:08:44 <l0rinc> Roman's PR is #33657
1432025-12-11T16:08:50 <corebot> l0rinc: Error: That URL raised <Connection timed out.>
1442025-12-11T16:09:02 <l0rinc> Rob pushed a pruned prototype of SwiftSync in #34004. My understanding is that it is meant as a first iteration, not a final implementation; high-level reviews and benchmarks would be interesting.
1452025-12-11T16:09:08 <corebot> https://github.com/bitcoin/bitcoin/issues/34004 | Implementation of SwiftSync by rustaceanrob · Pull Request #34004 · bitcoin/bitcoin · GitHub
1462025-12-11T16:09:18 <l0rinc> Now that we have stable access to a few benchmarking servers, we noticed some memory anomalies: a -reindex-chainstate with the default 450 MB -dbcache was running 4x slower on an rpi5 with 8 GB of memory than on an rpi5 with 16 GB of memory.
1472025-12-11T16:09:28 <l0rinc> We also observed that on the 16 GB system, runs with -dbcache values of 4 GB and higher were a lot slower than with -dbcache of 3 GB, and that an rpi5 with 16 GB of memory ran out of memory with -dbcache of 10 GB`.
1482025-12-11T16:09:36 <l0rinc> We are still investigating these, but so far it seems:
1492025-12-11T16:09:44 <l0rinc> * heavy memory fragmentation overhead may play a role in the premature OOMs. We are benchmarking lowering `M_ARENA_MAX` on 64-bit systems (similarly to the existing 32-bit architectures) to see if that helps in lower-memory environments (for example, an rpi4 with 2 GB of memory, which currently IBDs in about 3 weeks)
1502025-12-11T16:09:56 <l0rinc> * a high -dbcache value may crowd out the OS page cache (blocks + UTXO set), especially when the UTXO set size approaches the memory limit, which could be the cause of the reported sudden slowdown around block 800k (more reads from disk when the files cannot be cached in memory)
1512025-12-11T16:09:57 <stickies-v> not sure if rob is here, but might be worth opening an issue for conceptual discussion for swiftsync?
1522025-12-11T16:10:11 <Novo> I'll let Rob know
1532025-12-11T16:10:14 <l0rinc> * SSDs (and HDDs with certain filesystems) can experience severe performance degradation when they are nearly full, which, paired with more frequent disk access, dramatically slows down validation for existing 1 TB drives
1542025-12-11T16:10:27 <l0rinc> The good news is that #31132 seems to result in more than a 50% speedup on these pathological low-end devices.
1552025-12-11T16:10:35 <dergoegge> do we also have bench results for higher end machines?
1562025-12-11T16:10:36 <corebot> l0rinc: Error: That URL raised <Connection timed out.>
1572025-12-11T16:11:02 <l0rinc> yes, on my M4 max reindex-chainstate takes 1.5 hours with #31132 B-)
1582025-12-11T16:11:08 <corebot> https://github.com/bitcoin/bitcoin/issues/31132 | validation: fetch block inputs on parallel threads >40% faster IBD by andrewtoth · Pull Request #31132 · bitcoin/bitcoin · GitHub
1592025-12-11T16:11:08 <instagibbs> charts seem to have M4 max
1602025-12-11T16:11:21 <andrewtoth> dergoegge: https://github.com/bitcoin/bitcoin/pull/31132#pullrequestreview-3515011880
1612025-12-11T16:11:27 <dergoegge> ð
1622025-12-11T16:12:00 <darosior> l0rinc: re "4x slower on an rpi5 with 8 GB of memory than on an rpi5 with 16 GB of memory" -> probably LevelDB caching?
1632025-12-11T16:12:07 <l0rinc> and these are against master, which already contains several optimizations
1642025-12-11T16:12:57 <l0rinc> darosior yes, I think the frequently accessed files being cached by the OS end up being the LevelDB files I think
1652025-12-11T16:13:00 <cfields> l0rinc: if fragmentation turns out to be significant, you may want to experiment with other malloc impls (like tcmalloc) as well
1662025-12-11T16:13:23 <sipa> darosior: not LevelDB caching, which is limited - but OS-level caching possibly
1672025-12-11T16:13:26 <l0rinc> cfields: thanks, they're on my radar, but these measurements take very long
1682025-12-11T16:13:41 *** jdoman <jdoman!~jdoman@73.43.65.14> has joined #bitcoin-core-dev
1692025-12-11T16:13:48 <cfields> ð
1702025-12-11T16:14:04 <l0rinc> thank you for the comments, that's it from me
1712025-12-11T16:14:14 <darosior> sipa: is it? IIRC it's 4096 * 32 MiB by default
1722025-12-11T16:14:33 <stickies-v> thanks for the comprehensive overview again!
1732025-12-11T16:14:41 <stickies-v> #topic Silent Payments WG Update (Novo)
1742025-12-11T16:15:00 <darosior> sipa: (by our defaults, not LevelDB's)
1752025-12-11T16:15:33 <Novo> No changes from last week. I plan to do some tests with other silent payment wallets. I will give more updates by next week
1762025-12-11T16:15:37 <sipa> darosior: 128 GiB? we'd OOM every system if that was true
1772025-12-11T16:15:46 <darosior> sipa: see https://github.com/bitcoin/bitcoin/issues/33351
1782025-12-11T16:15:59 <stickies-v> ð
1792025-12-11T16:16:16 *** mudsip <mudsip!~mudsip@user/mudsip> has joined #bitcoin-core-dev
1802025-12-11T16:16:18 <sipa> darosior: that's mmap, which is nomimally in user space, but it's really the OS cache being exposed to the application
1812025-12-11T16:16:20 <vasild> hi
1822025-12-11T16:16:27 <Murch[m]> hi
1832025-12-11T16:16:32 <sipa> darosior: leveldb also has its own internal cache, which we set to some tiny value iirc
1842025-12-11T16:17:00 <darosior> sipa: oh ok, my bad. I was refering to LevelDB's mmaping when loosely saying "caching".
1852025-12-11T16:17:13 <l0rinc> darosior: #31644 indicates we're not using those caches: "readoptions.fill_cache=false"
1862025-12-11T16:17:18 <corebot> l0rinc: Error: That URL raised <HTTP Error 503: Service Unavailable>
1872025-12-11T16:17:30 <sipa> go home corebot, you're drunk
1882025-12-11T16:17:42 <darosior> :)
1892025-12-11T16:18:05 <sipa> Novo: sorry, continue, it's your topic
1902025-12-11T16:18:16 <fanquake> Novo: my understanding of the latest discussion in https://github.com/bitcoin-core/secp256k1/pull/1765 is that the BIP might need more clarifications?
1912025-12-11T16:18:19 <kevkevin> I'm core bot now https://github.com/bitcoin/bitcoin/issues/31644
1922025-12-11T16:18:27 <l0rinc> :)))
1932025-12-11T16:19:49 <stickies-v> let's move on to the next topic, we're slowing down a bit
1942025-12-11T16:19:53 <stickies-v> #topic Cluster Mempool WG Update (sdaftuar, sipa)
1952025-12-11T16:20:00 <sipa> I have split off #34023 (which contains just optimizations and follow-ups) from #32545 (which switches cluster linearization to the SFL algorithm). Reviews on the PR have focused mainly on the big algorithm description comment added in the beginning, but I hope to see code review soon. There is also the much simpler #33335 still open.
1962025-12-11T16:20:07 <corebot> https://github.com/bitcoin/bitcoin/issues/34023 | Optimized SFL cluster linearization by sipa · Pull Request #34023 · bitcoin/bitcoin · GitHub
1972025-12-11T16:20:13 <corebot> https://github.com/bitcoin/bitcoin/issues/32545 | Replace cluster linearization algorithm with SFL by sipa · Pull Request #32545 · bitcoin/bitcoin · GitHub
1982025-12-11T16:20:19 <corebot> https://github.com/bitcoin/bitcoin/issues/33335 | txgraph: randomize order of same-feerate distinct-cluster transactions by sipa · Pull Request #33335 · bitcoin/bitcoin · GitHub
1992025-12-11T16:20:20 <sipa> good bot
2002025-12-11T16:20:41 <sipa> that's it from me, if no questions
2012025-12-11T16:21:54 <stickies-v> #topic Stratum v2 WG Update (sjors)
2022025-12-11T16:23:08 <stickies-v> #topic Net Split WG Update (cfields)
2032025-12-11T16:24:15 <cfields> Been cleaning up my chacha20 simd impl this week (PR incoming), so no net split update.
2042025-12-11T16:24:26 *** mudsip <mudsip!~mudsip@user/mudsip> has quit IRC ()
2052025-12-11T16:24:47 <dergoegge> any conclusions from the discussion with aj?
2062025-12-11T16:25:47 <cfields> Not yet. I want to get a little further along and get some other opinions. I think we just pretty fundamentally disagree about shared memory and we'll have to pick one direction or the other...
2072025-12-11T16:25:55 <l0rinc> cfields: were you able to generalize the simd instructions (i.e. convince the compilers via hints)?
2082025-12-11T16:26:10 <cfields> But that decision doesn't have to be made yet, it's a good bit down the road.
2092025-12-11T16:26:25 <dergoegge> ð
2102025-12-11T16:26:41 <eugenesiegel> quick question
2112025-12-11T16:27:01 <cfields> l0rinc: yes, it's generic. Still beats the linux kernel's hand-written asm though :)
2122025-12-11T16:27:17 <l0rinc> sweet, looking forward to reviewing it
2132025-12-11T16:27:56 <eugenesiegel> I think it was brought up that process isolation was a good thing in the presence of an attacker who could take down our node. What happens if a DoS is found that takes down the process handling the message processing from peers? Does that just mean we get eclipsed since we can't process any more messages?
2142025-12-11T16:28:35 <darosior> eugenesiegel: i think in this case the entire node would have to be stopped to let the user know. But that seems tangential to Cory's work
2152025-12-11T16:28:59 <eugenesiegel> I thought this was one of the motivations for using shared memory? Or am I mistaken?
2162025-12-11T16:29:01 <darosior> As far as i understand his separation of processes was merely a demonstration, not an actual suggestion
2172025-12-11T16:29:26 <sipa> i don't think process separation between net and net processing isn't practically interesting - it's a nice demo of clean separation that it's possible, but i don't think it's useful to actually adopt
2182025-12-11T16:29:29 <cfields> eugenesiegel: multi-process is a bit out of scope for the net split project. We'd still need to discuss whether or not splitting p2p into a separate process even makes sense. It's just something that becomes possible.
2192025-12-11T16:29:47 <cfields> Hah, what sipa said.
2202025-12-11T16:29:54 <eugenesiegel> Ah, ok. Makes sense
2212025-12-11T16:29:56 <sipa> (replace one of my "isn't"s by "is")
2222025-12-11T16:30:10 <stickies-v> ooh, a puzzle
2232025-12-11T16:30:15 *** Novo <Novo!~Novo@129.18.197.162> has quit IRC (Ping timeout: 272 seconds)
2242025-12-11T16:30:30 <stickies-v> #topic libevent organization members team needs update (https://github.com/libevent/libevent/issues/1812) (pinheadmz)
2252025-12-11T16:30:41 <darosior> xz much?
2262025-12-11T16:30:45 <cfields> eugenesiegel: as for shared memory, there are 2 models for communicating between net and net_processing. Shared memory (like via CNode, which both sides access) like we have now, or generic handles on both sides.
2272025-12-11T16:31:20 <cfields> I prefer the latter as it's a cleaner separation, aj prefers the former as it's more performant.
2282025-12-11T16:31:53 <sipa> cfields: i've been casually following the discussion, but haven't formed an opinion myself
2292025-12-11T16:32:16 <dergoegge> i'd also lean towards cleaner separation
2302025-12-11T16:32:39 <dergoegge> don't think the performance difference matters much
2312025-12-11T16:32:59 <stickies-v> pinheadmz: are you here? otherwise we'll park it for next week
2322025-12-11T16:33:06 <vasild> what is "generic handles on both sides"?
2332025-12-11T16:33:14 <cfields> I think it's worth experimenting with both. Imo it just comes down to what the real-world performance penalty is.
2342025-12-11T16:33:59 <darosior> stickies-v: i think he was here, i've also got something to ask about, maybe we can do that until pinheadmz comes back?
2352025-12-11T16:34:06 <cfields> vasild: referencing NodeIds and performing lookups in CConnman/PeerMan
2362025-12-11T16:34:12 <pinheadmz> Connection issues. Park it
2372025-12-11T16:34:28 <stickies-v> darosior: yeah what's your topic?
2382025-12-11T16:34:35 <darosior> EOM / EOL https://github.com/bitcoin-core/bitcoincore.org/pull/1200
2392025-12-11T16:34:38 <vasild> cfields: ok, I see, thanks for the clarification
2402025-12-11T16:34:47 <stickies-v> cool. i'll let the net split convo finish and then move on
2412025-12-11T16:35:06 *** Emc99 <Emc99!~Emc99@212.129.75.189> has joined #bitcoin-core-dev
2422025-12-11T16:35:28 <sipa> from what i understand from the discussion, it's not really about performance, but about whether introducing the handles is actually considered cleaner or not
2432025-12-11T16:36:20 <bitcoin-git> [bitcoin] glozow pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/b26762bdcb94...b31f7866952a
2442025-12-11T16:36:21 <bitcoin-git> bitcoin/master cdaf25f Ava Chow: test: Log IP of download server in get_previous_releases.py
2452025-12-11T16:36:21 <bitcoin-git> bitcoin/master b31f786 merge-script: Merge bitcoin/bitcoin#34045: test: Log IP of download server in get_previo...
2462025-12-11T16:36:22 <bitcoin-git> [bitcoin] glozow merged pull request #34045: test: Log IP of download server in get_previous_releases.py (master...log-prev-releases-ip) https://github.com/bitcoin/bitcoin/pull/34045
2472025-12-11T16:37:11 <stickies-v> alright, looks like we're done with net split?
2482025-12-11T16:37:39 <cfields> Hmm, as it's pretty fundamental (though nothing has to be decided just yet), I supppose it's worth having a discussion at some point. I'll tee that up for a wg call at some point in the future.
2492025-12-11T16:37:47 <cfields> stickies-v: ð
2502025-12-11T16:37:50 <stickies-v> #topic Update the release lifecycle page to reflect current practices (https://github.com/bitcoin-core/bitcoincore.org/pull/1200) (darosior)
2512025-12-11T16:37:54 <darosior> I'd like to know if anyone else has an opinion about dropping the EOM status from our releases. We do not observe it, and as far as i can tell we never really have. This PR also updates a bunch of details about the release lifecycle and in general what users can expect from releases, to reflect current practices.
2522025-12-11T16:37:54 <darosior> https://github.com/bitcoin-core/bitcoincore.org/pull/1200
2532025-12-11T16:38:48 <sipa> concept ack on simiplifying things, but i've refrained from reviewing it because thinking about all the off-by-ones involved about these things hurts my brain
2542025-12-11T16:38:48 <stickies-v> sorry i was going to reply on the pr but lost track of it, at first thought i agree that the distinction is (at least currently) unnecessarily complicating things, so concept ack (but i'll do it on the pr too)
2552025-12-11T16:39:05 *** WizJin <WizJin!~Wizzy@user/WizJin> has joined #bitcoin-core-dev
2562025-12-11T16:39:47 <darosior> sipa: :) this one does not involve a shift, merely removing one column in the table and clarifying things in the text
2572025-12-11T16:40:03 <Murch[m]> I commented, and basically my point is, is something end-of-life when it got its last update, or when another update would be due and it wonât get it
2582025-12-11T16:40:26 <sipa> Murch[m]: that's the off-by-one i'm talking about
2592025-12-11T16:40:49 <darosior> A major branch N becomes end of life when the version N+3 is released
2602025-12-11T16:41:19 <Murch[m]> Seems fine with me
2612025-12-11T16:41:25 <darosior> But this is not changed by my PR, my PR just removed the unobserved "end of maintenance" middle state we had at N+2
2622025-12-11T16:41:41 <Murch[m]> But would you call the branch âmaintainedâ between N+2 release and N+3 release?
2632025-12-11T16:41:58 <darosior> We already maintain all branches until N+3 is released
2642025-12-11T16:42:16 <darosior> So, yes
2652025-12-11T16:42:36 <Murch[m]> How so? I donât think there are any backports going to N after N.x is released with the N+2 release.
2662025-12-11T16:42:50 <Murch[m]> What does it mean to be âmaintainedâ, then?
2672025-12-11T16:43:19 <darosior> There may be if necessary
2682025-12-11T16:43:37 <Murch[m]> If thatâs so, fine. I just donât think Iâve ever seen it
2692025-12-11T16:43:46 <darosior> cc fanquake since you usually take care of backports
2702025-12-11T16:43:58 <darosior> Murch[m]: really? That seems surprising to me
2712025-12-11T16:44:14 <darosior> We did backport stuff to 27 before the 30 release for instance
2722025-12-11T16:44:15 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has quit IRC (Quit: Client closed)
2732025-12-11T16:44:35 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has joined #bitcoin-core-dev
2742025-12-11T16:44:40 <Murch[m]> Okay, then I stand corrected
2752025-12-11T16:45:02 <fanquake> I think it's more a coincidence that point releases have stated to "sync up" around major releases
2762025-12-11T16:45:13 <darosior> For instance #33564
2772025-12-11T16:45:14 <sipa> Murch[m]: there was no 27.x release with those backports however, but it seems "maintained" is about the branch, not necessarily the guarantee of point releases for them
2782025-12-11T16:45:20 <corebot> https://github.com/bitcoin/bitcoin/issues/33564 | [27.x] Fix Qt download URLs by fanquake · Pull Request #33564 · bitcoin/bitcoin · GitHub
2792025-12-11T16:45:33 <sipa> also, backports are already a judgment call in any case between complexity of backport and severity
2802025-12-11T16:45:40 <fanquake> Yea, my next Q was going to be, if we push backports, but don't cut a release, is that still maintained? I'd say yes
2812025-12-11T16:45:57 <fanquake> And we are actively doing that, ad-hoc
2822025-12-11T16:46:09 <darosior> Yes and the release page does mention that as branches age the threshold for something to be backported gets higher
2832025-12-11T16:46:20 <sipa> ok i should just review it
2842025-12-11T16:46:35 <stickies-v> fanquake: the only reasing not releasing it being that the backports aren't important enough? if so, yes i agree
2852025-12-11T16:46:53 <fanquake> I agree that getting rid of a 3'rd state of maintenance is good
2862025-12-11T16:46:55 <Murch[m]> sipa: Oh okay
2872025-12-11T16:46:57 <Murch[m]> fanquake: Yeah, Iâd agree
2882025-12-11T16:47:02 <Murch[m]> If there is still work on the branch, Iâd call it maintained
2892025-12-11T16:47:18 <Murch[m]> darosior: That covers my questions then!
2902025-12-11T16:47:22 <Murch[m]> Yeah, I like the simplification
2912025-12-11T16:47:24 <fanquake> stickies-v: Yea. Sometimes things are backported that aren't user-facing
2922025-12-11T16:47:37 <fanquake> i.e: backport CI fixes incase we do need the CI to run later
2932025-12-11T16:47:39 <darosior> The release page was also claiming a bunch of stuff that was imprecise at best and maybe almost misleading
2942025-12-11T16:47:46 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
2952025-12-11T16:47:57 <Murch[m]> Iâll review again, then
2962025-12-11T16:48:06 <darosior> Alright, that's it from me then. Thanks!
2972025-12-11T16:48:17 <stickies-v> Anything else to discuss?
2982025-12-11T16:48:32 <Murch[m]> Maybe just briefly
2992025-12-11T16:48:33 <sipa> you added a topic yourself, stickies-v?
3002025-12-11T16:48:55 <sipa> oh, that was pinheadmz's topic, i see
3012025-12-11T16:48:55 <Murch[m]> I made a patch to BIPâ¯3 to address the review since I motioned to activate. Would love me some review, especially by the people who chimed in.
3022025-12-11T16:49:08 <stickies-v> yeah but we'll park pinheadmz's for next week as per his request
3032025-12-11T16:49:15 <sipa> Murch[m]: cool, will do
3042025-12-11T16:49:28 <Murch[m]> Thanks, sipa
3052025-12-11T16:49:29 <darosior> Murch[m]: will take a look
3062025-12-11T16:49:39 <Murch[m]> Okay thanks!
3072025-12-11T16:50:04 <stickies-v> #endmeeting
3082025-12-11T16:50:04 <corebot> stickies-v: Meeting ended at 2025-12-11T16:50+0000
3092025-12-11T16:50:05 <corebot> stickies-v: Raw log: https://achow101.com/ircmeetings/2025/bitcoin-core-dev.2025-12-11_16_00.log.json
3102025-12-11T16:50:05 <Murch[m]> https://github.com/bitcoin/bips/pull/2051
3112025-12-11T16:50:06 <corebot> stickies-v: Formatted log: https://achow101.com/ircmeetings/2025/bitcoin-core-dev.2025-12-11_16_00.log.html
3122025-12-11T16:50:07 <corebot> stickies-v: Minutes: https://achow101.com/ircmeetings/2025/bitcoin-core-dev.2025-12-11_16_00.html
3132025-12-11T16:50:42 <stickies-v> #proposedmeetingtopic libevent organization members team needs update (https://github.com/libevent/libevent/issues/1812) (pinheadmz)
3142025-12-11T16:51:35 *** jdoman <jdoman!~jdoman@73.43.65.14> has quit IRC (Quit: Client closed)
3152025-12-11T16:51:52 <andrewtoth> Could someone kindly unlock #19873?
3162025-12-11T16:51:59 <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
3172025-12-11T16:52:18 <fanquake> Yep
3182025-12-11T16:52:24 <andrewtoth> many thanks
3192025-12-11T16:53:15 *** Emc99 <Emc99!~Emc99@212.129.75.189> has quit IRC (Quit: Client closed)
3202025-12-11T17:00:55 <bitcoin-git> [bitcoin] glozow pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/b31f7866952a...5be20c380dcb
3212025-12-11T17:00:55 <bitcoin-git> bitcoin/master fa6c7a1 MarcoFalke: scripted-diff: LogPrintLevel(*,BCLog::Level::Debug,*) -> LogDebug()
3222025-12-11T17:00:56 <bitcoin-git> bitcoin/master fa89f60 MarcoFalke: scripted-diff: LogPrintLevel(*,BCLog::Level::*,*) -> LogError()/LogWarning...
3232025-12-11T17:00:56 <bitcoin-git> bitcoin/master 5be20c3 merge-script: Merge bitcoin/bitcoin#34033: scripted-diff: Unify error and warning log fo...
3242025-12-11T17:00:57 <bitcoin-git> [bitcoin] glozow merged pull request #34033: scripted-diff: Unify error and warning log formatting (master...2512-log-warn-err) https://github.com/bitcoin/bitcoin/pull/34033
3252025-12-11T17:21:35 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 240 seconds)
3262025-12-11T17:26:18 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
3272025-12-11T17:34:13 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 264 seconds)
3282025-12-11T17:34:25 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has quit IRC (Quit: Client closed)
3292025-12-11T17:46:45 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Read error: Connection reset by peer)
3302025-12-11T17:47:43 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
3312025-12-11T17:50:25 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Read error: Connection reset by peer)
3322025-12-11T17:50:57 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
3332025-12-11T17:55:51 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
3342025-12-11T17:58:32 *** f321x <f321x!~f321x@user/f321x> has quit IRC (Quit: f321x)
3352025-12-11T18:02:55 *** flag <flag!~flag@81.56.46.144> has quit IRC (Ping timeout: 240 seconds)
3362025-12-11T18:05:09 *** flag <flag!~flag@81.56.46.144> has joined #bitcoin-core-dev
3372025-12-11T18:08:31 *** Guyver2 <Guyver2!Guyver@77-174-98-73.fixed.kpn.net> has left #bitcoin-core-dev (Closing Window)
3382025-12-11T18:27:01 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
3392025-12-11T18:29:46 *** WizJin_ <WizJin_!~Wizzy@150.129.106.213> has joined #bitcoin-core-dev
3402025-12-11T18:30:41 <bitcoin-git> [bitcoin] l0rinc closed pull request #34046: bench: run `FindByte` across block-sized buffer (master...l0rinc/findbyte-bench) https://github.com/bitcoin/bitcoin/pull/34046
3412025-12-11T18:30:45 <bitcoin-git> [bitcoin] l0rinc reopened pull request #34046: bench: run `FindByte` across block-sized buffer (master...l0rinc/findbyte-bench) https://github.com/bitcoin/bitcoin/pull/34046
3422025-12-11T18:33:01 *** WizJin <WizJin!~Wizzy@user/WizJin> has quit IRC (Ping timeout: 264 seconds)
3432025-12-11T18:33:10 <bitcoin-git> [bitcoin] l0rinc closed pull request #32497: merkle: preâreserve leaves to prevent reallocs with odd vtx count (master...l0rinc/preâreserve-merkle-leaves-to-max) https://github.com/bitcoin/bitcoin/pull/32497
3442025-12-11T18:33:15 <bitcoin-git> [bitcoin] l0rinc reopened pull request #32497: merkle: preâreserve leaves to prevent reallocs with odd vtx count (master...l0rinc/preâreserve-merkle-leaves-to-max) https://github.com/bitcoin/bitcoin/pull/32497
3452025-12-11T18:43:32 <achow101> damn github having issues today
3462025-12-11T18:45:29 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
3472025-12-11T18:50:36 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
3482025-12-11T18:52:15 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
3492025-12-11T18:52:39 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
3502025-12-11T19:01:40 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
3512025-12-11T19:05:20 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
3522025-12-11T19:05:34 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
3532025-12-11T19:08:52 <bitcoin-git> [bitcoin] maflcko opened pull request #34051: log: Remove brittle and confusing LogPrintLevel (master...2512-log-final-cleanup) https://github.com/bitcoin/bitcoin/pull/34051
3542025-12-11T19:10:36 *** WizJin__ <WizJin__!~Wizzy@150.129.106.213> has joined #bitcoin-core-dev
3552025-12-11T19:14:38 *** WizJin_ <WizJin_!~Wizzy@150.129.106.213> has quit IRC (Ping timeout: 260 seconds)
3562025-12-11T19:19:15 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
3572025-12-11T19:23:55 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 240 seconds)
3582025-12-11T19:25:09 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
3592025-12-11T19:48:09 *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has quit IRC (Quit: Leaving)
3602025-12-11T19:55:09 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
3612025-12-11T19:56:43 <bitcoin-git> [bitcoin] achow101 pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/5be20c380dcb...d155fc12a0c7
3622025-12-11T19:56:44 <bitcoin-git> bitcoin/master 8482056 Andrew Toth: validation: periodically flush dbcache during reindex-chainstate
3632025-12-11T19:56:44 <bitcoin-git> bitcoin/master 41479ed Andrew Toth: test: add test for periodic flush inside ActivateBestChain
3642025-12-11T19:56:44 <bitcoin-git> bitcoin/master c1e554d Andrew Toth: refactor: consolidate 3 separate locks into one block
3652025-12-11T19:56:46 <bitcoin-git> [bitcoin] achow101 merged pull request #32414: validation: periodically flush dbcache during reindex-chainstate (master...reindex-flush) https://github.com/bitcoin/bitcoin/pull/32414
3662025-12-11T20:14:25 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Read error: Connection reset by peer)
3672025-12-11T20:20:50 <maflcko> I restarted all CI builds with the "failing" label: https://github.com/bitcoin/bitcoin/pulls?q=is%3Aopen+label%3A%22CI+failed%22+sort%3Aupdated-desc++is%3Apr+-label%3A%22Needs+rebase%22+-is%3Adraft
3682025-12-11T21:01:21 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
3692025-12-11T21:02:18 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
3702025-12-11T21:03:14 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Client Quit)
3712025-12-11T21:04:30 *** PaperSword <PaperSword!~Thunderbi@securemail.qrsnap.io> has quit IRC (Quit: PaperSword)
3722025-12-11T21:31:40 *** PaperSword <PaperSword!~Thunderbi@securemail.qrsnap.io> has joined #bitcoin-core-dev
3732025-12-11T22:11:55 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
3742025-12-11T22:12:40 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 256 seconds)
3752025-12-11T22:24:56 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Remote host closed the connection)
3762025-12-11T22:31:35 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
3772025-12-11T22:39:50 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
3782025-12-11T23:02:45 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Remote host closed the connection)
3792025-12-11T23:30:18 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
3802025-12-11T23:35:07 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Ping timeout: 264 seconds)
3812025-12-11T23:46:14 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
3822025-12-11T23:46:42 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev