16:00:01 <abubakarsadiq> #startmeeting 
16:00:01 <corebot> abubakarsadiq: Meeting started at 2026-11-12T16:00+0000
16:00:03 <corebot> abubakarsadiq: Current chairs: abubakarsadiq
16:00:04 <corebot> abubakarsadiq: Useful commands: #action #info #idea #link #topic #motion #vote #close #endmeeting
16:00:05 <corebot> abubakarsadiq: See also: https://hcoop-meetbot.readthedocs.io/en/stable/
16:00:06 <corebot> abubakarsadiq: Participants should now identify themselves with '#here' or with an alias like '#here FirstLast'
16:00:07 <provoostenator> hi
16:00:14 <brunoerg> hi
16:00:14 <janb84> hi
16:00:15 <abubakarsadiq> #bitcoin -core-dev Meeting: _aj_ abubakarsadiq achow101 andrewtoth b10c brunoerg cfields danielabrozzoni darosior dzxzg eugenesiegel fanquake fjahr furszy hebasto hodlinator instagibbs janb84 jarolrod johnny9dev jonatack josie jurraca kanzure kevkevin laanwj lightlike l0rinc maflcko marcofleon maxedw Murch pinheadmz provoostenator pseudoramdom ryanofsky sdaftuar sedited sipa sliv3r__ sr_gi stickies-v stringintech
16:00:15 <abubakarsadiq> theStack vasild willcl-ark
16:00:20 <tigerMafia> hello world
16:00:23 <lightlike> hi
16:00:24 <nervana21> hi
16:00:25 <willcl-ark> hi
16:00:26 <hebasto> hi
16:00:26 <sr_gi> hi
16:00:28 <sedited> hi
16:00:34 <hodlinator> hi
16:00:35 <viniciuscestarii> hi
16:00:36 <pinheadmz> yo
16:00:36 <pseudoramdom> hi
16:00:37 <stratospher> hi
16:00:39 <sliv3r__> hi
16:00:49 <abubakarsadiq> There is 1 pre-proposed meeting topics this week. Any last minute ones to add?
16:01:00 <stringintech> hi
16:01:32 <abubakarsadiq> I will start with the working groups
16:01:34 <abubakarsadiq> #topic Fuzzing WG Update (eugenesiegel, marcofleon)
16:02:09 <yuvicc> hi
16:02:42 <eugenesiegel> hi no update
16:02:42 <andrewtoth> hi
16:02:52 <b10c> hi
16:02:57 <abubakarsadiq> I think they are not here, I will call wg that are around then
16:03:04 <abubakarsadiq> #topic addr-relay WG update (stratospher)
16:03:33 <stratospher> no update. we've been thinking more about addr-relay protections.
16:04:14 <abubakarsadiq> any pr's to review there or write ups?
16:04:28 <stratospher> coming soon
16:04:40 <sedited> nice :)
16:04:40 <abubakarsadiq> 👍
16:04:50 <abubakarsadiq> #topic Kernel WG Update (sedited)
16:04:55 <sedited> purpleKarrot posted another RFC issue on encapsulation: #36842 .
16:04:56 <corebot> https://github.com/bitcoin/bitcoin/issues/36842 | Encapsulation of vocabulary types · Issue #36842 · bitcoin/bitcoin · GitHub
16:04:59 <sedited> I'd like to encourage people to comment there.
16:05:03 <sedited> I've explored down some rabbit holes, but nothing to present here yet.
16:05:33 <abubakarsadiq> #topic Benchmarking WG Update (l0rinc)
16:06:59 <abubakarsadiq> I noticed some activity on benchcoin, anything interesting to share @andrewtoth?
16:07:14 <andrewtoth> l0rinc isn't here?
16:07:32 <abubakarsadiq> yeah, i think he is travelling.
16:07:45 <yancy> hi
16:07:46 <andrewtoth> well sedited shared a branch he was working on, which he managed to reindex-chainstate in 20 minutes or so :rocket:
16:08:07 <abubakarsadiq> :rocket
16:08:08 <andrewtoth> I managed it in under an hour on my machine, others have similar speeds
16:08:40 <andrewtoth> I believe it's an amalgamation of many different techniques that have been experimented with in the past, notably sipa's suggestion to use a negative utxo set
16:08:40 <johnny9dev> hi
16:08:51 <andrewtoth> but really sedited can speak more to it
16:09:05 <cfields> hi
16:09:09 <dzxzg> hi
16:09:11 <andrewtoth> that's all I've got on it :)
16:09:30 <abubakarsadiq> @sedited anything to add there?
16:09:51 <abubakarsadiq> thanks @andrewtoth
16:09:52 <sedited> yes, the core of its architecture is inspired by a comment sipa left on delving some time ago: https://delvingbitcoin.org/t/libbitcoin-for-core-people/1222/36?u=thecharlatan
16:10:20 <sedited> i think it might be a promising direction to take things, but just exploring for now.
16:10:53 <abubakarsadiq> Is the speedup just from arch change, or we were able to max cpu?
16:11:09 <sedited> it does finally seem to bind validation performance to mostly the CPU on all its cores.
16:11:27 <andrewtoth> i think the arch change allows the max cpu
16:11:31 <abubakarsadiq> nice
16:11:51 <andrewtoth> the main gist is that it allows parallel connecting of blocks on multiple threads
16:12:06 <andrewtoth> swiftsync i believe would allow something like that as well
16:12:21 <andrewtoth> but this method does not need a precomputed hints file
16:12:38 <abubakarsadiq> nice thats a +
16:13:14 <abubakarsadiq> #topic QA WG Update (brunoerg)
16:13:26 <sedited> and works without assumevalid.
16:13:35 <yancy> im not sure what is meant by parallel connecting of blocks
16:13:47 <yancy> parsing a block in multiple threads?
16:14:06 <andrewtoth> rather out-of-order connecting yancy
16:14:17 <yancy> ah
16:14:19 <brunoerg> I ran mutation testing for src/validation.cpp and got over 300 surviving mutants, in case anyone wants to see, they're all on mutanthub now: https://mutanthub.space/mutants?q=&project=&mutationStatus=SURVIVED&reviewStatus=&operator=&contributor=&file=validation.cpp&commit=&since=&until=&drift=&superseded=&sort=
16:14:36 <abubakarsadiq> by connecting here, you mean validation and adding to the chain i presume?
16:15:28 <brunoerg> I'm reviewing them again that might be equivalent or not useful - but so far looks like there are many gaps to be addressed in the tests
16:15:47 <brunoerg> that's all
16:16:14 <sedited> sounds like we need to brace for a lot of PRs for that ^^
16:17:42 <abubakarsadiq> brunoerg: Do you have to manually validate each pr that the mutant was indeed killed? or its automated? then drahdbot link for that will be useful?
16:18:48 <brunoerg> I'm trying to automate but would be helpful if people put in the PR description the link to the mutant from mutanthub.space and/or the git diff of the mutant. Recently, I had to deal with a PR where the mutants were printscreen haha
16:20:22 <brunoerg> but yes, most of the time I validate manually, especially because LLMs can write test cases to kill mutants but it doesn't mean they are done correctly or in a good shape
16:20:22 <abubakarsadiq> #topic QML GUI WG Update (johnny9dev)
16:20:38 <johnny9dev> jarolrod handed off a document to us with 300 findings against gui-qml after spending a lot of time doing exhaustive QA with his clankers.
16:20:42 <yancy> grep screen :P
16:20:58 <johnny9dev> this certainly pushes back my schedule for opening up the PR to bitcoin/bitcoin
16:21:14 <johnny9dev> the good thing is that he can't seem to find any more issues and we are feature complete
16:21:34 <johnny9dev> so while it will take us longer to get a PR ready, we'll be much better after satisfying those findings
16:22:12 <johnny9dev> his experience was that having his agents model the software and investigate teh model uncovers a lot more
16:22:49 <Murch[m]> hi
16:22:51 <johnny9dev> "create an arc42 document" or "create a state machine with all of the implicit and explicit states in a single document" seemed to be juicy prompts
16:23:07 <abubakarsadiq> @johnny9dev, maybe a good idea to use scan with project loupe?
16:23:32 <johnny9dev> i think we already have reached out
16:23:41 <johnny9dev> so that will happen too
16:23:54 <abubakarsadiq> 👍
16:24:19 <johnny9dev> anyway, thats all for this week. working through issues and feedback
16:25:36 <abubakarsadiq> #topic re-activate Erlay WG and Signal chat (or alternative) (sr_gi)
16:26:02 <sr_gi> Just wanted to say that given the interest shown in the last two coredevs and the state of the reworked approach for Erlay, I wanted to re-activate our old Signal group for discussions (or find an alternative that works for people who are interested) and also re-activate the WG (will do that myself on GH).
16:26:34 <sr_gi> Those who are interested in joining, let me know so I can add you to the chat. That will be mostly to discuss some of the pending changes and open questions.
16:27:29 <abubakarsadiq> Okay I will move it from the archive to active wg, starting next week, you should be pinged for update
16:27:53 <abubakarsadiq> If there are updates already, we can discuss now too?
16:28:45 <sr_gi> Not really, I rebased the PR on master and I'm working on addressing some of the points that I brought up during coredev
16:29:13 <abubakarsadiq> #topic Erlay WG Update (sr_gi)
16:30:21 <sr_gi> Something that came up recently on another PR (cannot recall the number now) is that the Erlay handshake is special and now we have better ways to do it with BIP 434, so given BIP-330 is in draft mode, it may make sense to get rid of the custom negotiation and move to BIP-434 for that
16:31:11 <Murch[m]> That sounds reasonable
16:31:18 <sr_gi> Besides that, just working on addressing the points brought up at coredev, will have a todo list and report on that regularly
16:31:30 <sr_gi> That's it
16:32:03 <abubakarsadiq> Anything else to discuss?
16:33:32 <abubakarsadiq> #endmeeting