12024-10-31T00:06:28 *** Guest54 <Guest54!~Guest54@102.89.83.217> has joined #bitcoin-core-dev
22024-10-31T00:07:56 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has quit IRC (Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net)
32024-10-31T00:08:07 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has joined #bitcoin-core-dev
42024-10-31T00:15:30 *** Guest54 <Guest54!~Guest54@102.89.83.217> has quit IRC (Quit: Client closed)
52024-10-31T00:15:55 *** Guest54 <Guest54!~Guest54@102.89.83.217> has joined #bitcoin-core-dev
62024-10-31T00:16:14 *** Guest54 <Guest54!~Guest54@102.89.83.217> has quit IRC (Client Quit)
72024-10-31T00:16:48 *** Guest54 <Guest54!~Guest54@102.89.83.217> has joined #bitcoin-core-dev
82024-10-31T00:24:28 *** Guest54 <Guest54!~Guest54@102.89.83.217> has quit IRC (Quit: Client closed)
92024-10-31T00:24:37 *** Guest54 <Guest54!~Guest54@102.89.83.217> has joined #bitcoin-core-dev
102024-10-31T00:25:27 *** Guest54 <Guest54!~Guest54@102.89.83.217> has quit IRC (Client Quit)
112024-10-31T00:27:14 *** Guest54 <Guest54!~Guest54@102.89.83.135> has joined #bitcoin-core-dev
122024-10-31T00:27:15 *** zeropoint <zeropoint!~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net> has quit IRC (Quit: leaving)
132024-10-31T00:33:38 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has quit IRC (Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net)
142024-10-31T00:33:48 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has joined #bitcoin-core-dev
152024-10-31T00:35:49 *** Guest54 <Guest54!~Guest54@102.89.83.135> has quit IRC (Quit: Client closed)
162024-10-31T00:36:01 *** Guest54 <Guest54!~Guest54@102.89.83.135> has joined #bitcoin-core-dev
172024-10-31T00:39:47 *** Guest54 <Guest54!~Guest54@102.89.83.135> has quit IRC (Client Quit)
182024-10-31T00:41:06 *** Guest54 <Guest54!~Guest54@102.89.83.135> has joined #bitcoin-core-dev
192024-10-31T00:41:49 *** Guest54 <Guest54!~Guest54@102.89.83.135> has quit IRC (Client Quit)
202024-10-31T00:42:06 *** Guest54 <Guest54!~Guest54@102.89.83.135> has joined #bitcoin-core-dev
212024-10-31T00:46:53 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has quit IRC (Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net)
222024-10-31T00:47:30 *** Guest73 <Guest73!~Guest54@102.89.83.217> has joined #bitcoin-core-dev
232024-10-31T00:49:11 *** Guest73 <Guest73!~Guest54@102.89.83.217> has quit IRC (Client Quit)
242024-10-31T00:49:13 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has joined #bitcoin-core-dev
252024-10-31T00:50:38 *** Guest73 <Guest73!~Guest73@102.89.83.217> has joined #bitcoin-core-dev
262024-10-31T00:51:55 *** Guest54 <Guest54!~Guest54@102.89.83.135> has quit IRC (Ping timeout: 256 seconds)
272024-10-31T00:56:28 *** aleggg <aleggg!~aleggg@187.58.223.239> has joined #bitcoin-core-dev
282024-10-31T00:57:46 *** Guest73 <Guest73!~Guest73@102.89.83.217> has quit IRC (Quit: Client closed)
292024-10-31T00:58:37 *** Guest73 <Guest73!~Guest73@102.89.83.217> has joined #bitcoin-core-dev
302024-10-31T01:09:21 *** Guest73 <Guest73!~Guest73@102.89.83.217> has quit IRC (Quit: Client closed)
312024-10-31T01:09:49 *** Guest54 <Guest54!~Guest54@102.89.83.217> has joined #bitcoin-core-dev
322024-10-31T01:13:29 *** Guest54 <Guest54!~Guest54@102.89.83.217> has quit IRC (Client Quit)
332024-10-31T01:15:41 *** Guest54 <Guest54!~Guest54@102.89.83.217> has joined #bitcoin-core-dev
342024-10-31T01:22:26 *** Guest54 <Guest54!~Guest54@102.89.83.217> has quit IRC (Quit: Client closed)
352024-10-31T01:22:41 *** jeesica <jeesica!~jeesica@102.89.83.217> has joined #bitcoin-core-dev
362024-10-31T01:29:32 *** jeesica <jeesica!~jeesica@102.89.83.217> has quit IRC (Quit: Client closed)
372024-10-31T01:41:33 *** jeesica <jeesica!~jeesica@102.89.83.135> has joined #bitcoin-core-dev
382024-10-31T01:41:56 *** jeesica <jeesica!~jeesica@102.89.83.135> has quit IRC (Client Quit)
392024-10-31T01:47:38 *** jeesica <jeesica!~jeesica@102.89.83.135> has joined #bitcoin-core-dev
402024-10-31T01:47:50 *** jeesica <jeesica!~jeesica@102.89.83.135> has quit IRC (Client Quit)
412024-10-31T01:48:10 *** jeesica <jeesica!~jeesica@102.89.83.135> has joined #bitcoin-core-dev
422024-10-31T01:49:36 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has quit IRC (Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net)
432024-10-31T01:49:40 *** jeesica <jeesica!~jeesica@102.89.83.135> has quit IRC (Client Quit)
442024-10-31T01:51:34 *** jeesica <jeesica!~jeesica@102.89.83.135> has joined #bitcoin-core-dev
452024-10-31T01:52:09 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has joined #bitcoin-core-dev
462024-10-31T01:52:18 *** jeesica <jeesica!~jeesica@102.89.83.135> has quit IRC (Client Quit)
472024-10-31T03:24:42 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has quit IRC (Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net)
482024-10-31T03:24:53 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has joined #bitcoin-core-dev
492024-10-31T03:26:56 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has quit IRC (Client Quit)
502024-10-31T03:27:07 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 252 seconds)
512024-10-31T03:29:09 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has joined #bitcoin-core-dev
522024-10-31T03:30:50 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has quit IRC (Remote host closed the connection)
532024-10-31T03:31:00 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has joined #bitcoin-core-dev
542024-10-31T04:01:01 *** cmirror <cmirror!~cmirror@4.53.92.114> has quit IRC (Remote host closed the connection)
552024-10-31T04:01:31 *** cmirror <cmirror!~cmirror@4.53.92.114> has joined #bitcoin-core-dev
562024-10-31T04:06:55 *** John123 <John123!~John123@45.250.237.9> has quit IRC (Quit: Client closed)
572024-10-31T04:46:26 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has quit IRC (Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net)
582024-10-31T04:46:36 *** spynxic <spynxic!~spynxic@spynxic.powered.by.lunarbnc.net> has joined #bitcoin-core-dev
592024-10-31T05:12:12 *** jlest <jlest!~jlest@user/jlest> has quit IRC (Ping timeout: 246 seconds)
602024-10-31T05:46:41 *** conman <conman!~con@180-150-21-3.b49615.mel.static.aussiebb.net> has joined #bitcoin-core-dev
612024-10-31T06:01:48 *** mcey_ <mcey_!~emcy@148.252.146.198> has joined #bitcoin-core-dev
622024-10-31T06:05:18 *** mcey <mcey!~emcy@148.252.146.198> has quit IRC (Ping timeout: 265 seconds)
632024-10-31T07:07:00 *** sample <sample!~sample@82-64-162-213.subs.proxad.net> has quit IRC (Ping timeout: 246 seconds)
642024-10-31T07:07:01 *** aureleoules <aureleoules!~aureleoul@82-64-162-213.subs.proxad.net> has quit IRC (Ping timeout: 248 seconds)
652024-10-31T07:24:06 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
662024-10-31T07:31:29 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 255 seconds)
672024-10-31T07:32:17 *** flag <flag!~flag@81.56.89.175> has quit IRC (Ping timeout: 252 seconds)
682024-10-31T07:34:15 *** flag <flag!~flag@81.56.89.175> has joined #bitcoin-core-dev
692024-10-31T07:35:11 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
702024-10-31T07:41:24 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Read error: Connection reset by peer)
712024-10-31T07:55:31 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
722024-10-31T08:08:29 *** vysn <vysn!~vysn@user/vysn> has joined #bitcoin-core-dev
732024-10-31T08:22:20 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has joined #bitcoin-core-dev
742024-10-31T08:28:45 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 252 seconds)
752024-10-31T08:35:50 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
762024-10-31T08:38:17 *** storopoli <storopoli!~storopoli@user/storopoli> has joined #bitcoin-core-dev
772024-10-31T08:38:54 <storopoli> join #rust-bitcoin
782024-10-31T08:45:01 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 252 seconds)
792024-10-31T08:52:35 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
802024-10-31T08:54:38 *** storopoli <storopoli!~storopoli@user/storopoli> has quit IRC (Remote host closed the connection)
812024-10-31T09:08:55 *** storopoli <storopoli!~storopoli@user/storopoli> has joined #bitcoin-core-dev
822024-10-31T09:08:56 *** storopoli <storopoli!~storopoli@user/storopoli> has quit IRC (Excess Flood)
832024-10-31T09:09:15 *** storopoli <storopoli!~storopoli@169.150.198.83> has joined #bitcoin-core-dev
842024-10-31T09:09:16 *** storopoli <storopoli!~storopoli@user/storopoli> has quit IRC (Excess Flood)
852024-10-31T09:09:40 *** storopoli <storopoli!~storopoli@user/storopoli> has joined #bitcoin-core-dev
862024-10-31T09:09:41 *** storopoli <storopoli!~storopoli@user/storopoli> has quit IRC (Excess Flood)
872024-10-31T09:10:03 *** storopoli <storopoli!~storopoli@169.150.198.83> has joined #bitcoin-core-dev
882024-10-31T09:10:04 *** storopoli <storopoli!~storopoli@user/storopoli> has quit IRC (Excess Flood)
892024-10-31T09:10:26 *** storopoli <storopoli!~storopoli@169.150.198.83> has joined #bitcoin-core-dev
902024-10-31T09:10:27 *** storopoli <storopoli!~storopoli@user/storopoli> has quit IRC (Excess Flood)
912024-10-31T09:32:33 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has quit IRC (Remote host closed the connection)
922024-10-31T10:34:04 <laanwj> isn't it #bitcoin-rust
932024-10-31T10:38:41 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 255 seconds)
942024-10-31T10:53:31 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
952024-10-31T11:11:23 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 244 seconds)
962024-10-31T11:14:22 *** jespada <jespada!~jespada@cpc121308-nmal25-2-0-cust15.19-2.cable.virginm.net> has quit IRC (Quit: Textual IRC Client: www.textualapp.com)
972024-10-31T11:23:05 *** jespada <jespada!~jespada@cpc121308-nmal25-2-0-cust15.19-2.cable.virginm.net> has joined #bitcoin-core-dev
982024-10-31T11:24:49 *** szkl <szkl!uid110435@id-110435.uxbridge.irccloud.com> has joined #bitcoin-core-dev
992024-10-31T12:09:01 <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
1002024-10-31T12:13:04 *** SpellChecker <SpellChecker!~SpellChec@user/SpellChecker> has quit IRC (Remote host closed the connection)
1012024-10-31T12:15:37 *** SpellChecker <SpellChecker!~SpellChec@user/SpellChecker> has joined #bitcoin-core-dev
1022024-10-31T12:17:38 *** kevkevin <kevkevin!~kevkevin@209-242-39-30.rev.dls.net> has joined #bitcoin-core-dev
1032024-10-31T12:22:20 *** kevkevin <kevkevin!~kevkevin@209-242-39-30.rev.dls.net> has quit IRC (Ping timeout: 252 seconds)
1042024-10-31T12:28:20 <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
1052024-10-31T12:46:15 <bitcoin-git> [bitcoin] glozow opened pull request #31190: TxDownloadManager followups (master...2024-10-30110-followups) https://github.com/bitcoin/bitcoin/pull/31190
1062024-10-31T12:57:26 *** preimage <preimage!~halosghos@user/halosghost> has joined #bitcoin-core-dev
1072024-10-31T13:00:39 <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
1082024-10-31T13:01:04 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
1092024-10-31T13:21:02 <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
1102024-10-31T13:26:00 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Read error: Connection reset by peer)
1112024-10-31T13:26:05 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
1122024-10-31T13:31:04 *** l0rinc <l0rinc!~l0rinc@94.44.250.7> has joined #bitcoin-core-dev
1132024-10-31T13:31:27 *** szkl <szkl!uid110435@id-110435.uxbridge.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)
1142024-10-31T13:39:56 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Quit: WeeChat 4.4.2)
1152024-10-31T13:41:12 *** marcofleon <marcofleon!~marcofleo@82.163.218.33> has joined #bitcoin-core-dev
1162024-10-31T13:42:03 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
1172024-10-31T13:51:10 <bitcoin-git> [bitcoin] fanquake pushed 5 commits to 27.x: https://github.com/bitcoin/bitcoin/compare/882e0d730d6d...bf03c458e994
1182024-10-31T13:51:10 <bitcoin-git> bitcoin/27.x c838ce5 Vasil Dimov: doc: use proper doxygen formatting for CTxMemPool::cs
1192024-10-31T13:51:11 <bitcoin-git> bitcoin/27.x 6c09325 fanquake: doc: finalise release notes for 27.2
1202024-10-31T13:51:11 <bitcoin-git> bitcoin/27.x f42fcf6 fanquake: build: bump version to v27.2 final
1212024-10-31T13:51:12 <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
1222024-10-31T13:51:47 *** vysn <vysn!~vysn@user/vysn> has quit IRC (Ping timeout: 252 seconds)
1232024-10-31T13:55:35 <bitcoin-git> [bitcoin] fanquake pushed tag v27.2: https://github.com/bitcoin/bitcoin/compare/v27.2
1242024-10-31T13:56:24 *** John123 <John123!~John123@45.250.237.9> has joined #bitcoin-core-dev
1252024-10-31T13:58:10 *** andrewtoth <andrewtoth!~andrewtot@gateway/tor-sasl/andrewtoth> has joined #bitcoin-core-dev
1262024-10-31T13:59:02 *** dzxzg <dzxzg!~dzxzg@user/dzxzg> has joined #bitcoin-core-dev
1272024-10-31T14:00:14 <achow101> #startmeeting
1282024-10-31T14:00:18 <hebasto> hi
1292024-10-31T14:00:27 <Murch[m]> hi
1302024-10-31T14:00:29 <ajonas> hi
1312024-10-31T14:00:33 <willcl-ark> Hi
1322024-10-31T14:00:45 <stickies-v> hi
1332024-10-31T14:00:49 <maxedw> hi
1342024-10-31T14:00:49 <Chris_Stewart_5> hi
1352024-10-31T14:00:56 <gleb> hi
1362024-10-31T14:00:58 <josie> hi
1372024-10-31T14:01:04 <achow101> There are 2 preproposed meeting topics this week. Any last minute ones to add?
1382024-10-31T14:01:30 <achow101> #topic priority project reflections and working groups (ajonas)
1392024-10-31T14:01:32 <dzxzg> hi
1402024-10-31T14:01:35 *** kevkevin_ <kevkevin_!~kevkevin@209-242-39-30.rev.dls.net> has joined #bitcoin-core-dev
1412024-10-31T14:01:43 <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
1422024-10-31T14:01:47 <sipa> hi
1432024-10-31T14:02:07 <ajonas> I know jonatack had particular interest
1442024-10-31T14:02:15 <jonatack> hi
1452024-10-31T14:02:25 <cfields> hi
1462024-10-31T14:02:27 <kevkevin_> hi
1472024-10-31T14:02:33 <tdb3> hi
1482024-10-31T14:03:01 <pinheadmz> hi
1492024-10-31T14:03:05 <kevkevin_> hi
1502024-10-31T14:03:12 *** kevkevin_ <kevkevin_!~kevkevin@209-242-39-30.rev.dls.net> has quit IRC (Client Quit)
1512024-10-31T14:03:20 <marcofleon> hi
1522024-10-31T14:03:26 <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
1532024-10-31T14:03:33 *** kevkevin <kevkevin!~kevkevin@209-242-39-30.rev.dls.net> has joined #bitcoin-core-dev
1542024-10-31T14:03:44 <kevkevin> hi
1552024-10-31T14:03:47 <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?
1562024-10-31T14:04:28 <ajonas> sipa: maybe adding one's name to the wiki would be a place to keep track of that?
1572024-10-31T14:04:37 <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
1582024-10-31T14:04:38 <sipa> yeah, that's what i'd suggest
1592024-10-31T14:05:03 <ajonas> that would match something we tried in the first round -https://github.com/bitcoin-core/bitcoin-devwiki/wiki/Priorities
1602024-10-31T14:05:12 <josie> achow101: ack, also some groups might not have something every week
1612024-10-31T14:05:37 <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?
1622024-10-31T14:05:56 <stickies-v> (of course we can revisit if meetings start to take too long but I don't expect that to be an issue)
1632024-10-31T14:06:05 <emzy> hi
1642024-10-31T14:06:12 <Murch[m]> The priority project reports were usually pretty quick, I donât expect that it would be much longer with Working Groups
1652024-10-31T14:06:15 <josie> stickies-v: also fair, because i have some big updates for both groups im involved with this week haha
1662024-10-31T14:06:29 <achow101> stickies-v: I think there are too many groups for every group to report and that will take too long/dominate the meeting
1672024-10-31T14:06:35 <ajonas> this was an attempt to control the feast/famine nature of the IRC meetings
1682024-10-31T14:06:53 <Murch[m]> achow101: Itâs not like there are a ton of other topics usually
1692024-10-31T14:07:11 <sipa> i think it's fine to go over all WGs every time, if they don't have anything, that's alright
1702024-10-31T14:07:13 <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
1712024-10-31T14:07:18 <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?
1722024-10-31T14:07:18 <achow101> Murch[m]: but it's important to leave space for them
1732024-10-31T14:07:20 <sipa> if things take too long, we can revisit
1742024-10-31T14:07:25 <sdaftuar> hi
1752024-10-31T14:07:42 <josie> sdaftuar: *woops better say hi!*
1762024-10-31T14:07:43 <achow101> josie: that makes reporting optional, and I suspect that if it were optional, people would simply stop reporting
1772024-10-31T14:07:58 <josie> i mean, id prefer it be optional?
1782024-10-31T14:08:08 <josie> if youre not motivated to join and report, why force you?
1792024-10-31T14:08:14 <stickies-v> +1 josie
1802024-10-31T14:08:24 <josie> i certainly wont stop joining and reporting :)
1812024-10-31T14:08:44 <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
1822024-10-31T14:08:57 <josie> glozow: +1
1832024-10-31T14:08:59 <dergoegge> hi
1842024-10-31T14:09:04 <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
1852024-10-31T14:09:07 <Murch[m]> glozow: +1
1862024-10-31T14:09:20 <josie> make irc noisy again
1872024-10-31T14:09:35 <sipa> welcome to zombocom
1882024-10-31T14:09:53 <josie> lol
1892024-10-31T14:10:21 <sipa> this meta-topic is also not worth spending too much time on
1902024-10-31T14:10:29 <sipa> we can see what works
1912024-10-31T14:10:36 <jonatack> ajonas: thank you for the useful write-up. i have feedback, not sure when/where best to give it
1922024-10-31T14:10:36 <achow101> ok, hope everyone's ready
1932024-10-31T14:11:05 <achow101> I'll do the same as last week, if you don't say anything in one minute, i'm moving on
1942024-10-31T14:11:11 <achow101> #topic Erlay WG Update (sr_gi, naumenkogs, marcofleon)
1952024-10-31T14:11:13 <jonatack> ajonas: maybe i'll write to you directly
1962024-10-31T14:11:13 <ajonas> jonatack: you can leave comments on the doc unless you think it needs to be done here
1972024-10-31T14:11:21 <gleb> hi! it's me reporting on erlay this time
1982024-10-31T14:11:42 <cfields> better than reporting ltae :)
1992024-10-31T14:11:46 <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.
2002024-10-31T14:11:49 <gribble> https://github.com/bitcoin/bitcoin/issues/30116 | p2p: Fill reconciliation sets (Erlay) attempt 2 by sr-gi · Pull Request #30116 · bitcoin/bitcoin · GitHub
2012024-10-31T14:12:03 *** marcofleon <marcofleon!~marcofleo@82.163.218.33> has quit IRC (Quit: Client closed)
2022024-10-31T14:12:04 <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
2032024-10-31T14:12:13 <gleb> https://github.com/sr-gi/hyperion/pull/25
2042024-10-31T14:12:26 <josie> gleb: hyperion is an awesome name
2052024-10-31T14:12:36 <sipa> also, let's revive this: we've had some discussions that led up to sergi's simulator in #minisketch on this IRC network
2062024-10-31T14:12:43 <sipa> i can share history
2072024-10-31T14:12:49 <gleb> I had some one-to-one calls with WG members to bootstrap review. Different shapes of it, but mostly answering design questions.
2082024-10-31T14:13:14 <gleb> People are back from travel next week and i hope we see more in-pr involvement by then :)
2092024-10-31T14:13:32 <gleb> Promising so far. Let me know if you're willing to join, we have a signal chat.
2102024-10-31T14:13:45 <sipa> gleb: i'd like to join
2112024-10-31T14:14:05 <gleb> That's it. I'll answer quick questions here, otherwise we can move on
2122024-10-31T14:14:08 <gleb> sipa: will add
2132024-10-31T14:14:19 <sipa> thanks!
2142024-10-31T14:14:34 <achow101> #topic Fuzzing WG Update (dergoegge)
2152024-10-31T14:14:59 <dergoegge> No real update today but i've created a irc channel: #bitcoin-core-fuzzing
2162024-10-31T14:15:22 <achow101> #topic Kernel WG Update (TheCharlatan)
2172024-10-31T14:15:22 <dergoegge> There is also a signal group, let me know if you want to join
2182024-10-31T14:15:52 <TheCharlatan> yes, same for the kernel
2192024-10-31T14:16:04 *** marcofleon <marcofleon!~marcofleo@82.163.218.33> has joined #bitcoin-core-dev
2202024-10-31T14:16:11 <sipa> dergoegge: i'd like to join (i promise i will not be joining every WG)
2212024-10-31T14:16:33 <achow101> #topic Benchmarking WG Update (josibake, l0rinc)
2222024-10-31T14:16:37 *** John123 <John123!~John123@45.250.237.9> has quit IRC (Quit: Client closed)
2232024-10-31T14:16:42 <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
2242024-10-31T14:16:52 <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)
2252024-10-31T14:17:01 <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
2262024-10-31T14:17:10 <josie> if we end up finding things that are generally useful for our existing CI setup, we will port those over
2272024-10-31T14:17: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
2282024-10-31T14:17:27 <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
2292024-10-31T14:17:51 <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)
2302024-10-31T14:18:02 <sipa> *crickets*
2312024-10-31T14:18: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 :)
2322024-10-31T14:18:24 <josie> thats all for me
2332024-10-31T14:18:31 <achow101> #topic Silent Payments WG Update (josibake, RubenSomsen)
2342024-10-31T14:18:36 <achow101> josie: go again
2352024-10-31T14:18:43 <josie> for silent payments, the focus is still the libsecp256k1 PR (bitcoin-core/secp256k1#1519)
2362024-10-31T14:18:44 <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
2372024-10-31T14:18:50 <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!
2382024-10-31T14:18:58 <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)
2392024-10-31T14:19:02 <gleb> bad gribble
2402024-10-31T14:19:05 <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/#)
2412024-10-31T14:19:13 <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/#)
2422024-10-31T14:19:20 <josie> (i posted the gnusha links instead of the google group ones just for you vasild)
2432024-10-31T14:19:27 <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
2442024-10-31T14:19:37 <josie> this to help coordinate work across projects, if anyone is interested in joining / helping out
2452024-10-31T14:19:41 <cfields> josie: are you planning on using rented machines? Or looking to source self-hosted hardware/bandwidth?
2462024-10-31T14:19:43 <josie> same comment re: working group signal chat
2472024-10-31T14:19:48 <pinheadmz> josie add me to the discord
2482024-10-31T14:20:04 <josie> cfields: hetzner boxes for now, since weve all been buying our own in that group the last month or so
2492024-10-31T14:20:27 <josie> pinheadmz: will do!
2502024-10-31T14:20:38 <Murch[m]> Ugh discord. :(
2512024-10-31T14:20:42 *** John123 <John123!~John123@45.250.237.9> has joined #bitcoin-core-dev
2522024-10-31T14:20:51 <josie> cfields: if you have sauce on someone with self hosted stuff.. lemme know :)
2532024-10-31T14:21:09 <josie> Murch[m]: i know :( but it seems to work well for the bdk/bitshala folks!
2542024-10-31T14:21:25 <josie> the actual core related work we are discussing in signal tho
2552024-10-31T14:21:29 <Murch[m]> Matrix 2.0 was announced just recently! ^^
2562024-10-31T14:21:33 <josie> discord is for external project coordination
2572024-10-31T14:21:44 <josie> anywho, thats all from me
2582024-10-31T14:21:46 <achow101> #topic Cluster Mempool WG Update (sdaftuar)
2592024-10-31T14:21:55 <sdaftuar> hi
2602024-10-31T14:22:02 <sdaftuar> sipa, let me know if you want to join this working group too
2612024-10-31T14:22:09 <Murch[m]> haha
2622024-10-31T14:22:13 <sipa> sdaftuar: hmmm, tempting
2632024-10-31T14:22:15 <sipa> i shall join
2642024-10-31T14:22:20 <josie> sipa: wooooow
2652024-10-31T14:22:25 <cfields> josie: I might, will dm.
2662024-10-31T14:22:34 <sdaftuar> anyway, #31122 is the PR to review
2672024-10-31T14:22:38 <gribble> https://github.com/bitcoin/bitcoin/issues/31122 | cluster mempool: Implement changeset interface for mempool by sdaftuar · Pull Request #31122 · bitcoin/bitcoin · GitHub
2682024-10-31T14:23:15 <sdaftuar> i think it's making good progress
2692024-10-31T14:23:32 <sdaftuar> sipa continues to work on txgraph, so will let him update on that--
2702024-10-31T14:23:38 <sipa> txgraph will be ready for review in Two Weeks(tm)
2712024-10-31T14:23:44 <sdaftuar> sweet :)
2722024-10-31T14:24:09 <achow101> sdaftuar: do you think end of year for all of cluster mempool to be merged to still be doable?
2732024-10-31T14:24:10 <sipa> i have addtx/removetx working in a fuzz test, working on adddependency; no mining/eviction/staging/... yet
2742024-10-31T14:24:57 <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
2752024-10-31T14:25:15 <sdaftuar> but i'm workign towards that goal, if that's what you're asking
2762024-10-31T14:26:14 <achow101> #topic Stratum v2 WG Update (sjors)
2772024-10-31T14:26:47 <Murch[m]> I think Sjors may be traveling
2782024-10-31T14:27:10 <josie> +1 , no hi from him at the beginning
2792024-10-31T14:27:15 <achow101> #topic MuSig2 WG Update (achow101)
2802024-10-31T14:27:33 <achow101> have yet to actually form a wg, but if anyone would like to join me, let me know
2812024-10-31T14:27:53 <achow101> otherwise, waiting for libsecp to do a release
2822024-10-31T14:28:10 <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
2832024-10-31T14:28:13 <gribble> https://github.com/bitcoin/bitcoin/issues/30988 | Split CConnman by vasild · Pull Request #30988 · bitcoin/bitcoin · GitHub
2842024-10-31T14:28:19 <achow101> and I've updated the pr to fix the linking issue
2852024-10-31T14:28:22 <josie> achow101: interested! (also did a lot of review of the musig2 libsecp module)
2862024-10-31T14:29:01 <achow101> #topic Legacy Wallet Removal WG Update (achow101)
2872024-10-31T14:29:12 <achow101> also no group yet, but lmk if you want to join
2882024-10-31T14:29:22 <achow101> Waiting for review on #30328
2892024-10-31T14:29:24 <gribble> https://github.com/bitcoin/bitcoin/issues/30328 | wallet: Remove IsMine from migration code by achow101 · Pull Request #30328 · bitcoin/bitcoin · GitHub
2902024-10-31T14:29:44 <achow101> and #28710 is constantly being rebased
2912024-10-31T14:29:45 <gribble> https://github.com/bitcoin/bitcoin/issues/28710 | Remove the legacy wallet and BDB dependency by achow101 · Pull Request #28710 · bitcoin/bitcoin · GitHub
2922024-10-31T14:29:45 <Murch[m]> âï¸ I want to join the Legacy Wallet Removal WG
2932024-10-31T14:29:57 <dzxzg> I would like to join
2942024-10-31T14:30:15 <achow101> Murch[m]: dzxzg: will add / dm
2952024-10-31T14:30:16 <achow101> #topic Multiprocess WG Update (ryanofsky)
2962024-10-31T14:30:58 <ajonas> hold on...
2972024-10-31T14:31:20 <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
2982024-10-31T14:31:32 <josie> at least in the short term
2992024-10-31T14:31:39 <ryanofsky> Sorry wasn't ready for this, just several PRs out for review and working on wrapper binary implementation
3002024-10-31T14:32:01 <fanquake> pinheadmz: I thought that PR would no-longer be relevant for SV2 ?
3012024-10-31T14:32:19 <pinheadmz> fanquake oh. (....oh?)
3022024-10-31T14:32:20 <TheCharlatan> ryanofsky when do you think we can add libmultiprocess as a subtree?
3032024-10-31T14:32:24 <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)
3042024-10-31T14:33:04 <hebasto> ^ so do I
3052024-10-31T14:33:10 <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
3062024-10-31T14:33:14 <ryanofsky> I don't think anything is blockign libmultiprocess as a subtree, just needs a PR
3072024-10-31T14:33:28 <pinheadmz> fanquake ok
3082024-10-31T14:33:36 <fanquake> as I don't think there is general buy in to refactoring cconman to be more "general"
3092024-10-31T14:34:39 <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
3102024-10-31T14:35:11 <cfields> pinheadmz: I definitely have my thoughts on that PR as well, just haven't had time to chime in yet.
3112024-10-31T14:35:31 <pinheadmz> so a new http will have a lot of duplicate code (GenerateWaitSockets, BindAndListen blah blah blah)
3122024-10-31T14:35:46 <pinheadmz> ok ill formalize an issue with links to my WIP stuff
3132024-10-31T14:35:50 <sipa> i think this very much depends on what the refactoring looks like
3142024-10-31T14:36:47 <pinheadmz> sipa looks like #30988 ?
3152024-10-31T14:36:49 <gribble> https://github.com/bitcoin/bitcoin/issues/30988 | Split CConnman by vasild · Pull Request #30988 · bitcoin/bitcoin · GitHub
3162024-10-31T14:36:55 <sipa> oh, there is a PR
3172024-10-31T14:37:23 <sipa> will try to give a conceptual review
3182024-10-31T14:37:40 <achow101> this discussion is slightly off topic, going to move on
3192024-10-31T14:37:44 <achow101> #topic Monitoring WG Update (b10c)
3202024-10-31T14:38:00 <b10c> hi
3212024-10-31T14:38:47 <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
3222024-10-31T14:38:59 <b10c> that's it
3232024-10-31T14:39:58 <achow101> #topic package relay WG Update (glozow)
3242024-10-31T14:40:31 <glozow> hi
3252024-10-31T14:40:37 <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.
3262024-10-31T14:40:59 <josie> glozow: and the clever acronym you have decided on for this is..?
3272024-10-31T14:41:38 <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).
3282024-10-31T14:41:41 <gribble> https://github.com/bitcoin/bitcoin/issues/30110 | refactor: TxDownloadManager + fuzzing by glozow · Pull Request #30110 · bitcoin/bitcoin · GitHub
3292024-10-31T14:41:42 <gribble> https://github.com/bitcoin/bitcoin/issues/31190 | TxDownloadManager followups by glozow · Pull Request #31190 · bitcoin/bitcoin · GitHub
3302024-10-31T14:41:45 <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
3312024-10-31T14:42:17 <sdaftuar> so we're trying to Save the Children now?
3322024-10-31T14:42:26 <glozow> Oh no ð
3332024-10-31T14:42:42 <josie> introducing BIP: Save the Children
3342024-10-31T14:43:03 <glozow> better than sibling eviction i guess
3352024-10-31T14:43:16 <jonatack> :D
3362024-10-31T14:43:55 <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 ð
3372024-10-31T14:44:00 <sipa> i remember the time when the "top" manpage listed for the -S option something about "Count parents together with dead children".
3382024-10-31T14:44:20 <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?
3392024-10-31T14:45:07 <glozow> No. It is still used in the BIP 331 implementation
3402024-10-31T14:45:46 <stickies-v> okay thanks will need to refresh my reading then
3412024-10-31T14:46:27 <achow101> #topic Ad-hoc high priority for review
3422024-10-31T14:46:27 <achow101> Anything to add or remove from https://github.com/orgs/bitcoin/projects/1/views/4
3432024-10-31T14:46:38 <achow101> (maybe we should kill this too?)
3442024-10-31T14:46:42 <jonatack> A question on my mind is, if one is interested in reviewing, do they need to / should they join the related WG?
3452024-10-31T14:47:09 <glozow> Obviously not. They just leave a review on the PR
3462024-10-31T14:47:09 <achow101> jonatack: need to - no. should they - depends on how involved they want to be
3472024-10-31T14:47:36 <achow101> certainly I intend on reviewing prs from all working groups, but i'm not going to join every single one
3482024-10-31T14:47:46 <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
3492024-10-31T14:47:47 <josie> jonatack: if just casually interested in reviewing, pinging here seems fine too! can always ping the wg champions
3502024-10-31T14:47:56 <sipa> eh, makes sense to join
3512024-10-31T14:49:02 <jonatack> ok
3522024-10-31T14:49:06 <jonatack> Question 2
3532024-10-31T14:49:19 <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 :)
3542024-10-31T14:49:57 <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
3552024-10-31T14:50:41 <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
3562024-10-31T14:51:13 <achow101> i don't think anyone here is working on those currently
3572024-10-31T14:51:19 <sipa> that also seems like something that deserves discussion from a wider group than just bitcoin core contributors
3582024-10-31T14:51:32 <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
3592024-10-31T14:51:39 <cfields> jonatack: the wgs are for Bitcoin Core the software project. Those are a different thing...
3602024-10-31T14:51:50 <cfields> right ^^
3612024-10-31T14:51:55 <jonatack> yes. i see discussions happenng, but with few people from here (?) though did see josie post about it recently
3622024-10-31T14:52:30 <jonatack> cfields: yes, am thinking about the implementations aspects
3632024-10-31T14:52:52 <jonatack> just throwing that out there. josie: cool
3642024-10-31T14:53:01 <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)
3652024-10-31T14:53:12 <achow101> Anything else to discuss?
3662024-10-31T14:53:31 <josie> glozow: +1
3672024-10-31T14:53:40 <jonatack> glozow: it's more about the trade-offs/risks/benefits of the options,afaict
3682024-10-31T14:53:57 <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
3692024-10-31T14:54:01 <jonatack> am trying to be able to evaluate objectively without getting too close to any
3702024-10-31T14:54:29 *** vysn <vysn!~vysn@user/vysn> has joined #bitcoin-core-dev
3712024-10-31T14:54:47 <jonatack> sipa: sgtm
3722024-10-31T14:55:07 <achow101> #endmeeting
3732024-10-31T14:55:10 <dzxzg> Â thanks
3742024-10-31T14:55:18 <hebasto> could repo owners look into #31176 and enable two additional github actions, if that's okay?
3752024-10-31T14:55:19 <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
3762024-10-31T14:55:24 <josie> greating meeting everyone, really cool to get insights into what everyone is working on
3772024-10-31T14:55:48 <fanquake> hebasto: i think that needs some more concpetual discussion first. will leave a comment
3782024-10-31T14:56:01 <hebasto> okay
3792024-10-31T14:59:44 *** marcofleon <marcofleon!~marcofleo@82.163.218.33> has quit IRC (Quit: Client closed)
3802024-10-31T14:59:55 *** Emc99 <Emc99!~Emc99@212.129.79.13> has joined #bitcoin-core-dev
3812024-10-31T15:01:20 *** Emc99 <Emc99!~Emc99@212.129.79.13> has quit IRC (Client Quit)
3822024-10-31T15:01:42 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has joined #bitcoin-core-dev
3832024-10-31T15:05:54 <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
3842024-10-31T15:05:54 <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.
3852024-10-31T15:07:46 *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has joined #bitcoin-core-dev
3862024-10-31T15:09:20 <jonatack> glozow: yes, agree, and +1 on the open aspects. will join some of the signal groups and see
3872024-10-31T15:10:18 *** dzxzg <dzxzg!~dzxzg@user/dzxzg> has quit IRC (Quit: Client closed)
3882024-10-31T15:11:09 <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.
3892024-10-31T15:11:17 <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.
3902024-10-31T15:11:30 *** John123 <John123!~John123@45.250.237.9> has quit IRC (Quit: Client closed)
3912024-10-31T15:13:39 <sdaftuar> lightlike: i agree but i'd just add that i think maintainers should use their judgement on that point (as they always have)
3922024-10-31T15:26:15 *** l0rinc <l0rinc!~l0rinc@94.44.250.7> has quit IRC (Quit: Client closed)
3932024-10-31T15:30:07 *** Guest64 <Guest64!~Guest64@2a09:bac3:83f3:aa::11:1ad> has joined #bitcoin-core-dev
3942024-10-31T15:30:14 *** Guest64 <Guest64!~Guest64@2a09:bac3:83f3:aa::11:1ad> has quit IRC (Client Quit)
3952024-10-31T15:33:37 *** zeropoint <zeropoint!~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net> has joined #bitcoin-core-dev
3962024-10-31T15:33:58 *** John123 <John123!~John123@45.250.237.9> has joined #bitcoin-core-dev
3972024-10-31T15:37:05 *** storopoli <storopoli!~storopoli@169.150.198.70> has joined #bitcoin-core-dev
3982024-10-31T15:37:06 *** storopoli <storopoli!~storopoli@user/storopoli> has quit IRC (Excess Flood)
3992024-10-31T15:39:31 *** John123 <John123!~John123@45.250.237.9> has quit IRC (Quit: Client closed)
4002024-10-31T16:02:53 <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
4012024-10-31T16:10:35 <stickies-v> oooh it is, ty instagibbs - i'd read that in the past but didn't quite link it w orphanage. makes sense
4022024-10-31T16:10:57 *** juleeho <juleeho!~juleeho@81.174.12.248> has joined #bitcoin-core-dev
4032024-10-31T16:17:00 *** vysn <vysn!~vysn@user/vysn> has quit IRC (Ping timeout: 252 seconds)
4042024-10-31T16:19:13 *** Guest78 <Guest78!~Guest78@2a02:b025:10:73f6:d5c8:f52f:9cfe:b28f> has joined #bitcoin-core-dev
4052024-10-31T16:20:37 *** juleeho-droid <juleeho-droid!~juleeho-d@81.174.12.248> has joined #bitcoin-core-dev
4062024-10-31T16:23:41 *** Guest78 <Guest78!~Guest78@2a02:b025:10:73f6:d5c8:f52f:9cfe:b28f> has quit IRC (Client Quit)
4072024-10-31T16:30:55 *** juleeho-droid <juleeho-droid!~juleeho-d@user/juleeho> has quit IRC (Remote host closed the connection)
4082024-10-31T16:31:28 *** juleeho-droid <juleeho-droid!~juleeho-d@user/juleeho> has joined #bitcoin-core-dev
4092024-10-31T16:33:16 *** juleeho-droid is now known as juleeho_
4102024-10-31T16:44:16 *** pablomartin <pablomartin!~pablomart@185.137.36.33> has joined #bitcoin-core-dev
4112024-10-31T16:48:56 *** storopoli <storopoli!~storopoli@user/storopoli> has joined #bitcoin-core-dev
4122024-10-31T16:48:57 *** storopoli <storopoli!~storopoli@user/storopoli> has quit IRC (Excess Flood)
4132024-10-31T16:49:22 *** storopoli <storopoli!~storopoli@user/storopoli> has joined #bitcoin-core-dev
4142024-10-31T16:49:23 *** storopoli <storopoli!~storopoli@user/storopoli> has quit IRC (Excess Flood)
4152024-10-31T16:53:18 *** juleeho <juleeho!~juleeho@user/juleeho> has quit IRC (Read error: Connection reset by peer)
4162024-10-31T16:53:35 *** storopoli <storopoli!~storopoli@user/storopoli> has joined #bitcoin-core-dev
4172024-10-31T16:53:35 *** storopoli <storopoli!~storopoli@user/storopoli> has quit IRC (Excess Flood)
4182024-10-31T16:53:59 *** storopoli <storopoli!~storopoli@user/storopoli> has joined #bitcoin-core-dev
4192024-10-31T16:54:09 *** storopoli <storopoli!~storopoli@user/storopoli> has quit IRC (Max SendQ exceeded)
4202024-10-31T16:56:12 *** storopoli <storopoli!~storopoli@169.150.198.70> has joined #bitcoin-core-dev
4212024-10-31T16:56:13 *** storopoli <storopoli!~storopoli@user/storopoli> has quit IRC (Excess Flood)
4222024-10-31T16:56:35 *** storopoli <storopoli!~storopoli@user/storopoli> has joined #bitcoin-core-dev
4232024-10-31T16:56:36 *** juleeho-droid <juleeho-droid!~juleeho-d@user/juleeho> has joined #bitcoin-core-dev
4242024-10-31T16:56:36 *** storopoli <storopoli!~storopoli@user/storopoli> has quit IRC (Excess Flood)
4252024-10-31T16:59:15 *** juleeho_ <juleeho_!~juleeho-d@user/juleeho> has quit IRC (Ping timeout: 265 seconds)
4262024-10-31T17:03:29 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Read error: Connection reset by peer)
4272024-10-31T17:03:59 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
4282024-10-31T17:16:31 *** pablomartin <pablomartin!~pablomart@185.137.36.33> has quit IRC (Ping timeout: 252 seconds)
4292024-10-31T17:17:36 <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
4302024-10-31T17:19:26 *** mcey_ <mcey_!~emcy@148.252.146.198> has quit IRC (Remote host closed the connection)
4312024-10-31T17:19:49 *** mcey_ <mcey_!~emcy@148.252.146.198> has joined #bitcoin-core-dev
4322024-10-31T17:21:04 *** pablomartin <pablomartin!~pablomart@194.156.224.193> has joined #bitcoin-core-dev
4332024-10-31T17:22:49 *** szkl <szkl!uid110435@id-110435.uxbridge.irccloud.com> has joined #bitcoin-core-dev
4342024-10-31T17:26:06 *** pablomartin <pablomartin!~pablomart@194.156.224.193> has quit IRC (Remote host closed the connection)
4352024-10-31T17:31:01 *** jeremyrubin <jeremyrubin!~jeremyrub@ec2-44-199-24-18.compute-1.amazonaws.com> has joined #bitcoin-core-dev
4362024-10-31T17:31:53 *** vysn <vysn!~vysn@user/vysn> has joined #bitcoin-core-dev
4372024-10-31T17:46:38 *** pablomartin <pablomartin!~pablomart@152.170.208.150> has joined #bitcoin-core-dev
4382024-10-31T17:48:57 *** pablomartin <pablomartin!~pablomart@152.170.208.150> has quit IRC (Client Quit)
4392024-10-31T18:02:25 *** juleeho-droid <juleeho-droid!~juleeho-d@user/juleeho> has quit IRC (Read error: Connection reset by peer)
4402024-10-31T18:04:41 *** juleeho-droid <juleeho-droid!~juleeho-d@user/juleeho> has joined #bitcoin-core-dev
4412024-10-31T18:04:52 *** juleeho-droid <juleeho-droid!~juleeho-d@user/juleeho> has quit IRC (Remote host closed the connection)
4422024-10-31T18:07:18 <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
4432024-10-31T18:08:49 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Read error: Connection reset by peer)
4442024-10-31T18:09:23 *** John123 <John123!~John123@45.250.237.9> has joined #bitcoin-core-dev
4452024-10-31T18:10:43 <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
4462024-10-31T18:11:07 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
4472024-10-31T18:11:26 *** juleeho <juleeho!~juleeho@77-32-118-9.dyn.eolo.it> has joined #bitcoin-core-dev
4482024-10-31T18:18:40 *** juleeho <juleeho!~juleeho@77-32-118-9.dyn.eolo.it> has quit IRC (Remote host closed the connection)
4492024-10-31T19:06:22 *** Artea <Artea!~Lufia@artea.pt> has quit IRC (Quit: ZNC 1.9.1 - https://znc.in)
4502024-10-31T19:57:11 *** John123 <John123!~John123@45.250.237.9> has quit IRC (Quit: Client closed)
4512024-10-31T20:06:19 *** John123 <John123!~John123@45.250.237.9> has joined #bitcoin-core-dev
4522024-10-31T20:16:14 *** achow101 <achow101!~achow101@user/achow101> has quit IRC (Ping timeout: 260 seconds)
4532024-10-31T20:16:48 *** achow101 <achow101!~achow101@user/achow101> has joined #bitcoin-core-dev
4542024-10-31T20:41:00 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 252 seconds)
4552024-10-31T20:42:46 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
4562024-10-31T20:54:42 *** John123 <John123!~John123@45.250.237.9> has quit IRC (Quit: Client closed)
4572024-10-31T21:13:57 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Remote host closed the connection)
4582024-10-31T21:14:22 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
4592024-10-31T21:31:31 *** vysn <vysn!~vysn@user/vysn> has quit IRC (Remote host closed the connection)
4602024-10-31T21:34:43 *** Talkless <Talkless!~Talkless@mail.dargis.net> has joined #bitcoin-core-dev
4612024-10-31T21:34:59 *** achow101 <achow101!~achow101@user/achow101> has quit IRC (Ping timeout: 260 seconds)
4622024-10-31T21:35:28 *** achow101 <achow101!~achow101@user/achow101> has joined #bitcoin-core-dev
4632024-10-31T21:37:32 *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has quit IRC (Quit: Leaving)
4642024-10-31T21:43:15 *** preimage <preimage!~halosghos@user/halosghost> has quit IRC (Quit: WeeChat 4.4.2)
4652024-10-31T23:00:15 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has quit IRC (Quit: Going offline, see ya! (www.adiirc.com))
4662024-10-31T23:03:39 *** achow101_ <achow101_!~achow101@user/achow101> has joined #bitcoin-core-dev
4672024-10-31T23:03:51 *** achow101 <achow101!~achow101@user/achow101> has quit IRC (Ping timeout: 272 seconds)
4682024-10-31T23:08:18 *** achow101 <achow101!~achow101@user/achow101> has joined #bitcoin-core-dev
4692024-10-31T23:08:19 *** achow101_ <achow101_!~achow101@user/achow101> has quit IRC (Ping timeout: 260 seconds)
4702024-10-31T23:10:54 *** Talkless <Talkless!~Talkless@mail.dargis.net> has quit IRC (Remote host closed the connection)