<r​brunner7:monero.social> Meeting in a bit less than 1 hour, that is UTC 18:00. Now also Europeans enjoy DST.

<r​brunner7:monero.social> Meeting time. Hello! monero-project/meta #1179

<s​needlewoods:monero.social> Hello

<j​effro256:monero.social> Howdy

<s​yntheticbird:monero.social> hello

<r​brunner7:monero.social> Alright. What is there to report from last week?

<r​brunner7:monero.social> I could finally reproduce the multisig error that SNeedlewoods corrected

<r​brunner7:monero.social> As a small success ...

<j​berman:monero.social> *waves*

<r​brunner7:monero.social> If nobody waves, the meeting is less than complete :)

<j​effro256:monero.social> me: Carrot scanning in `wallet2` is confirmed and tested: github.com/monero-project/monero/bl…unit_tests/wallet_scanning.cpp#L657

<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: jeffro256/carrot 76449ab

<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

<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)

<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

<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

<r​brunner7:monero.social> That's quite a lot

<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?

<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

<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)

<r​brunner7:monero.social> Was that a test only, will you continue to work on the stage development branch?

<j​berman:monero.social> We're been working on fcmp++-stage for some weeks now and will continue to

<t​obtoht:monero.social> "which presumably would need PR 9801" <- 9801 + 9440

<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

<r​brunner7:monero.social> And build system in general, as it sounds

<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?

<r​brunner7:monero.social> *very busy

<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!

<r​brunner7:monero.social> I wonder how we will look back to these months in a few years' time ...

<s​pirobel:kernal.eu> fondly?

<s​needlewoods:monero.social> thanks everyone,

<s​needlewoods:monero.social> I hope until next week I have at least a draft PR for monero-gui

<r​brunner7:monero.social> I hope so!

<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 :)

<s​pirobel:kernal.eu> "cancler on brink of second bailout after ... monerochan ... "

<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 ...

<s​pirobel:kernal.eu> ... being multilingual also helps. Having the rust implementation means more eyes and more scrutiny. That wasnt the case before

<s​yntheticbird:monero.social> I'm a gambler and I want us to take this bait

<s​yntheticbird:monero.social> bet*