16:47:32 <m-relay> <r​brunner7:monero.social> Meeting in a bit more than 1 hour
18:00:01 <m-relay> <r​brunner7:monero.social> Meeting time. Hello! https://github.com/monero-project/meta/issues/1270
18:00:32 <m-relay> <s​needlewoods_xmr:matrix.org> Hello
18:01:08 <m-relay> <j​berman:monero.social> *waves*
18:01:48 <m-relay> <p​arasew:matrix.org> helo
18:02:11 <m-relay> <s​pirobel:kernal.eu> hi
18:03:04 <m-relay> <r​brunner7:monero.social> Seems jberman is already typing his report :)
18:03:14 <m-relay> <r​brunner7:monero.social> Yeah, what about last week?
18:03:58 <m-relay> <s​needlewoods_xmr:matrix.org> down to 77 `m_wallet`, also cleaned up a lot and went from ~1200 unstaged changes to ~100, also began to write some notes for the PR that will hopefully be made in foreseeable future
18:04:17 <m-relay> <r​brunner7:monero.social> That sounds splendid
18:05:55 <m-relay> <r​brunner7:monero.social> Did you continue to try to make a static build?
18:06:23 <m-relay> <j​berman:monero.social> me: completed FCMP++ refresh refactor PR 81 (jeffro approved) fortunately was able to make the code much cleaner without chaning the async structure as I originally posited, opened PR for daemons to kick invalid txs from pool upon popping blocks (e.g. to handle a reorg) although seems I'm in the minority in favor of that #10085, and for wallets to identify spends in the pool upon <clipped messag
18:06:23 <m-relay> <j​berman:monero.social> restore/if they're not the sending wallet (#10083). Stressnet launch nearly here (hopefully after a final round of testing from ofrn)
18:07:16 <m-relay> <j​berman:monero.social> I've also re-started on documentation for the fcmp++ integration, and will harden my plan for upstreaming my side of changes as I work through documentation
18:08:33 <m-relay> <r​brunner7:monero.social> "This change kicks these invalid txs from the pool" I can see why that could be controversial, especially compared with a much shorter keep-alive time, not those overly long 7 days
18:09:32 <m-relay> <j​effro256:monero.social> Howdy
18:10:28 <m-relay> <r​brunner7:monero.social> A reviewing / merging issue was opened somewhere that might be worth mentioning here, right? Don't have a link handy
18:10:55 <m-relay> <j​effro256:monero.social> The main downside is that it opens the door for other people  o perform double spend attacks when the reorg depth >= 10
18:11:31 <m-relay> <j​effro256:monero.social> I made a first draft of the Rusty Carrot library: https://github.com/jeffro256/carrot-rs
18:14:12 <m-relay> <r​brunner7:monero.social> Got it in the meantime: https://github.com/seraphis-migration/monero/issues/103
18:14:36 <m-relay> <j​berman:monero.social> ah, didn't know what you were referring to
18:14:59 <m-relay> <j​berman:monero.social> ya that issue is a solid tracking issue by jeffro / plan
18:15:51 <m-relay> <r​brunner7:monero.social> That will need quite some beating of drums to get people outside of our little circle here to read into FCMP++ tech and start to review ...
18:17:44 <m-relay> <r​brunner7:monero.social> I think it's not that often that one has to implement the same bigger thing in two different languages, like jeffro256 did now with Carrot. Allows for first-hand comparisons of programming languages, here between C++ and Rust.
18:18:45 <m-relay> <r​brunner7:monero.social> Alright, looks like we are through with the reports. Anything else we have to discuss today?
18:19:42 <m-relay> <s​needlewoods_xmr:matrix.org> is the rust lib "feature-complete" in comparison to the c++ one, or are there any differences?
18:20:51 <m-relay> <s​needlewoods_xmr:matrix.org> nothing else to discuss on my end
18:21:27 <m-relay> <r​brunner7:monero.social> Hopefully some potential memory leak "features" are missing from the Rust lib :)
18:21:54 <m-relay> <j​effro256:monero.social> Yes, it's feature complete to the `carrot_core` part
18:22:13 <m-relay> <r​brunner7:monero.social> I don't think that there will be noticable *speed* differences?
18:24:43 <m-relay> <j​effro256:monero.social> Depends on how fast the underlying cryptography primitives are for the Rust dependencies I used
18:24:45 <m-relay> <s​needlewoods_xmr:matrix.org> sorry, I completely missed that question, yes I tried and failed for a couple more attempts, then just continued to use the `master` branch
18:25:09 <m-relay> <j​effro256:monero.social> But the part of the code that is mine is more or less the exact same AFAICT
18:26:57 <m-relay> <r​brunner7:monero.social> Anyway, nice to see how we will most probably able to keep up Rust because there is enough engagement and interest. In theory, it could just wither because of not enough push.
18:27:05 <m-relay> <r​brunner7:monero.social> Ok, let me close the formal meeting while chat continues. Thanks everybody for attending, read you again next week!
18:27:30 <m-relay> <s​needlewoods_xmr:matrix.org> thanks everyone