--- Log opened Thu May 11 00:00:57 2023 00:04 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 264 seconds] 00:11 -!- Zenton [~user@user/zenton] has quit [Ping timeout: 264 seconds] 00:21 -!- flag [~flag@81.56.89.175] has joined #bitcoin-core-dev 00:22 -!- flag [~flag@81.56.89.175] has quit [Client Quit] 00:25 -!- flag [~flag@81.56.89.175] has joined #bitcoin-core-dev 00:33 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 00:38 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 264 seconds] 00:55 -!- Guyver2 [~Guyver@77.174.98.73] has joined #bitcoin-core-dev 00:57 -!- aielima [~aielima@user/aielima] has joined #bitcoin-core-dev 01:00 -!- puchka [~puchka@185.203.122.26] has quit [Ping timeout: 240 seconds] 01:06 -!- stevenwy37 [~stevenwy3@103.152.220.44] has quit [Remote host closed the connection] 01:07 -!- stevenwy37 [~stevenwy3@103.152.220.44] has joined #bitcoin-core-dev 01:08 -!- puchka [~puchka@185.203.122.26] has joined #bitcoin-core-dev 01:45 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev 01:50 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 240 seconds] 02:02 -!- berndj [~berndj@197.189.254.139] has quit [Quit: ZNC - http://znc.in] 02:02 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 02:02 -!- Guyver2 [~Guyver@77.174.98.73] has left #bitcoin-core-dev [Closing Window] 02:02 -!- berndj [~berndj@197.189.254.139] has joined #bitcoin-core-dev 02:07 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 265 seconds] 02:13 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 02:18 -!- puchka [~puchka@185.203.122.26] has quit [Ping timeout: 268 seconds] 02:18 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 264 seconds] 02:18 -!- puchka [~puchka@185.203.122.26] has joined #bitcoin-core-dev 02:27 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 02:34 -!- cncr04s [~cncr04s@afxr.net] has quit [Ping timeout: 246 seconds] 02:35 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 265 seconds] 02:36 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 02:41 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 265 seconds] 02:41 -!- cncr04s [~cncr04s@afxr.net] has joined #bitcoin-core-dev 03:00 -!- aielima [~aielima@user/aielima] has quit [Quit: Ciao] 03:00 -!- Zenton [~user@user/zenton] has joined #bitcoin-core-dev 03:04 -!- aielima [~aielima@user/aielima] has joined #bitcoin-core-dev 03:07 -!- pharonix71 [~pharonix7@user/pharonix71] has quit [Ping timeout: 240 seconds] 03:09 -!- pharonix71 [~pharonix7@user/pharonix71] has joined #bitcoin-core-dev 03:09 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 03:14 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 240 seconds] 03:15 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 03:17 -!- SpellChecker_ [~SpellChec@user/SpellChecker] has joined #bitcoin-core-dev 03:17 -!- SpellChecker [~SpellChec@user/SpellChecker] has quit [Ping timeout: 240 seconds] 03:19 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 264 seconds] 03:30 -!- vyHamii [~vyHamii@116.104.87.246] has quit [Remote host closed the connection] 03:35 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 264 seconds] 03:37 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 03:39 -!- pablomartin [~pablomart@185.169.255.243] has joined #bitcoin-core-dev 03:42 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 265 seconds] 03:48 < dviola> how does one verifies the binaries nowadays? 03:48 < dviola> https://github.com/bitcoin/bitcoin/tree/master/contrib/builder-keys/keys.txt seems gone 03:49 < dviola> bitcoincore.org still links to it 03:50 < darosior> dviola: this was just fixed this week on the website Github repo. I expect the website will be updated shortly. 03:51 < fanquake> dviola: updates for binary verification instructions have been made to https://github.com/bitcoin-core/bitcoincore.org/, but are not yet reflected on the website 03:52 < dviola> oh, ok.. thanks 03:59 -!- Guest74 [~Guest44@m83-179-70-96.cust.tele2.lt] has joined #bitcoin-core-dev 04:00 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 04:03 -!- Guest74 [~Guest44@m83-179-70-96.cust.tele2.lt] has quit [Client Quit] 04:04 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 240 seconds] 04:07 -!- stevenwy37 [~stevenwy3@103.152.220.44] has quit [Remote host closed the connection] 04:08 -!- stevenwy37 [~stevenwy3@103.152.220.44] has joined #bitcoin-core-dev 04:11 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 04:16 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 265 seconds] 04:33 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 04:38 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 246 seconds] 04:46 -!- PaperSword [~Thunderbi@securemail.qrsnap.io] has quit [Ping timeout: 246 seconds] 04:56 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 05:01 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 265 seconds] 05:13 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 05:18 -!- Guest6 [~Guest6@201-13-215-146.dial-up.telesp.net.br] has joined #bitcoin-core-dev 05:21 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 264 seconds] 05:21 -!- gundam964 [~gundam964@201-13-215-146.dial-up.telesp.net.br] has joined #bitcoin-core-dev 05:22 -!- Guest6 [~Guest6@201-13-215-146.dial-up.telesp.net.br] has quit [Client Quit] 05:23 < josie> fyi - https://bitcoincore.org/en/meetings/ still has the cal invites for the old meeting time. not sure how much people use that, but prob nice to have an updated cal invite. I can create a calendar and open a PR to change it, unless someone already has a good public calendar we can use 05:23 < josie> could also just remove the cal invite and put the actual meeting time on the page 05:24 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 05:29 -!- gundam964 [~gundam964@201-13-215-146.dial-up.telesp.net.br] has quit [Quit: Client closed] 05:30 -!- martinus [~martinus@046125249096.public.t-mobile.at] has quit [Remote host closed the connection] 05:32 -!- martinus [~martinus@046125249096.public.t-mobile.at] has joined #bitcoin-core-dev 05:34 -!- Earnestly [~earnest@user/earnestly] has joined #bitcoin-core-dev 05:34 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev 05:39 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev 05:39 -!- stevenwy37 [~stevenwy3@103.152.220.44] has quit [Remote host closed the connection] 05:39 -!- stevenwy37 [~stevenwy3@103.152.220.44] has joined #bitcoin-core-dev 05:43 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 246 seconds] 05:47 < achow101> Huh, I thought it was updated? 05:47 < achow101> Maybe it's just the gcal? 05:48 < achow101> Oh, maybe updating it changed the link 05:49 -!- preimage [~halosghos@user/halosghost] has joined #bitcoin-core-dev 05:51 < josie> achow101: I just updated the devwiki (altho it still has the outdated gcal link), not sure where else we have it listed 05:51 < achow101> We can probably drop the gcal link, the ics invite should be pretty easy to re-generate 05:52 < achow101> That page should also list the time 05:53 -!- ZeroMaster_ [~webirc@87-126-6-81.ip.btc-net.bg] has quit [Ping timeout: 268 seconds] 05:56 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: WeeChat 3.8] 06:00 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev 06:00 -!- TheRec_ [~toto@84-75-225-47.dclient.hispeed.ch] has quit [Ping timeout: 260 seconds] 06:06 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev 06:10 -!- bugs_ [~bugs@user/bugs/x-5128603] has joined #bitcoin-core-dev 06:27 < fanquake> Backport review beg in https://github.com/bitcoin/bitcoin/pull/27614 06:32 < brunoerg> Is there an issue (or other place) to track BIP324 like package relay/libbitcoinkernel? 06:32 < achow101> brunoerg: not yet 06:33 < instagibbs> it should take a few minutes only? 06:33 < brunoerg> achow101: ok, thanks 06:33 < instagibbs> just a bare "here's a list of open PRs" would be helpful 06:34 < fanquake> nice timing GH https://www.githubstatus.com 06:35 < instagibbs> > github down 06:35 < instagibbs> > refreshed loaded page 06:35 < instagibbs> > lose page 06:35 < instagibbs> dont know what i expected 06:35 < brunoerg> instagibbs: same here lol 06:35 -!- vysn [~vysn@user/vysn] has quit [Remote host closed the connection] 06:36 < achow101> instagibbs: I suppose someone else could make it, but ideally the champion should so that they can edit it 06:37 < fanquake> brunoerg: probably just delete your comment about the link not working 06:37 < fanquake> obviously a temporary GH issue 06:38 < brunoerg> fanquake: I tried it yet but not successful 06:39 < brunoerg> after some attempts, I could do it 06:39 -!- vysn [~vysn@user/vysn] has joined #bitcoin-core-dev 06:48 -!- stevenwy37 [~stevenwy3@103.152.220.44] has quit [Remote host closed the connection] 06:49 -!- stevenwy37 [~stevenwy3@103.152.220.44] has joined #bitcoin-core-dev 06:53 -!- stevenwy37 [~stevenwy3@103.152.220.44] has quit [Ping timeout: 256 seconds] 06:57 -!- dviola [~diego@user/dviola] has quit [Ping timeout: 240 seconds] 07:00 < achow101> #startmeeting 07:00 < 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. 07:00 < core-meetingbot> Available commands: action commands idea info link nick 07:00 < hebasto> hi 07:00 < pinheadmz_> gm 07:00 < 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 07:00 < josie> hi 07:00 < instagibbs> hallo 07:00 < brunoerg> hi 07:00 < theStack> hi 07:00 < vasild> hi 07:00 < luke-jr> hi 07:00 < glozow> hi 07:00 < achow101> Welcome to the weekly IRC meeting 07:00 < kouloumos> hi 07:00 < lightlike> hi 07:00 < dergoegge> hi 07:00 < achow101> We'll start with our priority projects. 07:00 < josie> pinheadmz_: ga 07:00 < furszy> hi 07:00 < jonatack> hi -- temporarily back in Europe for a wedding :) 07:00 < glozow> look at this amazing attendance - new timeslot is a win! 07:01 < achow101> #topic assumeutxo updates (jamesob) 07:01 < core-meetingbot> topic: assumeutxo updates (jamesob) 07:01 < pinheadmz_> 馃寧馃實馃審 07:01 < achow101> #link https://github.com/bitcoin/bitcoin/pull/27596 07:01 < achow101> any updates on assumeutxo? what's next to review? 07:02 < Murch> hi 07:02 < achow101> The current pr to review seems to be #24008 07:02 <@gribble> https://github.com/bitcoin/bitcoin/issues/24008 | assumeutxo: net_processing changes by jamesob 路 Pull Request #24008 路 bitcoin/bitcoin 路 GitHub 07:03 < provoostenator> Oh hi we changed the time? 07:03 < instagibbs> he's alive, might take a min 07:03 < jamesob> hi 07:03 < stickies-v> hi 07:03 < jamesob> got the ol instagibbs alarm clock treatment 07:03 < jamesob> yeah, 24008 is the one right now 07:03 < luke-jr> lol 07:04 < jamesob> although the monster branch (#27596) is definitely functioning 07:04 <@gribble> https://github.com/bitcoin/bitcoin/issues/27596 | assumeutxo (2) by jamesob 路 Pull Request #27596 路 bitcoin/bitcoin 路 GitHub 07:04 < 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 07:04 < jamesob> in any case, it's definitely ready for testing so if you're feeling the urge to load "production" snapshots, go nuts 07:04 < achow101> awesome. will test it out 07:05 < josie> jamesob: sweet, will run it 07:05 < achow101> #topic package relay updates (glozow) 07:05 < core-meetingbot> topic: package relay updates (glozow) 07:05 < achow101> #link https://github.com/bitcoin/bitcoin/issues/27463 07:05 < 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). 07:05 <@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 07:05 < josie> jamesob: just to clarify, the monster branch includes the distributing over p2p? 07:06 < instagibbs> would really like to get that and sub-package evaluation in soonish 07:06 < glozow> I've also updated #26711, which is now rebased on top of that. 07:06 < glozow> For p2p changes, I am currently ironing out the approach for orphanage. I plan to have the "big branch" up soon. 07:06 < josie> or how does the monster branch differ from 24008? 07:06 < jamesob> josie: no it definitely doesn't; that's going to be a massive project 07:06 <@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 07:06 < provoostenator> josie: no that's an even bigger monster, but not implemented 07:06 < _aj_> oops, hi 07:06 < instagibbs> I think we can get that and 26711 merged in short order 07:06 < achow101> glozow: switch primary blocker to #27609? 07:06 <@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 07:06 < glozow> achow101: yes! thank you 07:07 < jamesob> josie: if the respective PR descriptions do not make the distinction between those branches clear, let me know (sorry for interrupting pkgrelay) 07:07 < achow101> cool 07:08 < achow101> #topic libbitcoinkernel updates (TheCharlatan) 07:08 < core-meetingbot> topic: libbitcoinkernel updates (TheCharlatan) 07:08 < achow101> #link https://github.com/bitcoin/bitcoin/issues/27587 07:09 < achow101> The tracking issue is up now, but I don't think there's any open prs currently? 07:09 < instagibbs> 2 just got merged, I think, so progress being made? 07:09 < fanquake> there is one draft, and one to-be-opened PR 07:09 < fanquake> that new PR should be the new prio 07:09 < achow101> fanquake: number? 07:09 < fanquake> it鈥檚 not open yet 07:10 < achow101> ah 07:10 < lightlike> #27576 is the draft one 07:10 <@gribble> https://github.com/bitcoin/bitcoin/issues/27576 | kernel: Remove args, chainparams, chainparamsbase from kernel library by TheCharlatan 路 Pull Request #27576 路 bitcoin/bitcoin 路 GitHub 07:10 < fanquake> good progress in any case 07:10 < achow101> yep 07:10 < achow101> #topic BIP 324 (sipa) 07:10 < core-meetingbot> topic: BIP 324 (sipa) 07:10 < TheCharlatan> should be up by tomorrow hopefully. 07:11 < achow101> There's no tracking issue yet, I think sipa is not here 07:11 < instagibbs> is tim around 07:11 < provoostenator> When new monster PR for p2p encryption? 07:11 < instagibbs> real_or_random? anything people should be looking at 07:11 < achow101> I think right now it's all secp stuff? 07:12 -!- b_101 [~robert@185.242.5.35] has joined #bitcoin-core-dev 07:12 < willcl_ark> I can see Pieter 07:12 < willcl_ark> Perhaps a matrix issue? 07:12 < real_or_random> hi, sorry, I'm here 07:12 < theStack> would be good to update https://bip324.com/sections/code-review/ (not sure who is in charge of that those days) 07:13 < real_or_random> I'm in touch with pieter but apparently his messages don't go through 07:13 < achow101> current pr is #27479? 07:13 <@gribble> https://github.com/bitcoin/bitcoin/issues/27479 | BIP324: ElligatorSwift integrations by sipa 路 Pull Request #27479 路 bitcoin/bitcoin 路 GitHub 07:13 -!- sipa_ [~pw@user/sipa] has joined #bitcoin-core-dev 07:13 < sipa_> hi 07:13 < achow101> sipa_: hi 07:14 < provoostenator> That's weird. Mine are showing up in the log, and I can see Pieter. 07:14 < provoostenator> (I'm also using the Matrx bridge) 07:14 < 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 07:14 < glozow> perhaps https://github.com/bitcoin-core/secp256k1/pull/1129 also? 07:14 < sipa_> So, we're currently in a libsecp256k1 sprint this week, which resulted already in some changes to the ellswift PR there 07:14 < sipa_> Next week I'll update the PR in core to update for that. 07:14 < instagibbs> nice 07:15 < sipa_> And also open a tracking issue, as I want to think a bit about how to structure future PRs. 07:15 < achow101> great, looking forward to it 07:15 < jamesob> sipa_: anything we can run in the wild right now to test? 07:15 < 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. 07:15 < sipa_> jamesob: nothing to play around with right, sorry. 07:16 < sipa_> *right now 07:16 < jamesob> no prob; no shortage of prospective changes to run :) 07:16 < jamesob> fee market has made sure of that 07:16 < sipa_> haha 07:16 -!- b_101 [~robert@185.242.5.35] has quit [Ping timeout: 264 seconds] 07:17 < achow101> #topic High priority for review 07:17 < core-meetingbot> topic: High priority for review 07:17 < sipa_> errr, i mean, the next thing to look at is #27479 07:17 <@gribble> https://github.com/bitcoin/bitcoin/issues/27479 | BIP324: ElligatorSwift integrations by sipa 路 Pull Request #27479 路 bitcoin/bitcoin 路 GitHub 07:17 < achow101> Anything we should change in the ad-hoc high priority? 07:17 < _aj_> add the backport prs? 07:18 < achow101> good idea 07:18 < fanquake> The current priority there is the 24.1rc3 PR 07:18 < josie> high prio is now any high priority PR that is NOT connected to a project, yeah? 07:18 < achow101> yes 07:18 < glozow> #27614 07:18 <@gribble> https://github.com/bitcoin/bitcoin/issues/27614 | [24.1] Backports for rc3 by fanquake 路 Pull Request #27614 路 bitcoin/bitcoin 路 GitHub 07:18 < jonatack> achow101: can you please add #27231 for me, happy to trade reviews with anyone on that 07:18 <@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 07:19 < glozow> #27624 07:19 <@gribble> https://github.com/bitcoin/bitcoin/issues/27624 | [23.2] Backports for rc1 by fanquake 路 Pull Request #27624 路 bitcoin/bitcoin 路 GitHub 07:19 < achow101> please review the backports, we'd like to get some releases out soon 07:19 < fanquake> Ideally 24.1rc3 will be tagged today 07:19 < glozow> fanquake: +1 07:19 < achow101> jonatack: done 07:20 < fanquake> 25 still a little ways off 07:20 < jonatack> achow101: ty 07:20 < fanquake> 23.2 should be straightforward with review. I鈥檒l push rel notes and similar up to that branch 07:21 < achow101> cool 07:21 < achow101> Are there any other topics to discuss? 07:21 < fanquake> +1 for the new meeting time 07:21 < josie> fanquake: im running 24.1rc3, lookin good so far 07:22 < fanquake> great turnout 07:22 < instagibbs> chasing concept acks I guess https://github.com/bitcoin/bitcoin/pull/27626 07:22 < glozow> achow101: last time you were going to mention "cancel wallet meeting" and we didn't get to it? 07:22 < fanquake> Good high prio updates too 07:22 < jamesob> instagibbs: will be deploying that to bmon shortly 07:22 < achow101> instagibbs: added 07:22 < instagibbs> reviving an old PR because I've seen some ummmmm, "persistent" peers that actually never hand us a full block 07:22 < achow101> glozow: oh yeah 07:22 < josie> +1 regarding project updates, really helpful to know what to focus on and really appreciate the project "leads" showing up for the meeting 07:22 < instagibbs> and these peers seem to connect to a LOT of listening nodes 07:23 < instagibbs> jamesob cheers 07:23 < instagibbs> If you look in your logs you may see "Timeout"s 07:23 < instagibbs> let me know if you do 07:23 < achow101> since we have time, I have a wallet meeting topic, and I forgot to run last week's wallet meeting 07:23 < jonatack> instagibbs: been seeing timeouts indeed 07:23 < instagibbs> We can DM about it :) 07:23 < achow101> #topic Cancel wallet meeting 07:23 < core-meetingbot> topic: Cancel wallet meeting 07:23 < instagibbs> fin 07:24 < brunoerg> Is there a specific channel for wallet stuff? 07:24 < jonatack> brunoerg: i don't believe so 07:24 < instagibbs> i think this channel is fine 07:24 < jonatack> only for builds and the gui 07:25 < 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 07:25 < jonatack> (and signet) 07:26 < 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. 07:26 < achow101> we can re-evaluate if there isn't space in the general meeting to discuss wallet (or other specific subsystem) topics 07:27 < sipa_> sgtm to cancel it for now 07:28 < josie> +1, one meeting per week seems like enough 07:28 < achow101> ok, unless someone raises an objection between now and next friday, I think we can consider it canceled for now 07:28 < glozow> sgtm. I'm in favor of wallet topics being discussed in the general meeting 07:28 < achow101> Any other topics? 07:28 < 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. 07:28 < fanquake> sounds like if anyone raises objections they are nominating themselves to run it in any case 07:29 < furszy> and well, I'm a bit tired of reviewing 24914 over and over. 07:29 < josie> furszy: maybe a project? 07:29 < sipa_> #24914 07:29 <@gribble> https://github.com/bitcoin/bitcoin/issues/24914 | wallet: Load database records in a particular order by achow101 路 Pull Request #24914 路 bitcoin/bitcoin 路 GitHub 07:29 < instagibbs> is that a RFM complaint, or "someone else please review" complaint 07:29 < furszy> RFM? 07:30 < sipa_> ready for merge 07:30 < furszy> both then :p. 07:30 < achow101> we could setup a wallet project board 07:32 < achow101> seems like no topics 07:32 < achow101> #endmeeting 07:32 < core-meetingbot> topic: Bitcoin Core development discussion and commit log | Feel free to watch, but please take commentary and usage questions to #bitcoin | Channel logs: http://www.erisian.com.au/bitcoin-core-dev/, http://gnusha.org/bitcoin-core-dev/ | Weekly Meeting Thursday @ 14:00 UTC | Meeting topics http://gnusha.org/bitcoin-core-dev/proposedmeetingtopics.txt / http://gnusha.org/bitcoin-core-dev/proposed 07:32 < core-meetingbot> Meeting ended Thu May 11 14:32:12 2023 UTC. 07:32 < core-meetingbot> Minutes: https://bitcoin.jonasschnelli.ch/ircmeetings/logs/bitcoin-core-dev/2023/bitcoin-core-dev.2023-05-11-14.00.moin.txt 07:32 -!- sipa_ [~pw@user/sipa] has left #bitcoin-core-dev [] 07:33 < fanquake> If anyone is looking at 27614, you can ignore the CI failures as spurious/GH issues. The jobs are re-running in any case 07:34 < achow101> github seems to be having some problems 07:34 < achow101> and I think our irc bot is dead 07:43 -!- kevkevin [~kevkevin@2600:1700:b30:47c0:45e3:f1aa:c091:7a78] has joined #bitcoin-core-dev 07:51 -!- dviola [~diego@187.66.113.165] has joined #bitcoin-core-dev 07:51 < bitcoin-git> [bitcoin] hebasto opened pull request #27627: [24.x] qt: 24.1rc3 translations update (24.x...230511-24.1rc3-tr) https://github.com/bitcoin/bitcoin/pull/27627 08:00 -!- b_101 [~robert@185.242.5.35] has joined #bitcoin-core-dev 08:04 -!- b_101 [~robert@185.242.5.35] has quit [Ping timeout: 240 seconds] 08:20 < provoostenator> Is there any reason the chainstate ldb files are only 2 MB each? 08:21 < fanquake> * [new tag] v24.1rc3 -> v24.1rc3 08:21 < provoostenator> (oh I'm guessing because they need to be randomly updated) 08:22 < _aj_> provoostenator: (oh) 08:23 < provoostenator> The reason I wondered is because after an IBD with very large -dbcache it took my 2019 MBP almost half an hour to store them. Meanwhile the shutdown log says nothing and I might have forced quit it if I didn't notice the new files getting added. 08:23 -!- pablomartin [~pablomart@185.169.255.243] has quit [Ping timeout: 265 seconds] 08:23 < provoostenator> (using v25.0rc1) 08:26 -!- pablomartin [~pablomart@185.174.108.246] has joined #bitcoin-core-dev 08:32 -!- pablomartin [~pablomart@185.174.108.246] has quit [Ping timeout: 240 seconds] 08:44 -!- pablomartin [~pablomart@89.38.69.99] has joined #bitcoin-core-dev 08:56 -!- Tanner_LCC [~Tanner@2a00:23c7:4506:b101:f4cd:7681:7f8:fac] has joined #bitcoin-core-dev 08:56 -!- Tanner_LCC [~Tanner@2a00:23c7:4506:b101:f4cd:7681:7f8:fac] has quit [Client Quit] 09:07 < vasild> sr_gi[m]: yo, wrt #27602, I think in master we would not reply to GETDATA for transactions that entered the mempool after the MEMPOOL request 09:07 <@gribble> https://github.com/bitcoin/bitcoin/issues/27602 | net processing: avoid serving non-announced txs as a result of a MEMPOOL message by sr-gi 路 Pull Request #27602 路 bitcoin/bitcoin 路 GitHub 09:09 < vasild> except if it happens in the same second, e.g. mempool request at 1683821264.2 and a new tx arrives at 1683821264.7, in this case the tx entered the pool after the mempool request but both times will be rounded up to a second so both will equal 1683821264 and thus txinfo.m_time <= mempool_req would allow the reply to getdata 09:09 < vasild> s/rounded up/truncated/ 09:10 < _aj_> vasild: we'd start replying exactly 2mins after it had entered though? 09:11 < vasild> yes, I guess 09:52 -!- b_101 [~robert@185.242.5.35] has joined #bitcoin-core-dev 09:54 -!- ZeroMaster [~webirc@87-126-6-81.ip.btc-net.bg] has joined #bitcoin-core-dev 10:01 < fanquake> All changes for a 23.2rc1 should now be in #27624. So that's open for review 10:01 <@gribble> https://github.com/bitcoin/bitcoin/issues/27624 | [23.2] Backports for rc1 by fanquake 路 Pull Request #27624 路 bitcoin/bitcoin 路 GitHub 10:01 < fanquake> Note that 2 of the commits being backported in there are not clean cherry-picks 10:02 -!- dviola [~diego@187.66.113.165] has quit [Changing host] 10:02 -!- dviola [~diego@user/dviola] has joined #bitcoin-core-dev 10:10 -!- flag [~flag@81.56.89.175] has quit [Remote host closed the connection] 10:10 -!- hernanmarino [~hernanmar@190.245.116.245] has joined #bitcoin-core-dev 10:17 -!- stevenwy37 [~stevenwy3@103.152.220.44] has joined #bitcoin-core-dev 10:39 -!- stevenwy37 [~stevenwy3@103.152.220.44] has quit [Remote host closed the connection] 10:39 -!- stevenwy37 [~stevenwy3@116.206.100.4] has joined #bitcoin-core-dev 10:40 -!- Zenton [~user@user/zenton] has quit [Read error: Connection reset by peer] 10:44 -!- stevenwy37 [~stevenwy3@116.206.100.4] has quit [Ping timeout: 265 seconds] 10:46 -!- jamesob4 [~jamesob@141.156.173.67] has quit [Ping timeout: 246 seconds] 10:47 -!- jamesob [~jamesob@141.156.173.67] has quit [Ping timeout: 246 seconds] 10:52 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 265 seconds] 10:52 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev 10:59 -!- jamesob [~jamesob@141.156.173.67] has joined #bitcoin-core-dev 10:59 -!- jamesob4 [~jamesob@141.156.173.67] has joined #bitcoin-core-dev 10:59 < glozow> apologies for the flip flop, package relay blocker PR is once again #26711 10:59 <@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 11:00 < achow101> jb55: are you able to provide any more details for #27599? 11:00 <@gribble> https://github.com/bitcoin/bitcoin/issues/27599 | Node stuck with repeated "Cache size exceeds total space" log message 路 Issue #27599 路 bitcoin/bitcoin 路 GitHub 11:00 < instagibbs> great, that's the one ive reviewed :) 11:00 -!- jamesob4 [~jamesob@141.156.173.67] has quit [Read error: Connection reset by peer] 11:00 -!- jamesob2 [~jamesob@141.156.173.67] has joined #bitcoin-core-dev 11:00 -!- jamesob44 [~jamesob@141.156.173.67] has joined #bitcoin-core-dev 11:00 -!- jamesob [~jamesob@141.156.173.67] has quit [Read error: Connection reset by peer] 11:00 -!- jamesob2 is now known as jamesob 11:00 -!- vysn [~vysn@user/vysn] has quit [Remote host closed the connection] 11:01 < glozow> 馃檶 11:01 < glozow> updated the project board 11:02 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 256 seconds] 11:07 -!- hernanmarino [~hernanmar@190.245.116.245] has quit [Quit: Leaving] 11:10 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev 11:16 < fanquake> * [new tag] v25.0rc2 -> v25.0rc2 11:19 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: WeeChat 3.8] 11:22 < fanquake> To github.com:bitcoin-core/bitcoin-detached-sigs.git 11:22 < fanquake> * [new tag] v24.1rc3 -> v24.1rc3 11:32 -!- pablomartin [~pablomart@89.38.69.99] has quit [Ping timeout: 265 seconds] 11:39 -!- ___nick___ [~quassel@host86-164-104-11.range86-164.btcentralplus.com] has joined #bitcoin-core-dev 11:53 -!- svanstaa [~svanstaa@194.169.217.94] has joined #bitcoin-core-dev 11:54 -!- svanstaa [~svanstaa@194.169.217.94] has quit [Client Quit] 11:56 -!- svanstaa [~svanstaa@194.169.217.67] has joined #bitcoin-core-dev 11:59 -!- flag [~flag@81.56.89.175] has joined #bitcoin-core-dev 12:03 -!- svanstaa [~svanstaa@194.169.217.67] has quit [Quit: Connection closed] 12:20 -!- ___nick___ [~quassel@host86-164-104-11.range86-164.btcentralplus.com] has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.] 12:22 -!- ___nick___ [~quassel@host86-164-104-11.range86-164.btcentralplus.com] has joined #bitcoin-core-dev 12:25 -!- ___nick___ [~quassel@host86-164-104-11.range86-164.btcentralplus.com] has quit [Client Quit] 12:27 -!- ___nick___ [~quassel@host86-164-104-11.range86-164.btcentralplus.com] has joined #bitcoin-core-dev 12:53 < jamesob> There's something funky going on with logging. I'm not seeing `LogPrint(BCLog::BLOCKSTORE, ...)` messages appear even when running with `-debug=blockstore`. 12:53 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!] 13:04 -!- ___nick___ [~quassel@host86-164-104-11.range86-164.btcentralplus.com] has quit [Ping timeout: 256 seconds] 13:05 < achow101> jamesob: are you sure those lines are reached? 13:10 -!- vysn [~vysn@user/vysn] has joined #bitcoin-core-dev 13:28 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev 13:32 < jamesob> achow101: yeah; I changed them to LogPrintf and they started printing 13:33 < jamesob> will verify... 13:36 < achow101> ah, the category is apparently blockstorage, not blockstore 13:37 < achow101> even though it's BCLog::BLOCKSTORE 13:39 < jamesob> achow101: good spot! 14:32 < jonatack> achow101: i've been wanting to align those two for a good while now but doubted anyone would agree to making the change :p 14:36 < jamesob> we should at least error if someone passes a faulty -debug=x option 14:38 < jonatack> we do 14:39 < jonatack> well, we warn 14:43 -!- kevkevin [~kevkevin@2600:1700:b30:47c0:45e3:f1aa:c091:7a78] has quit [Remote host closed the connection] 14:44 -!- realies [~realies@user/realies] has joined #bitcoin-core-dev 14:44 -!- Zenton [~user@user/zenton] has joined #bitcoin-core-dev 14:58 < jb55> achow101: haven't seen it since. maybe if there was a way I could simulate the same mempool state as that crazy day. 14:59 < achow101> jb55: no debug.log? 15:23 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Quit: Leaving...] 15:24 -!- kevkevin [~kevkevin@2600:1700:b30:47c0:716f:c04:1348:3558] has joined #bitcoin-core-dev 15:28 -!- kevkevin [~kevkevin@2600:1700:b30:47c0:716f:c04:1348:3558] has quit [Ping timeout: 240 seconds] 15:55 -!- aielima [~aielima@user/aielima] has quit [Quit: Ciao] 16:20 -!- bugs_ [~bugs@user/bugs/x-5128603] has quit [Quit: Leaving] 16:25 < jonatack> jamesob: done 16:26 < jonatack> jamesob: https://github.com/bitcoin/bitcoin/pull/27632 16:35 -!- PaperSword [~Thunderbi@securemail.qrsnap.io] has joined #bitcoin-core-dev 16:40 -!- stevenwy37 [~stevenwy3@116.206.100.4] has joined #bitcoin-core-dev 16:45 -!- stevenwy37 [~stevenwy3@116.206.100.4] has quit [Ping timeout: 264 seconds] 17:05 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev 17:20 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection] 17:20 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev 17:32 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: WeeChat 3.8] 17:33 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Remote host closed the connection] 17:34 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 17:35 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev 17:36 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev 17:39 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 265 seconds] 18:07 -!- jarthur [~jarthur@user/jarthur] has quit [Quit: jarthur] 18:11 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 18:11 -!- preimage [~halosghos@user/halosghost] has quit [Quit: WeeChat 3.8] 18:15 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 264 seconds] 18:20 -!- vysn [~vysn@user/vysn] has quit [Remote host closed the connection] 18:46 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 18:50 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 240 seconds] 19:19 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 19:19 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Remote host closed the connection] 19:35 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 19:40 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 265 seconds] 20:08 -!- stevenwy37 [~stevenwy3@116.206.100.4] has joined #bitcoin-core-dev 20:08 -!- stevenwy37 [~stevenwy3@116.206.100.4] has quit [Remote host closed the connection] 20:08 -!- stevenwy37 [~stevenwy3@116.206.100.4] has joined #bitcoin-core-dev 20:11 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev 20:17 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 265 seconds] 20:20 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 20:30 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 264 seconds] 20:42 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 20:47 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 265 seconds] 20:56 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev 20:59 -!- puchka [~puchka@185.203.122.26] has quit [Ping timeout: 246 seconds] 21:01 -!- cmirror [~cmirror@4.53.92.114] has quit [Remote host closed the connection] 21:01 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 240 seconds] 21:01 -!- cmirror [~cmirror@4.53.92.114] has joined #bitcoin-core-dev 21:06 -!- puchka [~puchka@185.203.122.26] has joined #bitcoin-core-dev 21:10 -!- puchka [~puchka@185.203.122.26] has quit [Ping timeout: 240 seconds] 21:13 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 21:17 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 265 seconds] 21:25 -!- kevkevin [~kevkevin@2600:1700:b30:47c0:716f:c04:1348:3558] has joined #bitcoin-core-dev 21:29 -!- kevkevin [~kevkevin@2600:1700:b30:47c0:716f:c04:1348:3558] has quit [Ping timeout: 256 seconds] 21:39 -!- b_101 [~robert@185.242.5.35] has quit [Ping timeout: 240 seconds] 21:41 -!- mxz- [~mxz@user/mxz] has quit [Quit: cya] 21:42 -!- mxz [~mxz@user/mxz] has joined #bitcoin-core-dev 22:15 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev 22:19 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 240 seconds] 22:22 -!- robobub [uid248673@id-248673.uxbridge.irccloud.com] has quit [Ping timeout: 240 seconds] 22:24 -!- robobub [uid248673@id-248673.uxbridge.irccloud.com] has joined #bitcoin-core-dev 22:43 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 22:47 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 240 seconds] 22:55 -!- puchka [~puchka@185.203.122.32] has joined #bitcoin-core-dev 23:05 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 23:10 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 265 seconds] 23:11 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 23:13 -!- b_101 [~robert@185.242.5.35] has joined #bitcoin-core-dev 23:15 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 240 seconds] 23:17 -!- b_101 [~robert@185.242.5.35] has quit [Ping timeout: 240 seconds] 23:27 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 23:33 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 265 seconds] 23:34 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 23:38 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 246 seconds] 23:40 -!- aielima [~aielima@user/aielima] has joined #bitcoin-core-dev 23:44 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has joined #bitcoin-core-dev 23:49 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:3594:8a78:c69a:3bd4] has quit [Ping timeout: 264 seconds] --- Log closed Fri May 12 00:00:59 2023