14:00:15 <achow101> #startmeeting 
14:00:17 <pinheadmz> hi
14:00:18 <TheCharlatan> hi
14:00:19 <josie> hi
14:00:20 <achow101> #bitcoin -core-dev Meeting: abubakarsadiq achow101 _aj_ ajonas b10c brunoerg cfields darosior dergoegge fanquake fjahr furszy gleb glozow hebasto instagibbs jarolrod jonatack josibake kanzure laanwj LarryRuane lightlike luke-jr maflcko maxedw Murch pinheadmz provoostenator ryanofsky sdaftuar S3RK stickies-v sipa sr_gi tdb3 theStack TheCharlatan vasild willcl-ark
14:00:20 <jarolrod> Hi
14:00:22 <kanzure> hi
14:00:23 <b10c> hi
14:00:28 <abubakarsadiq> hi
14:00:30 <ryanofsky> hi
14:00:31 <furszy> hi
14:00:31 <achow101> There is one pre-proposed meeting topic this week. Any last minute ones to add?
14:00:39 <dergoegge> hi
14:00:40 <lightlike> Hi
14:00:48 <sipa> hi
14:00:53 <maxedw> hi
14:00:55 <stickies-v> hi
14:01:07 <willcl-ark> hi
14:01:28 <achow101> #topic Fuzzing WG Update (dergoegge)
14:02:21 <theStack> hi
14:02:35 <cfields> hi
14:02:42 <dergoegge> no update
14:02:47 <dergoegge> I thought we're doing these monthly
14:02:56 <achow101> #topic Kernel WG Update (TheCharlatan)
14:03:16 <TheCharlatan> The focus is currently on "de-risking" the necessary "glue" code between the external header and the internal code. This means de-duplicating redundant logic between the various interfaces.
14:03:18 <josie> dergoegge: i think some people will have updates each week, others monthly ?
14:03:27 <TheCharlatan> In the working group we recently discussed approaches for handling the logging in a better way. An alternative that was not explored yet could be directly exposing a kernel logging macro.
14:03:52 <TheCharlatan> The experimental rust-bitcoinkernel crate, which implements a Rust wrapper around the API as implemented in #30595, is now available through crates.io.
14:03:53 <gribble> https://github.com/bitcoin/bitcoin/issues/30595 | kernel: Introduce initial C header API by TheCharlatan · Pull Request #30595 · bitcoin/bitcoin · GitHub
14:04:13 <TheCharlatan> This makes it a bit easier for other developers that might also want to experiment with it.
14:04:20 <TheCharlatan> I also started work on an experimental kernel-based node to validate the API.
14:04:57 <TheCharlatan> This has already surfaced some stuff that I put into the API PR.
14:05:10 <TheCharlatan> that's it from me
14:05:15 <achow101> dergoegge: last week, seemed like most people wanted updates every week. so doing it based on who's here to minimize downtime.
14:05:40 <achow101> #topic Benchmarking WG Update (josibake, l0rinc)
14:05:48 <josie> since last week, willcl-ark and i have been working on a CI workflow for long running benchmarks. so far, making good progress!
14:05:57 <josie> we have a workflow where someone can take their branch and open it as a PR against https://github.com/bitcoin-dev-tools/benchcoin and this will automatically kick off a benchmark and publish the final results as artifacts on the PR
14:06:09 <josie> right now, the only benchmark we have working is an assumeutxo benchmark on signet (i.e., loading a snapshot and doing IBD from snapshot to chaintip with background validation paused)
14:06:17 <josie> next steps will be to make this work on mainnet and figure out how to intelligently distribute workloads to our dedicated runners pool
14:06:23 <josie> Novo__ has been working on rebasing fjahr 's batch validation PR, as thats one of the first ones we'd like to start benchmarking using the assumeutxo bench method
14:06:36 <josie> thats all for benchmarking!
14:06:45 <achow101> #topic Silent Payments WG Update (josibake, RubenSomsen)
14:06:48 <cfields> which PR#?
14:06:54 <josie> ive been incorporating all of the review comments / feedback from coredev on the bitcoin-core/secp256k1#1519, hoping to finish that this week
14:06:55 <gribble> https://github.com/bitcoin/bitcoin/issues/1519 | GUI: change language selection format to "language - country (locale name)" by Diapolo · Pull Request #1519 · bitcoin/bitcoin · GitHub
14:07:01 <josie> next will be rebasing the bitcoin core PRs on top of that. for a list of the PRs / status, im keeping the tracking issue up to date (bitcoin/bitcoin#28536)
14:07:02 <gribble> https://github.com/bitcoin/bitcoin/issues/28536 | BIP352 tracking issue · Issue #28536 · bitcoin/bitcoin · GitHub
14:07:24 <josie> thats all for silent payments
14:07:34 <josie> cfields: was that a question for the benchmarking update?
14:07:43 <cfields> josie: yes
14:08:08 <willcl-ark> cfields: #29491
14:08:10 <gribble> https://github.com/bitcoin/bitcoin/issues/29491 | [DO NOT MERGE] Schnorr batch verification for blocks by fjahr · Pull Request #29491 · bitcoin/bitcoin · GitHub
14:08:18 <cfields> ah, nice. thanks.
14:08:34 <achow101> #topic Cluster Mempool WG Update (sdaftuar, sipa)
14:08:40 <sipa> Update on txgraph (part of cluster mempool). My plan is to have a first PR for the "txgraph" module open next week (this is the layer that reasons about dependencies/clusters/linearizations for the entire mempool, as opposed to the cluster_linearize.h file that is already merged, which is for reasoning about a single individual cluster). Txgraph will probably be a few PRs (mining/eviction logic may
14:08:46 <sipa> be added later, some memory usage optimizations, reorg...
14:08:48 <sipa> logic), but i hope to have the basics out next week.
14:09:27 <sipa> After that, the main PR for cluster mempool can be rebased on the txgraph logic + the mempool changeset PR.
14:09:42 <sipa> That's it for me, suhas doesn't seem to be around.
14:10:07 <achow101> #topic MuSig2 WG Update (achow101)
14:10:52 <achow101> The libsecp subtree has been updated to 0.6.0 which includes the musig module.  #29675 is no longer draft. the WG will be meeting after the IRC meeting to discuss breaking it up so it isn't 30 commits
14:10:54 <gribble> 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
14:11:09 <achow101> #topic Legacy Wallet Removal WG Update (achow101)
14:11:49 <achow101> Still waiting on review on #30328, otherwise, no update
14:11:51 <gribble> https://github.com/bitcoin/bitcoin/issues/30328 | wallet: Remove IsMine from migration code by achow101 · Pull Request #30328 · bitcoin/bitcoin · GitHub
14:12:14 <achow101> there's signal groups for both of my WGs, lmk if you would like to join
14:12:26 <achow101> #topic Multiprocess WG Update (ryanofsky)
14:13:50 <kanzure> brb 5min
14:14:49 <cfields> heh perhaps "WG call directly after the IRC meeting" isn't the best approach for _every_ WG.
14:15:06 <achow101> saw ryanofsky, but i guess no update
14:15:17 <achow101> #topic package relay WG Update (glozow)
14:15:23 <josie> cfields: certainly not for people in multiple working groups
14:15:31 <glozow> working on #31190 followup
14:15:33 <gribble> https://github.com/bitcoin/bitcoin/issues/31190 | TxDownloadManager followups by glozow · Pull Request #31190 · bitcoin/bitcoin · GitHub
14:15:45 <glozow> That’s it
14:16:03 <achow101> #topic Ad-hoc high priority for review
14:16:03 <achow101> Anything to add or remove from https://github.com/orgs/bitcoin/projects/1/views/4
14:16:09 <glozow> (I thought we signed up for the dates we were gonna give updates? Or did I read that wrong?)
14:16:41 <ryanofsky> Sorry was afk. Multiprocess update was: Not much new, priority is to get multiprocess code enabled in next release so mining IPC interface is easily accessible. Tracking issue is #28722 with PRs to review, and there is now a Signal group linked there. That's it.
14:16:43 <gribble> https://github.com/bitcoin/bitcoin/issues/28722 | Multiprocess tracking issue · Issue #28722 · bitcoin/bitcoin · GitHub
14:16:49 <achow101> glozow: last week, seemed like most people wanted weekly updates from all WGs; will be doing it based on who's here (people saying hi)
14:18:02 <achow101> Perhaps we should kill this high priority for review topic. it doesn't seem like anyone is using, and if you have something high priority for review, maybe make a working group?
14:18:10 <glozow> Ok my bad
14:18:48 <josie> achow101: iirc, everyone seemed to favor that last meeting? or if you have a high prio, just drop it here? i could be misremembering tho
14:18:52 <stickies-v> achow101: sounds good. people can still suggest ad-hoc topics too if anything urgent non-wg comes up, of course
14:19:05 <sipa> we're all still figuring things ouy
14:19:07 <sipa> out
14:19:13 <achow101> josie: I don't recall there being discussion about this topic
14:20:50 <achow101> right now there is only one pr in the board, and things that have been added to it previously don't seem to have actually gotten any more review than if they hadn't been on it
14:21:45 <achow101> will remove it for now
14:22:05 <achow101> #topic bitcoin-dev mailing list archive links (kanzure)
14:22:14 <kanzure> lists.linuxfoundation.org is no more and is no longer hosting the mailing list static archives at this time (not just for bitcoin-dev but ~everything including some LKML stuff?)
14:22:19 <kanzure> see recently announced on https://x.com/kanzure/status/1853779672514826334
14:22:23 <kanzure> see general mailing list migration background here https://gnusha.org/pi/bitcoindev/CABaSBaxDjj6ySBx4v+rmpfrw4pE9b=JZJPzPQj_ZUiBg1HGFyA@mail.gmail.com/
14:22:30 <kanzure> to be fair, they did give us some notice, hence the actual migration was done earlier this year
14:22:36 <kanzure> there's a lot of backlinks out there, it's really sad to have this many links broken :(
14:22:43 <kanzure> someone is working on asking them to re-host the static archives to preserve backlinks and fight against bit rot on the web, dunno if they will
14:22:48 <achow101> kanzure: I thought they promised to keep the archive?
14:23:03 <kanzure> well if they did then i did not receive that, i don't have LF contactperson details
14:23:06 <kanzure> i have made https://gnusha.org/url to help with the link rot, try it out:
14:23:10 <kanzure> https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-June/014472.html
14:23:14 <kanzure> https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/lightning-dev/2015-November/000313.html
14:23:18 <kanzure> just made lightning-dev work a few minutes ago, pls test and let me know if something is broken
14:23:23 <kanzure> attachments do not presently work for lightning-dev, someone can make a public-inbox archive from lightning-dev.mbox if they have a complete archive.
14:23:29 <kanzure> the mapping (used by my /url service) from {id}.html -> {Message-ID} was made with these scripts, pls review if you are bored: https://gist.github.com/kanzure/4e7bcc58344ceaa1a668e65a434adb2b
14:23:39 <kanzure> btctranscripts.com pull request here: https://github.com/bitcointranscripts/bitcointranscripts/pull/566
14:23:45 <kanzure> bitcoin.git can also be updated, please see https://github.com/bitcoin/bitcoin/pull/29782#issuecomment-2460974096 which is asking about what to do about the comments in the codebase that need to be updated
14:23:54 <kanzure> oh just saw a new pull request for that, maybe 31240 https://github.com/bitcoin/bitcoin/pull/31240
14:24:08 <kanzure> uhh there was one more thing
14:24:22 <achow101> these links are sprinkled all over the place. this is gonna be a pain
14:24:25 <kanzure> oh right, it occurs to me that bitcoin-core-dev is not supported on gnusha.org/url at the moment, does anyone have strong opinions about this. announcement emails always went out to bitcoin-dev AFAIK so they are captured there at least.
14:24:51 <bitcoin-git> [bitcoin] kevkevinpal closed pull request #30570: [tests] New fuzz target wallet_rpc (master...fuzzwalletrpc) https://github.com/bitcoin/bitcoin/pull/30570
14:25:18 <achow101> considering the demise of that list, i'm not sure that migrating it will even be useful as everyone who was previously on it won't be notified of the new list location
14:25:45 <achow101> and the announcements occur in a ton of other places too, including bitcoin-dev
14:26:08 <kanzure> maybe post a question publicly and ask if anyone was using just the bitcoin-core-dev announcement list specifically, or thinks it should continue to exist, i would hate to break something important
14:27:34 <achow101> perhaps ask on bitcoindev?
14:29:08 <achow101> Any other topics to discuss?
14:31:13 <achow101> #endmeeting