05:00:53 Hello everyone, 05:00:53 a second update on my project after some private discussions with kayaba. I decided to re-evaluate what I want to achieve with this project. So I believe I will only be able to give a "final first draft" by mid-end of August as I included others things that I want to try as well. 05:00:53 What was achieved so far: 05:00:53 [... more lines follow, see https://mrelay.p2pool.observer/e/34ix-pMLZTdFRzdZ ] 16:52:42 Thanks, @dangerousfreedom:matrix.org , for this detailed report. 16:53:25 Meeting in a bit more than 1 hour 18:00:01 Meeting time. Hello! https://github.com/monero-project/meta/issues/1416 18:00:05 hi 18:00:50 Hello 18:01:24 waves 18:02:29 On to the reports from last week! 18:02:39 @dangerousfreedom:matrix.org left a report a while before this meeting, in this room. Looks like he made great progress. Not 100% what was planned, but still solid. 18:03:01 Mostly reviews, also started to look into this (https://github.com/oxen-io/oxen-core/pull/1466) refresh lock issue that selsta brought up in the last meeting, but with my limited knowledge I didn't spot any issue so far. 18:03:31 Me: worked on baking I2P support into the GUI, plus regular patches as normal; helped with testing Qt6 builds of the GUI 18:04:10 I myself did two passes through my Polyseed PR, based on review comments from 3 people (thanks to all!), and I could update with improved code. 18:04:30 Maybe @jeffro256:monero.social will find time for a re-review, or anybody else for a first review 18:04:31 me: continuing handling upstream FCMP++ PR's, beta stressnet v2.1, and continuing finalizing investigation into sporadic observed double spends on stressnet 18:05:07 It's this here of course: https://github.com/monero-project/monero/pull/10765 18:05:31 @jberman:monero.social: So these double-spends are still with you? 18:05:53 Seems to be a tough nut to crack :) 18:07:37 @rucknium mentioned one was still observed one with a fix in place, and I haven't yet had a chance to dig into those logs. My initial take is that it's revealing multiple interconnected / related upstream bugs that only trigger on very rare occassion, that's exacerbated by stressnet 18:08:23 So this goes into a long row of things that broke when real pressure was applied to a Monero network ... 18:08:46 No "battle-tested" without any battle, lol 18:09:01 essentially yes 18:11:41 Alright, seems that's about it regarding reports. 18:11:52 Do we have to discuss something this week beyond those? 18:12:17 Howdy sorry I'm late 18:12:42 Right on time still to drop your report :) 18:13:01 Not too much to report from me other then I'm still deep in reviewland 18:14:08 Ok, I guess that progress if you are not mostly producing more mountains of code anymore 18:14:41 Are any bigger programming jobs left at all on the way to FCMP++? 18:15:04 With emphasis on "bigger" 18:15:38 I opened multiple PRs in regards to our test suite that would need review in case anyone has time 18:17:45 On the normal Monero repo? Somehow can't see multiples 18:18:40 @rbrunner7: Multisig, HW 18:18:41 Ah, no, just did not go back far enough, sorry for the false alarm 18:18:54 hot/cold is mostly done, tx proofs are mostly done 18:19:10 consensus code is mostly done 18:19:17 the rest of Carrot is mostly done 18:19:49 HW support is mostly done on the hot side, the bulk of the work left for HW support is on the HW side 18:20:12 So for the core repo, mainly Multisig which Koe is working on 18:20:24 Sounds good 18:20:40 Does multisig require a separate audit? 18:21:02 @rbrunner7: too slow, but I think selsta is referring to these 18:21:02 10818 10820 10823 10826 10844 10855 18:22:17 @jpk68:matrix.org: Maybe depends on the definition of "require" ... I am pessimistic that we would find the funds to do a proper audit there, but that's only MHO. 18:22:19 @jpk68:matrix.org: If we were to audit yes 18:22:44 AKA it's not under the scope of any currently contracted or planned audit 18:23:00 It's "experimental", all is good :) 18:24:15 Maybe we will end up using the improved Rust implementation of a much more solid multisig approach, one that does not result in 1000 messages passed back and forth if you want 7 signers or so .... 18:25:47 Alright, looks like we are through for today. Thanks everybody for attending, read you again next week! 18:25:58 thanks everyone, cu 18:26:03 Thanks everyone ! 18:26:05 Thanks :)) 18:27:20 I think I actually did 7 signers once, to stress-test the MMS, and it did go up into the hundreds of messages exchanged before all the keys were established 18:29:23 Yeah, thankfully FROST doesn't have exponentially big signings / setup ceremonies 18:29:49 Ande that's what Kayaba implemented for FCMP++ SA/L multisig in the Rust lib, amongst other things 20:34:14 multisig is mostly done, just has some wallet2 issues blocking the test 20:34:37 on pause while I slowly review other things