--- Log opened Thu Sep 28 00:00:35 2023
00:00 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has joined #bitcoin-core-dev
00:06 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has quit [Ping timeout: 272 seconds]
00:15 -!- jarthur [~jarthur@user/jarthur] has quit [Quit: jarthur]
00:33 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has joined #bitcoin-core-dev
00:35 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
00:40 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 272 seconds]
00:53 -!- vasild [~vd@user/vasild] has quit [Remote host closed the connection]
00:55 -!- PaperSword [~Thunderbi@securemail.qrsnap.io] has quit [Quit: PaperSword]
01:10 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has joined #bitcoin-core-dev
01:15 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has quit [Ping timeout: 272 seconds]
01:21 -!- Earnestly [~earnest@user/earnestly] has joined #bitcoin-core-dev
01:26 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-dev
01:30 -!- _aj__ [aj@azure.erisian.com.au] has joined #bitcoin-core-dev
01:30 -!- _aj__ [aj@user/aj/x-5857768] has changed host
01:30 -!- _aj_ [aj@user/aj/x-5857768] has quit [Killed (NickServ (GHOST command used by _aj__))]
01:30 -!- _aj__ is now known as _aj_
01:40 -!- vasild [~vd@user/vasild] has quit [Ping timeout: 252 seconds]
01:45 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has joined #bitcoin-core-dev
01:50 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has quit [Ping timeout: 260 seconds]
02:18 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has joined #bitcoin-core-dev
02:23 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has quit [Ping timeout: 272 seconds]
02:28 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-dev
02:31 -!- vasild [~vd@user/vasild] has quit [Remote host closed the connection]
02:33 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-dev
02:38 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
02:39 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has left #bitcoin-core-dev [Closing Window]
02:42 -!- vasild [~vd@user/vasild] has quit [Remote host closed the connection]
02:43 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-dev
02:44 < darosior> Does anyone have an idea how could an in-memory CDbWrapper leak memory? Running it in a fuzzer, it seems the memory is never dropped. For instance the memory usage of this trivial repro grows from a couple MBs to >1GB of memory after only 6 minutes: https://paste.ec/paste/EVPsg0ju#r1xd5pqzk74er0m2bgY73oev6+t-LHPMlp4pbxIQsK5 
02:52 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has joined #bitcoin-core-dev
02:56 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has quit [Ping timeout: 240 seconds]
03:01 -!- vasild [~vd@user/vasild] has quit [Remote host closed the connection]
03:01 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-dev
03:04 -!- qubenix [~qubenix@user/qubenix] has quit [Quit: quit]
03:05 -!- Earnestly [~earnest@user/earnestly] has quit [Read error: Connection reset by peer]
03:06 -!- Earnestly [~earnest@user/earnestly] has joined #bitcoin-core-dev
03:06 -!- qubenix [~qubenix@user/qubenix] has joined #bitcoin-core-dev
03:09 -!- qubenix [~qubenix@user/qubenix] has quit [Client Quit]
03:12 -!- vasild [~vd@user/vasild] has quit [Remote host closed the connection]
03:12 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-dev
03:17 -!- qubenix [~qubenix@user/qubenix] has joined #bitcoin-core-dev
03:17 -!- vyHamii [~vyHamii@113.160.73.210] has joined #bitcoin-core-dev
03:23 -!- lightningbot [lightningb@azure.erisian.com.au] has quit [Killed (NickServ (GHOST command used by lightningbot`))]
03:25 -!- lightningbot [lightningb@azure.erisian.com.au] has joined #bitcoin-core-dev
03:25 -!- abubakarsadiq [uid602234@id-602234.hampstead.irccloud.com] has joined #bitcoin-core-dev
03:28 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has joined #bitcoin-core-dev
03:31 -!- vyHamii [~vyHamii@113.160.73.210] has quit [Quit: Leaving]
03:33 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has quit [Ping timeout: 272 seconds]
03:53 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
03:58 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 255 seconds]
04:25 -!- furszy [~furszy@user/furszy] has changed host
04:26 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Remote host closed the connection]
04:36 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has joined #bitcoin-core-dev
04:37 -!- Guest6 [~Guest6@2607:fb90:eeb1:a32:a8d4:a96d:eabe:50ef] has joined #bitcoin-core-dev
04:39 -!- DarrylTheFiish [~DarrylThe@user/DarrylTheFish] has joined #bitcoin-core-dev
04:40 -!- Guest6 [~Guest6@2607:fb90:eeb1:a32:a8d4:a96d:eabe:50ef] has quit [Client Quit]
04:42 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has quit [Ping timeout: 248 seconds]
04:50 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 255 seconds]
04:50 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
04:57 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
05:07 -!- josibake____ [sid509132@helmsley.irccloud.com] has quit []
05:20 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has joined #bitcoin-core-dev
05:23 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 255 seconds]
05:26 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
05:35 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
05:44 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has joined #bitcoin-core-dev
05:46 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has left #bitcoin-core-dev []
06:14 -!- Nekorand [~Random@cm-188-171-200-176.telecable.es] has joined #bitcoin-core-dev
06:30 -!- Nekorand [~Random@cm-188-171-200-176.telecable.es] has quit [Quit: Leaving]
07:00 < achow101> #startmeeting
07:00 < pinheadmz> hi
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 TheCharlatan vasild
07:00 < brunoerg> hi
07:00 < instagibbs> hi
07:00 < darosior> hi
07:00 < josie> hi
07:00 < glozow> hi
07:00 < dergoegge> hi
07:00 < achow101> There are no preproposed meeting topics this week. Any last minute ones to add
07:00 < stickies-v> hi
07:01 < gleb> hi
07:01 < lightlike> hi
07:01 < ajonas> hi
07:01 < achow101> #topic package relay updates (glozow)
07:01 < hebasto> hi
07:02 < glozow> #28450 was merged (yay) so #26711 is now ready for review!
07:02 <@gribble> https://github.com/bitcoin/bitcoin/issues/28450 | Add package evaluation fuzzer by instagibbs · Pull Request #28450 · bitcoin/bitcoin · GitHub
07:02 <@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:02 < glozow> As discussed last week, I've put all of the p2p PRs in draft to focus review attention on the validation stuff for now. I'll continue working on them.
07:02 < instagibbs> achow101 proposed topic: voting/signaling for priority projects?
07:03 < glozow> instagibbs and I had a conversation yesterday about re-opening #27609 now that we have fuzzing / it feels a bit safer
07:03 <@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:03 < glozow> unsure if that's something people want
07:03 < _aj_> do it
07:03 < instagibbs> there's at least one project which would use submitpackage, in a limited way, to avoid a song and dance
07:03 < darosior> Yeah
07:04 < fjahr> hi
07:04 < instagibbs> ldk-node, which does a song and dance, then hopes a miner with a large mempool sees it, essentially 
07:04 < glozow> I remember speaking about it with sdaftuar, mostly concerned about encouraging direct-submits to miners. Not really what we'd want but maybe the lesser of evils for now?
07:04 < instagibbs> They're doing... interesting stuff without our help, so I'm less and less persuaded myself that we shouldn't open it up
07:05 < sdaftuar> hi
07:05 < glozow> hi!
07:05 < instagibbs> !!! welcome
07:05 <@gribble> Error: "!!" is not a valid command.
07:05 < lightningbot> instagibbs: Error: "!" is not a valid command.
07:05 < dergoegge> good bots
07:05 < glozow> lol
07:05 < josie> instagibbs has angered all the bots
07:05 < achow101> perhaps reopen the pr and have the discussion there?
07:05 < sdaftuar> sorry i'm not up to speed at all on where the package relay/package acceptance logic is these days. i think one of our concerns was whether there were dos vectors in submitpackage that we didn't want to leave open for exploitation?
07:06 < sdaftuar> if those have been closed off (enough), then i think i would not be opposed
07:06 < glozow> We've fixed a lot of bugs in the last month or so (yay) and it would be through rpc so hopefully trusted clients only. can have loud warnings in release notes
07:07 < sdaftuar> cool, sounds good
07:07 < instagibbs> I'm working on more fuzzing stuff, will just have glozow pick up what she wants to get 26711 pristine
07:07 < glozow> Agree with moving discussion to PR. We have a really small window before feature freeze (assuming people want this for 26) so please leave your comments asap if y'all have opinions
07:08 < glozow> achow101: we can move on, thanks
07:08 < b10c> hi
07:08 < achow101> #topic BIP 324 updates (sipa)
07:09 < achow101> perhaps sipa is not here
07:09 < dergoegge> i think we're just waiting for review on the integration PR
07:09 < _aj_> there's the breaking protocol change
07:09 < achow101> #28331 is the main pr, but I think #28525 is probably next for priority?
07:09 <@gribble> https://github.com/bitcoin/bitcoin/issues/28331 | BIP324 integration by sipa · Pull Request #28331 · bitcoin/bitcoin · GitHub
07:09 <@gribble> https://github.com/bitcoin/bitcoin/issues/28525 | net: Drop v2 garbage authentication packet by real-or-random · Pull Request #28525 · bitcoin/bitcoin · GitHub
07:09 < achow101> since it's a breaking protocol change
07:09 < dergoegge> ah right
07:10 < _aj_> yeah; it seems just about RFM though
07:10 < achow101> there's the corresponding bips pr for that: https://github.com/bitcoin/bips/pull/1498
07:10 < achow101> it looks ready, but I'd prefer to wait for the bip change to go in first
07:10 < _aj_> +1
07:10 < achow101> cc luke-jr
07:11 < instagibbs> I don't think it's required to miss an entire release cycle... but give it a shot
07:11 < sipa> hi
07:12 < sipa> not much to say in addition to what was mentioned
07:12 < achow101> #topic assumeutxo updates (jamesob)
07:12 < _aj_> the bip pr could probably do with an explicit "merge me" from an author
07:13 < instagibbs> _aj_ +1
07:13 < sipa> _aj_: will do
07:14 < achow101> #27596 looks like it's probably rfm?
07:14 < fjahr> I guess James is not here. #27596 has received more review.
07:14 <@gribble> https://github.com/bitcoin/bitcoin/issues/27596 | assumeutxo (2) by jamesob · Pull Request #27596 · bitcoin/bitcoin · GitHub
07:14 <@gribble> https://github.com/bitcoin/bitcoin/issues/27596 | assumeutxo (2) by jamesob · Pull Request #27596 · bitcoin/bitcoin · GitHub
07:14 < fjahr> The chain params question was opened as a follow-up by sjors
07:14 < fjahr> #28516
07:14 <@gribble> https://github.com/bitcoin/bitcoin/issues/28516 | validation: assumeutxo params for testnet and signet by Sjors · Pull Request #28516 · bitcoin/bitcoin · GitHub
07:15 < fjahr> So might be rfm
07:16 < achow101> #topic libbitcoinkernel updates (TheCharlatan)
07:16 < achow101> TheCharlatan informed me that he won't be able to make the meeting this week. he wants #28051 to be the next priority
07:16 <@gribble> https://github.com/bitcoin/bitcoin/issues/28051 | Get rid of shutdown.cpp/shutdown.h, use SignalInterrupt directly by ryanofsky · Pull Request #28051 · bitcoin/bitcoin · GitHub
07:17 < achow101> #topic Ad-hoc high priority for review
07:17 < achow101> Anything to add or remove from https://github.com/orgs/bitcoin/projects/1/views/4 ?
07:18 < josie> #27827 is closed in favor of a tracking issue 
07:18 < achow101> josie: removing #27827 since it's closed, and silent payments seems to have concept acks
07:18 <@gribble> https://github.com/bitcoin/bitcoin/issues/27827 | Silent Payments: send and receive by josibake · Pull Request #27827 · bitcoin/bitcoin · GitHub
07:18 <@gribble> https://github.com/bitcoin/bitcoin/issues/27827 | Silent Payments: send and receive by josibake · Pull Request #27827 · bitcoin/bitcoin · GitHub
07:18 < josie> achow101: jinx
07:19 < josie> would be really nice to get #25273 in
07:19 <@gribble> https://github.com/bitcoin/bitcoin/issues/25273 | wallet: Pass through transaction locktime and preset input sequences and scripts to CreateTransaction by achow101 · Pull Request #25273 · bitcoin/bitcoin · GitHub
07:20 < josie> I need it for the silent payments sending PR, will be reviewing it over the next few days
07:21 < achow101> #topic 26.0 feature freeze
07:22 < achow101> According to the release schedule for 26.0 (#27758), feature freeze is on this sunday
07:22 <@gribble> https://github.com/bitcoin/bitcoin/issues/27758 | Release schedule for 26.0 · Issue #27758 · bitcoin/bitcoin · GitHub
07:22 < achow101> but with 2 priority projects so close to the finish line, I think we could move it back another week so we can have those for this release?
07:22 < glozow> concept ACK
07:22 < achow101> (not that priority projects are intended to go in for the next release, but it'd be cool to have these in)
07:22 < lightlike> makes sense to me
07:22 < fjahr> +1
07:23 < hebasto> agree
07:23 < sipa> that (obviously) sounds reasonable to me
07:23 < darosior> Sounds good to me.
07:23 < dergoegge> +1
07:23 < josie> +1
07:24 < _aj_> *2
07:24 < achow101> #topic voting/signaling for priority projects
07:25 < achow101> we discussed this at coredev and for the next round of priority projects we're going to try to do the voting online
07:25 < darosior> I need to bounce but if we are doing the prio projects thing, just letting people know i'll personally try to carve out some time to help package relay move forward. No promise though.
07:25 < darosior> (if that counts as a vote)
07:26 < _aj_> (have priority projects been successful in minimising how much unwanted rebasing those projects have had to do?)
07:26 < achow101> my thoughts were that after feature freeze, i'll open an issue to gather possible projects (seeded with the list from coredev). then a week later, we can vote by posting comments in an (new?) issue.
07:27 < instagibbs> _aj_ there was pretty good consensus on a strong "yes" there
07:27 < achow101> _aj_: the general sentiment was that they were successful
07:27 < stickies-v> _aj_: I have seen at least a few instances of PRs getting closed/drafted because of priority conflicts. Could probably be more though.
07:27 < achow101> voting would be open for a week. then we'd have our votes done by branching
07:28 < _aj_> achow101: there's https://github.com/bitcoin-core/bitcoin-devwiki/wiki/Priorities ; if we do it via issues instead, probably should kill that page
07:28 < josie> achow101: sounds good, but I do think its important to limit voting to people who are actively contributing/reviewing in the project. this isnt a vote of "what would you like to see in bitcoin core" and more signaling "i will prioritise working on and reviewing x"
07:29 < achow101> there's a bit of an open question of whether it should be anonymous or not. doing it in an issue would be inherently public, unless everyone pgp encrypts their votes or something like that
07:29 < _aj_> achow101: if voting == "i'm aiming to review", then anonymity doesn't seem needed
07:30 < fanquake> who are they encrypting to?
07:30 < instagibbs> "I want to not make them rebase" + "I will review"
07:30 < fanquake> the maintainer group?
07:30 < achow101> fanquake: the maintainers? or perhaps just me?
07:30 < stickies-v> +1 on limiting the vote. i don't mind doing it in public
07:31 < stickies-v> also liked josie's idea of having two votes: one being "what should be priority" and another being "what will i actively contribute to" because the two don't always have to overlap because of e.g. skillsets, experience, ...
07:31 < achow101> I think the only votes that will be counted are from those that are in the github org(s)
07:31 < stickies-v> but that may overly complicate the system
07:31 < _aj_> imo, it's not really a "vote", it's "which projects have the most reviewer interest, so are likely to make the most progress, and are least likely to spend a long time unmerged, and hence will only cause minimal rebasing in conflicting PRs"
07:32 < josie> if votes will only be counted from within the github org, then i dont see the point of anonymous? 
07:32 < sipa> i don't think anonymity is necessary
07:32 < instagibbs> anon seems like overhead for no purpose
07:32 < josie> _aj_: +1
07:32 < fanquake> isn’t the whole reason we skipped the vote before because people complained about posting their votes publicly last time
07:32 < fanquake> or am I misremembering
07:33 < _aj_> i thought it was "sounds good, let's just do it" ?
07:33 < achow101> fanquake: no, it was that some people were anon and others were not. the complain was that everyone should have the option for anon, or no one should
07:33 < sipa> really the priority projects help break the cyclic dependency in decisions of the form "i'd like to work/help on X, but only if sufficient other people think the same"
07:33 < glozow> yeah I think we didn't vote last week because people said it was unfair to the people who weren't there, i.e. because no anon
07:33 < _aj_> oh, before = 6 months ago, or last week?
07:34 < fjahr> fanquake: i think it would have been possible to vote for a week but nobody did 6 months ago
07:34 < achow101> I think we can just try it non-anon on github this time, and if people complain or there are less votes this time, we can try something else next time?
07:35 < glozow> ACK
07:35 < instagibbs> whatever is simplest, thanks
07:35 < josie> worth making the distinction: voting in person requires doxxing meatspace identity, voting on github does not. so in that sense, yeah voting on github does allow people to vote
07:35 < instagibbs> keep forward momentum folks
07:35 < josie> ACK
07:35 < stickies-v> +1 keep it simple, github works
07:35 < sipa> yeah
07:36 < lightlike> should we have a phase for assembling / completing the list of candidates (before the voting starts)?
07:36 < achow101> lightlike: yes "i'll open an issue to gather possible projects (seeded with the list from coredev)."
07:37 < lightlike> ah thx, missed this
07:37 < stickies-v> can't we just do that here? if no one here brings up a certain topic, it's probably not gonna make it into the top anyway?
07:37 < _aj_> https://bitcoin.jonasschnelli.ch/ircmeetings/logs/bitcoin-core-dev/2023/bitcoin-core-dev.2023-05-04-19.00.log.html -- was the discussion last time around fwiw
07:37 < achow101> re the 2 votes idea, I'm not sure that's useful?
07:38 < _aj_> stickies-v: not everyone is available at this particular hour
07:38 < fjahr> last time we each had 3...
07:38 < achow101> sorry, meant the two different votes thing of "priority" and "review".
07:38 < achow101> for deciding the actual priority, I think having each person vote for 3 is still good
07:39 < sipa> the consensus at coredev was that the concept of priority projects was a success, so we don't *need* to change anything
07:39 < fjahr> I think nobody will check later if people actually reviewed so I think it doesn't matter
07:39 < sipa> except of course the fact that the voting was not done in person
07:39 < josie> sipa: +1
07:39 < glozow> I like the 2 votes idea, but agree with not hindering the process by talking about potential improvements
07:39 < instagibbs> signaling you'll review doesn't procedurally change anything, just nice 
07:40 < instagibbs> so stick with what worked
07:40 < achow101> any other topics to discuss?
07:41 < fjahr> so what are the next steps?
07:41 < _aj_> achow101 will open an issue
07:41 < fjahr> And there will be one week to add topics?
07:41 < sipa> an issue, or an org discussion?
07:41 < achow101> fjahr: after feature freeze (in one week): open an issue for projects gathering. one week after that: voting in another issue, open for 1 week
07:42 < fjahr> ok, thanks
07:43 < achow101> #endmeeting
07:45 < josie> achow101: not sure if you missed (or maybe you disagree?), but id like this on ad-hoc/high prio: https://github.com/bitcoin/bitcoin/pull/25273
07:46 -!- Murch[m] [~murchmatr@2620:6e:a000:ce11::1b] has quit [Quit: Reconnecting]
07:46 -!- Murch[m] [~murch@2620:6e:a000:ce11::1b] has joined #bitcoin-core-dev
07:48 -!- Murch[m] [~murch@2620:6e:a000:ce11::1b] has quit [Client Quit]
07:48 -!- Murch[m] [~murch@2620:6e:a000:ce11::1b] has joined #bitcoin-core-dev
07:48 < achow101> josie: missed that, adding
07:48 < josie> ty!
07:50 -!- Murch[m] [~murch@user/murch] has changed host
07:50 < Murch[m]> New bridge, forgot to auth. Can y’all read me now?
07:51 < sdaftuar> yes murch!
07:51 < Murch[m]> Thanks
07:55 < Murch[m]> I wanted to say that I don’t think having two separate votes for what projects you like vs will review adds to the process. It’ll put an onus on us to find a scoring mechanism for the two different votes to end up having a single order and just complicates things. I’d prefer that people just do their best to support the projects that they would like to see prioritized and vote for only that
08:06 -!- jarthur [~jarthur@user/jarthur] has joined #bitcoin-core-dev
08:08 -!- achow101 [~achow101@user/achow101] has quit [Remote host closed the connection]
08:08 -!- achow101 [~achow101@user/achow101] has joined #bitcoin-core-dev
08:37 -!- bugs_ [~bugs@user/bugs/x-5128603] has joined #bitcoin-core-dev
08:52 -!- jespada [~jespada@cpc121308-nmal25-2-0-cust15.19-2.cable.virginm.net] has quit [Read error: Connection reset by peer]
08:53 -!- jespada [~jespada@cpc121308-nmal25-2-0-cust15.19-2.cable.virginm.net] has joined #bitcoin-core-dev
09:25 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Remote host closed the connection]
09:26 -!- Chris_Stewart_5 [~Chris_Ste@96.44.189.105] has quit [Ping timeout: 240 seconds]
09:28 -!- Chris_Stewart_5 [~Chris_Ste@37.19.200.133] has joined #bitcoin-core-dev
09:41 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
09:41 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Read error: Connection reset by peer]
09:50 -!- nanotube [~nanotube@user/nanotube] has joined #bitcoin-core-dev
09:52 -!- preimage [~halosghos@user/halosghost] has joined #bitcoin-core-dev
10:09 -!- test__ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
10:12 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 255 seconds]
10:12 -!- test_ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 255 seconds]
10:12 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
10:17 -!- preimage [~halosghos@user/halosghost] has quit [Quit: WeeChat 4.0.4]
10:24 < stickies-v> Murch[m]: I don't think it has to complicate things too much, besides adding an additional round. The "what should be priority" would be entirely informational, to help us inform perceived importance. The actual priorities should then only be based on the second "what will i actively contribute to" vote, because if not enough people are willing/able to work on it then there's no point making it prio
10:24 < Murch[m]> Sure, that would be a way to solve it
10:42 -!- lbia [~lbia@user/lbia] has quit [Ping timeout: 240 seconds]
10:43 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has quit [Remote host closed the connection]
10:43 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has joined #bitcoin-core-dev
10:44 -!- lbia [~lbia@user/lbia] has joined #bitcoin-core-dev
10:48 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has quit [Ping timeout: 264 seconds]
10:52 -!- pablomartin [~pablomart@193.160.246.51] has joined #bitcoin-core-dev
10:54 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has joined #bitcoin-core-dev
10:55 -!- Guest78 [~Guest78@2a01:a8:201:2::183] has joined #bitcoin-core-dev
10:58 -!- Guest78 [~Guest78@2a01:a8:201:2::183] has quit [Client Quit]
10:59 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has quit [Ping timeout: 272 seconds]
11:01 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev
11:19 -!- dermoth [~dermoth@user/dermoth] has quit [Ping timeout: 240 seconds]
11:20 -!- dermoth [~dermoth@user/dermoth] has joined #bitcoin-core-dev
11:28 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has joined #bitcoin-core-dev
11:33 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has quit [Ping timeout: 272 seconds]
11:34 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has joined #bitcoin-core-dev
11:39 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has quit [Ping timeout: 240 seconds]
11:39 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
11:40 -!- DarrylTheFiish [~DarrylThe@user/DarrylTheFish] has quit [Ping timeout: 272 seconds]
11:44 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 255 seconds]
12:00 < kanzure> are there written summaries available oof the recent IRL meets?
12:02 < sipa> kanzure: my understanding is that there will be
12:10 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has joined #bitcoin-core-dev
12:14 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has joined #bitcoin-core-dev
12:14 < ajonas> kanzure: aiming to have them published tomorrow
12:16 < kanzure> thank you.
12:17 < kanzure> sorry i couldn't be there to do it :)
12:18 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has quit [Remote host closed the connection]
12:20 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has joined #bitcoin-core-dev
12:29 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!]
12:37 -!- guest4 [~guest4@node-1w7jr9qsj12kzn5b2wpawug7y.ipv6.telus.net] has joined #bitcoin-core-dev
12:38 -!- guest4 [~guest4@node-1w7jr9qsj12kzn5b2wpawug7y.ipv6.telus.net] has quit [Client Quit]
12:39 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has quit [Remote host closed the connection]
12:41 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has joined #bitcoin-core-dev
12:41 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has quit [Remote host closed the connection]
12:43 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has joined #bitcoin-core-dev
12:53 -!- preimage [~halosghos@user/halosghost] has joined #bitcoin-core-dev
12:57 -!- dermoth [~dermoth@user/dermoth] has quit [Ping timeout: 255 seconds]
13:13 -!- guest4 [~guest4@node-1w7jr9qsj12kzn5b2wpawug7y.ipv6.telus.net] has joined #bitcoin-core-dev
13:14 -!- preimage [~halosghos@user/halosghost] has quit [Ping timeout: 260 seconds]
13:16 -!- preimage [~halosghos@user/halosghost] has joined #bitcoin-core-dev
13:17 -!- guest4 [~guest4@node-1w7jr9qsj12kzn5b2wpawug7y.ipv6.telus.net] has quit [Client Quit]
13:30 -!- DarrylTheFiish [~DarrylThe@user/DarrylTheFish] has joined #bitcoin-core-dev
13:33 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has quit [Ping timeout: 255 seconds]
14:19 -!- preimage [~halosghos@user/halosghost] has quit [Quit: WeeChat 4.0.4]
14:42 -!- DarrylTheFiish [~DarrylThe@user/DarrylTheFish] has quit [Read error: Connection reset by peer]
15:02 -!- bugs_ [~bugs@user/bugs/x-5128603] has quit [Quit: Leaving]
15:05 -!- darosior [~darosior@109.205.214.46] has quit [Ping timeout: 255 seconds]
15:11 -!- abubakarsadiq [uid602234@id-602234.hampstead.irccloud.com] has quit [Quit: Connection closed for inactivity]
15:13 -!- jarthur [~jarthur@user/jarthur] has quit [Quit: jarthur]
15:26 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:696d:4f81:cbea:259a] has quit [Remote host closed the connection]
15:27 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has joined #bitcoin-core-dev
15:31 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has quit [Ping timeout: 248 seconds]
15:37 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has joined #bitcoin-core-dev
15:38 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
15:42 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has quit [Ping timeout: 272 seconds]
15:46 -!- darosior [~darosior@109.205.214.46] has joined #bitcoin-core-dev
15:54 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has joined #bitcoin-core-dev
15:59 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has quit [Ping timeout: 240 seconds]
16:05 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
16:10 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 255 seconds]
16:10 -!- dermoth [~dermoth@user/dermoth] has joined #bitcoin-core-dev
16:23 -!- MatrixBot1234561 [~matrixbot@2001:bc8:1824:bc3::1] has quit [Ping timeout: 248 seconds]
16:24 -!- windsok [~windsok@rarepepe.cash] has quit [Ping timeout: 248 seconds]
16:24 -!- harding [quassel@newmail.dtrt.org] has quit [Ping timeout: 248 seconds]
16:24 -!- harding [quassel@newmail.dtrt.org] has joined #bitcoin-core-dev
16:25 -!- takinbo [~takinbo@user/takinbo] has quit [Ping timeout: 248 seconds]
16:25 -!- takinbo [~takinbo@user/takinbo] has joined #bitcoin-core-dev
16:26 -!- windsok [~windsok@rarepepe.cash] has joined #bitcoin-core-dev
16:33 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has joined #bitcoin-core-dev
16:37 -!- MatrixBot1234561 [~matrixbot@2001:bc8:1824:bc3::1] has joined #bitcoin-core-dev
16:38 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has quit [Ping timeout: 240 seconds]
17:02 -!- Earnestly [~earnest@user/earnestly] has quit [Ping timeout: 255 seconds]
17:11 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has joined #bitcoin-core-dev
17:18 -!- cotsuka [~cotsuka@user/cotsuka] has quit [Remote host closed the connection]
17:19 -!- cotsuka [~cotsuka@user/cotsuka] has joined #bitcoin-core-dev
17:21 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has quit [Ping timeout: 264 seconds]
17:29 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has joined #bitcoin-core-dev
17:38 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has quit [Ping timeout: 272 seconds]
17:55 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has joined #bitcoin-core-dev
18:00 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has quit [Ping timeout: 240 seconds]
18:05 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has joined #bitcoin-core-dev
18:08 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
18:10 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has quit [Ping timeout: 272 seconds]
18:15 -!- vyHamii [~vyHamii@113.160.45.182] has joined #bitcoin-core-dev
18:18 -!- benwestgate [~BenWestga@2603-8080-74f0-5ac0-e5c3-9358-74b4-5c4e.res6.spectrum.com] has quit [Quit: Leaving.]
18:35 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has joined #bitcoin-core-dev
18:39 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has quit [Ping timeout: 240 seconds]
18:40 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
18:45 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 260 seconds]
18:47 -!- robobub [uid248673@id-248673.uxbridge.irccloud.com] has joined #bitcoin-core-dev
18:49 -!- benwestgate [~BenWestga@108.79.33.187] has joined #bitcoin-core-dev
18:56 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has joined #bitcoin-core-dev
19:04 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has quit [Ping timeout: 240 seconds]
19:18 -!- pablomartin [~pablomart@193.160.246.51] has quit [Ping timeout: 272 seconds]
19:18 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has joined #bitcoin-core-dev
19:25 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has quit [Ping timeout: 264 seconds]
19:27 -!- realies [~realies@user/realies] has quit [Quit: Ping timeout (120 seconds)]
19:27 -!- realies [~realies@user/realies] has joined #bitcoin-core-dev
19:28 -!- pablomartin [~pablomart@193.160.246.54] has joined #bitcoin-core-dev
19:29 -!- bob_x1 [~bob_x@user/bob-x1/x-8934932] has quit [Remote host closed the connection]
19:30 -!- bob_x1 [~bob_x@user/bob-x1/x-8934932] has joined #bitcoin-core-dev
19:30 -!- benwestgate [~BenWestga@108.79.33.187] has quit [Quit: Leaving.]
19:31 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has joined #bitcoin-core-dev
19:42 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has quit [Ping timeout: 240 seconds]
19:44 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has joined #bitcoin-core-dev
19:48 -!- vyHamii [~vyHamii@113.160.45.182] has quit [Quit: Leaving]
19:49 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has quit [Ping timeout: 272 seconds]
20:07 -!- benwestgate [~BenWestga@035-146-116-090.res.spectrum.com] has joined #bitcoin-core-dev
20:30 -!- PaperSword [~Thunderbi@securemail.qrsnap.io] has joined #bitcoin-core-dev
20:32 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
20:33 -!- pablomartin [~pablomart@193.160.246.54] has quit [Ping timeout: 255 seconds]
20:40 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 255 seconds]
21:01 -!- cmirror [~cmirror@4.53.92.114] has quit [Remote host closed the connection]
21:01 -!- cmirror [~cmirror@4.53.92.114] has joined #bitcoin-core-dev
21:05 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has joined #bitcoin-core-dev
21:19 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has quit [Ping timeout: 272 seconds]
21:29 -!- conman [~con@180-150-21-3.b49615.mel.static.aussiebb.net] has joined #bitcoin-core-dev
21:35 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
21:42 -!- benwestgate [~BenWestga@035-146-116-090.res.spectrum.com] has quit [Quit: Leaving.]
21:45 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 272 seconds]
21:52 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
21:57 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 255 seconds]
22:04 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has joined #bitcoin-core-dev
22:09 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has quit [Ping timeout: 264 seconds]
22:15 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has joined #bitcoin-core-dev
22:19 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has quit [Ping timeout: 272 seconds]
23:08 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
23:11 -!- Earnestly [~earnest@user/earnestly] has joined #bitcoin-core-dev
23:13 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 240 seconds]
23:30 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has joined #bitcoin-core-dev
23:33 -!- TheRec [~toto@user/therec] has quit []
23:35 -!- brunoerg [~brunoerg@2804:14c:3bfb:8a:9d11:3637:bf59:503e] has quit [Ping timeout: 264 seconds]
23:35 -!- Guest6 [~Guest6@2607:fb90:eeb1:a32:a8d4:a96d:eabe:50ef] has joined #bitcoin-core-dev
23:41 -!- Guest6 [~Guest6@2607:fb90:eeb1:a32:a8d4:a96d:eabe:50ef] has quit [Quit: Client closed]
--- Log closed Fri Sep 29 00:00:36 2023