06:20:10 Hello everyone, 06:20:10 first of all, it is an honor to play with FCMP++ and witness the great work done here! 06:20:10 I would like to give an update regarding the task 1 (https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/645#task-1-c).[... more lines follow, see https://mrelay.p2pool.observer/e/_-aQ2f8KanJhMVkw ] 16:59:20 Meeting in 1 hour 18:00:14 Meeting time. Hello! https://github.com/monero-project/meta/issues/1382 18:00:29 hey 18:00:29 Hello 18:01:25 waves 18:02:02 Alright, on to the reports about last week 18:02:41 @dangerousfreedom:matrix.org left a report in this room this morning UTC, about making progress with the curves relevant for FCMP++. Interesting stuff. 18:02:47 Beta stressnet launched, kicked off Phase 1 of the integration audit 18:03:18 Made some solid progress on I2P work 18:03:22 testing, small fixes, clean-up, resolve merge conflicts for the rpc and cli and everything downstream 18:03:22 also I was reminded that the "restore height on wallet creation" is still an issue, and I did some research again. IMO this PR (https://github.com/monero-project/monero/pull/10165) would help (if done for release, so it can be used by GUI) 18:03:31 I did make some progress regarding Polyseed in the CLI wallet app, but not that much 18:04:02 hi, multisig WIP 18:06:39 Those 26 days of deviation for mainnet surprise me a bit. I got only about 5 days difference when I compared a Polyseed birthday based height calculcated once without daemon connection, and once with. Maybe not exactly the same thing? 18:06:41 @rbunner7 do you already have a plan how you will get the restore height for the Polyseed? 18:07:40 What is done already elsewhere in the code: Ask the daemon if it's possible to reach one, and do some estimate if not. (That's what I claim currently gives about 5 days of difference for mainnet) 18:07:56 Maybe I have to check again 18:08:46 Your approximation kicks in in the "no daemon" case, right? So Polyseed birthday to blockheight translation will benefit 18:10:13 howdy, sorry I'm late. Working on beta stressnet, and some potential DoS mitigations 18:10:17 Will take a closer look at your PR this weekend and compare 18:11:40 just checked again, getting 18888 blocks (~26.2 days) deviation > <@rbrunner7> Those 26 days of deviation for mainnet surprise me a bit. I got only about 5 days difference when I compared a Polyseed birthday based height calculcated once without daemon connection, and once with. Maybe not exactly the same thing? 18:11:56 @rbrunner7: yes 18:12:38 Ah, I remember, I think I got those 5 days of difference for a Polyseed that was a year old or so 18:13:24 Will check again in any case, might be interesting 18:14:26 btw Feather wallet uses a Websocket service to get the restore height from a daemon before the wallet is created, AFAICT 18:14:55 else they use a similar approach to estimate the restore height, based on a known height from last release 18:15:37 Don't know, I just saw that the wallet loads a file with correction values if no daemon connection is possible. @tobtoht:monero.social is a bit of a perfectionist :) 18:16:20 I remember to wonder whether the code to evaluate and write that file is open sourced or not ... 18:17:17 I saw the Cypherstack audit of the GBPs is discontinued 18:17:37 https://github.com/cypherstack/generalized-bulletproofs-fix/issues/2#issuecomment-4370448089 18:17:44 You mean they started, but finally gave up? 18:18:20 Something like that 18:19:17 I don't understand much of the things discussed there, so can't judge whether progress was achieved, and if yes how much 18:19:51 So hardfork of the beta testnet to FCMP++ is in 2 days? 18:20:22 Ah, beta stressnet 18:20:23 "testnet" would be a bit misleading 18:20:37 @ixr3:matrix.org: Erm, I wouldn't exactly say that's the conclusion from that comment. Have they responded to that comment elsewhere? 18:21:55 @rbrunner7: Yep :) 18:23:00 Is there a party somewhere? :) 18:23:12 No, seriously, quite a milestone I would say 18:23:37 Not that I know of heh 18:24:20 @jberman: They didn't respond, but doesn't KayabaNerve gently asked them to end it? That's how I read it. I may be wrong. 18:27:55 My read of that comment is just kayaba not wanting to demand continued work on it as it's unpaid. And the general plan with GBP's is to continue with zk security as an additional qualified independent party. Though CS is obviously still free to respond there 18:28:19 Could you call this beta stressnet code something like "feature complete"? Except multisig, and hardware wallet support maybe 18:29:16 and hot/cold wallets and tx proofs (for now, jeffro mentioned he's aiming to have hot/cold wallets complete before beta is finished) 18:29:47 Sounds good 18:30:32 Will be interesting to see how this software reacts if the network gets stressed 18:31:29 How about that PoW for large transactions? How was that called again? 18:32:02 ah yes, PoWER 18:32:08 @jberman: This is true. Working on it now, I want to have it done by the end of the week (fingers crossed) 18:32:32 Depends on if I can lock in and stop jumping between different tasks 18:33:00 @hinto:monero.social has implemented PoWER ( https://github.com/seraphis-migration/monero/pull/230 ), will review that fully and we can aim to have that in for beta too 18:33:34 I think it would be nice to have that in early. Seems to me it's an important part of the overall system 18:33:48 @jeffro256: When I'm in a being-locked-in competition and my opponent is Jeffro 18:35:34 @rbrunner7: fwiw it shouldn't have a very noticeable effect on perf (if noticeable at all), it's more of a layered in DoS protection mechanism 18:36:03 Will beta include P2P Encryption+Authentication? 18:36:16 I see. But still important to test a brand new and not exactly simple part of the whole system 18:36:53 @ixr3:matrix.org: ah right, I mentioned we can get that tested in beta stressnet too. I think it would be good to get in. I can start a list of things we want in for the beta 18:38:04 Good that you can hardfork the thing pretty much as often as you like :) 18:38:37 @jberman: I hate that it increases the attack surface 18:39:08 @ixr3:matrix.org: Interesting, this is a good idea 18:39:29 I hate that nodes default relay data in plaintext 🙃 18:40:02 TBC Authentication wouldn't really be present at the beginning AFAIK, just encryption 18:40:10 https://github.com/seraphis-migration/monero/issues/354 18:40:26 Which changes the failure mode for relay-level confidentiality from passive to active 18:40:42 "wishlist", how cute 18:40:51 And this would just be integrating the existing P2P encryption PR? 18:40:54 Using TLS 18:41:05 yep https://github.com/monero-project/monero/pull/8996 18:41:26 That's a solid start I guess? 18:45:16 Alright. Quite a large undertaking, getting this all in. 18:45:27 Do we have something left to discuss today? 18:47:21 Does not look like it. So thanks everybody for participation, and read you again next week! 18:47:49 thanks everyone 18:50:46 Thanks :)