12025-10-09T00:08:04 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
22025-10-09T00:09:39 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
32025-10-09T00:11:33 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 256 seconds)
42025-10-09T00:17:25 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 264 seconds)
52025-10-09T00:17:25 *** Earnestly <Earnestly!~earnest@user/earnestly> has quit IRC (Ping timeout: 264 seconds)
62025-10-09T00:36:11 *** Guest85 <Guest85!~Guest85@216.224.124.100> has joined #bitcoin-core-dev
72025-10-09T00:40:16 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Read error: No route to host)
82025-10-09T00:40:30 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Ping timeout: 272 seconds)
92025-10-09T00:40:48 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
102025-10-09T00:41:36 *** Guest85 <Guest85!~Guest85@216.224.124.100> has quit IRC (Quit: Client closed)
112025-10-09T00:56:33 *** Earnestly <Earnestly!~earnest@user/earnestly> has joined #bitcoin-core-dev
122025-10-09T01:03:44 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
132025-10-09T01:04:05 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
142025-10-09T01:05:41 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
152025-10-09T02:05:49 *** vasild_ <vasild_!~vd@user/vasild> has joined #bitcoin-core-dev
162025-10-09T02:07:54 *** vasild <vasild!~vd@user/vasild> has quit IRC (Ping timeout: 272 seconds)
172025-10-09T02:24:38 *** dzxzg <dzxzg!~dzxzg@user/dzxzg> has quit IRC (Remote host closed the connection)
182025-10-09T03:23:10 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Remote host closed the connection)
192025-10-09T03:47:13 *** BUSY <BUSY!~BUSY@user/busy> has quit IRC (Quit: Leaving)
202025-10-09T04:01:01 *** cmirror <cmirror!~cmirror@4.53.92.114> has quit IRC (Remote host closed the connection)
212025-10-09T04:01:33 *** cmirror <cmirror!~cmirror@4.53.92.114> has joined #bitcoin-core-dev
222025-10-09T04:08:53 *** WizJin <WizJin!~Wizzy@2402:a00:184:8354:5910:460e:8420:12f6> has joined #bitcoin-core-dev
232025-10-09T04:23:58 *** l0rinc_ <l0rinc_!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc_)
242025-10-09T04:24:05 *** Nebraskka <Nebraskka!~Nebraskka@user/nebraskka> has quit IRC (Ping timeout: 245 seconds)
252025-10-09T04:30:14 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
262025-10-09T04:31:15 *** Nebraskka <Nebraskka!~Nebraskka@user/nebraskka> has joined #bitcoin-core-dev
272025-10-09T04:31:50 *** vasild_ <vasild_!~vd@user/vasild> has quit IRC (Remote host closed the connection)
282025-10-09T04:31:58 *** vasild <vasild!~vd@user/vasild> has joined #bitcoin-core-dev
292025-10-09T04:35:11 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Ping timeout: 265 seconds)
302025-10-09T06:09:44 *** chjj <chjj!~chjj@user/chjj> has quit IRC (Ping timeout: 240 seconds)
312025-10-09T06:12:44 *** chjj <chjj!~chjj@user/chjj> has joined #bitcoin-core-dev
322025-10-09T06:26:36 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
332025-10-09T06:26:36 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Remote host closed the connection)
342025-10-09T06:26:53 *** pablomartin4btc <pablomartin4btc!~pablomart@190.189.182.120> has joined #bitcoin-core-dev
352025-10-09T06:27:00 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
362025-10-09T06:27:00 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
372025-10-09T06:27:59 *** pablomartin <pablomartin!~pablomart@190.189.182.120> has quit IRC (Ping timeout: 256 seconds)
382025-10-09T06:28:18 *** cmirror <cmirror!~cmirror@4.53.92.114> has quit IRC (Ping timeout: 256 seconds)
392025-10-09T06:28:18 *** chjj <chjj!~chjj@user/chjj> has quit IRC (Ping timeout: 256 seconds)
402025-10-09T06:28:18 *** Nebraskka <Nebraskka!~Nebraskka@user/nebraskka> has quit IRC (Ping timeout: 256 seconds)
412025-10-09T06:28:55 *** Nebraskka <Nebraskka!~Nebraskka@user/nebraskka> has joined #bitcoin-core-dev
422025-10-09T06:41:21 *** chjj <chjj!~chjj@user/chjj> has joined #bitcoin-core-dev
432025-10-09T07:31:24 *** f321x <f321x!~f321x@user/f321x> has joined #bitcoin-core-dev
442025-10-09T07:43:56 *** f321x_ <f321x_!~f321x@user/f321x> has joined #bitcoin-core-dev
452025-10-09T07:43:56 *** f321x <f321x!~f321x@user/f321x> has quit IRC (Remote host closed the connection)
462025-10-09T08:48:05 *** janb84 <janb84!~janb84@user/janb84> has quit IRC (Ping timeout: 256 seconds)
472025-10-09T08:49:59 *** janb84 <janb84!~janb84@user/janb84> has joined #bitcoin-core-dev
482025-10-09T09:33:50 <bitcoin-git> [bitcoin] Aathish101 opened pull request #33583: Update .style.yapf (master...patch-1) https://github.com/bitcoin/bitcoin/pull/33583
492025-10-09T09:45:17 <bitcoin-git> [bitcoin] maflcko closed pull request #33583: Update .style.yapf (master...patch-1) https://github.com/bitcoin/bitcoin/pull/33583
502025-10-09T10:00:37 *** sliv3r__ <sliv3r__!~sliv3r__@user/sliv3r-:76883> has quit IRC (Ping timeout: 264 seconds)
512025-10-09T10:03:14 *** sliv3r__ <sliv3r__!~sliv3r__@user/sliv3r-:76883> has joined #bitcoin-core-dev
522025-10-09T10:11:38 <bitcoin-git> [bitcoin] maflcko closed pull request #33218: refactor: rename `fees.{h,cpp}` to `fees/block_policy_estimator{h,cpp}` (master...08-2025-block-policy-refactor) https://github.com/bitcoin/bitcoin/pull/33218
532025-10-09T10:11:41 <bitcoin-git> [bitcoin] maflcko reopened pull request #33218: refactor: rename `fees.{h,cpp}` to `fees/block_policy_estimator{h,cpp}` (master...08-2025-block-policy-refactor) https://github.com/bitcoin/bitcoin/pull/33218
542025-10-09T10:30:24 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
552025-10-09T10:33:59 <_aj_> maflcko: missing a "." in that pr title
562025-10-09T10:34:22 <bitcoin-git> [bitcoin] MamunC0der opened pull request #33584: Upgrade GitHub Action to download-artifact@v5 (master...patch-1) https://github.com/bitcoin/bitcoin/pull/33584
572025-10-09T10:34:53 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Ping timeout: 256 seconds)
582025-10-09T10:47:13 *** memset_ <memset_!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
592025-10-09T10:51:02 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Ping timeout: 272 seconds)
602025-10-09T11:16:26 <abubakarsadiq> _aj_: fixed
612025-10-09T11:19:18 *** flooded <flooded!~flooded@149.88.18.223> has joined #bitcoin-core-dev
622025-10-09T12:18:58 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Quit: = "")
632025-10-09T12:20:38 *** PaperSword <PaperSword!~Thunderbi@securemail.qrsnap.io> has joined #bitcoin-core-dev
642025-10-09T12:31:28 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
652025-10-09T12:34:28 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
662025-10-09T12:57:33 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
672025-10-09T13:02:28 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Remote host closed the connection)
682025-10-09T13:12:30 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has joined #bitcoin-core-dev
692025-10-09T13:29:46 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
702025-10-09T13:54:39 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
712025-10-09T14:00:45 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
722025-10-09T14:21:25 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
732025-10-09T14:21:36 <glozow> Could we get a "Tracking issue" label? It'd be a nice way to find all the tracking issues, and make it easier to label an issue as "the place to post updates about a longer-running project"
742025-10-09T14:22:53 <glozow> Also requesting that we do tracking issues for minor releases, as a place to link all the PRs and post updates on bins, tags, etc.
752025-10-09T14:25:50 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Client Quit)
762025-10-09T15:04:43 *** Guest36 <Guest36!~Guest36@syn-068-202-179-088.res.spectrum.com> has joined #bitcoin-core-dev
772025-10-09T15:06:35 *** Guest36 <Guest36!~Guest36@syn-068-202-179-088.res.spectrum.com> has quit IRC (Client Quit)
782025-10-09T15:20:19 *** Guest54 <Guest54!~Guest54@syn-098-149-050-178.res.spectrum.com> has joined #bitcoin-core-dev
792025-10-09T15:21:09 *** Guest54 <Guest54!~Guest54@syn-098-149-050-178.res.spectrum.com> has quit IRC (Client Quit)
802025-10-09T15:24:36 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
812025-10-09T15:39:31 <bitcoin-git> [bitcoin] fanquake merged pull request #33584: ci: upgrade GitHub Action to download-artifact@v5 (master...patch-1) https://github.com/bitcoin/bitcoin/pull/33584
822025-10-09T15:42:25 <bitcoin-git> [bitcoin] fanquake merged pull request #33581: ci: Properly include $FILE_ENV in DEPENDS_HASH (master...ci-depends-hash-file-env) https://github.com/bitcoin/bitcoin/pull/33581
832025-10-09T15:43:09 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 256 seconds)
842025-10-09T15:44:58 <bitcoin-git> [bitcoin] purpleKarrot opened pull request #33585: cmake: Use builtin support for .manifest files (master...win32-manifest) https://github.com/bitcoin/bitcoin/pull/33585
852025-10-09T15:51:24 <bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/b510893d0076...d44b860cd09e
862025-10-09T15:51:25 <bitcoin-git> bitcoin/master b35341b Coder: Update ci.yml
872025-10-09T15:51:25 <bitcoin-git> bitcoin/master d44b860 merge-script: Merge bitcoin/bitcoin#33584: ci: upgrade GitHub Action to download-artifac...
882025-10-09T15:54:46 <bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/d44b860cd09e...90b2884ce4ba
892025-10-09T15:54:46 <bitcoin-git> bitcoin/master ceeb53a Ava Chow: ci: Properly include $FILE_ENV in DEPENDS_HASH
902025-10-09T15:54:47 <bitcoin-git> bitcoin/master 90b2884 merge-script: Merge bitcoin/bitcoin#33581: ci: Properly include $FILE_ENV in DEPENDS_HASH
912025-10-09T15:55:07 <bitcoin-git> [bitcoin] waketraindev reopened pull request #32741: rpc: add optional peer_ids param to filter getpeerinfo (master...2025-06-getpeerinfo-filterid) https://github.com/bitcoin/bitcoin/pull/32741
922025-10-09T15:56:51 *** Emc99 <Emc99!~Emc99@212.129.74.46> has joined #bitcoin-core-dev
932025-10-09T15:57:38 <TheCharlatan> glozow: yes please, re. minor release issues.
942025-10-09T15:59:29 <lightlike> We could also have a tracking issue for tracking issues :)
952025-10-09T16:00:11 <achow101> #startmeeting
962025-10-09T16:00:11 <corebot`> achow101: Meeting started at 2025-10-09T16:00+0000
972025-10-09T16:00:12 <corebot`> achow101: Current chairs: achow101
982025-10-09T16:00:13 <corebot`> achow101: Useful commands: #action #info #idea #link #topic #motion #vote #close #endmeeting
992025-10-09T16:00:14 <corebot`> achow101: See also: https://hcoop-meetbot.readthedocs.io/en/stable/
1002025-10-09T16:00:15 <corebot`> achow101: Participants should now identify themselves with '#here' or with an alias like '#here FirstLast'
1012025-10-09T16:00:20 <achow101> #bitcoin-core-dev Meeting: abubakarsadiq achow101 _aj_ ajonas b10c brunoerg cfields darosior dergoegge fanquake fjahr furszy gleb glozow hebasto hodlinator instagibbs jarolrod jonatack josibake kanzure laanwj LarryRuane lightlike luke-jr maflcko marcofleon maxedw Murch pinheadmz provoostenator ryanofsky sdaftuar S3RK stickies-v sipa sr_gi tdb3 theStack TheCharlatan vasild willcl-ark
1022025-10-09T16:00:23 <hodlinator> hi
1032025-10-09T16:00:23 <stickies-v> hi
1042025-10-09T16:00:27 <brunoerg> hi
1052025-10-09T16:00:28 <janb84> hi
1062025-10-09T16:00:29 <sipa> hi
1072025-10-09T16:00:31 <pinheadmz> ð¥
1082025-10-09T16:00:31 <maxedw> hi
1092025-10-09T16:00:45 <lightlike> Hi
1102025-10-09T16:00:49 <achow101> There are no pre-proposed meeting topics this week. Any last minute ones to add?
1112025-10-09T16:00:53 <eugenesiegel> hi
1122025-10-09T16:00:53 <willcl-ark> hi
1132025-10-09T16:01:30 <TheCharlatan> hi
1142025-10-09T16:01:50 <glozow> hi
1152025-10-09T16:01:54 <achow101> #topic Kernel WG Update (TheCharlatan)
1162025-10-09T16:02:06 <TheCharlatan> Review has been coming in on #30595, which is great to see. So far this has not triggered any additional major changes.
1172025-10-09T16:02:10 <corebot`> https://github.com/bitcoin/bitcoin/issues/30595 | kernel: Introduce initial C header API by TheCharlatan · Pull Request #30595 · bitcoin/bitcoin · GitHub
1182025-10-09T16:02:11 <lightlike> hi
1192025-10-09T16:02:27 <cfields_> hi
1202025-10-09T16:02:33 *** cfields_ is now known as cfields
1212025-10-09T16:02:38 <TheCharlatan> Also got some more people to test it out for various prototypes, and feedback so far has been positive.
1222025-10-09T16:03:03 <TheCharlatan> asking for even more people to look at it :)
1232025-10-09T16:03:06 <TheCharlatan> that's all.
1242025-10-09T16:04:02 <achow101> #topic Cluster Mempool WG Update (sdaftuar, sipa)
1252025-10-09T16:04:32 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
1262025-10-09T16:04:45 <sipa> Hi.
1272025-10-09T16:04:52 <kanzure> hi
1282025-10-09T16:05:27 <sipa> Getting some good review on #33157 (thanks l0rinc and glozow), which I'm addressing, and will push soon. I think it's pretty close otherwise.
1292025-10-09T16:05:32 <corebot`> https://github.com/bitcoin/bitcoin/issues/33157 | cluster mempool: control/optimize TxGraph memory usage by sipa · Pull Request #33157 · bitcoin/bitcoin · GitHub
1302025-10-09T16:06:14 <glozow> And then it's #28676?
1312025-10-09T16:06:19 <corebot`> https://github.com/bitcoin/bitcoin/issues/28676 | Cluster mempool implementation by sdaftuar · Pull Request #28676 · bitcoin/bitcoin · GitHub
1322025-10-09T16:06:33 <sipa> sdaftuar and i are doing some more simulation work on figuring out the optimality of block building, and how far off we are; i posted about it on https://github.com/bitcoin/bitcoin/pull/28676#issuecomment-3362136518, but will post more graphs soon
1332025-10-09T16:06:47 *** Emc99 <Emc99!~Emc99@212.129.74.46> has quit IRC (Quit: Client closed)
1342025-10-09T16:07:03 <sipa> glozow: yeah, though 28676 is rebased on top of 33157 already, and it doesn't really impact the interface, so 28676 can be reviewed fine right now too
1352025-10-09T16:07:12 <sipa> it doesn't need to actually blocked by it
1362025-10-09T16:07:17 *** Emc99 <Emc99!~Emc99@212.129.74.46> has joined #bitcoin-core-dev
1372025-10-09T16:08:29 <sipa> that's it from me
1382025-10-09T16:08:49 <achow101> #topic MuSig2 WG Update (achow101)
1392025-10-09T16:09:29 <achow101> #29675 has been getting review which I've been addressing. It's got 3 ACKs now so I think it's probably rfm.
1402025-10-09T16:09:33 <corebot`> https://github.com/bitcoin/bitcoin/issues/29675 | wallet: Be able to receive and spend inputs involving MuSig2 aggregate keys by achow101 · Pull Request #29675 · bitcoin/bitcoin · GitHub
1412025-10-09T16:10:02 <achow101> #topic Releases
1422025-10-09T16:10:39 <achow101> v30.0rc3 is up, and the tag for final is scheduled for tomorrow. Have any new issues been found in testing?
1432025-10-09T16:11:32 <achow101> 28.3rc1 and 29.2rc2 are also up for testing as well
1442025-10-09T16:12:07 *** sbddesign <sbddesign!~sbddesign@user/sbddesign> has joined #bitcoin-core-dev
1452025-10-09T16:13:08 <achow101> Or any other topics to discuss this week?
1462025-10-09T16:13:23 <glozow> review nag for #33577
1472025-10-09T16:13:24 <corebot`> https://github.com/bitcoin/bitcoin/issues/33577 | Revert "depends: Update URL for `qrencode` package source tarball" by achow101 · Pull Request #33577 · bitcoin/bitcoin · GitHub
1482025-10-09T16:13:26 <cfields> #33577 (and the ones around it) need some quick acks
1492025-10-09T16:13:27 <corebot`> https://github.com/bitcoin/bitcoin/issues/33577 | Revert "depends: Update URL for `qrencode` package source tarball" by achow101 · Pull Request #33577 · bitcoin/bitcoin · GitHub
1502025-10-09T16:13:31 <cfields> heh
1512025-10-09T16:13:33 <glozow> jinx
1522025-10-09T16:13:34 <sipa> jinx!
1532025-10-09T16:13:39 <glozow> DOUBLE JINX
1542025-10-09T16:14:07 <sipa> how critical is #33517 ?
1552025-10-09T16:14:11 <corebot`> https://github.com/bitcoin/bitcoin/issues/33517 | multiprocess: Fix high overhead from message logging by theuni · Pull Request #33517 · bitcoin/bitcoin · GitHub
1562025-10-09T16:15:09 <cfields> given how late things already are, I suppose we should just ship without it.
1572025-10-09T16:15:22 <achow101> that pr is also currently a draft
1582025-10-09T16:16:41 <cfields> the overhead was very significant for my bitcoin-p2p binary. Sjors[m]1 would know best how much it affects mining.
1592025-10-09T16:17:59 <sipa> ok
1602025-10-09T16:18:17 <achow101> Any other topics to discuss?
1612025-10-09T16:19:46 <Sjors[m]1> I'm not terribly worried because getting a block template and its header involve tiny messages.
1622025-10-09T16:20:07 <Sjors[m]1> Getting the full block, for inspection by the pool, is less urgent.
1632025-10-09T16:21:37 <cfields> Sjors[m]1: well the client side is fixed by bumping libmp. But I suppose the same is true of the messages sent/received on the Core side?
1642025-10-09T16:22:23 <cfields> (I have no idea how chatty/poll-y either side is)
1652025-10-09T16:24:08 *** dzxzg2 <dzxzg2!~dzxzg@user/dzxzg> has joined #bitcoin-core-dev
1662025-10-09T16:24:52 <Sjors[m]1> cfields: not very chatty, waitNext() doesn't poll, it blocks
1672025-10-09T16:25:09 <cfields> ok, good to know. thanks.
1682025-10-09T16:25:47 <achow101> Anything else to discuss?
1692025-10-09T16:28:09 <achow101> #endmeeting
1702025-10-09T16:28:09 <corebot`> achow101: Meeting ended at 2025-10-09T16:28+0000
1712025-10-09T16:28:10 <corebot`> achow101: Raw log: https://achow101.com/ircmeetings/2025/bitcoin-core-dev.2025-10-09_16_00.log.json
1722025-10-09T16:28:11 <corebot`> achow101: Formatted log: https://achow101.com/ircmeetings/2025/bitcoin-core-dev.2025-10-09_16_00.log.html
1732025-10-09T16:28:12 <corebot`> achow101: Minutes: https://achow101.com/ircmeetings/2025/bitcoin-core-dev.2025-10-09_16_00.html
1742025-10-09T16:28:15 *** Emc99 <Emc99!~Emc99@212.129.74.46> has quit IRC (Quit: Client closed)
1752025-10-09T16:32:59 *** dzxzg <dzxzg!~dzxzg@user/dzxzg> has joined #bitcoin-core-dev
1762025-10-09T16:33:24 *** dzxzg2 <dzxzg2!~dzxzg@user/dzxzg> has quit IRC (Read error: Connection reset by peer)
1772025-10-09T16:41:59 <phantomcircuit> sipa, on #33335, the behavior where a tie is broken by wtxid means it's more likely that nodes mempools match miners mempools for compact block reconstruction, tie breaking using random per node values would very likely make compact block reconstruction rates worse, though im not sure exactly how much worse
1782025-10-09T16:42:02 <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
1792025-10-09T16:42:52 <bitcoin-git> [bitcoin] bavani-2024-aia opened pull request #33587: No remote repository configured (fatal: 'origin' does not appear to be a git repository)Add files via upload (master...master) https://github.com/bitcoin/bitcoin/pull/33587
1802025-10-09T16:42:55 <bitcoin-git> [bitcoin] DrahtBot closed pull request #33587: No remote repository configured (fatal: 'origin' does not appear to be a git repository)Add files via upload (master...master) https://github.com/bitcoin/bitcoin/pull/33587
1812025-10-09T16:43:33 <sipa> phantomcircuit: yeah, i considered that - but i think it really only matters in fairly adverserial settings, and in those, there are many ways to trigger inconsistencies
1822025-10-09T16:43:56 <sipa> (plus, wtxid ordering possibly opens an attack vector too, by grinding wtxids)
1832025-10-09T16:48:40 <phantomcircuit> sipa, i believe it matters in the non-adversarial setting where nodes mempools are yoyo'ing around being full for a bit and then empty completely, with random ordering the transactions that just barely survived being ejected will be random between nodes while the higher fee transactions will be consistent, but as the mempool drains we'll get into those transactions that were on the edge and have maximally different mempools
1842025-10-09T16:49:07 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Remote host closed the connection)
1852025-10-09T16:49:08 <instagibbs> looking at the last PR, IIUC this is only being used for INV ordering
1862025-10-09T16:49:46 <sipa> instagibbs: it should affect eviction too
1872025-10-09T16:50:00 <instagibbs> gotta re-read clearly
1882025-10-09T16:50:04 <phantomcircuit> grinding wtxid's seems like an acceptable issue since it doesn't help skip the queue or anything so unless there's some other issue im missing iono why that matters
1892025-10-09T16:50:26 <phantomcircuit> i mean it helps skip the queue but only if you're already at the very end which seems kinda irrelevant
1902025-10-09T16:50:46 <sipa> i hadn't really considered eviction here, only INV ordering
1912025-10-09T16:51:36 <phantomcircuit> yeah for inv ordering random is better, but for eviction deterministic is better
1922025-10-09T16:51:53 <instagibbs> ah hm right, changes ChunkOrder too
1932025-10-09T16:52:28 <_aj_> phantomcircuit: are you assuming no one rebroadcasts the evicted txs when they're no longer below the minimum fee?
1942025-10-09T16:52:31 <sipa> phantomcircuit: i think the same issue applies already, depending on the ordering of transactions received, you may evict just slightly more or slightly less transactions every time the max is hit
1952025-10-09T16:53:00 <phantomcircuit> _aj_, no im assuming that they do actually
1962025-10-09T16:53:10 <sipa> random ordering may make it somewhat worse, but i don't think it qualitatively changes anything - mempool ranges which spent lots of time near the eviction point will be inconsistent already
1972025-10-09T16:53:57 <_aj_> phantomcircuit: what's the problem you're seeing then?
1982025-10-09T16:54:34 <phantomcircuit> _aj_, the issue is when things get evicted and then re-broadcast after the mempool shrinks, then those transactions are the same feerate so won't be replaced and nodes will end up with mempools with transactions that are the same feerate but different transactions, which makes compact block relay worse
1992025-10-09T16:54:44 <sipa> i'm pushing back, because having multiple different orderings would be a huge pain, and random is easier just from an abstraction perspective (txgraph doesn't need to be aware of anything but fees/sizes/dependencies)
2002025-10-09T16:55:06 <_aj_> phantomcircuit: if the chunks have equal feerates but conflict because the signers of the txs are playing silly games?
2012025-10-09T16:55:17 <instagibbs> extremely flat mempools would get completely random evictions?
2022025-10-09T16:55:41 <sipa> instagibbs: yup, which is likely preferable over biasing low wtxids
2032025-10-09T16:55:42 <phantomcircuit> i haven't considered it enough to say it would effect more than like one block every 300/$MEAN_BLOCK_SIZE blocks
2042025-10-09T16:55:57 <phantomcircuit> and only when the feerate is dropping and the mempool is emptying
2052025-10-09T16:56:04 <sipa> at least they'll all get slightly degraded relay, as opposed to picking winners and losers that get perfect and terrible relay
2062025-10-09T16:56:11 <_aj_> oh, like the top feerate is 10sat/vb, but there's 600MvB of txs between 10sat/vb and 9.9sat/vb?
2072025-10-09T16:56:41 <_aj_> but everyone's going to just say "for a feebump to an 11sat/vb i guarantee next block? okay then"
2082025-10-09T16:56:48 <phantomcircuit> sipa, so the issue kinda exists now except that there's nodes with larger than default mempools re-broadcasting their entire mempool every so often, so things that get dropped at the edge tend to get re-added
2092025-10-09T16:57:04 <phantomcircuit> so as long as the re-adding is deterministic the top part of mempools tends to be similar
2102025-10-09T16:57:58 <phantomcircuit> sipa, yeah iono if im even making an argument for something here, just pointing out something that it seems should be considered
2112025-10-09T16:57:59 <sipa> also, wtxid ordering is pretty hard to make consistent with chunk ordering; it probably needs something like "among equal-chunk-feerate distinct-cluster transactions, sort by the wtxid of the first transaction in the cluster with that chunk feerate"
2122025-10-09T16:58:04 <sipa> it's not a simpe "sort by wtxid"
2132025-10-09T16:58:05 *** dzxzg <dzxzg!~dzxzg@user/dzxzg> has quit IRC ()
2142025-10-09T16:58:13 *** dzxzg2 <dzxzg2!~dzxzg@user/dzxzg> has joined #bitcoin-core-dev
2152025-10-09T16:58:46 <_aj_> sipa: sort by the *last* transaction in the chunk?
2162025-10-09T16:59:13 <phantomcircuit> _aj_, if the chunks have equal feerates but there's multiple conflicting chunks a deterministic decisions on who "wins" would "fix" that
2172025-10-09T17:00:09 <sipa> _aj_: it'd need to be sort by the last transaction in the last chunk in the cluster with the same feerate
2182025-10-09T17:00:32 <bitcoin-git> [bitcoin] bavani-2024-aia opened pull request #33588: config.ini headers missing causes test framework failure (master...master) https://github.com/bitcoin/bitcoin/pull/33588
2192025-10-09T17:00:33 <sipa> _aj_: otherwise you get inconsistent if there are multiple equal-feerate chunks in a cluster
2202025-10-09T17:00:35 <bitcoin-git> [bitcoin] DrahtBot closed pull request #33588: config.ini headers missing causes test framework failure (master...master) https://github.com/bitcoin/bitcoin/pull/33588
2212025-10-09T17:00:49 <_aj_> phantomcircuit: should only matter if the feerate of the worst chunk in the top 1MvB of the mempool is the same as the feerate of the worst chunk in the mempool, though, which just seems vanishingly unlikely to me? anything else, you'll just be picking the txs up from slightly lower in the mempool which is fine
2222025-10-09T17:01:00 <phantomcircuit> sipa, anyways this is my monkey wrench for the day good luck *ducks*
2232025-10-09T17:01:08 <_aj_> sipa: sort the chunks in the cluster in the same way though?
2242025-10-09T17:01:44 <sipa> _aj_: they may have dependencies between them that require a particular order
2252025-10-09T17:01:55 *** sbddesign <sbddesign!~sbddesign@user/sbddesign> has quit IRC (Ping timeout: 256 seconds)
2262025-10-09T17:02:38 *** eugenesiegel <eugenesiegel!~eugenesie@user/eugenesiegel> has quit IRC (Quit: Client closed)
2272025-10-09T17:02:54 <_aj_> sipa: fair, i guess
2282025-10-09T17:02:55 <phantomcircuit> _aj_, no you have to think about it overtime, consider that the bottom feerate cluster is where a tie actually matters, so one of 2 clusters gets evicted, then the overall feerate declines and that cluster ends up being in next mined block, you won't replace the decision you made on which cluster to pick
2292025-10-09T17:03:21 <phantomcircuit> i think with re-broadcasts this is only an issue if the clusters are *also* trying to spend the same outputs
2302025-10-09T17:03:23 <bitcoin-git> [bitcoin] bavani-2024-aia opened pull request #33589: config.ini headers missing causes test framework failure (master...master) https://github.com/bitcoin/bitcoin/pull/33589
2312025-10-09T17:03:27 <bitcoin-git> [bitcoin] DrahtBot closed pull request #33589: config.ini headers missing causes test framework failure (master...master) https://github.com/bitcoin/bitcoin/pull/33589
2322025-10-09T17:04:11 <_aj_> phantomcircuit: if it's getting mined in the next block, why hasn't it been rebroadcast before then?
2332025-10-09T17:04:45 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 256 seconds)
2342025-10-09T17:05:02 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
2352025-10-09T17:05:04 <phantomcircuit> sipa, actually i guess this is an issue for all feerates regardless if they're mutually exclusive in which case using random values would give an attacker trying to fragment the mempool an advantage
2362025-10-09T17:05:35 <sipa> we have no way of making mempools confluent in the case of conflicting transactions received in distinct order
2372025-10-09T17:05:35 <phantomcircuit> i think the ordering for eviction has to be consistent to avoid that
2382025-10-09T17:05:57 <phantomcircuit> i guess today we don't handle this and just whoever is first wins
2392025-10-09T17:06:16 <phantomcircuit> which is kinda a "speed of light wins" tie breaker
2402025-10-09T17:06:21 <sipa> sdaftuar points out that today we tie-break eviction by latest received first
2412025-10-09T17:06:53 <phantomcircuit> and i guess that prevents a DoS churn issue with grinding wtxids
2422025-10-09T17:09:08 *** memset_ <memset_!~memset@gateway/tor-sasl/memset> has quit IRC (Ping timeout: 272 seconds)
2432025-10-09T17:13:46 *** DurchDenMonsun <DurchDenMonsun!~DurchDenM@2001:e68:5419:a45a:9c7b:a31:f45e:e2f1> has joined #bitcoin-core-dev
2442025-10-09T17:14:00 <phantomcircuit> sipa, so wouldn't that mean we leak the same ordering information you're trying to avoid leaking if nodes can figure out if we have a tx in our mempool?
2452025-10-09T17:15:30 <sipa> phantomcircuit: that's already the case due to conflicts, though
2462025-10-09T17:17:02 *** jerryf_ <jerryf_!~jerryf@user/jerryf> has quit IRC (Remote host closed the connection)
2472025-10-09T17:17:26 *** jerryf <jerryf!~jerryf@user/jerryf> has joined #bitcoin-core-dev
2482025-10-09T17:22:38 <DurchDenMonsun> Hi guys, How to disable logs complete in bitcoin core? new to this stuff and just want to run wallet without mining and without wearing out my ssd drive.
2492025-10-09T17:26:02 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
2502025-10-09T17:26:12 *** f321x_ <f321x_!~f321x@user/f321x> has quit IRC (Quit: f321x_)
2512025-10-09T17:26:21 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
2522025-10-09T17:28:41 <sipa> DurchDenMonsun: you can't disable logging entirely, but just synchronization with the network (downloading, storing, and processing new blocks as they are found) will have a much bigger impact on your drive
2532025-10-09T17:30:35 *** Talkless <Talkless!~Talkless@138.199.6.197> has joined #bitcoin-core-dev
2542025-10-09T17:30:54 <sdaftuar> phantomcircuit: my conjecture is that it would be very rare that randomized eviction will cause an issue. i think we can get some kind of sense of whether that is true by measuring how often (on historical data) we might mine a block that would include mempool transactions below the minimum feerate required to be relayed.
2552025-10-09T17:32:15 <DurchDenMonsun> Hi sipa: thanks for replaying, any tips how to tweak the config so it will use less writing to my ssd?
2562025-10-09T17:32:29 <DurchDenMonsun> for 2 core 4gb ram system.
2572025-10-09T17:33:08 <sipa> DurchDenMonsun: this isn't really a place for support, but you can ask questions on https://bitcoin.stackexchange.com (i'm pretty active myself answering questions there)
2582025-10-09T17:33:56 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
2592025-10-09T17:36:19 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
2602025-10-09T17:36:33 <DurchDenMonsun> Ok, i'll try that. I also tried to register on bitcointalk, but it seems that the IP I am using has been blacklisted. It's really unfortunate because the biggest ISP in my country provides dynamic IPs to home users.
2612025-10-09T17:40:22 *** sbddesign <sbddesign!~sbddesign@user/sbddesign> has joined #bitcoin-core-dev
2622025-10-09T17:45:24 *** sbddesign <sbddesign!~sbddesign@user/sbddesign> has quit IRC (Ping timeout: 260 seconds)
2632025-10-09T17:47:31 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
2642025-10-09T17:47:44 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
2652025-10-09T17:55:40 <bitcoin-git> [bitcoin] Aathish101 opened pull request #33590: newly Update funcs.mk (master...patch-2) https://github.com/bitcoin/bitcoin/pull/33590
2662025-10-09T17:58:28 *** dzxzg <dzxzg!~dzxzg@user/dzxzg> has joined #bitcoin-core-dev
2672025-10-09T18:00:24 <bitcoin-git> [bitcoin] achow101 pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/90b2884ce4ba...6b4a92b0fab8
2682025-10-09T18:00:24 <bitcoin-git> bitcoin/master a1226bc Sjors Provoost: doc: how to update a subtree
2692025-10-09T18:00:24 <bitcoin-git> bitcoin/master 6b4a92b Ava Chow: Merge bitcoin/bitcoin#33568: doc: how to update a subtree
2702025-10-09T18:00:26 <bitcoin-git> [bitcoin] achow101 merged pull request #33568: doc: how to update a subtree (master...2025/10/subtree-doc) https://github.com/bitcoin/bitcoin/pull/33568
2712025-10-09T18:05:22 *** sbddesign <sbddesign!~sbddesign@user/sbddesign> has joined #bitcoin-core-dev
2722025-10-09T18:06:08 <bitcoin-git> [bitcoin] maflcko closed pull request #33590: newly Update funcs.mk (master...patch-2) https://github.com/bitcoin/bitcoin/pull/33590
2732025-10-09T18:18:30 <achow101> the "existing users" interaction limit is enabled for the next 24 hours.
2742025-10-09T18:31:31 *** Ademan <Ademan!~Ademan@user/Ademan> has joined #bitcoin-core-dev
2752025-10-09T18:42:48 *** sbddesign <sbddesign!~sbddesign@user/sbddesign> has quit IRC (Ping timeout: 252 seconds)
2762025-10-09T18:52:05 <glozow> achow101: thanks
2772025-10-09T19:04:07 *** sbddesign <sbddesign!~sbddesign@user/sbddesign> has joined #bitcoin-core-dev
2782025-10-09T19:06:43 <bitcoin-git> [bitcoin] sdaftuar opened pull request #33591: Cluster mempool followups (master...2025-10-rebase-cluster-mempool) https://github.com/bitcoin/bitcoin/pull/33591
2792025-10-09T19:08:51 *** sbddesign <sbddesign!~sbddesign@user/sbddesign> has quit IRC (Ping timeout: 256 seconds)
2802025-10-09T19:22:26 *** DurchDenMonsun <DurchDenMonsun!~DurchDenM@user/DurchDenMonsun> has quit IRC (Quit: Client closed)
2812025-10-09T19:24:21 <bitcoin-git> [bitcoin] glozow pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/6b4a92b0fab8...cd1b7fa1ff7c
2822025-10-09T19:24:22 <bitcoin-git> bitcoin/master a89a822 Ava Chow: Revert "depends: Use hash instead of file name for package download stamp"
2832025-10-09T19:24:22 <bitcoin-git> bitcoin/master e4335a3 Ava Chow: Revert "depends: Update URL for `qrencode` package source tarball"
2842025-10-09T19:24:23 <bitcoin-git> bitcoin/master cd1b7fa merge-script: Merge bitcoin/bitcoin#33577: Revert "depends: Update URL for `qrencode` pa...
2852025-10-09T19:24:24 <bitcoin-git> [bitcoin] glozow merged pull request #33577: Revert "depends: Update URL for `qrencode` package source tarball" (master...revert-qrencode-url) https://github.com/bitcoin/bitcoin/pull/33577
2862025-10-09T19:32:59 *** sbddesign <sbddesign!~sbddesign@user/sbddesign> has joined #bitcoin-core-dev
2872025-10-09T19:47:01 *** Talkless <Talkless!~Talkless@138.199.6.197> has quit IRC (Quit: Konversation terminated!)
2882025-10-09T20:05:06 <bitcoin-git> [bitcoin] glozow pushed 4 commits to 30.x: https://github.com/bitcoin/bitcoin/compare/d5e0077bef4c...d0f6d9953a15
2892025-10-09T20:05:07 <bitcoin-git> bitcoin/30.x d7c89ba fanquake: build: bump version to v30.0
2902025-10-09T20:05:07 <bitcoin-git> bitcoin/30.x f725754 fanquake: doc: update manual pages for v30.0
2912025-10-09T20:05:07 <bitcoin-git> bitcoin/30.x d615eb6 fanquake: doc: re-import release notes for v30.0
2922025-10-09T20:05:09 <bitcoin-git> [bitcoin] glozow merged pull request #33559: [30.x] Finalise v30.0 (30.x...finalise_30_0) https://github.com/bitcoin/bitcoin/pull/33559
2932025-10-09T20:05:55 <bitcoin-git> [bitcoin] glozow pushed tag v30.0: https://github.com/bitcoin/bitcoin/compare/v30.0
2942025-10-09T20:10:34 <achow101> \o/
2952025-10-09T20:11:46 <glozow> the end is near
2962025-10-09T20:11:56 <instagibbs> *cough* end of release cycle, yes
2972025-10-09T20:12:18 <phantomcircuit> sipa, yeah i meant that the current state was that we leak the ordering currently
2982025-10-09T20:12:25 <glozow> that's what I meant yes
2992025-10-09T20:14:24 <phantomcircuit> sdaftuar, that doesn't sound right to me, but im now too tired to really think about the edge off the edge case
3002025-10-09T20:15:01 <phantomcircuit> but also it does sound like the thing sipa is proposing isn't strictly worse than ordering based on speed of light race
3012025-10-09T20:16:58 <Ademan> congrats y'all
3022025-10-09T20:17:38 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
3032025-10-09T20:18:00 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
3042025-10-09T20:28:55 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
3052025-10-09T20:31:36 <sipa> yay
3062025-10-09T20:31:56 *** thoragh <thoragh!~username@user/thoragh> has quit IRC (Read error: Connection reset by peer)
3072025-10-09T20:44:08 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Read error: Connection reset by peer)
3082025-10-09T20:44:32 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
3092025-10-09T20:52:22 <darosior> \o/
3102025-10-09T21:01:39 *** memset_ <memset_!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
3112025-10-09T21:05:22 *** memset <memset!~memset@gateway/tor-sasl/memset> has quit IRC (Ping timeout: 272 seconds)
3122025-10-09T21:11:19 <bitcoin-git> [bitcoin] amishhaa opened pull request #33592: Contrib: Updated macdeployqtplus to remove deprecated --deep signing (master...fix-deep-arg) https://github.com/bitcoin/bitcoin/pull/33592
3132025-10-09T21:16:07 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 255 seconds)
3142025-10-09T21:17:54 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
3152025-10-09T21:32:31 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Remote host closed the connection)
3162025-10-09T21:46:48 <bitcoin-git> [bitcoin] hebasto opened pull request #33593: guix: Use UCRT runtime for Windows release binaries (master...251009-guix-ucrt) https://github.com/bitcoin/bitcoin/pull/33593
3172025-10-09T21:49:21 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has joined #bitcoin-core-dev
3182025-10-09T21:54:01 *** kevkevin <kevkevin!~kevkevin@209.242.39.30> has quit IRC (Ping timeout: 264 seconds)
3192025-10-09T21:56:30 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
3202025-10-09T21:56:57 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 252 seconds)
3212025-10-09T22:04:14 *** sbddesign <sbddesign!~sbddesign@user/sbddesign> has quit IRC (Ping timeout: 256 seconds)
3222025-10-09T22:11:20 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
3232025-10-09T22:13:01 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 256 seconds)
3242025-10-09T22:18:41 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
3252025-10-09T22:19:37 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 250 seconds)
3262025-10-09T22:31:45 <bitcoin-git> [bitcoin] abishek003-tech opened pull request #33594: mzumsande (master...master) https://github.com/bitcoin/bitcoin/pull/33594
3272025-10-09T22:32:57 <bitcoin-git> [bitcoin] fanquake closed pull request #33594: mzumsande (master...master) https://github.com/bitcoin/bitcoin/pull/33594
3282025-10-09T22:35:26 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 265 seconds)
3292025-10-09T22:36:38 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
3302025-10-09T22:39:09 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
3312025-10-09T22:42:01 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 264 seconds)
3322025-10-09T22:44:13 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Quit: l0rinc)
3332025-10-09T22:45:00 *** _flood <_flood!~flooded@149.88.18.223> has joined #bitcoin-core-dev
3342025-10-09T22:49:32 *** flooded <flooded!~flooded@149.88.18.223> has quit IRC (Ping timeout: 256 seconds)
3352025-10-09T22:49:33 *** dzxzg2 <dzxzg2!~dzxzg@user/dzxzg> has quit IRC (Ping timeout: 256 seconds)
3362025-10-09T22:49:54 *** jadi <jadi!~jadi@74.49.178.126> has joined #bitcoin-core-dev
3372025-10-09T22:50:04 *** dzxzg2 <dzxzg2!~dzxzg@user/dzxzg> has joined #bitcoin-core-dev
3382025-10-09T23:00:44 *** hodlinator6 <hodlinator6!~user@user/hodlinator> has joined #bitcoin-core-dev
3392025-10-09T23:02:27 *** BlueMattTest1 <BlueMattTest1!~test-acct@2620:6e:a000:ce11::c> has quit IRC (Ping timeout: 246 seconds)
3402025-10-09T23:02:49 *** hodlinator <hodlinator!~user@user/hodlinator> has quit IRC (Ping timeout: 246 seconds)
3412025-10-09T23:02:50 *** hodlinator6 is now known as hodlinator
3422025-10-09T23:03:22 *** BlueMattTest1 <BlueMattTest1!~test-acct@2620:6e:a000:ce11::c> has joined #bitcoin-core-dev
3432025-10-09T23:04:48 *** kevkevin <kevkevin!~kevkevin@2603:300a:2305:c000:f09e:3e27:fd:deca> has joined #bitcoin-core-dev
3442025-10-09T23:05:07 *** jerryf <jerryf!~jerryf@user/jerryf> has quit IRC (Remote host closed the connection)
3452025-10-09T23:05:24 *** jerryf <jerryf!~jerryf@user/jerryf> has joined #bitcoin-core-dev
3462025-10-09T23:07:43 *** laanwj <laanwj!~laanwj@user/laanwj> has quit IRC (*.net *.split)
3472025-10-09T23:07:43 *** BlueMattMtrxBot <BlueMattMtrxBot!~bluemattm@2620:6e:a000:ce11::44> has quit IRC (*.net *.split)
3482025-10-09T23:13:26 *** laanwj <laanwj!~laanwj@user/laanwj> has joined #bitcoin-core-dev
3492025-10-09T23:13:26 *** BlueMattMtrxBot <BlueMattMtrxBot!~bluemattm@2620:6e:a000:ce11::44> has joined #bitcoin-core-dev
3502025-10-09T23:20:41 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has joined #bitcoin-core-dev
3512025-10-09T23:22:07 *** l0rinc <l0rinc!~l0rinc@user/l0rinc> has quit IRC (Client Quit)
3522025-10-09T23:37:36 *** memset_ <memset_!~memset@gateway/tor-sasl/memset> has quit IRC (Remote host closed the connection)
3532025-10-09T23:37:51 *** memset <memset!~memset@gateway/tor-sasl/memset> has joined #bitcoin-core-dev
3542025-10-09T23:50:38 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
3552025-10-09T23:52:13 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 264 seconds)
3562025-10-09T23:54:57 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 250 seconds)