--- Log opened Thu Aug 28 00:00:23 2025
00:07 -!- f321x [~f321x@user/f321x] has joined #bitcoin-core-dev
00:09 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has joined #bitcoin-core-dev
00:23 -!- w0xlt [~w0xlt@209.184.121.14] has quit [Ping timeout: 256 seconds]
00:25 -!- w0xlt [~w0xlt@209.184.121.14] has joined #bitcoin-core-dev
00:28 < Sjors[m]1> Should we move the achow101/signapple repo to bitcoin-core? Maybe for the v30 release.
00:29 < bitcoinlover> Hi guys, ask a question, I need to measure performance of verifying some real blocks (including utxo loading from disk), I'm going to use -stopafterblockimport to achieve this. But I found the beginning blocks starting from genesis block has few Txs which is not a good choice to test with. Any hints?
00:31 < Sjors[m]1> bitcoinlover: I think l0rinc has been working on that issue
00:40 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev
00:44 -!- thelounge042 [~thelounge@701909757.box.freepro.com] has joined #bitcoin-core-dev
01:00 -!- w0xlt [~w0xlt@209.184.121.14] has quit [Ping timeout: 258 seconds]
01:00 -!- Guest6605 [~gmaxwell@user/gmaxwell] has changed host
01:00 -!- Guest6605 is now known as gmaxwell
01:18 -!- bitcoinlover is now known as HowHsu
01:19 -!- ___nick___ [~quassel@82-132-214-210.dab.02.net] has joined #bitcoin-core-dev
01:23 -!- f321x_ [~f321x@user/f321x] has joined #bitcoin-core-dev
01:24 -!- f321x [~f321x@user/f321x] has quit [Ping timeout: 272 seconds]
01:44 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Ping timeout: 256 seconds]
01:52 < HowHsu> @Sjors[m]1, does bitcoin core currently has benchmark like so, allow selecting some block files, then testing the connection?
02:12 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev
02:17 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Ping timeout: 260 seconds]
02:31 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev
02:38 -!- w0xlt [~w0xlt@209.184.121.14] has joined #bitcoin-core-dev
02:42 -!- yonson [sid663712@id-663712.helmsley.irccloud.com] has quit [Quit: Connection closed for inactivity]
02:42 -!- w0xlt [~w0xlt@209.184.121.14] has quit [Ping timeout: 260 seconds]
02:58 -!- S3RK_ [~S3RK@user/s3rk] has joined #bitcoin-core-dev
03:02 -!- S3RK [~S3RK@user/s3rk] has quit [Ping timeout: 248 seconds]
03:33 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Ping timeout: 260 seconds]
03:36 -!- f321x_ [~f321x@user/f321x] has quit [Ping timeout: 272 seconds]
03:39 -!- f321x [~f321x@user/f321x] has joined #bitcoin-core-dev
03:47 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev
03:57 -!- dviola [~diego@user/dviola] has quit [Read error: Connection reset by peer]
04:02 -!- diego [~diego@2804:14c:5781:836f::871] has joined #bitcoin-core-dev
04:02 -!- diego is now known as Guest7107
04:09 -!- brunoerg [~brunoerg@187.183.60.121] has quit [Remote host closed the connection]
04:10 -!- brunoerg [~brunoerg@2804:14d:5285:8318:199a:76d:db5a:c4be] has joined #bitcoin-core-dev
04:15 -!- brunoerg [~brunoerg@2804:14d:5285:8318:199a:76d:db5a:c4be] has quit [Ping timeout: 260 seconds]
04:23 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has left #bitcoin-core-dev [Closing Window]
04:32 -!- Guest7107 [~diego@2804:14c:5781:836f::871] has quit [Ping timeout: 260 seconds]
04:33 -!- diego [~diego@177.34.235.126] has joined #bitcoin-core-dev
04:33 -!- diego is now known as Guest2701
04:50 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Ping timeout: 260 seconds]
05:18 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev
05:23 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Ping timeout: 260 seconds]
05:26 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev
05:50 -!- cncr04s [~cncr04s@ns1.afxr.net] has quit [Server closed connection]
05:50 -!- cncr04s [~cncr04s@ns1.afxr.net] has joined #bitcoin-core-dev
06:06 -!- Cory98 [~Cory91@user/pasha] has joined #bitcoin-core-dev
06:09 -!- Cory91 [~Cory91@user/pasha] has quit [Ping timeout: 250 seconds]
06:22 -!- Cory48 [~Cory98@user/pasha] has joined #bitcoin-core-dev
06:26 -!- Cory98 [~Cory91@user/pasha] has quit [Ping timeout: 250 seconds]
06:30 -!- Cory76 [~Cory48@user/pasha] has joined #bitcoin-core-dev
06:33 -!- HowHsu [~hacker4we@user/hacker4web3bitco] has quit [Ping timeout: 256 seconds]
06:33 -!- Cory48 [~Cory98@user/pasha] has quit [Ping timeout: 250 seconds]
06:43 -!- Cory75 [~Cory76@user/pasha] has joined #bitcoin-core-dev
06:43 -!- HowHsu [~hacker4we@user/hacker4web3bitco] has joined #bitcoin-core-dev
06:47 -!- Cory76 [~Cory48@user/pasha] has quit [Ping timeout: 250 seconds]
07:00 -!- Cory75 [~Cory76@user/pasha] has quit [Quit: Client closed]
07:00 -!- Cory75 [~Cory75@user/pasha] has joined #bitcoin-core-dev
07:37 -!- mudsip [~mudsip@user/mudsip] has joined #bitcoin-core-dev
07:38 -!- mudsip [~mudsip@user/mudsip] has quit [Client Quit]
07:49 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
08:02 -!- emcy__ [~durandal@85.255.236.63] has joined #bitcoin-core-dev
08:04 -!- Guest2701 [~diego@177.34.235.126] has left #bitcoin-core-dev []
08:05 -!- _durandal [~durandal@148.252.146.167] has quit [Ping timeout: 258 seconds]
08:06 -!- dviola [~diego@user/dviola] has joined #bitcoin-core-dev
08:07 -!- Cory65 [~Cory75@user/pasha] has joined #bitcoin-core-dev
08:11 -!- Cory75 [~Cory75@user/pasha] has quit [Ping timeout: 250 seconds]
08:12 -!- Cory37 [~Cory65@user/pasha] has joined #bitcoin-core-dev
08:16 -!- Cory65 [~Cory75@user/pasha] has quit [Ping timeout: 250 seconds]
08:21 -!- f321x [~f321x@user/f321x] has quit [Remote host closed the connection]
08:21 -!- f321x [~f321x@user/f321x] has joined #bitcoin-core-dev
08:43 < bitcoin-git> [gui-qml] johnny9 opened pull request #497: Add first unittest (qt6...unittest) https://github.com/bitcoin-core/gui-qml/pull/497
08:48 -!- enochazariah [uid710351@id-710351.hampstead.irccloud.com] has joined #bitcoin-core-dev
08:50 -!- johnny9dev [johnny9dev@user/johnny9dev] has quit [Server closed connection]
08:50 -!- johnny9dev [johnny9dev@user/johnny9dev] has joined #bitcoin-core-dev
08:51 -!- eugenesiegel [~eugenesie@user/eugenesiegel] has joined #bitcoin-core-dev
08:53 < achow101> Sjors[m]1: any reason to do so?
08:54 < Sjors[m]1> achow101: consistency with other maintainer tooling and a bit easier to find. But not a big deal.
08:57 < Sjors[m]1> Quick sv2 workgroup update since I'll be afk during some of the meeting. I just launched a standalone sv2 template provider that connects over IPC: https://github.com/Sjors/sv2-tp
08:57 -!- dzxzg [~dzxzg@user/dzxzg] has joined #bitcoin-core-dev
08:58 -!- Emc99 [~Emc99@212.129.78.208] has joined #bitcoin-core-dev
08:58 < Sjors[m]1> Thanks everyone for getting #31802 over the finish line.
08:58 < corebot> https://github.com/bitcoin/bitcoin/issues/31802 | Add bitcoin-{node,gui} to release binaries for IPC by Sjors · Pull Request #31802 · bitcoin/bitcoin · GitHub
08:59 -!- l0rinc [~l0rinc@user/l0rinc] has joined #bitcoin-core-dev
09:00 < achow101> #startmeeting
09:00 < corebot> achow101: Meeting started at 2025-08-28T16:00+0000
09:00 < corebot> achow101: Current chairs: achow101
09:00 < corebot> achow101: Useful commands: #action #info #idea #link #topic #motion #vote #close #endmeeting
09:00 < corebot> achow101: See also: https://hcoop-meetbot.readthedocs.io/en/stable/
09:00 < corebot> achow101: Participants should now identify themselves with '#here' or with an alias like '#here FirstLast'
09:00 < 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
09:00 < cfields> hi
09:00 < dzxzg> hi
09:00 < sliv3r__> hi
09:00 < jonatack> hi
09:00 < johnny9dev> hi
09:00 < l0rinc> hi
09:01 < eugenesiegel> hi
09:01 < stickies-v> hi
09:01 < achow101> There are no pre-proposed meeting topics this week. Any last minute ones to add?
09:01 < Murch[m]> Good morning
09:01 < kanzure> hi
09:01 < kevkevin> hi
09:02 < achow101> #topic Stratum v2 WG Update (sjors)
09:02 < achow101> <Sjors[m]1> Quick sv2 workgroup update since I'll be afk during some of the meeting. I just launched a standalone sv2 template provider that connects over IPC: https://github.com/Sjors/sv2-tp
09:02 < achow101> <Sjors[m]1> Thanks everyone for getting #31802 over the finish line.
09:02 < corebot> https://github.com/bitcoin/bitcoin/issues/31802 | Add bitcoin-{node,gui} to release binaries for IPC by Sjors · Pull Request #31802 · bitcoin/bitcoin · GitHub
09:02 < achow101> #topic MuSig2 WG Update (achow101)
09:02 < instagibbs> hi
09:03 < achow101> No updates since last week, #29675 is the pr to review
09:03 < _aj_> hi
09:03 < corebot> achow101: Error: That URL raised <Connection timed out.>
09:03 < achow101> #topic QML GUI WG Update (jarolrod, johnny9dev)
09:03 < kevkevin> https://github.com/bitcoin/bitcoin/pull/29675
09:03 < johnny9dev> was out last week (summer time). But getting back this week and focused on testing. I opened a PR to add a basic unittest (bitcoin-core/gui-qml#497). Going to use Qt's unittest framework and likely add GMock later on for more complex test scenarios. Will try to cover all c++ modules and use the QML test framework to do basic testing on the qml views as well.
09:03 < corebot> https://github.com/bitcoin-core/gui-qml/issues/497 | Add first unittest by johnny9 · Pull Request #497 · bitcoin-core/gui-qml · GitHub
09:04 < johnny9dev> that's all from me. 
09:04 < achow101> #topic Benchmarking WG Update (josie, l0rinc)
09:04 < l0rinc> I have been measuring IBD on raspberry pis as well, was surprised to see that it took 2 minutes to connect a block
09:05 < l0rinc> was talking to localhost about having a few raspberry pi 5 servers to be able to measure these things continuously 
09:05 < l0rinc> that's it from me
09:06 < achow101> #topic 30.0 feature freeze
09:06 < Murch[m]> l0rinc: Is there some data anywhere where we could see how time for IBD is progressing over time?
09:06 -!- Ademan [~Ademan@user/Ademan] has quit [Ping timeout: 256 seconds]
09:07 < achow101> we're still in feature freeze for 30.0, and the milestone has several bugfix prs on it that need review
09:07 < achow101> https://github.com/bitcoin/bitcoin/milestone/72
09:07 < achow101> anything that should be added or removed from the milestone?
09:08 < l0rinc> murch: https://github.com/bitcoin/bitcoin/pull/32043 shows how each PR affected the IBD time individually if that's what you're asking
09:08 < Murch[m]> No, that’s not what I meant, but I’ll follow up later.
09:08 < stickies-v> I think #33208 can be removed from the milestone, it's not completely fixed but the most common case should be, seems fine to me to not have this be a blocker
09:08 < corebot> https://github.com/bitcoin/bitcoin/issues/33208 | Indexes stuck on unknown best block after unclean shutdown · Issue #33208 · bitcoin/bitcoin · GitHub
09:09 < l0rinc> achow101: https://github.com/bitcoin/bitcoin/pull/33224 has 9 acks, how can we help to move it further? 
09:09 < achow101> stickies-v: removed
09:09 < achow101> #33224
09:09 < corebot> https://github.com/bitcoin/bitcoin/issues/33224 | doc: unify `datacarriersize` warning with release notes by l0rinc · Pull Request #33224 · bitcoin/bitcoin · GitHub
09:09 < achow101> the blocker on that is the translation string
09:10 < sipa> hi. not here. no clustermempool updates
09:10 < achow101> since updating transifex will mess up translations that have already been done
09:11 < l0rinc> is there a way to update the English one without messing up anything else? The translations can stay the same as far as I'm concerned
09:11 < achow101> if the string is updated in the source code, but we don't update transifex, it will be english for all languages
09:11 < achow101> even if there is a translation for the old string
09:12 < _aj_> could update the source test for the translations when the translations are merged?
09:12 < _aj_> source text
09:13 < achow101> _aj_: we don't update transifex after translation strings freeze
09:13 < achow101> not even for minor releaes
09:13 < achow101> but we do pull down new translations for minor releases
09:14 -!- Guest29 [~Guest29@2406:7400:75:de86:d520:db03:96bb:db42] has joined #bitcoin-core-dev
09:14 < l0rinc> sounds like transifex is holding us prisoners here
09:15 < l0rinc> or hostages or whatever the term is :)
09:15 < _aj_> achow101: we get the translation data out of transifex and merge it in though eg #32004. do that, then bulk search and replace the current english text with the change
09:15 < corebot> https://github.com/bitcoin/bitcoin/issues/32004 | qt: 29.0 translations update by hebasto · Pull Request #32004 · bitcoin/bitcoin · GitHub
09:15 < achow101> _aj_: that's prone to breakage on the next translations update
09:16 < achow101> l0rinc: it's more of our own policy to not screw the translators
09:16 < l0rinc> how could it break exactly, isn't the source code being used as the source of truth? 
09:16 < l0rinc> could other translation be messed up or just that they would have to retranslate this one in the worst case?
09:17 < achow101> l0rinc: the translation files also contain the untranslated string so that they can be matched against the source. what _aj_ is proposing is to modify the untranslated string contained in the translation file
09:18 < l0rinc> yes, it's what I proposed as well
09:18 < l0rinc> if we change all the keys, wouldn't that solve the problem deterministically?
09:19 < achow101> updating the source file in transifex will result in collateral damage in that _other_ strings will be marked as untranslated, requiring translators to re-enter and/or re-review those translations. while transifex has "memory", it doesn't fill things in automatically
09:19 < _aj_> so let's not do that until 31.0?
09:19 < achow101> this particular string would appear as a completely new string with no memory, and so has to be translated from scratch
09:20 < achow101> changing the translation files manually will require them to be changed manually for all strings update, otherwise the change gets reverted
09:21 < achow101> we do pull down translations for minor releases, and it's done by a script
09:21 -!- eugenesiegel [~eugenesie@user/eugenesiegel] has quit [Ping timeout: 250 seconds]
09:22 < l0rinc> I'm not sure I fully understand why this is an unsolvable problem, seems like a very minor inconvenience only - and I don't mind helping where I can  
09:22 -!- eugenesiegel [~eugenesie@user/eugenesiegel] has joined #bitcoin-core-dev
09:23 < achow101> it's an inconvenience to all translators, and an inconvenience to the maintainers for the next 2 years. I don't think that's "very minor"
09:23 < achow101> *either an
09:23 < _aj_> seems like it would be pretty easy to change update-translations to do it automatically
09:24 -!- Ademan [~Ademan@user/Ademan] has joined #bitcoin-core-dev
09:25 < l0rinc> we will have the same problem again regardless of this particular issue
09:26 < stickies-v> nothing against the change but i'm not sure it's worth spending this much time on tbh
09:27 -!- Guest29 [~Guest29@2406:7400:75:de86:d520:db03:96bb:db42] has left #bitcoin-core-dev []
09:27 < achow101> stickies-v: right, is changing the string worth this much energy?
09:27 < achow101> l0rinc: why do you think we would have the same problem again?
09:28 < l0rinc> refactoring and updating strings is happening daily 
09:28 < achow101> but not in the release branches, and generally not after translation strings freeze
09:28 < achow101> once we branch off, we can strings as we want
09:29 < achow101> this has been the process for at least a decade
09:29 < l0rinc> ok, seems I'm still missing some details, I'll accept of course and try to understand it better
09:29 < stickies-v> for #33189, maybe request review from some of the reviewers of the original PR? it was on my list for a while, but it's going to take me a lot more time than the many people familiar with the original pr
09:29 < corebot> https://github.com/bitcoin/bitcoin/issues/33189 | rpc: followups for 33106 by glozow · Pull Request #33189 · bitcoin/bitcoin · GitHub
09:30 < l0rinc> #33106
09:30 < corebot> https://github.com/bitcoin/bitcoin/issues/33106 | policy: lower the default blockmintxfee, incrementalrelayfee, minrelaytxfee by glozow · Pull Request #33106 · bitcoin/bitcoin · GitHub
09:32 -!- Talkless [~Talkless@138.199.6.197] has joined #bitcoin-core-dev
09:32 < achow101> stickies-v: requested a couple reviewers
09:32 < achow101> Any other topics to discuss today?
09:34 < eugenesiegel> Just one question, how much prior knowledge is required to review #32159
09:34 < corebot> https://github.com/bitcoin/bitcoin/issues/32159 | net, pcp: handle multi-part responses and filter for default route while querying default gateway by willcl-ark · Pull Request #32159 · bitcoin/bitcoin · GitHub
09:34 < achow101> eugenesiegel: I don't think a whole lot is needed
09:34 < eugenesiegel> I am pretty ignorant of how pcp works
09:35 < achow101> you don't need any knowledge of pcp or natpmp. just need to figure out the details from the netlink and rtnetlink manpages
09:35 < eugenesiegel> achow101: ok great, I will review it
09:37 < achow101> #endmeeting
09:37 < corebot> achow101: Meeting ended at 2025-08-28T16:37+0000
09:37 < corebot> achow101: Raw log: https://achow101.com/ircmeetings/2025/bitcoin-core-dev.2025-08-28_16_00.log.json
09:37 < corebot> achow101: Formatted log: https://achow101.com/ircmeetings/2025/bitcoin-core-dev.2025-08-28_16_00.log.html
09:37 < corebot> achow101: Minutes: https://achow101.com/ircmeetings/2025/bitcoin-core-dev.2025-08-28_16_00.html
09:37 -!- Emc99 [~Emc99@212.129.78.208] has quit [Quit: Client closed]
09:37 -!- _Sam-- [~sam-@user/-Sam-:39802] has joined #bitcoin-core-dev
09:38 -!- Guest13 [~Guest13@nat-130-132-173-182.central.yale.edu] has joined #bitcoin-core-dev
09:48 -!- Guest13 [~Guest13@nat-130-132-173-182.central.yale.edu] has quit [Quit: Client closed]
09:51 -!- eugenesiegel [~eugenesie@user/eugenesiegel] has quit [Quit: Client closed]
09:58 -!- Ademan [~Ademan@user/Ademan] has quit [Ping timeout: 248 seconds]
10:00 -!- thelounge042 [~thelounge@701909757.box.freepro.com] has quit [Quit: The Lounge - https://thelounge.chat]
10:15 -!- w0xlt [~w0xlt@32.141.102.6] has joined #bitcoin-core-dev
10:23 -!- Ademan [~Ademan@user/Ademan] has joined #bitcoin-core-dev
10:27 -!- HowHsu [~hacker4we@user/hacker4web3bitco] has quit [Ping timeout: 260 seconds]
10:34 -!- brunoerg [~brunoerg@186.204.131.48] has joined #bitcoin-core-dev
10:39 < achow101> 29.1rc2 bins are up
11:13 -!- brunoerg [~brunoerg@186.204.131.48] has quit [Remote host closed the connection]
11:15 -!- brunoerg [~brunoerg@186.204.131.48] has joined #bitcoin-core-dev
11:16 < shiza> \o/
11:17 -!- Guest86 [~Guest86@182.239.89.23] has joined #bitcoin-core-dev
11:17 -!- Guest86 [~Guest86@182.239.89.23] has quit [Client Quit]
11:23 -!- qubuepe24 [~qubuepe24@user/qubuepe24] has joined #bitcoin-core-dev
11:28 < bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/6ca6f3b37b99...9ae23950ef80
11:28 < bitcoin-git> bitcoin/master 509ffea fanquake: ci: return to using dash in CentOS job
11:28 < bitcoin-git> bitcoin/master 9ae2395 merge-script: Merge bitcoin/bitcoin#33261: ci: return to using dash in CentOS job
11:28 < bitcoin-git> [bitcoin] fanquake merged pull request #33261: ci: return to using dash in CentOS job (master...centos_restore_dash) https://github.com/bitcoin/bitcoin/pull/33261
11:35 < bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/9ae23950ef80...4d54bb2b92cc
11:35 < bitcoin-git> bitcoin/master 493ba0f kevkevinpal: threading: reduce the scope of lock in getblocktemplate
11:35 < bitcoin-git> bitcoin/master 4d54bb2 merge-script: Merge bitcoin/bitcoin#33264: threading: reduce the scope of lock in getblo...
11:35 < bitcoin-git> [bitcoin] fanquake merged pull request #33264: threading: reduce the scope of lock in getblocktemplate (master...reduceScopeOfGetBlockTemplateLock) https://github.com/bitcoin/bitcoin/pull/33264
11:38 -!- ___nick___ [~quassel@82-132-214-210.dab.02.net] has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
11:39 -!- aleggg [~aleggg@187.34.168.103] has joined #bitcoin-core-dev
11:40 -!- ___nick___ [~quassel@82-132-214-210.dab.02.net] has joined #bitcoin-core-dev
11:41 -!- ___nick___ [~quassel@82-132-214-210.dab.02.net] has quit [Client Quit]
11:44 -!- ___nick___ [~quassel@82-132-214-210.dab.02.net] has joined #bitcoin-core-dev
11:44 < bitcoin-git> [bitcoin] fanquake pushed 5 commits to master: https://github.com/bitcoin/bitcoin/compare/4d54bb2b92cc...6ff2d423625d
11:44 < bitcoin-git> bitcoin/master 9169a50 glozow: [rpc] expose blockmintxfee via getmininginfo
11:44 < bitcoin-git> bitcoin/master 636fa21 glozow: test fixups
11:44 < bitcoin-git> bitcoin/master c568511 glozow: test fixup for incremental feerate
11:44 < bitcoin-git> [bitcoin] fanquake merged pull request #33189: rpc: followups for 33106 (master...2025-08-minrelay) https://github.com/bitcoin/bitcoin/pull/33189
11:45 < bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/6ff2d423625d...084fd68fda2c
11:45 < bitcoin-git> bitcoin/master 4cf0ae4 fanquake: ci: use LLVM 21
11:45 < bitcoin-git> bitcoin/master 084fd68 merge-script: Merge bitcoin/bitcoin#33258: ci: use LLVM 21
11:45 < bitcoin-git> [bitcoin] fanquake merged pull request #33258: ci: use LLVM 21 (master...ci_llvm_21) https://github.com/bitcoin/bitcoin/pull/33258
11:54 -!- Cory70 [~Cory37@user/pasha] has joined #bitcoin-core-dev
11:57 -!- Cory37 [~Cory65@user/pasha] has quit [Ping timeout: 250 seconds]
12:03 -!- Cory32 [~Cory70@user/pasha] has joined #bitcoin-core-dev
12:06 -!- w0xlt [~w0xlt@32.141.102.6] has quit [Ping timeout: 248 seconds]
12:07 -!- Cory59 [~Cory32@user/pasha] has joined #bitcoin-core-dev
12:07 -!- Cory70 [~Cory37@user/pasha] has quit [Ping timeout: 250 seconds]
12:11 -!- Cory32 [~Cory70@user/pasha] has quit [Ping timeout: 250 seconds]
12:19 -!- Cory82 [~Cory59@user/pasha] has joined #bitcoin-core-dev
12:23 -!- Cory59 [~Cory32@user/pasha] has quit [Ping timeout: 250 seconds]
12:28 -!- l0rinc [~l0rinc@user/l0rinc] has quit [Quit: l0rinc]
12:34 -!- Guest52 [~Guest77@2402:4000:2249:7d62:185f:fef4:f328:5b4a] has joined #bitcoin-core-dev
12:34 -!- Guest52 [~Guest77@2402:4000:2249:7d62:185f:fef4:f328:5b4a] has quit [Client Quit]
12:38 -!- enochazariah [uid710351@id-710351.hampstead.irccloud.com] has quit [Quit: Connection closed for inactivity]
12:43 -!- sliv3r__ [~sliv3r__@user/sliv3r-:76883] has quit [Ping timeout: 248 seconds]
12:44 -!- sliv3r__ [~sliv3r__@user/sliv3r-:76883] has joined #bitcoin-core-dev
12:44 -!- w0xlt [~w0xlt@32.141.102.6] has joined #bitcoin-core-dev
12:49 -!- w0xlt [~w0xlt@32.141.102.6] has quit [Ping timeout: 260 seconds]
12:54 -!- w0xlt [~w0xlt@32.141.102.6] has joined #bitcoin-core-dev
13:04 < bitcoin-git> [bitcoin] hebasto closed pull request #32054: cmake, guix: Skip building tests in subtrees for releases (master...250313-test-binary) https://github.com/bitcoin/bitcoin/pull/32054
13:04 -!- ___nick___ [~quassel@82-132-214-210.dab.02.net] has quit [Ping timeout: 260 seconds]
13:14 -!- Talkless [~Talkless@138.199.6.197] has quit [Quit: Konversation terminated!]
13:33 -!- hugohn____ [sid304114@id-304114.lymington.irccloud.com] has quit [Server closed connection]
13:33 -!- hugohn____ [sid304114@id-304114.lymington.irccloud.com] has joined #bitcoin-core-dev
14:16 -!- l0rinc [~l0rinc@user/l0rinc] has joined #bitcoin-core-dev
14:17 -!- l0rinc [~l0rinc@user/l0rinc] has quit [Client Quit]
14:17 -!- MyNickname [~default@107-137-16-146.lightspeed.chtnsc.sbcglobal.net] has joined #bitcoin-core-dev
14:18 -!- MyNickname [~default@107-137-16-146.lightspeed.chtnsc.sbcglobal.net] has quit [Read error: Connection reset by peer]
14:18 -!- tqfoley [~default@107-137-16-146.lightspeed.chtnsc.sbcglobal.net] has joined #bitcoin-core-dev
14:20 -!- l0rinc [~l0rinc@user/l0rinc] has joined #bitcoin-core-dev
14:42 -!- l0rinc [~l0rinc@user/l0rinc] has quit [Quit: l0rinc]
14:43 -!- l0rinc [~l0rinc@user/l0rinc] has joined #bitcoin-core-dev
14:53 -!- Cory95 [~Cory82@user/pasha] has joined #bitcoin-core-dev
14:57 -!- Cory82 [~Cory59@user/pasha] has quit [Ping timeout: 250 seconds]
15:02 -!- Cory61 [~Cory95@user/pasha] has joined #bitcoin-core-dev
15:05 -!- Cory95 [~Cory82@user/pasha] has quit [Ping timeout: 250 seconds]
15:18 -!- Cory71 [~Cory61@user/pasha] has joined #bitcoin-core-dev
15:21 -!- Cory61 [~Cory95@user/pasha] has quit [Ping timeout: 250 seconds]
15:28 < bitcoin-git> [bitcoin] achow101 opened pull request #33268: wallet: Identify transactions spending 0-value outputs, and add tests for anchor outputs in a wallet (master...zero-value-from-me) https://github.com/bitcoin/bitcoin/pull/33268
15:42 -!- purpleKarrot [~purpleKar@user/purpleKarrot] has quit [Ping timeout: 256 seconds]
15:56 -!- l0rinc [~l0rinc@user/l0rinc] has quit [Quit: l0rinc]
15:59 -!- l0rinc [~l0rinc@user/l0rinc] has joined #bitcoin-core-dev
16:04 -!- l0rinc [~l0rinc@user/l0rinc] has quit [Quit: l0rinc]
16:05 -!- l0rinc [~l0rinc@user/l0rinc] has joined #bitcoin-core-dev
16:10 < bitcoin-git> [bitcoin] achow101 pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/084fd68fda2c...7cc9a087069b
16:11 < bitcoin-git> bitcoin/master df5a50e Anthony Towns: bench/blockencodings: add compact block reconstruction benchmark
16:11 < bitcoin-git> bitcoin/master b9300d8 Anthony Towns: Revert "refactor: Simplify `extra_txn` to be a vec of CTransactionRef inst...
16:11 < bitcoin-git> bitcoin/master b7b249d Anthony Towns: Revert "[refactor] rewrite vTxHashes as a vector of CTransactionRef"
16:11 < bitcoin-git> [bitcoin] achow101 merged pull request #33253: Revert compact block cache inefficiencies (master...202508-cache-friendly-compactblock) https://github.com/bitcoin/bitcoin/pull/33253
16:28 -!- jerryf [~jerryf@user/jerryf] has joined #bitcoin-core-dev
16:35 -!- Cory56 [~Cory71@user/pasha] has joined #bitcoin-core-dev
16:39 -!- Cory71 [~Cory61@user/pasha] has quit [Ping timeout: 250 seconds]
17:00 < _Sam--> It's telling that the same people who claim a UTXO commitment is too "complex" or "changes the security model" championed SegWit. SegWit was a far more convoluted change that involved separating signature data and redefining transaction IDs. And for what? So Blockstream could patent and build second-layer solutions like Liquid.
17:01 < _Sam--> We could have used a simple commitment scheme to improve scalability and light client security for everyone, but instead, the protocol was bent to serve corporate interests. They solved a business problem, not a Bitcoin problem.
17:03 -!- Cory30 [~Cory56@user/pasha] has joined #bitcoin-core-dev
17:05 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 256 seconds]
17:05 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
17:07 -!- Cory56 [~Cory71@user/pasha] has quit [Ping timeout: 250 seconds]
17:28 -!- l0rinc [~l0rinc@user/l0rinc] has quit [Quit: l0rinc]
17:34 -!- l0rinc [~l0rinc@user/l0rinc] has joined #bitcoin-core-dev
17:34 -!- brunoerg [~brunoerg@186.204.131.48] has quit [Remote host closed the connection]
17:34 -!- w0xlt [~w0xlt@32.141.102.6] has quit [Ping timeout: 248 seconds]
17:35 -!- brunoerg [~brunoerg@186.204.131.48] has joined #bitcoin-core-dev
17:35 -!- Cory56 [~Cory30@user/pasha] has joined #bitcoin-core-dev
17:39 -!- Cory30 [~Cory56@user/pasha] has quit [Ping timeout: 250 seconds]
17:39 -!- brunoerg [~brunoerg@186.204.131.48] has quit [Ping timeout: 258 seconds]
17:39 -!- Cory56 [~Cory30@user/pasha] has quit [Client Quit]
17:40 -!- Cory56 [~Cory56@user/pasha] has joined #bitcoin-core-dev
17:42 -!- Cory35 [~Cory56@user/pasha] has joined #bitcoin-core-dev
17:45 -!- Cory56 [~Cory56@user/pasha] has quit [Ping timeout: 250 seconds]
17:55 -!- tqfoley [~default@107-137-16-146.lightspeed.chtnsc.sbcglobal.net] has quit [Ping timeout: 248 seconds]
17:56 -!- brunoerg [~brunoerg@186.204.131.48] has joined #bitcoin-core-dev
17:59 -!- Cory35 [~Cory56@user/pasha] has quit [Quit: Client closed]
17:59 -!- Cory35 [~Cory35@user/pasha] has joined #bitcoin-core-dev
18:02 -!- brunoerg [~brunoerg@186.204.131.48] has quit [Ping timeout: 260 seconds]
18:04 -!- brunoerg [~brunoerg@186.204.131.48] has joined #bitcoin-core-dev
18:06 -!- l0rinc [~l0rinc@user/l0rinc] has quit [Quit: l0rinc]
18:10 -!- l0rinc [~l0rinc@user/l0rinc] has joined #bitcoin-core-dev
18:19 -!- Cory48 [~Cory35@user/pasha] has joined #bitcoin-core-dev
18:19 < gmaxwell> _Sam--: your remarks may not have recieved a reply, since they appear transparently malicious given that Liquid has litterally nothing to do with segwit.  And while that kind of remark might decieve people elsewhere, it's a lot less likely to here.
18:19 -!- l0rinc [~l0rinc@user/l0rinc] has quit [Quit: l0rinc]
18:19 -!- MyNickname [~default@107-137-16-146.lightspeed.chtnsc.sbcglobal.net] has joined #bitcoin-core-dev
18:20 < _Sam--> thanks for your reply, and hope life finds you well.   With all due respect, Greg, claiming Liquid has "literally nothing to do with SegWit" is historical revisionism.
18:21 < _Sam--> SegWit's primary technical achievement was fixing third-party transaction malleability. Without a fix for malleability, building complex, multi-transaction contracts required for payment channels and federated sidechains like Liquid is unacceptably risky and complex.
18:21 < _Sam--> So while Liquid may not use witness data directly for its transfers, the fundamental enabling technology that made it—and the Lightning Network—viable to build robustly on top of Bitcoin was the malleability fix that SegWit delivered. To deny that connection is just gaslighting.
18:22 -!- l0rinc [~l0rinc@user/l0rinc] has joined #bitcoin-core-dev
18:22 -!- Cory35 [~Cory35@user/pasha] has quit [Ping timeout: 250 seconds]
18:22 < _Sam--> We could have used a simple commitment scheme to improve scalability and light client security for everyone, but instead, the protocol was bent to serve corporate interests. They solved a business problem, not a Bitcoin problem.
18:24 < gmaxwell> That's simply untrue, and liquid launched without any support for segwit at all.  (I believe a recentish revision finally added segwit support).  It's lack of relation is absolute and complete.
18:25 < _Sam--> That's a textbook misdirection. The argument isn't whether Liquid uses SegWit addresses. It's that the entire project was made viable by SegWit fixing transaction malleability on the Bitcoin mainnet.
18:25 < _Sam--> instead of doing something more useful.
18:25 < _Sam--> You're deliberately ignoring the foundational prerequisite to focus on a trivial implementation detail. Before SegWit, the malleability bug made the complex, multi-stage contracts required for a secure two-way peg dangerously unreliable. Fixing malleability was the green light for building robust sidechains and L2s.
18:25 < gmaxwell> What 'simple commitment scheme'?  I'm not aware of any such proposals now, there certantly weren't any back then or for years after.
18:25 < _Sam--> To claim the relationship is "absolute and complete" zero because you initially used P2SH addresses for the peg-in is like saying a skyscraper has "no relation" to the bedrock it's built on because the lobby is decorated with marble. It's a transparently deceptive argument.
18:25 < gmaxwell> _Sam--: it wasn't any kind of prerequsite at all,  it made no use of it.  Malleability isn't a problem for liquid.
18:26 < gmaxwell> _Sam--: segwit is an optional signature style one could _NOT USE_ with liquid.  It's just unrelated.
18:26 < _Sam-->  It's telling that the same people who claim a UTXO commitment is too "complex" or "changes the security model" championed SegWit. SegWit was a far more convoluted change that involved separating signature data and redefining transaction IDs. And for what? So Blockstream could patent and build second-layer solutions like Liquid.
18:27 < _Sam--> <_Sam--> Let me spell it out: SegWit works by making transactions look like **anyone-can-spend** garbage to any non-upgraded node. The entire security of every SegWit coin hinges on the "economic majority" benevolently enforcing rules that old nodes literally cannot see or validate. It was a convoluted hack that broke transaction finality by separating the witness.
18:27 < gmaxwell> You're now just repeating yourself SamGPT.  What UTXO commitment scheme are you referring to? What comments by what people?
18:28 < _Sam--> The UTXO commitment, such as a Merkle root, would be part of the block header. It would be just as integral to the block as the transaction Merkle root is today.
18:28 < _Sam--> A new node would first download the chain of block headers, which is extremely small. The heaviest chain of headers is the trust anchor, secured by the immense hash power of the network.
18:28 < gmaxwell> How is transaction finality changed in any way?  
18:28 < _Sam--> You then ask any untrusted peer for the UTXO set and for a Merkle proof for a random UTXO.
18:28 < _Sam--> You verify that the provided proof connects that UTXO to the Merkle root that is committed to in the PoW-secured block header.
18:28 < _Sam--> If a malicious node gives you a fake UTXO set, the Merkle proofs they generate for it will not match the valid root in the block header. You would detect the fraud instantly.
18:29 < _Sam--> it's the same thing i told you 10 years ago when we were fighting about big blocks
18:29 < gmaxwell> So you're referring to some imaginary scheme that exists only inside your head and your chatbot's head, which has never been proposed anywhere, and which you imagine people would call too complex?  Why not also just keep your deluded and abusive IRC commentary also in the land of your imagination?
18:29 < _Sam--> gmaxwell: you've not proven anything
18:29 < _Sam--> We could have used a simple commitment scheme to improve scalability and light client security for everyone, but instead, the protocol was bent to serve corporate interests. They solved a business problem, not a Bitcoin problem.
18:29 < _Sam--> You were part of it.
18:30 < gmaxwell> What scheme? got a hyperlink?
18:30 < _Sam--> i just told you how it works, read it.  we're older and more mature now.
18:30 < gmaxwell> where is this supposed commitment scheme that unspecfied people have rejected?
18:31 < _Sam--> i outlined it on #bitcoin but nobody was smart enough to reply.
18:31 < _Sam--> in more detail.
18:31 < gmaxwell> _Sam--: so it's a scheme you've just suggested now.  And your questoin is why a litteral decade ago people did not see into the future and implement your proposal which doesn't fix transaction malleability in favor of something that does?
18:31 < _Sam--> gmaxwell: the point was the entire protocol was bent towards your business interests instead of those of the community.
18:31 < _Sam--> we're older now it's ok to say "youre right"
18:32 < _Sam--> i don't want to be enemies.
18:32 < gmaxwell> As I established above, segwit provided no benefit to Liquid.
18:32 < _Sam--> You're deliberately ignoring the foundational prerequisite to focus on a trivial implementation detail. Before SegWit, the malleability bug made the complex, multi-stage contracts required for a secure two-way peg dangerously unreliable. Fixing malleability was the green light for building robust sidechains and L2s.
18:32 < gmaxwell> perhaps you'd prefer to move your goalpoast now?
18:32 < _Sam--> now i'd like to for you acknowledge that in 2025 you can deliver a trustlessly verifiable utxo set.
18:33 < _Sam--> *no
18:33 < gmaxwell> _Sam--: How is something that wasn't even used at all when Liquid was created in any way "foundational"?  it's just unrelated. 
18:33 < _Sam--> That's a textbook misdirection. The argument isn't whether Liquid uses SegWit addresses. It's that the entire project was made viable by SegWit fixing transaction malleability on the Bitcoin mainnet.
18:34 -!- brunoerg [~brunoerg@186.204.131.48] has quit [Ping timeout: 260 seconds]
18:34 < _Sam--> we're not on opposite teams.
18:34 < _Sam--> my idea isn't to make "bitcoin worse"
18:34 < gmaxwell> Repeating yourself again, SamGPT.  I didn't say anything about addresses, I said it didn't use it in any form.  It couldn't tell that segwit was active on bitcoin and would have worked identically were it not.
18:34 < _Sam--> it's that you refuse to make it better.
18:34 < gmaxwell> I don't have anything to do with it, dimwit.
18:36 < _Sam--> i mean after verifying 1million blocks that i didn't have to for the nth time, it's like i remember why i wanted it in the first place.
18:36 < gmaxwell> you know you can just start bitcoin core up with a utxo snapshot and it will work, right? as of over a year ago I believe.
18:37 < _Sam--> i have old pruned copies i just keep around
18:37 < gmaxwell> Sure you do.
18:37 < _Sam--> cmon dude, i dont want to fight.
18:37 < _Sam--> let's keep it intellectual this time.
18:39 < _Sam--> are you still doing any robot wars?  i lived in vegas practically across the street for a bit there.
18:44 -!- MyNickname [~default@107-137-16-146.lightspeed.chtnsc.sbcglobal.net] has quit [Ping timeout: 258 seconds]
18:47 < _Sam--> gmaxwell: no disrespect for real, there's not many people probably thinking of these things, but think about if you want to:
18:47 < _Sam--> The UTXO commitment is a result that a miner must calculate after applying the valid transactions in their block.
18:47 < _Sam--> Think of it like this:
18:47 < _Sam--> Every full node knows the correct UTXO set at block N-1.
18:47 < _Sam--> When a miner proposes block N, every full node processes the transactions in it, destroying the old UTXOs and creating the new ones.
18:48 < _Sam--> Based on this, every full node independently calculates what the correct UTXO root for block N should be.
18:48 < _Sam--> They then compare their calculated root to the one the miner put in the block header.
18:48 < _Sam--> If the miner tried to "add their own UTXO," their calculated root would not match the root that every honest node calculates. The block would be a blatant violation of the consensus rules and would be rejected instantly.
18:48 -!- lightningbot [lightningb@azure.erisian.com.au] has quit [Server closed connection]
18:48 -!- lightningbot [~supybot@2400:8901::f03c:91ff:febb:bbc1] has joined #bitcoin-core-dev
18:51 < _Sam--> it's almost the exact thing i remember saying 10 years ago but still don't know why segwit was more important, except to your team.
19:01 -!- w0xlt [~w0xlt@209.184.121.14] has joined #bitcoin-core-dev
19:03 -!- jerryf [~jerryf@user/jerryf] has quit [Remote host closed the connection]
19:03 -!- jerryf [~jerryf@user/jerryf] has joined #bitcoin-core-dev
19:06 -!- w0xlt [~w0xlt@209.184.121.14] has quit [Ping timeout: 260 seconds]
19:08 -!- MyNickname [~default@107-137-16-146.lightspeed.chtnsc.sbcglobal.net] has joined #bitcoin-core-dev
19:08 -!- shwouchk [~shwouchk@user/shwouchk] has quit [Ping timeout: 258 seconds]
19:10 -!- shwouchk [~shwouchk@user/shwouchk] has joined #bitcoin-core-dev
19:10 -!- Cory94 [~Cory48@user/pasha] has joined #bitcoin-core-dev
19:12 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
19:13 < _Sam--> again with the utmost gracious appreciate for all of the efforts of you and everyone else, please take a holistic view of 2025.   You could buy more things a bitcoin in 2015.  More people ran nodes in 2015.   Less borrowed money was being used buy bitcoin and put it in corporate treasuries.  Mining wasn't (probably) quite as badly centralized.  Again, i'm just being a devil's advocate here folks, not a jerk, even though i am.
19:13 < _Sam--> *appreciation.
19:13 -!- MyNickname [~default@107-137-16-146.lightspeed.chtnsc.sbcglobal.net] has quit [Ping timeout: 248 seconds]
19:13 < _Sam--> you had your chance it was great for corporate america.
19:14 -!- Cory48 [~Cory35@user/pasha] has quit [Ping timeout: 250 seconds]
19:15 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 248 seconds]
19:16 < _Sam--> which is the antithesis of what i would have pegged you for, gmaxwell 
19:20 -!- Cory63 [~Cory94@user/pasha] has joined #bitcoin-core-dev
19:23 -!- Cory94 [~Cory48@user/pasha] has quit [Ping timeout: 250 seconds]
19:29 < _Sam--> you were my knowledge is free hero.   wisdom is expensive.
19:32 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 248 seconds]
19:33 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
19:34 < _Sam--> how patents you got for your free knowledge?
19:35 -!- Cory66 [~Cory63@user/pasha] has joined #bitcoin-core-dev
19:38 -!- Cory74 [~Cory66@user/pasha] has joined #bitcoin-core-dev
19:38 -!- Cory63 [~Cory94@user/pasha] has quit [Ping timeout: 250 seconds]
19:39 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 260 seconds]
19:41 -!- Cory66 [~Cory63@user/pasha] has quit [Ping timeout: 250 seconds]
19:41 -!- Cory81 [~Cory74@user/pasha] has joined #bitcoin-core-dev
19:44 -!- Cory74 [~Cory66@user/pasha] has quit [Ping timeout: 250 seconds]
19:47 -!- Cory62 [~Cory81@user/pasha] has joined #bitcoin-core-dev
19:51 -!- Cory81 [~Cory74@user/pasha] has quit [Ping timeout: 250 seconds]
19:57 < _Sam--> gmaxwell: i've realized this as always for what it is.  Let's stop pretending this is a good-faith technical debate. Your entire argument is a masterclass in deflection, so let's talk about something you can't obscure with technical jargon: your patents.
19:58 < _Sam--> How can you, a co-founder of Blockstream, lecture anyone about the purity of Bitcoin's security model when your name is on patents for sidechain technology? Bitcoin was created to be an open, permissionless system, the antithesis of the rent-seeking, proprietary enclosure that the patent system represents.
19:58 < _Sam--> You position yourself as a steward of the protocol while your company was simultaneously building a patent moat around the ecosystem. This isn't about what's best for Bitcoin; it's about what's best for Blockstream's shareholders. You championed the convoluted SegWit soft-fork because it enabled your business model, while dismissing cleaner, more direct scaling approaches that didn't require your proprietary solutions.
19:58 < _Sam--> So, please, spare me the disingenuous lectures. The community's distrust isn't "malicious"; it's a perfectly rational response to the corporate capture of an open-source project that you helped orchestrate.
19:58 < _aj_> _Sam--: take it to reddit, no one here is paying you any attention
20:05 < _Sam--> _aj_: nobody can reddit can explain why merkle root of the utxo set in the block wouldn't work
20:05 < _Sam--> *on reddit
20:05 < _Sam--> only gmaxwell thinks he can
20:08 < _aj_> gmaxwell is active on reddit
20:09 < _Sam--> he was active on irc we were having a lively convo.
20:09 < _Sam--> but it turned into a disingenious exchange. like always.
20:09 -!- w0xlt [~w0xlt@209.184.121.14] has joined #bitcoin-core-dev
20:10 -!- Cory77 [~Cory62@user/pasha] has joined #bitcoin-core-dev
20:14 -!- Cory62 [~Cory81@user/pasha] has quit [Ping timeout: 250 seconds]
20:18 -!- w0xlt [~w0xlt@209.184.121.14] has quit [Ping timeout: 248 seconds]
20:20 < _Sam--> _aj_: tell gmaxwell if aaron swartz were alive gmaxwelll would be banned from reddit for being a patently a troll.
20:21 -!- _Sam-- [~sam-@user/-Sam-:39802] has left #bitcoin-core-dev [Leaving]
20:24 -!- Cory49 [~Cory77@user/pasha] has joined #bitcoin-core-dev
20:28 -!- Cory77 [~Cory62@user/pasha] has quit [Ping timeout: 250 seconds]
20:40 -!- rszarka [~szarka@2603:3003:4eac:100:c01a:cfa:a330:cd8b] has joined #bitcoin-core-dev
20:43 -!- robszarka [~szarka@2603:3003:4eac:100:3cbf:a0bf:5a8b:676] has quit [Ping timeout: 260 seconds]
20:45 -!- HowHsu [~hacker4we@user/hacker4web3bitco] has joined #bitcoin-core-dev
21:01 -!- cmirror [~cmirror@4.53.92.114] has quit [Remote host closed the connection]
21:01 -!- cmirror [~cmirror@4.53.92.114] has joined #bitcoin-core-dev
21:08 -!- shwouchk [~shwouchk@user/shwouchk] has quit [Ping timeout: 260 seconds]
21:08 -!- w0xlt [~w0xlt@209.184.121.14] has joined #bitcoin-core-dev
21:13 -!- w0xlt [~w0xlt@209.184.121.14] has quit [Ping timeout: 260 seconds]
21:40 -!- w0xlt [~w0xlt@209.184.121.14] has joined #bitcoin-core-dev
21:43 -!- l0rinc [~l0rinc@user/l0rinc] has quit [Quit: l0rinc]
21:47 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Remote host closed the connection]
21:56 -!- w0xlt [~w0xlt@209.184.121.14] has quit [Ping timeout: 258 seconds]
22:03 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev
22:16 -!- l0rinc [~l0rinc@user/l0rinc] has joined #bitcoin-core-dev
22:34 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Ping timeout: 260 seconds]
22:36 -!- TheCharlatan [~drgrid@2a01:4f8:c013:ed0b::1] has quit [Server closed connection]
22:37 -!- TheCharlatan [~drgrid@2a01:4f8:c013:ed0b::1] has joined #bitcoin-core-dev
22:49 -!- w0xlt [~w0xlt@209.184.121.14] has joined #bitcoin-core-dev
22:50 -!- qubuepe24 [~qubuepe24@user/qubuepe24] has quit [Quit: Leaving]
22:55 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev
22:57 -!- w0xlt [~w0xlt@209.184.121.14] has quit [Ping timeout: 260 seconds]
22:59 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Ping timeout: 258 seconds]
23:15 < bitcoin-git> [bitcoin] maflcko opened pull request #33269: test: Fixup fill_mempool docstring (master...2508-test-fill-mempool-docs) https://github.com/bitcoin/bitcoin/pull/33269
23:30 -!- w0xlt [~w0xlt@209.184.121.14] has joined #bitcoin-core-dev
23:31 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev
23:34 -!- w0xlt [~w0xlt@209.184.121.14] has quit [Ping timeout: 248 seconds]
--- Log closed Fri Aug 29 00:00:24 2025