--- Log opened Thu Oct 31 00:00:36 2024
00:07 -!- sample [~sample@82-64-162-213.subs.proxad.net] has quit [Ping timeout: 246 seconds]
00:07 -!- aureleoules [~aureleoul@82-64-162-213.subs.proxad.net] has quit [Ping timeout: 248 seconds]
00:24 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
00:31 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 255 seconds]
00:32 -!- flag [~flag@81.56.89.175] has quit [Ping timeout: 252 seconds]
00:34 -!- flag [~flag@81.56.89.175] has joined #bitcoin-core-dev
00:35 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
00:41 -!- jonatack [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
00:55 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
01:08 -!- vysn [~vysn@user/vysn] has joined #bitcoin-core-dev
01:22 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has joined #bitcoin-core-dev
01:28 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 252 seconds]
01:35 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
01:38 -!- storopoli [~storopoli@user/storopoli] has joined #bitcoin-core-dev
01:38 < storopoli> join #rust-bitcoin
01:45 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 252 seconds]
01:52 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
01:54 -!- storopoli [~storopoli@user/storopoli] has quit [Remote host closed the connection]
02:08 -!- storopoli [~storopoli@user/storopoli] has joined #bitcoin-core-dev
02:08 -!- storopoli [~storopoli@user/storopoli] has quit [Excess Flood]
02:09 -!- storopoli [~storopoli@user/storopoli] has joined #bitcoin-core-dev
02:09 -!- storopoli [~storopoli@user/storopoli] has quit [Excess Flood]
02:09 -!- storopoli [~storopoli@user/storopoli] has joined #bitcoin-core-dev
02:09 -!- storopoli [~storopoli@user/storopoli] has quit [Excess Flood]
02:10 -!- storopoli [~storopoli@user/storopoli] has joined #bitcoin-core-dev
02:10 -!- storopoli [~storopoli@user/storopoli] has quit [Excess Flood]
02:10 -!- storopoli [~storopoli@user/storopoli] has joined #bitcoin-core-dev
02:10 -!- storopoli [~storopoli@user/storopoli] has quit [Excess Flood]
02:32 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has quit [Remote host closed the connection]
03:34 < laanwj> isn't it #bitcoin-rust
03:38 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 255 seconds]
03:53 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
04:11 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 244 seconds]
04:14 -!- jespada [~jespada@cpc121308-nmal25-2-0-cust15.19-2.cable.virginm.net] has quit [Quit: Textual IRC Client: www.textualapp.com]
04:23 -!- jespada [~jespada@cpc121308-nmal25-2-0-cust15.19-2.cable.virginm.net] has joined #bitcoin-core-dev
04:24 -!- szkl [uid110435@id-110435.uxbridge.irccloud.com] has joined #bitcoin-core-dev
05:09 < bitcoin-git> [bitcoin] dergoegge opened pull request #31189: Revert "Introduce `g_fuzzing` global for fuzzing checks" (master...2024-10-revert-31093) https://github.com/bitcoin/bitcoin/pull/31189
05:13 -!- SpellChecker [~SpellChec@user/SpellChecker] has quit [Remote host closed the connection]
05:15 -!- SpellChecker [~SpellChec@user/SpellChecker] has joined #bitcoin-core-dev
05:17 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has joined #bitcoin-core-dev
05:22 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has quit [Ping timeout: 252 seconds]
05:28 < bitcoin-git> [bitcoin] dergoegge closed pull request #31189: Revert "Introduce `g_fuzzing` global for fuzzing checks" (master...2024-10-revert-31093) https://github.com/bitcoin/bitcoin/pull/31189
05:46 < bitcoin-git> [bitcoin] glozow opened pull request #31190: TxDownloadManager followups (master...2024-10-30110-followups) https://github.com/bitcoin/bitcoin/pull/31190
05:57 -!- preimage [~halosghos@user/halosghost] has joined #bitcoin-core-dev
06:00 < bitcoin-git> [bitcoin] maflcko opened pull request #31191:  Make G_FUZZING constexpr, require -DBUILD_FOR_FUZZING=ON to fuzz (master...2410-fuzz-build) https://github.com/bitcoin/bitcoin/pull/31191
06:01 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
06:21 < bitcoin-git> [bitcoin] hebasto opened pull request #31192: depends, doc: List packages required to build `qt` package separately (master...241031-dep-doc) https://github.com/bitcoin/bitcoin/pull/31192
06:25 -!- jonatack [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
06:26 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
06:31 -!- l0rinc [~l0rinc@94.44.250.7] has joined #bitcoin-core-dev
06:31 -!- szkl [uid110435@id-110435.uxbridge.irccloud.com] has quit [Quit: Connection closed for inactivity]
06:39 -!- jon_atack [~jonatack@user/jonatack] has quit [Quit: WeeChat 4.4.2]
06:41 -!- marcofleon [~marcofleo@82.163.218.33] has joined #bitcoin-core-dev
06:42 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
06:51 < bitcoin-git> [bitcoin] fanquake pushed 5 commits to 27.x: https://github.com/bitcoin/bitcoin/compare/882e0d730d6d...bf03c458e994
06:51 < bitcoin-git> bitcoin/27.x c838ce5 Vasil Dimov: doc: use proper doxygen formatting for CTxMemPool::cs
06:51 < bitcoin-git> bitcoin/27.x 6c09325 fanquake: doc: finalise release notes for 27.2
06:51 < bitcoin-git> bitcoin/27.x f42fcf6 fanquake: build: bump version to v27.2 final
06:51 < bitcoin-git> [bitcoin] fanquake merged pull request #31154: [27.x] rc2 or final (27.x...27_2_maybe_rc2_or_final) https://github.com/bitcoin/bitcoin/pull/31154
06:51 -!- vysn [~vysn@user/vysn] has quit [Ping timeout: 252 seconds]
06:55 < bitcoin-git> [bitcoin] fanquake pushed tag v27.2: https://github.com/bitcoin/bitcoin/compare/v27.2
06:56 -!- John123 [~John123@45.250.237.9] has joined #bitcoin-core-dev
06:58 -!- andrewtoth [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #bitcoin-core-dev
06:59 -!- dzxzg [~dzxzg@user/dzxzg] has joined #bitcoin-core-dev
07:00 < achow101> #startmeeting
07:00 < hebasto> hi
07:00 < Murch[m]> hi
07:00 < ajonas> hi
07:00 < willcl-ark> Hi
07:00 < stickies-v> hi
07:00 < maxedw> hi
07:00 < Chris_Stewart_5> hi
07:00 < gleb> hi
07:00 < josie> hi 
07:01 < achow101> There are 2 preproposed meeting topics this week. Any last minute ones to add?
07:01 < achow101> #topic priority project reflections and working groups (ajonas)
07:01 < dzxzg> hi
07:01 -!- kevkevin_ [~kevkevin@209-242-39-30.rev.dls.net] has joined #bitcoin-core-dev
07:01 < ajonas> I promised last week I’d have a write up on priority projects and the evolution to working groups. Here it is: https://gist.github.com/adamjonas/aa5e7a46bff8111a1b41285a195c0937
07:01 < sipa> hi
07:02 < ajonas> I know jonatack had particular interest
07:02 < jonatack> hi
07:02 < cfields> hi
07:02 < kevkevin_> hi
07:02 < tdb3> hi
07:03 < pinheadmz> hi
07:03 < kevkevin_> hi
07:03 -!- kevkevin_ [~kevkevin@209-242-39-30.rev.dls.net] has quit [Client Quit]
07:03 < marcofleon> hi
07:03 < ajonas> As part of this, I've reached out to some working groups to report this week and that schedule is posted at https://github.com/bitcoin-core/bitcoin-devwiki/wiki/Working-Groups
07:03 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has joined #bitcoin-core-dev
07:03 < kevkevin> hi
07:03 < sipa> unsure if this is the place/time to bring this up, but i wonder if it would be useful to have a list of workgroup membership (which would be informal, anyone can join/leave), as a signal to indicate what is worth participating in?
07:04 < ajonas> sipa: maybe adding one's name to the wiki would be a place to keep track of that?
07:04 < achow101> in terms of logistics, I think we can try having 3 groups report each week. There are 11 working groups so far, so that would be each group reports ~once per month
07:04 < sipa> yeah, that's what i'd suggest
07:05 < ajonas> that would match something we tried in the first round -https://github.com/bitcoin-core/bitcoin-devwiki/wiki/Priorities
07:05 < josie> achow101: ack, also some groups might not have something every week 
07:05 < stickies-v> I don't think we should necessarily put a number of the # of groups reporting each week. If groups have something to share, I'd want to hear, no matter the count. If they don't, just skip. If groups have nothing to say for weeks on end, perhaps good to just check in on why that is?
07:05 < stickies-v> (of course we can revisit if meetings start to take too long but I don't expect that to be an issue)
07:06 < emzy> hi
07:06 < Murch[m]> The priority project reports were usually pretty quick, I don’t expect that it would be much longer with Working Groups
07:06 < josie> stickies-v: also fair, because i have some big updates for both groups im involved with this week haha
07:06 < achow101> stickies-v: I think there are too many groups for every group to report and that will take too long/dominate the meeting
07:06 < ajonas> this was an attempt to control the feast/famine nature of the IRC meetings
07:06 < Murch[m]> achow101: It’s not like there are a ton of other topics usually
07:07 < sipa> i think it's fine to go over all WGs every time, if they don't have anything, that's alright
07:07 < stickies-v> achow101: oh, yeah last week i suggested leads flag ahead of time to you that they have something to share to avoid that waiting problem
07:07 < josie> what about the suggestion where if a champion doesnt say hi at the beginning, just skip that group? seems like a low effort way to start?
07:07 < achow101> Murch[m]: but it's important to leave space for them
07:07 < sipa> if things take too long, we can revisit
07:07 < sdaftuar> hi
07:07 < josie> sdaftuar: *woops better say hi!*
07:07 < achow101> josie: that makes reporting optional, and I suspect that if it were optional, people would simply stop reporting
07:07 < josie> i mean, id prefer it be optional? 
07:08 < josie> if youre not motivated to join and report, why force you?
07:08 < stickies-v> +1 josie
07:08 < josie> i certainly wont stop joining and reporting :) 
07:08 < glozow> +1 to no restrictions on updates at the meetings. I don’t think we’re anywhere close to it taking too much time. on the contrary we should sync here more
07:08 < josie> glozow: +1 
07:08 < dergoegge> hi
07:09 < sipa> part of this i think is to make the IRC meeting more interesting, i think just more people giving updates about things is a good thing
07:09 < Murch[m]> glozow: +1
07:09 < josie> make irc noisy again 
07:09 < sipa> welcome to zombocom
07:09 < josie> lol
07:10 < sipa> this meta-topic is also not worth spending too much time on
07:10 < sipa> we can see what works
07:10 < jonatack> ajonas: thank you for the useful write-up. i have feedback, not sure when/where best to give it
07:10 < achow101> ok, hope everyone's ready
07:11 < achow101> I'll do the same as last week, if you don't say anything in one minute, i'm moving on
07:11 < achow101> #topic Erlay WG Update (sr_gi, naumenkogs, marcofleon)
07:11 < jonatack> ajonas: maybe i'll write to you directly
07:11 < ajonas> jonatack: you can leave comments on the doc unless you think it needs to be done here
07:11 < gleb> hi! it's me reporting on erlay this time
07:11 < cfields> better than reporting ltae :)
07:11 < gleb> Making progress on #30116, although for now it's mostly me and sergi, and bruno. There are pending comments the author intends to address asap. Nothing breaking.
07:11 <@gribble> https://github.com/bitcoin/bitcoin/issues/30116 | p2p: Fill reconciliation sets (Erlay) attempt 2 by sr-gi · Pull Request #30116 · bitcoin/bitcoin · GitHub
07:12 -!- marcofleon [~marcofleo@82.163.218.33] has quit [Quit: Client closed]
07:12 < gleb> Sergi continues his work on simulator. It's more efficient now. If Erlay coefficients is something you've been interested in — worth taking a look here
07:12 < gleb> https://github.com/sr-gi/hyperion/pull/25
07:12 < josie> gleb: hyperion is an awesome name
07:12 < sipa> also, let's revive this: we've had some discussions that led up to sergi's simulator in #minisketch on this IRC network
07:12 < sipa> i can share history
07:12 < gleb> I had some one-to-one calls with WG members to bootstrap review. Different shapes of it, but mostly answering design questions.
07:13 < gleb> People are back from travel next week and i hope we see more in-pr involvement by then :)
07:13 < gleb> Promising so far. Let me know if you're willing to join, we have a signal chat.
07:13 < sipa> gleb: i'd like to join
07:14 < gleb> That's it. I'll answer quick questions here, otherwise we can move on
07:14 < gleb> sipa: will add
07:14 < sipa> thanks!
07:14 < achow101> #topic Fuzzing WG Update (dergoegge)
07:14 < dergoegge> No real update today but i've created a irc channel: #bitcoin-core-fuzzing
07:15 < achow101> #topic Kernel WG Update (TheCharlatan)
07:15 < dergoegge> There is also a signal group, let me know if you want to join
07:15 < TheCharlatan> yes, same for the kernel
07:16 -!- marcofleon [~marcofleo@82.163.218.33] has joined #bitcoin-core-dev
07:16 < sipa> dergoegge: i'd like to join (i promise i will not be joining every WG)
07:16 < achow101> #topic Benchmarking WG Update (josibake, l0rinc)
07:16 -!- John123 [~John123@45.250.237.9] has quit [Quit: Client closed]
07:16 < josie> had a lot of great discussions at the recent core dev around benchmarking (transcripts should be posted at some point), and one of the key takeways was building better infrastructure is the best next step
07:16 < josie> so this past week and going into next week, thats going to be our focus. i started a high level design doc here (https://gist.github.com/josibake/185f913d8b6b1d8d5bdcc4abd2017784)
07:17 < josie> our initial approach is to fork our current CI infra and see how we can modify that for the "long running benchmark" usecase. ill be purchasing some dedicated boxes for that and willcl-ark is experimenting with some nix stuff to help us better manage the environments
07:17 < josie> if we end up finding things that are generally useful for our existing CI setup, we will port those over
07:17 < josie> the main focus for us will be reproducibility, auditability, and determinism. once we have that nailed down, we will actually start using this to benchmark some existing PRs in bitcoin core
07:17 < josie> theres also been a lot of work from l0rinc and andrewtoth on specific improvements for core, motivated by some of the ad hoc benching thats been going on, but i think its premature to talk about that until we have some more solid tooling and reporting in place
07:17 < josie> we also have a WG signal chat , let me know if youre interested (gonna be a bit hurt if this is the only one sipa doesnt ask to join)
07:18 < sipa> *crickets*
07:18 < josie> altho if youre only interested in following along with the work, we will be giving detailed updates here in IRC. if you join the WG we will try to get you to do work / review :) 
07:18 < josie> thats all for me 
07:18 < achow101> #topic Silent Payments WG Update (josibake, RubenSomsen)
07:18 < achow101> josie: go again
07:18 < josie> for silent payments, the focus is still the libsecp256k1 PR (bitcoin-core/secp256k1#1519)
07:18 <@gribble> https://github.com/bitcoin/bitcoin/issues/1519 | GUI: change language selection format to "language - country (locale name)" by Diapolo · Pull Request #1519 · bitcoin/bitcoin · GitHub
07:18 < josie> ill be working on updating that before the next meeting with some feedback we got at coredev. also a big thanks to nickler for helping thestack and i get ctime tests in place!
07:18 < josie> after that, ill be working on rebasing all of the bitcoin core PRs with help from novo__ (hes been working on a receiving PR with labels support for the bitcoin core wallet)
07:19 < gleb> bad gribble
07:19 < josie> on the bip side, we reviewed the silent payments psbt bip from andrewtoth and he recently posted that to the mailling list (https://gnusha.org/pi/bitcoindev/cde77c84-b576-4d66-aa80-efaf4e50468fn@googlegroups.com/T/#)
07:19 < josie> he also posted a bip proposal for DLEQ proofs, which are relevant for silent payments sending (https://gnusha.org/pi/bitcoindev/b0f40eab-42f3-4153-8083-b455fbd17e19n@googlegroups.com/T/#)
07:19 < josie> (i posted the gnusha links instead of the google group ones just for you vasild)
07:19 < josie> theres also a lot of interest outside of bitcoin core in implementing silent payments so we'll also be running a discord (ew) for other dev teams (bdk, ledger, rust-bitcoin, bitshala, electrs, etc) with the help of some folks from the bitcoin design community
07:19 < josie> this to help coordinate work across projects, if anyone is interested in joining / helping out
07:19 < cfields> josie: are you planning on using rented machines? Or looking to source self-hosted hardware/bandwidth?
07:19 < josie> same comment re: working group signal chat 
07:19 < pinheadmz> josie add me to the discord
07:20 < josie> cfields: hetzner boxes for now, since weve all been buying our own in that group the last month or so
07:20 < josie> pinheadmz: will do! 
07:20 < Murch[m]> Ugh discord. :(
07:20 -!- John123 [~John123@45.250.237.9] has joined #bitcoin-core-dev
07:20 < josie> cfields: if you have sauce on someone with self hosted stuff.. lemme know :) 
07:21 < josie> Murch[m]: i know :( but it seems to work well for the bdk/bitshala folks! 
07:21 < josie> the actual core related work we are discussing in signal tho 
07:21 < Murch[m]> Matrix 2.0 was announced just recently! ^^
07:21 < josie> discord is for external project coordination 
07:21 < josie> anywho, thats all from me
07:21 < achow101> #topic Cluster Mempool WG Update (sdaftuar)
07:21 < sdaftuar> hi
07:22 < sdaftuar> sipa, let me know if you want to join this working group too
07:22 < Murch[m]> haha
07:22 < sipa> sdaftuar: hmmm, tempting
07:22 < sipa> i shall join
07:22 < josie> sipa: wooooow 
07:22 < cfields> josie: I might, will dm.
07:22 < sdaftuar> anyway, #31122 is the PR to review
07:22 <@gribble> https://github.com/bitcoin/bitcoin/issues/31122 | cluster mempool: Implement changeset interface for mempool by sdaftuar · Pull Request #31122 · bitcoin/bitcoin · GitHub
07:23 < sdaftuar> i think it's making good progress
07:23 < sdaftuar> sipa continues to work on txgraph, so will let him update on that--
07:23 < sipa> txgraph will be ready for review in Two Weeks(tm)
07:23 < sdaftuar> sweet :)
07:24 < achow101> sdaftuar: do you think end of year for all of cluster mempool to be merged to still be doable?
07:24 < sipa> i have addtx/removetx working in a fuzz test, working on adddependency; no mining/eviction/staging/... yet
07:24 < sdaftuar> achow101: really depends on txgraph timing i think. i'm working in parallel on getting all the non-txgraph dependencies i can think of out of my big PR for review at the same time
07:25 < sdaftuar> but i'm workign towards that goal, if that's what you're asking
07:26 < achow101> #topic Stratum v2 WG Update (sjors)
07:26 < Murch[m]> I think Sjors may be traveling
07:27 < josie> +1 , no hi from him at the beginning 
07:27 < achow101> #topic MuSig2 WG Update (achow101)
07:27 < achow101> have yet to actually form a wg, but if anyone would like to join me, let me know
07:27 < achow101> otherwise, waiting for libsecp to do a release
07:28 < pinheadmz> re: Sv2 #30988 by vasild is the one to review, I need that as well for HTTP, will prob join the Sv2 wg just to stay in that loop
07:28 <@gribble> https://github.com/bitcoin/bitcoin/issues/30988 | Split CConnman by vasild · Pull Request #30988 · bitcoin/bitcoin · GitHub
07:28 < achow101> and I've updated the pr to fix the linking issue
07:28 < josie> achow101: interested! (also did a lot of review of the musig2 libsecp module)
07:29 < achow101> #topic Legacy Wallet Removal WG Update (achow101)
07:29 < achow101> also no group yet, but lmk if you want to join
07:29 < achow101> Waiting for review on #30328
07:29 <@gribble> https://github.com/bitcoin/bitcoin/issues/30328 | wallet: Remove IsMine from migration code by achow101 · Pull Request #30328 · bitcoin/bitcoin · GitHub
07:29 < achow101> and #28710 is constantly being rebased
07:29 <@gribble> https://github.com/bitcoin/bitcoin/issues/28710 | Remove the legacy wallet and BDB dependency by achow101 · Pull Request #28710 · bitcoin/bitcoin · GitHub
07:29 < Murch[m]> ✋️ I want to join the Legacy Wallet Removal WG
07:29 < dzxzg> I would like to join
07:30 < achow101> Murch[m]: dzxzg: will add / dm
07:30 < achow101> #topic Multiprocess WG Update (ryanofsky)
07:30 < ajonas> hold on...
07:31 < josie> not sure if this has been discussed, but might be a lot of overlap between the sv2 / mp working groups, given the recent mining interface that was merged for mp
07:31 < josie> at least in the short term 
07:31 < ryanofsky> Sorry wasn't ready for this, just several PRs out for review and working on wrapper binary implementation
07:32 < fanquake> pinheadmz: I thought that PR would no-longer be relevant for SV2 ?
07:32 < pinheadmz> fanquake oh. (....oh?)
07:32 < TheCharlatan> ryanofsky when do you think we can add libmultiprocess as a subtree?
07:32 < josie> ryanofsky: if you have a signal group or place you are discussing mp stuff, id like to join (planning to spend a lot of review time on mp)
07:33 < hebasto> ^ so do I
07:33 < fanquake> It would also be good to get an issue or similar open for your http re-writing, as it's not entirely clear of the direction, or what is actually happening there
07:33 < ryanofsky> I don't think anything is blockign libmultiprocess as a subtree, just needs a PR
07:33 < pinheadmz> fanquake ok
07:33 < fanquake> as I don't think there is general buy in to refactoring cconman to be more "general"
07:34 < pinheadmz> fanquake ok that makes a big difference then bc I have a branch with my own sockman and im in progress of rebasing that on the general sockman
07:35 < cfields> pinheadmz: I definitely have my thoughts on that PR as well, just haven't had time to chime in yet.
07:35 < pinheadmz> so a new http will have  a lot of duplicate code (GenerateWaitSockets, BindAndListen blah blah blah)
07:35 < pinheadmz> ok ill formalize an issue with links to my WIP stuff
07:35 < sipa> i think this very much depends on what the refactoring looks like
07:36 < pinheadmz> sipa looks like #30988 ?
07:36 <@gribble> https://github.com/bitcoin/bitcoin/issues/30988 | Split CConnman by vasild · Pull Request #30988 · bitcoin/bitcoin · GitHub
07:36 < sipa> oh, there is a PR
07:37 < sipa> will try to give a conceptual review
07:37 < achow101> this discussion is slightly off topic, going to move on
07:37 < achow101> #topic Monitoring WG Update (b10c)
07:37 < b10c> hi
07:38 < b10c> I've updated the nodes to a recent master, enabled ABORT_ON_FAILED_ASSUME (i.e. treating `Assume` as asserts as we do during fuzzing too) on all, and now run a node with ASan and USan enabled. Might enable LSan and/or TSan soon too
07:38 < b10c> that's it
07:39 < achow101> #topic package relay WG Update (glozow)
07:40 < glozow> hi
07:40 < glozow> so package relay is the name, but the actual “feature milestone” we are working towards now is a proper orphan resolution module with reliable orphan protections. This is to prevent package censorship.
07:40 < josie> glozow: and the clever acronym you have decided on for this is..?
07:41 < glozow> Since #30110 was merged (yay!), I've opened a followup at #31190. The next PRs will be one_honest_peer fuzzer (ensure we can always download), orphan resolution tracker (rebase of #28031 which will look quite different), and making the module internally thread-safe (not started).
07:41 <@gribble> https://github.com/bitcoin/bitcoin/issues/30110 | refactor: TxDownloadManager + fuzzing by glozow · Pull Request #30110 · bitcoin/bitcoin · GitHub
07:41 <@gribble> https://github.com/bitcoin/bitcoin/issues/31190 | TxDownloadManager followups by glozow · Pull Request #31190 · bitcoin/bitcoin · GitHub
07:41 <@gribble> https://github.com/bitcoin/bitcoin/issues/28031 | Package Relay 1/3: Introduce TxDownloadManager and improve orphan-handling by glozow · Pull Request #28031 · bitcoin/bitcoin · GitHub
07:42 < sdaftuar> so we're trying to Save the Children now?
07:42 < glozow> Oh no 😂
07:42 < josie> introducing BIP: Save the Children 
07:43 < glozow> better than sibling eviction i guess
07:43 < jonatack> :D
07:43 < glozow> I’m not sure what order I’ll do the next things / may find tasks to give out if people are looking for work. I need time to think about what to do next, so likely it’ll just be the 30110 followups for a few weeks. It’s been a lot of sprinting this year 😅
07:44 < sipa> i remember the time when the "top" manpage listed for the -S option something about "Count parents together with dead children".
07:44 < stickies-v> glozow: perhaps this is drifting off-topic, but i thought using the orphanage for package relay was just a temporary/duct-tape approach to have opportunistic package relay until the p2p stuff is done and we don't need the orphanage for this anymore, right?
07:45 < glozow> No. It is still used in the BIP 331 implementation
07:45 < stickies-v> okay thanks will need to refresh my reading then
07:46 < achow101> #topic Ad-hoc high priority for review
07:46 < achow101> Anything to add or remove from https://github.com/orgs/bitcoin/projects/1/views/4
07:46 < achow101> (maybe we should kill this too?)
07:46 < jonatack> A question on my mind is, if one is interested in reviewing, do they need to / should they join the related WG?
07:47 < glozow> Obviously not. They just leave a review on the PR
07:47 < achow101> jonatack: need to - no. should they - depends on how involved they want to be
07:47 < achow101> certainly I intend on reviewing prs from all working groups, but i'm not going to join every single one
07:47 < sipa> my thinking is that if you're planning to keep track of all the things the WG is working on, it makes sense to review - but obviously there can't be a requirement
07:47 < josie> jonatack: if just casually interested in reviewing, pinging here seems fine too! can always ping the wg champions 
07:47 < sipa> eh, makes sense to join
07:49 < jonatack> ok
07:49 < jonatack> Question 2
07:49 < sdaftuar> regarding the cluster mempool working group specifically, feel free to let me know if you want to be pinged for review on PRs as they come up, or if you have questions that woudl be helpful for me to answer. or just review PRs as you see fit, that works too :)
07:49 < jonatack> by dint of the bips work, am spending a fair amount of time on keeping up with the new opcodes / covenants / (centralized) MEV discussions
07:50 < jonatack> idk how much bandwidth and creedance people here are giving to those topics, but if there is a WG on that I'd be interested to join
07:51 < achow101> i don't think anyone here is working on those currently
07:51 < sipa> that also seems like something that deserves discussion from a wider group than just bitcoin core contributors 
07:51 < josie> personally, i think there should be an important distinction between BIPs (broader bitcoin ecosystem) and bitcoin core (implementation). if you are interested in running a bips irc channel / or a wg, id be happy to join tho, as im interested in both 
07:51 < cfields> jonatack: the wgs are for Bitcoin Core the software project. Those are a different thing...
07:51 < cfields> right ^^
07:51 < jonatack> yes. i see discussions happenng, but with few people from here (?) though did see josie post about it recently
07:52 < jonatack> cfields: yes, am thinking about the implementations aspects
07:52 < jonatack> just throwing that out there. josie: cool
07:53 < glozow> fwiw I think it would be great for people working on those things to talk about their ideas and progress here (unless it’s about activation/politics)
07:53 < achow101> Anything else to discuss?
07:53 < josie> glozow: +1 
07:53 < jonatack> glozow: it's more about the trade-offs/risks/benefits of the options,afaict
07:53 < sipa> also, people can bring up meeting topics/updates here when they have interesting news to share, even if it's not part of a WG
07:54 < jonatack> am trying to be able to evaluate objectively without getting too close to any
07:54 -!- vysn [~vysn@user/vysn] has joined #bitcoin-core-dev
07:54 < jonatack> sipa: sgtm
07:55 < achow101> #endmeeting
07:55 < dzxzg>  thanks
07:55 < hebasto> could repo owners look into #31176 and enable two additional github actions, if that's okay?
07:55 <@gribble> https://github.com/bitcoin/bitcoin/issues/31176 | [POC] ci: Test cross-built Windows executables on Windows natively by hebasto · Pull Request #31176 · bitcoin/bitcoin · GitHub
07:55 < josie> greating meeting everyone, really cool to get insights into what everyone is working on 
07:55 < fanquake> hebasto: i think that needs some more concpetual discussion first. will leave a comment
07:56 < hebasto> okay
07:59 -!- marcofleon [~marcofleo@82.163.218.33] has quit [Quit: Client closed]
07:59 -!- Emc99 [~Emc99@212.129.79.13] has joined #bitcoin-core-dev
08:01 -!- Emc99 [~Emc99@212.129.79.13] has quit [Client Quit]
08:01 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has joined #bitcoin-core-dev
08:05 < glozow> jonatack: fwiw as someone who also wasn’t part of the WG discussion, my view is that it’s a way to continue working in the open while acknowledging that large projects require people to continuously work directly together. People naturally form groups based on their interests, and leave/join them over time. Sometimes it’s hard to jump in to a project because there’s a lot of context. I think it’s great that everybody is trying to do 
08:05 < glozow> as much as possible in the open by making room for updates at this meeting, posting groups publicly, and always inviting people to join.
08:07 -!- bugs_ [~bugs@user/bugs/x-5128603] has joined #bitcoin-core-dev
08:09 < jonatack> glozow: yes, agree, and +1 on the open aspects. will join some of the signal groups and see
08:10 -!- dzxzg [~dzxzg@user/dzxzg] has quit [Quit: Client closed]
08:11 < lightlike> also worth noting that people who wanted to work together on something have always done so, just in private. It's just more open and transparent now.
08:11 < lightlike> However, given that now anyone can open a WG (no more voting), I think that PRs from a WG should no longer automatically get merge priority automatically over other PRs.
08:11 -!- John123 [~John123@45.250.237.9] has quit [Quit: Client closed]
08:13 < sdaftuar> lightlike: i agree but i'd just add that i think maintainers should use their judgement on that point (as they always have)
08:26 -!- l0rinc [~l0rinc@94.44.250.7] has quit [Quit: Client closed]
08:30 -!- Guest64 [~Guest64@2a09:bac3:83f3:aa::11:1ad] has joined #bitcoin-core-dev
08:30 -!- Guest64 [~Guest64@2a09:bac3:83f3:aa::11:1ad] has quit [Client Quit]
08:33 -!- zeropoint [~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-core-dev
08:33 -!- John123 [~John123@45.250.237.9] has joined #bitcoin-core-dev
08:37 -!- storopoli [~storopoli@user/storopoli] has joined #bitcoin-core-dev
08:37 -!- storopoli [~storopoli@user/storopoli] has quit [Excess Flood]
08:39 -!- John123 [~John123@45.250.237.9] has quit [Quit: Client closed]
09:02 < instagibbs> stickies-v https://github.com/bitcoin/bips/blob/master/bip-0331.mediawiki#cite_note-8 reference to sender vs receiver initiated package relay which might be helpful
09:10 < stickies-v> oooh it is, ty instagibbs - i'd read that in the past but didn't quite link it w orphanage. makes sense
09:10 -!- juleeho [~juleeho@81.174.12.248] has joined #bitcoin-core-dev
09:17 -!- vysn [~vysn@user/vysn] has quit [Ping timeout: 252 seconds]
09:19 -!- Guest78 [~Guest78@2a02:b025:10:73f6:d5c8:f52f:9cfe:b28f] has joined #bitcoin-core-dev
09:20 -!- juleeho-droid [~juleeho-d@81.174.12.248] has joined #bitcoin-core-dev
09:23 -!- Guest78 [~Guest78@2a02:b025:10:73f6:d5c8:f52f:9cfe:b28f] has quit [Client Quit]
09:28 -!- juleeho [~juleeho@user/juleeho] has changed host
09:30 -!- juleeho-droid [~juleeho-d@user/juleeho] has changed host
09:30 -!- juleeho-droid [~juleeho-d@user/juleeho] has quit [Remote host closed the connection]
09:31 -!- juleeho-droid [~juleeho-d@user/juleeho] has joined #bitcoin-core-dev
09:33 -!- juleeho-droid is now known as juleeho_
09:44 -!- pablomartin [~pablomart@185.137.36.33] has joined #bitcoin-core-dev
09:48 -!- storopoli [~storopoli@user/storopoli] has joined #bitcoin-core-dev
09:48 -!- storopoli [~storopoli@user/storopoli] has quit [Excess Flood]
09:49 -!- storopoli [~storopoli@user/storopoli] has joined #bitcoin-core-dev
09:49 -!- storopoli [~storopoli@user/storopoli] has quit [Excess Flood]
09:53 -!- juleeho [~juleeho@user/juleeho] has quit [Read error: Connection reset by peer]
09:53 -!- storopoli [~storopoli@user/storopoli] has joined #bitcoin-core-dev
09:53 -!- storopoli [~storopoli@user/storopoli] has quit [Excess Flood]
09:53 -!- storopoli [~storopoli@169.150.198.70] has joined #bitcoin-core-dev
09:53 -!- storopoli [~storopoli@user/storopoli] has changed host
09:54 -!- storopoli [~storopoli@user/storopoli] has quit [Max SendQ exceeded]
09:56 -!- storopoli [~storopoli@user/storopoli] has joined #bitcoin-core-dev
09:56 -!- storopoli [~storopoli@user/storopoli] has quit [Excess Flood]
09:56 -!- storopoli [~storopoli@user/storopoli] has joined #bitcoin-core-dev
09:56 -!- juleeho-droid [~juleeho-d@user/juleeho] has joined #bitcoin-core-dev
09:56 -!- storopoli [~storopoli@user/storopoli] has quit [Excess Flood]
09:59 -!- juleeho_ [~juleeho-d@user/juleeho] has quit [Ping timeout: 265 seconds]
10:03 -!- jonatack [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
10:03 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
10:16 -!- pablomartin [~pablomart@185.137.36.33] has quit [Ping timeout: 252 seconds]
10:17 < bitcoin-git> [bitcoin] Sjors opened pull request #31196: Remove processNewBlock from mining interface (master...2024/10/mining-drop-processnewblock) https://github.com/bitcoin/bitcoin/pull/31196
10:19 -!- mcey_ [~emcy@148.252.146.198] has quit [Remote host closed the connection]
10:19 -!- mcey_ [~emcy@148.252.146.198] has joined #bitcoin-core-dev
10:21 -!- pablomartin [~pablomart@194.156.224.193] has joined #bitcoin-core-dev
10:22 -!- szkl [uid110435@id-110435.uxbridge.irccloud.com] has joined #bitcoin-core-dev
10:26 -!- pablomartin [~pablomart@194.156.224.193] has quit [Remote host closed the connection]
10:31 -!- jeremyrubin [~jeremyrub@ec2-44-199-24-18.compute-1.amazonaws.com] has joined #bitcoin-core-dev
10:31 -!- vysn [~vysn@user/vysn] has joined #bitcoin-core-dev
10:46 -!- pablomartin [~pablomart@152.170.208.150] has joined #bitcoin-core-dev
10:48 -!- pablomartin [~pablomart@152.170.208.150] has quit [Client Quit]
11:02 -!- juleeho-droid [~juleeho-d@user/juleeho] has quit [Read error: Connection reset by peer]
11:04 -!- juleeho-droid [~juleeho-d@user/juleeho] has joined #bitcoin-core-dev
11:04 -!- juleeho-droid [~juleeho-d@user/juleeho] has quit [Remote host closed the connection]
11:07 < bitcoin-git> [bitcoin] Sjors opened pull request #31197: refactor: mining interface 30955 followups (master...2024/10/pr30955-followups) https://github.com/bitcoin/bitcoin/pull/31197
11:08 -!- jonatack [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
11:09 -!- John123 [~John123@45.250.237.9] has joined #bitcoin-core-dev
11:10 < bitcoin-git> [bitcoin] darosior opened pull request #31198: init: warn, don't error, when '-upnp' is set (master...2024_upnp_unbreak_gui) https://github.com/bitcoin/bitcoin/pull/31198
11:11 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
11:11 -!- juleeho [~juleeho@77-32-118-9.dyn.eolo.it] has joined #bitcoin-core-dev
11:18 -!- juleeho [~juleeho@77-32-118-9.dyn.eolo.it] has quit [Remote host closed the connection]
12:06 -!- Artea [~Lufia@artea.pt] has quit [Quit: ZNC 1.9.1 - https://znc.in]
12:57 -!- John123 [~John123@45.250.237.9] has quit [Quit: Client closed]
13:06 -!- John123 [~John123@45.250.237.9] has joined #bitcoin-core-dev
13:16 -!- achow101 [~achow101@user/achow101] has quit [Ping timeout: 260 seconds]
13:16 -!- achow101 [~achow101@user/achow101] has joined #bitcoin-core-dev
13:41 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 252 seconds]
13:42 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
13:54 -!- John123 [~John123@45.250.237.9] has quit [Quit: Client closed]
14:13 -!- jonatack [~jonatack@user/jonatack] has quit [Remote host closed the connection]
14:14 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
14:31 -!- vysn [~vysn@user/vysn] has quit [Remote host closed the connection]
14:34 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev
14:34 -!- achow101 [~achow101@user/achow101] has quit [Ping timeout: 260 seconds]
14:35 -!- achow101 [~achow101@user/achow101] has joined #bitcoin-core-dev
14:37 -!- bugs_ [~bugs@user/bugs/x-5128603] has quit [Quit: Leaving]
14:43 -!- preimage [~halosghos@user/halosghost] has quit [Quit: WeeChat 4.4.2]
16:00 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
16:03 -!- achow101_ [~achow101@user/achow101] has joined #bitcoin-core-dev
16:03 -!- achow101 [~achow101@user/achow101] has quit [Ping timeout: 272 seconds]
16:08 -!- achow101 [~achow101@user/achow101] has joined #bitcoin-core-dev
16:08 -!- achow101_ [~achow101@user/achow101] has quit [Ping timeout: 260 seconds]
16:10 -!- Talkless [~Talkless@mail.dargis.net] has quit [Remote host closed the connection]
17:11 -!- grimjow [~grimjow@197.210.227.86] has joined #bitcoin-core-dev
17:14 -!- grimjow [~grimjow@197.210.227.86] has quit [Client Quit]
17:25 -!- hardtotell7 [~hardtotel@user/hardtotell] has joined #bitcoin-core-dev
17:50 -!- andrewtoth [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Ping timeout: 260 seconds]
17:52 -!- zeropoint [~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net] has quit [Quit: leaving]
18:49 -!- johnny9dev584508 [~johnny9de@136.56.172.142] has joined #bitcoin-core-dev
19:07 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 265 seconds]
19:08 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
20:07 -!- eval-exec [~Thunderbi@45.78.48.202.16clouds.com] has quit [Ping timeout: 252 seconds]
20:13 -!- eval-exec [~Thunderbi@96.45.190.137.16clouds.com] has joined #bitcoin-core-dev
20:19 -!- eval-exec [~Thunderbi@96.45.190.137.16clouds.com] has quit [Ping timeout: 252 seconds]
20:45 -!- Guest88 [~Guest88@2001:1670:10:1358:51d6:f294:84d3:d56e] has joined #bitcoin-core-dev
20:45 -!- Guest88 [~Guest88@2001:1670:10:1358:51d6:f294:84d3:d56e] has quit [Client Quit]
20:46 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 272 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:15 -!- brunoerg [~brunoerg@2804:14c:3bfb:37:440f:9f71:5fa5:d199] has joined #bitcoin-core-dev
21:21 -!- brunoerg [~brunoerg@2804:14c:3bfb:37:440f:9f71:5fa5:d199] has quit [Ping timeout: 265 seconds]
23:01 -!- mcey_ [~emcy@148.252.146.198] has quit [Remote host closed the connection]
23:01 -!- mcey_ [~emcy@148.252.146.198] has joined #bitcoin-core-dev
23:12 -!- johnny9dev584508 [~johnny9de@136.56.172.142] has quit [Ping timeout: 276 seconds]
23:14 -!- johnny9dev584508 [~johnny9de@136.56.172.142] has joined #bitcoin-core-dev
23:37 -!- brunoerg [~brunoerg@2804:14c:3bfb:37:440f:9f71:5fa5:d199] has joined #bitcoin-core-dev
23:42 -!- brunoerg [~brunoerg@2804:14c:3bfb:37:440f:9f71:5fa5:d199] has quit [Ping timeout: 276 seconds]
--- Log closed Fri Nov 01 00:00:37 2024