14:00:09 <achow101> #startmeeting 14:00:10 <core-meetingbot> Meeting started Thu May 11 14:00:10 2023 UTC. The chair is achow101. Information about MeetBot at https://bitcoin.jonasschnelli.ch/ircmeetings. 14:00:10 <core-meetingbot> Available commands: action commands idea info link nick 14:00:17 <hebasto> hi 14:00:17 <pinheadmz_> gm 14:00:20 <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 vasild 14:00:21 <josie> hi 14:00:25 <instagibbs> hallo 14:00:28 <brunoerg> hi 14:00:29 <theStack> hi 14:00:29 <vasild> hi 14:00:30 <luke-jr> hi 14:00:32 <glozow> hi 14:00:33 <achow101> Welcome to the weekly IRC meeting 14:00:37 <kouloumos> hi 14:00:39 <lightlike> hi 14:00:42 <dergoegge> hi 14:00:45 <achow101> We'll start with our priority projects. 14:00:45 <josie> pinheadmz_: ga 14:00:47 <furszy> hi 14:00:52 <jonatack> hi -- temporarily back in Europe for a wedding :) 14:00:58 <glozow> look at this amazing attendance - new timeslot is a win! 14:01:10 <achow101> #topic assumeutxo updates (jamesob) 14:01:10 <core-meetingbot> topic: assumeutxo updates (jamesob) 14:01:14 <pinheadmz_> ðÂÂÂðÂÂÂð 14:01:18 <achow101> #link https://github.com/bitcoin/bitcoin/pull/27596 14:01:35 <achow101> any updates on assumeutxo? what's next to review? 14:02:11 <Murch> hi 14:02:15 <achow101> The current pr to review seems to be #24008 14:02:20 <gribble> https://github.com/bitcoin/bitcoin/issues/24008 | assumeutxo: net_processing changes by jamesob ÷ Pull Request #24008 ÷ bitcoin/bitcoin ÷ GitHub 14:03:02 <provoostenator> Oh hi we changed the time? 14:03:04 <instagibbs> he's alive, might take a min 14:03:13 <jamesob> hi 14:03:18 <stickies-v> hi 14:03:26 <jamesob> got the ol instagibbs alarm clock treatment 14:03:36 <jamesob> yeah, 24008 is the one right now 14:03:44 <luke-jr> lol 14:04:01 <jamesob> although the monster branch (#27596) is definitely functioning 14:04:03 <gribble> https://github.com/bitcoin/bitcoin/issues/27596 | assumeutxo (2) by jamesob ÷ Pull Request #27596 ÷ bitcoin/bitcoin ÷ GitHub 14:04:28 <jamesob> I'm ironing out some weirdness with pruning - during snapshot use, that branch doesn't prune as aggressively as it should, but I'm hoping to have that resolved in the next few days 14:04:48 <jamesob> in any case, it's definitely ready for testing so if you're feeling the urge to load "production" snapshots, go nuts 14:04:59 <achow101> awesome. will test it out 14:05:19 <josie> jamesob: sweet, will run it 14:05:25 <achow101> #topic package relay updates (glozow) 14:05:26 <core-meetingbot> topic: package relay updates (glozow) 14:05:30 <achow101> #link https://github.com/bitcoin/bitcoin/issues/27463 14:05:36 <glozow> The PR to review right now is #27609. It fixes an issue sdaftuar found, and allows submitpackage on mainnet (which I've been told may be helpful given current conditions). 14:05:38 <gribble> https://github.com/bitcoin/bitcoin/issues/27609 | rpc: allow submitpackage to be called outside of regtest by glozow ÷ Pull Request #27609 ÷ bitcoin/bitcoin ÷ GitHub 14:05:59 <josie> jamesob: just to clarify, the monster branch includes the distributing over p2p? 14:06:01 <instagibbs> would really like to get that and sub-package evaluation in soonish 14:06:12 <glozow> I've also updated #26711, which is now rebased on top of that. 14:06:13 <glozow> For p2p changes, I am currently ironing out the approach for orphanage. I plan to have the "big branch" up soon. 14:06:14 <josie> or how does the monster branch differ from 24008? 14:06:14 <jamesob> josie: no it definitely doesn't; that's going to be a massive project 14:06:15 <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:06:18 <provoostenator> josie: no that's an even bigger monster, but not implemented 14:06:19 <_aj_> oops, hi 14:06:47 <instagibbs> I think we can get that and 26711 merged in short order 14:06:49 <achow101> glozow: switch primary blocker to #27609? 14:06:50 <gribble> https://github.com/bitcoin/bitcoin/issues/27609 | rpc: allow submitpackage to be called outside of regtest by glozow ÷ Pull Request #27609 ÷ bitcoin/bitcoin ÷ GitHub 14:06:54 <glozow> achow101: yes! thank you 14:07:12 <jamesob> josie: if the respective PR descriptions do not make the distinction between those branches clear, let me know (sorry for interrupting pkgrelay) 14:07:48 <achow101> cool 14:08:11 <achow101> #topic libbitcoinkernel updates (TheCharlatan) 14:08:12 <core-meetingbot> topic: libbitcoinkernel updates (TheCharlatan) 14:08:17 <achow101> #link https://github.com/bitcoin/bitcoin/issues/27587 14:09:06 <achow101> The tracking issue is up now, but I don't think there's any open prs currently? 14:09:24 <instagibbs> 2 just got merged, I think, so progress being made? 14:09:26 <fanquake> there is one draft, and one to-be-opened PR 14:09:45 <fanquake> that new PR should be the new prio 14:09:50 <achow101> fanquake: number? 14:09:57 <fanquake> itâÂÂs not open yet 14:10:00 <achow101> ah 14:10:04 <lightlike> #27576 is the draft one 14:10:06 <gribble> https://github.com/bitcoin/bitcoin/issues/27576 | kernel: Remove args, chainparams, chainparamsbase from kernel library by TheCharlatan ÷ Pull Request #27576 ÷ bitcoin/bitcoin ÷ GitHub 14:10:28 <fanquake> good progress in any case 14:10:31 <achow101> yep 14:10:42 <achow101> #topic BIP 324 (sipa) 14:10:42 <core-meetingbot> topic: BIP 324 (sipa) 14:10:47 <TheCharlatan> should be up by tomorrow hopefully. 14:11:01 <achow101> There's no tracking issue yet, I think sipa is not here 14:11:20 <instagibbs> is tim around 14:11:39 <provoostenator> When new monster PR for p2p encryption? 14:11:41 <instagibbs> real_or_random? anything people should be looking at 14:11:58 <achow101> I think right now it's all secp stuff? 14:12:06 <willcl_ark> I can see Pieter 14:12:06 <willcl_ark> Perhaps a matrix issue? 14:12:35 <real_or_random> hi, sorry, I'm here 14:12:39 <theStack> would be good to update https://bip324.com/sections/code-review/ (not sure who is in charge of that those days) 14:13:06 <real_or_random> I'm in touch with pieter but apparently his messages don't go through 14:13:23 <achow101> current pr is #27479? 14:13:25 <gribble> https://github.com/bitcoin/bitcoin/issues/27479 | BIP324: ElligatorSwift integrations by sipa ÷ Pull Request #27479 ÷ bitcoin/bitcoin ÷ GitHub 14:13:47 <sipa_> hi 14:13:54 <achow101> sipa_: hi 14:14:00 <provoostenator> That's weird. Mine are showing up in the log, and I can see Pieter. 14:14:01 <provoostenator> (I'm also using the Matrx bridge) 14:14:08 <real_or_random> the next thing is that we need to merge https://github.com/bitcoin-core/secp256k1/pull/1129, which will happen within the next days 14:14:10 <glozow> perhaps https://github.com/bitcoin-core/secp256k1/pull/1129 also? 14:14:26 <sipa_> So, we're currently in a libsecp256k1 sprint this week, which resulted already in some changes to the ellswift PR there 14:14:37 <sipa_> Next week I'll update the PR in core to update for that. 14:14:56 <instagibbs> nice 14:15:03 <sipa_> And also open a tracking issue, as I want to think a bit about how to structure future PRs. 14:15:12 <achow101> great, looking forward to it 14:15:30 <jamesob> sipa_: anything we can run in the wild right now to test? 14:15:47 <sipa_> So the current thing to look at is 1129, it's not mergable in current condition (because it depends on secp changes), and slightly outdated, but the Core code won't change much. 14:15:56 <sipa_> jamesob: nothing to play around with right, sorry. 14:16:07 <sipa_> *right now 14:16:07 <jamesob> no prob; no shortage of prospective changes to run :) 14:16:13 <jamesob> fee market has made sure of that 14:16:18 <sipa_> haha 14:17:02 <achow101> #topic High priority for review 14:17:03 <core-meetingbot> topic: High priority for review 14:17:08 <sipa_> errr, i mean, the next thing to look at is #27479 14:17:10 <gribble> https://github.com/bitcoin/bitcoin/issues/27479 | BIP324: ElligatorSwift integrations by sipa ÷ Pull Request #27479 ÷ bitcoin/bitcoin ÷ GitHub 14:17:25 <achow101> Anything we should change in the ad-hoc high priority? 14:17:57 <_aj_> add the backport prs? 14:18:12 <achow101> good idea 14:18:19 <fanquake> The current priority there is the 24.1rc3 PR 14:18:20 <josie> high prio is now any high priority PR that is NOT connected to a project, yeah? 14:18:26 <achow101> yes 14:18:27 <glozow> #27614 14:18:29 <gribble> https://github.com/bitcoin/bitcoin/issues/27614 | [24.1] Backports for rc3 by fanquake ÷ Pull Request #27614 ÷ bitcoin/bitcoin ÷ GitHub 14:18:57 <jonatack> achow101: can you please add #27231 for me, happy to trade reviews with anyone on that 14:18:59 <gribble> https://github.com/bitcoin/bitcoin/issues/27231 | Fix logging RPC and -debugexclude with 0/none values, add test coverage, improve docs by jonatack ÷ Pull Request #27231 ÷ bitcoin/bitcoin ÷ GitHub 14:19:05 <glozow> #27624 14:19:06 <gribble> https://github.com/bitcoin/bitcoin/issues/27624 | [23.2] Backports for rc1 by fanquake ÷ Pull Request #27624 ÷ bitcoin/bitcoin ÷ GitHub 14:19:08 <achow101> please review the backports, we'd like to get some releases out soon 14:19:40 <fanquake> Ideally 24.1rc3 will be tagged today 14:19:50 <glozow> fanquake: +1 14:19:51 <achow101> jonatack: done 14:20:00 <fanquake> 25 still a little ways off 14:20:11 <jonatack> achow101: ty 14:20:24 <fanquake> 23.2 should be straightforward with review. IâÂÂll push rel notes and similar up to that branch 14:21:11 <achow101> cool 14:21:43 <achow101> Are there any other topics to discuss? 14:21:57 <fanquake> +1 for the new meeting time 14:21:58 <josie> fanquake: im running 24.1rc3, lookin good so far 14:22:00 <fanquake> great turnout 14:22:03 <instagibbs> chasing concept acks I guess https://github.com/bitcoin/bitcoin/pull/27626 14:22:08 <glozow> achow101: last time you were going to mention "cancel wallet meeting" and we didn't get to it? 14:22:10 <fanquake> Good high prio updates too 14:22:28 <jamesob> instagibbs: will be deploying that to bmon shortly 14:22:30 <achow101> instagibbs: added 14:22:33 <instagibbs> reviving an old PR because I've seen some ummmmm, "persistent" peers that actually never hand us a full block 14:22:35 <achow101> glozow: oh yeah 14:22:41 <josie> +1 regarding project updates, really helpful to know what to focus on and really appreciate the project "leads" showing up for the meeting 14:22:48 <instagibbs> and these peers seem to connect to a LOT of listening nodes 14:23:01 <instagibbs> jamesob cheers 14:23:24 <instagibbs> If you look in your logs you may see "Timeout"s 14:23:34 <instagibbs> let me know if you do 14:23:40 <achow101> since we have time, I have a wallet meeting topic, and I forgot to run last week's wallet meeting 14:23:44 <jonatack> instagibbs: been seeing timeouts indeed 14:23:53 <instagibbs> We can DM about it :) 14:23:53 <achow101> #topic Cancel wallet meeting 14:23:54 <core-meetingbot> topic: Cancel wallet meeting 14:23:55 <instagibbs> fin 14:24:34 <brunoerg> Is there a specific channel for wallet stuff? 14:24:42 <jonatack> brunoerg: i don't believe so 14:24:53 <instagibbs> i think this channel is fine 14:24:54 <jonatack> only for builds and the gui 14:25:04 <achow101> I think it's probably time to sunset the wallet meeting. there's been less focus on wallet things and we could probably bring wallet related topics back to the general meeting when they come up 14:25:15 <jonatack> (and signet) 14:26:05 <provoostenator> achow101: sounds good. I was thinking the new time slot could help with (my poor) attendance, but we seem to have plenty of room in the regular meeting anyway. 14:26:50 <achow101> we can re-evaluate if there isn't space in the general meeting to discuss wallet (or other specific subsystem) topics 14:27:42 <sipa_> sgtm to cancel it for now 14:28:18 <josie> +1, one meeting per week seems like enough 14:28:18 <achow101> ok, unless someone raises an objection between now and next friday, I think we can consider it canceled for now 14:28:24 <glozow> sgtm. I'm in favor of wallet topics being discussed in the general meeting 14:28:37 <achow101> Any other topics? 14:28:45 <furszy> would be nice to have a wallet's PRs queue. Even when we aren't chatting much publicly about it, there is lot of stuff going on there. 14:28:45 <fanquake> sounds like if anyone raises objections they are nominating themselves to run it in any case 14:29:02 <furszy> and well, I'm a bit tired of reviewing 24914 over and over. 14:29:26 <josie> furszy: maybe a project? 14:29:26 <sipa_> #24914 14:29:28 <gribble> https://github.com/bitcoin/bitcoin/issues/24914 | wallet: Load database records in a particular order by achow101 ÷ Pull Request #24914 ÷ bitcoin/bitcoin ÷ GitHub 14:29:36 <instagibbs> is that a RFM complaint, or "someone else please review" complaint 14:29:56 <furszy> RFM? 14:30:00 <sipa_> ready for merge 14:30:16 <furszy> both then :p. 14:30:44 <achow101> we could setup a wallet project board 14:32:05 <achow101> seems like no topics 14:32:12 <achow101> #endmeeting