16:59:02 Meeting in a bit than 1 hour. If not everybody is down at the beach anyway, without any code in sight :) 16:59:10 *a bit more 16:59:34 Why not the three at the same time ? 17:02:12 there is mobile network at beach too 17:02:30 :) 18:00:01 Meeting time. Hello! https://github.com/monero-project/meta/issues/1221 18:00:58 Hi 18:02:44 *waves* 18:02:51 While we wait, and before I forget, let me propose that after today we meet again in **two** weeks, because of the MoneroKon weekend 18:04:03 Alright, any reports about last week? 18:05:25 hey 18:06:37 lots of real life, no beach time, but made a little progress on the CLI 18:07:05 Nothing significant to report. Still continuing current open tasks (FFI cleanup, open PR fixups, PR review). I also started on supporting >8-input txs. In a past meeting, I shared some thinking behind the idea to group multiple FCMP++ proofs into 1 tx where each proof has a max of 8-inputs, primarily to avoid txs taking minutes to construct (so that even 128-input txs take seconds instead of minutes). I started dabbling in changes for that approach 18:07:56 So only the size goes up considerably, but not construction time as well? 18:08:07 The size of the tx 18:08:08 Correct 18:08:29 Certainly a worthwhile approach to think through 18:09:07 Just gives a whole new "hierarchical level" to transactions, and sometimes such new levels are a bit expensive to implement ... 18:10:13 Link to a past MRL meeting where I initially brought this up too: https://github.com/monero-project/meta/issues/1200 18:10:52 I somehow missed that idea ... never mind. 18:11:05 Ok, looks like that's it already about reports. Anything else to discuss today? 18:12:12 I wanted to ask jeffro256 if he thinks it's OK to disclose the spy node detection method at MoneroKon. I don't intend to rush anything, but it would be an opportunity to do so. 18:12:16 Not to discuss, but maybe interesting to mention, if you didn't see it already: It looks that at long last, somebody started to implement someting like a "layer 2" on top of the Monero blockchain in earnest. It's called *Grease* and made quite some waves already on Reddit. 18:12:29 I think there will be a presentation about it at MoneroKon 18:12:38 I am very curious how that will turn out 18:13:21 IIRC, someone said, late last year, that a project was looking for Rust developers for a Monero payment channel implementation. Probably, Grease is that project. 18:14:06 Ok, the gras was whispering already back then :) 18:14:55 I think somebody mentioned that so far it's two devs. Pretty big job for a duo 18:15:08 wonder how they deal with Monero's lack of HTLC-equivalent 18:15:35 In 1 week we will probably know 18:16:14 I am always a bit uneasy when people hear "L2" and immediately and without much questioning attribute almost magical properties to that thing ... 18:16:41 I as the old skeptic that I am 18:17:52 I saw this in bounties today https://bounties.monero.social/posts/192/0-000m-creat-a-payment-channel-for-monero-based-in-monet-and-auxchannel 18:17:54 haven't read the links yet 18:18:52 Hmm, looks a bit controversial, and a bit late frankly 18:19:23 Ok, looks like we can close already for today. Happy trip if you should travel to Prague, and read you again in **two** weeks! 18:19:24 They have some docs here: https://github.com/grease-xmr/grease 18:19:26 https://github.com/grease-xmr/grease/blob/main/docs/introduction.md 18:20:07 thanks, cu 18:20:22 Yes, so far I was just lazy to read those carefully, putting my hope on an easy-to-digest presentation 22:21:04 Yeah I don't have a problem with that now that rbrunner7 took the initiative to make an implementation of a mitigation, and due to your research stating that the subnet dedup mitigation would mostly make the issue go away. Perhaps the information could also be useful to BTC node operators ? 22:21:39 Sorry I missed the meeting y'all, timezones messed me up 22:31:51 Thanks for weighing in :)