16:49:13 Meeting in a bit more than 1 hour 18:00:04 Meeting time. Hello! https://github.com/monero-project/meta/issues/1438 18:00:08 Hello 18:00:13 hey 18:00:57 Hi 18:01:44 Alright, any reports since last meeting? 18:01:50 hi 18:02:02 waves 18:02:16 Howdy 18:02:20 reviews, review comments and some more investigation into the slow sync with large subaddress lookahead 18:02:23 Not much from me, waiting for some more review activity on my Polyseed PR ... 18:02:41 @rbrunner7: Noted 18:03:34 mostly PR's from stressnet / improvements to monerod where notable 18:03:36 Me: reviewed some PRs, investigated ways to improve wallet sync times (which resulted in some findings, see #11063), regular stuff 18:05:05 I try now to sync stressnet to help later with multisig testing and noticed that this will take my notebook literally days ... where are the stressnet checkpoints :) 18:05:28 me: lots of PR review 18:06:46 I lean in favor of just starting a new beta v3 at this point that includes the latest round of changes to tx relay v2, to alleviate disk space reqs for stressnet participants 18:07:22 Well, if that gains loose consensus today I can relieve my poor notebook today still 18:07:35 Yeah, we could start the v3 with a min block size equal to or greater than currently realized block sizes 18:08:00 To remove the warm-up period 18:08:15 It's not only the disk space, as I said it's also the verifying of all those large blocks 18:08:20 I'm definitely a nack on messing with block size stuff further hah, last time we tried that was not fun 18:08:49 What do you mean with "min blocksize"? 18:09:13 The threshold when some fee changes kick in? 18:10:28 We already change the min block size for FCMP++ though, it would be a single-line config change 18:10:29 To a line we already change 18:10:43 By min block size, I mean the penalty free zone 18:11:02 That's what it's called in the code, which is a bad name IMO 18:12:05 I don't mean actually putting a hard minimum on the block weight 18:13:00 I guess if @jberman:monero.social and @jeffro256:monero.social agree to start over then stressnet V2 is history quite soon? 18:13:59 (news from the front: 9440 merged, sets way for 10359) 18:14:43 raising penalty free zone doesn't sound terrible to me actually, fair rebuttal 18:15:00 tobtoht: Does that one need anything else before merge? 18:15:34 It has approvals from Ukoe and I 18:15:40 @rbrunner7: still pending on https://github.com/seraphis-migration/monero/pull/450 18:15:54 Anything that j-berman wants to add to 10359? 18:16:09 That would be good to get out of the way so that we can start chugging on the other FCMP++ PRs 18:16:30 @jeffro256: nothing planned on my end 18:16:57 jpk68: Just a rebase and a 4 line diff to activate Guix rust machinery for CI. 18:16:59 AFAICT discussions mainly revolved around Rust integration in general, not anything specific to the Rust FFI in that PR 18:17:29 +1 18:17:34 @tobtoht: oh yes, sorry will do that asap 18:19:02 Well, the "Rust ship" has sailed. People who don't agree on fundamental grounds probably have to stay on the old chain ... 18:20:16 At least building is no problem, just a compiler more that is involved, as it looks from the outside. But of course lots and lots of library stuff drawn in. 18:21:30 Ok, looks that's it about the reports. Anything to discuss today beyond those? 18:22:34 Does not look like it. Thanks for attending everybody, read you again in 1 week! 18:22:55 Thanks, everyone :)) 18:22:55 Thanks everyone 18:23:13 Jinx! 18:24:17 "9% of total synced, estimated 1.7 days left" Hmm. A stressnet V3 would restart at current testnet height I guess? 18:25:35 Yes 18:30:46 @kayabanerve:matrix.org: another nudge on https://github.com/monero-oxide/monero-oxide/pull/187 and https://github.com/monero-oxide/monero-oxide/pull/188 now that https://github.com/monero-oxide/monero-oxide/pull/191 has been merged for 10 days 18:38:34 20:06:46 I lean in favor of just starting a new beta v3 at this point that includes the latest round of changes to tx relay v2, to alleviate disk space reqs for stressnet participants 18:38:35 +1 from me, I am running my stressnet explorer from a remote RPC due to size, and a few changes that live on staging could also be introduced (including the double-spend fix during the waiting period) 18:55:03 The tx output serialization was changed on fcmp++-stage, which is a hard fork change 18:57:02 yeah, so it'd be on v3? 19:12:15 10359 docker fails jberman 19:14:10 oh let me fix that 22:06:12 +1 (and new rebase to latest master?) > <@jberman> I lean in favor of just starting a new beta v3 at this point that includes the latest round of changes to tx relay v2, to alleviate disk space reqs for stressnet participants