14:00:29 <achow101> #startmeeting 14:00:29 <core-meetingbot> Meeting started Thu May 18 14:00:29 2023 UTC. The chair is achow101. Information about MeetBot at https://bitcoin.jonasschnelli.ch/ircmeetings. 14:00:29 <core-meetingbot> Available commands: action commands idea info link nick 14:00:29 <_aj_> meeting? 14:00:33 <_aj_> hi! 14:00:33 <glozow> hi 14:00:35 <instagibbs> meeting. 14:00:35 <josie> hi 14:00:39 <brunoerg> hi 14:00:40 <hebasto> hi 14:00:41 <achow101> #bitcoin -core-dev Meeting: achow101 _aj_ amiti ariard aureleoules b10c BlueMatt brunoerg cfields darosior dergoegge dongcarl fanquake fjahr furszy gleb glozow hebasto instagibbs jamesob jarolrod jonatack josibake kallewoof kanzure kouloumos kvaciral laanwj LarryRuane lightlike luke-jr MacroFake Murch phantomcircuit pinheadmz promag provoostenator ryanofsky sdaftuar S3RK stickies-v sipa theStack TheCharlatan vasild 14:00:43 <sipa> hi 14:00:46 <pinheadmz> hi hi hi 14:00:47 <willcl-ark> hi 14:00:54 <cfields> hi 14:00:55 <pinheadmz> heyyyyy 14:00:59 <kouloumos> hi 14:01:01 <abubakarsadiq> hi 14:01:06 <achow101> There is one pre-proposed meeting topic today, are there are any last minute topics to add to the list? 14:01:06 <furszy> hi 14:01:11 <fjahr> hi 14:01:11 <vasild> hi 14:01:40 <TheCharlatan> hi 14:01:54 <achow101> we'll start with the usual 14:02:18 <achow101> #topic assumeutxo updates (jamesob) 14:02:18 <core-meetingbot> topic: assumeutxo updates (jamesob) 14:03:01 <achow101> anything changed since last week? i've noticed a lot of review and testing going on which is a good sign 14:03:21 <fjahr> seems james isn't here: There is some movement in the current focus on the current focus PR, sjors and me are reviewing and suhas is working on an alternative approach 14:04:09 <achow101> that's great! 14:04:10 <sdaftuar> waves 14:04:11 <josie> after our most recent bitdevs, got a few people trying assumeutxo out on a bitcoin ATM, which is kinda cool 14:04:31 <achow101> #topic package relay (glozow) 14:04:31 <core-meetingbot> topic: package relay (glozow) 14:04:52 <glozow> I'm traveling currently. Main PR to review is #26711. I've gotten some review on the BIP and am going to address that soon. Big branch soonTM. 14:04:56 <gribble> https://github.com/bitcoin/bitcoin/issues/26711 | validate package transactions with their in-package ancestor sets by glozow ÷ Pull Request #26711 ÷ bitcoin/bitcoin ÷ GitHub 14:05:38 <achow101> cool! 14:05:42 <instagibbs> ill do another comb through once tests are passing again 14:05:42 <instagibbs> :P 14:05:52 <achow101> #topic libbitcoinkernel updates (TheCharlatan) 14:05:52 <core-meetingbot> topic: libbitcoinkernel updates (TheCharlatan) 14:07:01 <achow101> there's no primary PR listed for it 14:07:29 <achow101> something got merged and the next thing is still being implemented? 14:07:32 <fanquake> #27636 14:07:35 <gribble> https://github.com/bitcoin/bitcoin/issues/27636 | kernel: Remove interface_ui, util/system from kernel library by TheCharlatan ÷ Pull Request #27636 ÷ bitcoin/bitcoin ÷ GitHub 14:07:41 <fanquake> is what is being actively reviewed/worked on atm 14:08:03 <instagibbs> can I add to primary blocker 14:08:09 <fanquake> sure 14:08:19 <TheCharlatan> next thing is ready for review. By my estimates 2 more for stage 2 completion. 14:08:48 <achow101> great! 14:09:01 <achow101> #topic BIP 324 (sipa) 14:09:01 <core-meetingbot> topic: BIP 324 (sipa) 14:09:29 <achow101> The libsecp pr looks quite active 14:09:30 <sipa> good progress on the libsecp256k1 side of ellswift (https://github.com/bitcoin-core/secp256k1/pull/1129) 14:09:45 <sipa> I think we'll get it in soon. 14:09:53 <achow101> awesome 14:10:04 <sipa> I'll update the Bitcoin Core PR afterwards and look into opening the next one. But for now, focus is there. 14:10:17 <achow101> #topic ad-hoc high priority for review 14:10:17 <core-meetingbot> topic: ad-hoc high priority for review 14:10:31 <achow101> anything to add/remove from https://github.com/orgs/bitcoin/projects/1/views/4 14:10:53 <sdaftuar> is parallel downloads still chasing concept ACK? 14:11:01 <instagibbs> no I think it's chasing regular review 14:11:08 <fanquake> Yep 14:11:10 <sdaftuar> let's upgrade it 14:11:15 <achow101> moved to the blockers list 14:11:15 <instagibbs> #27626 killed off your fresh ack sorry 14:11:18 <gribble> https://github.com/bitcoin/bitcoin/issues/27626 | Parallel compact block downloads, take 3 by instagibbs ÷ Pull Request #27626 ÷ bitcoin/bitcoin ÷ GitHub 14:11:25 <sdaftuar> will re-ack shortly 14:11:31 <instagibbs> on the plus side anyone running it will get cpu usage fixes 14:11:51 <instagibbs> Would like to get it in early this cycle, thanks 14:12:06 <fanquake> Not exactly "priority for review", but we are at last call for 25.x backports. Either we'll do an rc3, or it'll be about time for final. Comment in #27686 if there is anything. 14:12:08 <gribble> https://github.com/bitcoin/bitcoin/issues/27686 | [25.x] Changes for rc3 || finalize by fanquake ÷ Pull Request #27686 ÷ bitcoin/bitcoin ÷ GitHub 14:12:11 <josie> instagibbs: nice way to motivate testers 14:12:26 <instagibbs> josie there are a few of us running the PR now, but wider pool is better 14:13:22 <achow101> #topic Important changes in 25.0 to cover in the new RC Testing Guide (abubakarsadiq) 14:13:23 <core-meetingbot> topic: Important changes in 25.0 to cover in the new RC Testing Guide (abubakarsadiq) 14:13:52 <abubakarsadiq> Context: I worked on the v25rc Candidate testing guide and I would be glad to have some feedback on the changes that should or should not be included. 14:14:12 <abubakarsadiq> The changes I selected to test are random from the release notes. (https://github.com/bitcoin-core/bitcoin-devwiki/wiki/25.0-Release-Notes-Draft) 14:14:16 <achow101> thanks for working on that 14:14:33 <achow101> I think we're probably about to cut the final release? 14:14:40 <josie> abubakarsadiq: looks good so far! 14:14:55 <abubakarsadiq> thanks anchow, josie 14:14:58 <abubakarsadiq> 1 Test -maxconnections=0 will now disable -dnsseed and -listen 14:15:05 <josie> can we add a link to the guide in the umbrella testing issue for 25.0? (assuming it looks good to go) 14:15:54 <abubakarsadiq> 2 Test non-witness transactions that are greater than 65 are allowed in the mempool 14:16:14 <instagibbs> non-witness *serialization* transactions, they can be witness :) 14:16:29 <fanquake> added to #27621 14:16:30 <gribble> https://github.com/bitcoin/bitcoin/issues/27621 | v25.0 testing ÷ Issue #27621 ÷ bitcoin/bitcoin ÷ GitHub 14:16:38 <abubakarsadiq> 3 Test Finalizing a PSBT with inputs spending Miniscript-compatible P2WSH scripts and test spending the coin. 14:16:53 <sipa> cool 14:17:02 <kanzure> hi. 14:17:08 <abubakarsadiq> I will update that @instagibs thanks 14:17:17 <instagibbs> ð 14:17:29 <abubakarsadiq> 4 Ensure sendrawtransaction rpc with transaction containing unspendable value > maxburnamount argument value will not be submitted. 14:17:48 <josie> the guide is also scheduled for the review club next week, iirc (small shill for PR review club) 14:18:07 <abubakarsadiq> yes josie :) 14:18:23 <abubakarsadiq> 5 Test unloadwallet fails if a rescan is in progress 14:19:26 <abubakarsadiq> 6 Test the new endpoint /rest/deploymentinfo that has been added for fetching various state regarding deployment of consensus changes 14:19:58 <abubakarsadiq> 7 Ensure verifychain returns false if the check can't be completed 14:20:49 <achow101> any other topics? 14:21:06 <fanquake> 23.2 and 24.1 have been tagged. Bin available shortly 14:21:12 <fanquake> *bins 14:21:28 <abubakarsadiq> there are more on the guide bonus tests https://github.com/bitcoin-core/bitcoin-devwiki/wiki/25.0-Release-Candidate-Testing-Guide 14:21:36 <fanquake> Website posts/release annoucements to follow etc etc 14:21:57 <sdaftuar> achow101: quick mempool thing? 14:22:10 <achow101> #topic mempool thing (sdaftuar) 14:22:10 <core-meetingbot> topic: mempool thing (sdaftuar) 14:22:31 <sdaftuar> i wrote up the new mempool design idea that sipa and recently presented https://github.com/bitcoin/bitcoin/issues/27677 14:23:36 <sdaftuar> i'll be doing some research on historical data in the near future, so if people have feedback on any of the open questions, or ideas/concerns for what to look for in historical data as i try to analyze the impact of cluster size limits on the network, i'd love to hear it 14:23:47 <sdaftuar> that's it 14:23:50 <josie> sdaftuar: gave it a read last night, its really well written 14:24:09 <sdaftuar> thanks! credit to many people who have given me feedback and copy edits :) 14:24:23 <sipa> Maybe some rough expectations around it: I think the idea is very solid, and code experiments seem to show it's very viable, but there are a lot of open questions, and we don't expect it to be PR'ed for at least a few months 14:24:34 <achow101> any idea on the timelines for that? 14:24:47 <sdaftuar> maybe a PR in the fall if all goes well? 14:25:02 <josie> regarding historic data, would love to chat more about that (offline), ive been working with historic mempool data from 2017 - present. sounds like you guys already have some historic data but happy to share what I have + any insights if its helpful 14:26:19 <achow101> any other topics? 14:26:40 <sdaftuar> josie: sounds good, thanks. i have a datalogger and simulation system that i can use for this analysis but happy to chat 14:28:33 <fanquake> Another good meeting 14:28:40 <achow101> #endmeeting