17:04:23 <m-relay> <r​brunner7:monero.social> Meeting in a bit less than 1 hour, that is UTC 18:00. Now also Europeans enjoy DST.
18:00:01 <m-relay> <r​brunner7:monero.social> Meeting time. Hello! https://github.com/monero-project/meta/issues/1179
18:00:41 <m-relay> <s​needlewoods:monero.social> Hello
18:00:59 <m-relay> <j​effro256:monero.social> Howdy
18:01:05 <m-relay> <s​yntheticbird:monero.social> hello
18:02:07 <m-relay> <r​brunner7:monero.social> Alright. What is there to report from last week?
18:02:28 <m-relay> <r​brunner7:monero.social> I could finally reproduce the multisig error that SNeedlewoods corrected
18:02:43 <m-relay> <r​brunner7:monero.social> As a small success ...
18:03:07 <m-relay> <j​berman:monero.social> *waves*
18:03:25 <m-relay> <r​brunner7:monero.social> If nobody waves, the meeting is less than complete :)
18:04:25 <m-relay> <j​effro256:monero.social> me: Carrot scanning in `wallet2` is confirmed and tested: https://github.com/monero-project/monero/blob/40b04ef372d191f8991da22c220ccce2ba457b47/tests/unit_tests/wallet_scanning.cpp#L657
18:05:26 <m-relay> <j​effro256:monero.social> I made a tiny tweak to the Carrot protocol that shouldn't affect security but makes supporting hybrid key hierarchies a lot less annoying: https://github.com/jeffro256/carrot/commit/76449ab073a94a2f001d2c21951d3c6053db6a04
18:06:11 <m-relay> <j​berman:monero.social> me: implemented banning torsioned output pubkeys and commitments at consensus at the fork (after the fork, wallets won't have to do the expensive check for/clear torsion when building the tree), fixed a recently introduced issue with reorg handling in the wallet scanner tree builder, implemented a static table for FCMP++ proof size (calculating it from n inputs and n layers can be<clipped messag
18:06:12 <m-relay> <j​berman:monero.social>  slow), just implemented banning n_tree_layers >12 to keep the table small and portable (the tree supports a max of ~200 quadrillion outputs at 12 layers by my math)
18:06:14 <m-relay> <j​berman:monero.social> This week I'm going to work on including the tree root in the block's PoW hash so clients can (eventually) verify PoW on the daemon's reported tree root, and therefore have a solid degree of confidence in the tree the client is using to construct or verify txs 
18:06:16 <m-relay> <j​berman:monero.social> Also going to write up the blog post for the FCMP++ competition and commence the marketing blitz with xmrack 's help
18:07:17 <m-relay> <r​brunner7:monero.social> That's quite a lot
18:09:32 <m-relay> <r​brunner7:monero.social> jeffro256: So this is strictly only about Janus protection and nothing else, so we don't have to worry about invalidating the Carrot audit results?
18:12:00 <m-relay> <j​effro256:monero.social> Validating the Janus protection was in-scope for the Carrot audit, so technically it invalidates it, but the security proof / concepts involved literally shouldn't change whatsoever, since the `K_s` in `anchor_sp` wasn't part of the reasoning for why Janus protection held
18:14:27 <m-relay> <j​berman:monero.social> Also of note, jeffro256 tobtoht (and little bit of work on my end) got the seraphis-migration/fcmp++-stage development branch back onto master, CI builds are passing minus GUIX stuff which presumably would need PR 9801 (special shoutout to tobtoht for identifying / fixing some pesky build issues)
18:15:10 <m-relay> <r​brunner7:monero.social> Was that a test only, will you continue to work on the stage development branch?
18:15:39 <m-relay> <j​berman:monero.social> We're been working on fcmp++-stage for some weeks now and will continue to
18:15:57 <m-relay> <t​obtoht:monero.social> "which presumably would need PR 9801" <- 9801 + 9440
18:16:09 <m-relay> <r​brunner7:monero.social> Yeah, I mean too early to continue work on master, so I guess that was a test to see where you stand with conflicts
18:16:54 <m-relay> <r​brunner7:monero.social> And build system in general, as it sounds
18:18:17 <m-relay> <r​brunner7:monero.social> Ok, everybody is very busing, and moving fast, which is nice. Do we have to discuss something in particular beyond these reports?
18:18:27 <m-relay> <r​brunner7:monero.social> *very busy
18:19:40 <m-relay> <r​brunner7:monero.social> Doesn't look like it, so I think we can close already. Thanks everybody for attending, read you in 1 week!
18:20:14 <m-relay> <r​brunner7:monero.social> I wonder how we will look back to these months in a few years' time ...
18:21:11 <m-relay> <s​pirobel:kernal.eu> fondly?
18:22:01 <m-relay> <s​needlewoods:monero.social> thanks everyone,
18:22:02 <m-relay> <s​needlewoods:monero.social> I hope until next week I have at least a draft PR for monero-gui
18:22:04 <m-relay> <r​brunner7:monero.social> I hope so!
18:23:13 <m-relay> <r​brunner7:monero.social> "The total breakdown of the Monero network in Summer 2027 could be traced back to some Carrot Janus protection modification that was thought to be totally harmless, but ...."     can't resist :)
18:25:04 <m-relay> <s​pirobel:kernal.eu> "cancler on brink of second bailout after ... monerochan ... "
18:26:51 <m-relay> <r​brunner7:monero.social> Seriously, I am glad we have many competent and attentive eyes on what is happening. Remember for example the Wownero stunt with the DSA stuck years in the past ...
18:30:38 <m-relay> <s​pirobel:kernal.eu> ... being multilingual also helps. Having the rust implementation means more eyes and more scrutiny. That wasnt the case before
18:31:45 <m-relay> <s​yntheticbird:monero.social> I'm a gambler and I want us to take this bait
18:31:51 <m-relay> <s​yntheticbird:monero.social> bet*