15:09:27 <br-m> <rucknium> MRL meeting in this room in two hours.
16:47:19 <br-m> <neptunian:unredacted.org> I forgot the meeting was at 17:00 and thought it was 12:00 so I thought I had overslept lmao.
16:48:05 <br-m> <gingeropolous> I'ma kinda be here
16:48:21 <br-m> <ravfx:xmr.mx> o/
17:00:30 <br-m> <rucknium> Meeting time! https://github.com/monero-project/meta/issues/1415
17:00:40 <br-m> <rucknium> 1. Greetings
17:00:44 <br-m> <neptunian:unredacted.org> Hello, all.
17:01:07 <br-m> <syntheticbird> Hi
17:01:09 <rbrunner> Hello
17:01:18 <br-m> <emsczkp:matrix.org> hello
17:01:29 <br-m> <redsh4de:matrix.org> Hi
17:01:30 <br-m> <jberman> waves
17:02:00 <br-m> <vtnerd> hi
17:02:04 <br-m> <jeffro256> Howdy
17:02:42 <br-m> <boog900> Hi
17:03:11 <br-m> <rucknium> 2. Updates. What is everyone working on?
17:03:46 <br-m> <rucknium> me: Keeping stressnet stressed and investigating bugs.
17:03:58 <br-m> <sgp_> Hello
17:04:23 <br-m> <vtnerd> me: going through claude reports (via @sgp_) on monero-lws, lwsf, and fhse repos
17:04:50 <br-m> <neptunian:unredacted.org> Some FHE shenanigans and stuff related to Raccoon-G.
17:05:12 <br-m> <jeffro256> me: reworked a large portion of the Carrot libraries to support making OutProofV2 proofs to selfsends (currently possibly but unused behavior in wallet2)
17:05:29 <br-m> <jberman> Me: finalized the first set of FCMP++ integration PR's that were audited (thank you to UkoeHB  for reviewing), continued investigating @rucknium:monero.social 's observed sporadic wallet errors (the double spend issue) and identified a bug and suspected culprit, reviewed @jeffro256:monero.social 's hot-cold FCMP++/Carrot PR + other upstream PR's for next release, prepping stressnet v2.1
17:05:30 <br-m> <jeffro256> me: reviewing PRs and going through views of my upstream PRs
17:06:23 <br-m> <rucknium> 3. emsczkp research Bulletproofs* Milestone 2 completed (https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/626#note_36734).
17:07:25 <br-m> <jpk68:matrix.org> Hello
17:07:47 <br-m> <gingeropolous> Me: trying to see if monerosim is done
17:08:05 <br-m> <rucknium> Last time @emsczkp:matrix.org  discussed his progress. @jberman:monero.social  intended to look at the revised paper IIRC.
17:08:46 <br-m> <emsczkp:matrix.org> I have nothing to add beyond what said during the previous meeting. It was great to see positive comments on socials
17:10:46 <br-m> <jberman> I haven't had a chance to dive, but the revised paper (and proofs) looks solid
17:10:57 <br-m> <neptunian:unredacted.org> @jberman: ++
17:11:39 <br-m> <jberman> I think once the work is complete, it'll make sense to get another maths review on it, similar to how we've done for FCMP++
17:12:45 <br-m> <jberman> But reiterating, looking like great progress, and exciting results! Well done @emsczkp:matrix.org
17:13:08 <br-m> <emsczkp:matrix.org> thank you!
17:14:14 <br-m> <rucknium> Last meeting, @emsczkp:matrix.org asked whether it is OK to payout Milestone 2 of his CCS at this point or if more review is necessary.
17:14:56 <br-m> <jberman> I'm a +1 on payout
17:14:59 <br-m> <emsczkp:matrix.org> @rucknium: Exactly, thank you for the clarification
17:15:07 <br-m> <rucknium> @emsczkp:matrix.org: When the paper is complete, do you intend to submit it to a peer-reviewed journal or conference?
17:15:23 <br-m> <emsczkp:matrix.org> @rucknium: yes, that's the goal
17:15:43 <br-m> <rucknium> That wouldn't necessarily be as rigorous as MRL would like it, but it would be at least another set of critical eyes on it.
17:16:11 <br-m> <rucknium> I mean, if the results were to be used in actual production Monero code.
17:17:03 <br-m> <rucknium> I am +1 on payout too, but I have not tried to understand the paper. Any other opinions here?
17:17:09 <br-m> <emsczkp:matrix.org> Exactly, and I’ll work on a submission to the first major conference on the subject asap
17:17:24 <br-m> <rucknium> @emsczkp:matrix.org: Thank you.
17:18:34 <br-m> <neptunian:unredacted.org> @emsczkp:matrix.org: Hope to see you at EUROCRYPT :-)
17:19:49 <br-m> <emsczkp:matrix.org> Thank you, community, for the support on this reseach , which I strongly believe in and it is a very long story to me
17:20:12 <br-m> <rucknium> luigi1111 luigi1111_  : FWIW, we have support in this MRL meeting to payout @emsczkp:matrix.org  Milestone 2 of https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/626
17:21:14 <br-m> <rucknium> More discussion on this item?
17:22:07 <br-m> <rucknium> Thanks, @emsczkp:matrix.org
17:22:14 <br-m> <rucknium> 4. Post-quantum encryption (https://github.com/monero-project/research-lab/issues/151#issuecomment-4412416686). Jamtis (https://gist.github.com/tevador/639d083c994c1ef9401832c08e2b7832#appendix-c-instant-sync-protocol).
17:22:33 <tevador> No updates from me today.
17:25:40 <br-m> <neptunian:unredacted.org> Have there been any changes in regards to CSIDH and the security level assumptions?
17:25:44 <br-m> <neptunian:unredacted.org> I haven't kept up with it, apologies.
17:27:18 <br-m> <jberman> Not to my knowledge
17:27:34 <tevador> I haven't seen any papers regarding that
17:28:35 <br-m> <neptunian:unredacted.org> I have no further comments in that case. I don't feel the need to try to find other primitives to use here, as I like CSIDH currently.
17:32:22 <br-m> <rucknium> 5. FCMP beta stressnet (https://github.com/seraphis-migration/monero/releases/).
17:32:54 <br-m> <rucknium> DataHoarder set up a view key scanner on stressnet: https://stressnet.p2pool.observer/payments
17:33:30 <br-m> <jeffro256> Thanks to @j-berman for reviewing the hot/cold PR. It is in a good spot, I don't know if it will make it into v2.1, but I feel like it should be ready v soon 
17:33:54 <br-m> <jeffro256> Lots of review/implementation going on there 
17:33:56 <br-m> <jberman> Aiming to put v2.1 out today or tomorrow that fixes the window GUI binary, hopefully also fixes the observed sporadic double spends as well
17:34:08 <br-m> <rucknium> And I provided the view keys to my spamming wallets. I have a basic set of tables at the bottom of https://stressnetnode1.redteam.cash/ that help me see which of my spam wallets are actually getting txs into blocks.
17:34:09 <br-m> <jberman> (The latter appears to be an upstream issue)
17:34:28 <br-m> <jeffro256> @j-berman also debugged several issues with the daemon and RPC, reviewing those fixes 
17:34:43 <br-m> <rucknium> @jeffro256:monero.social: Is the hot/cold PR the same one that speeds up getblock.bin?
17:34:56 <br-m> <jeffro256> Completely separate 
17:35:22 <br-m> <jeffro256> The hot/cold wallet PR is here: https://github.com/seraphis-migration/monero/pull/52
17:35:35 <br-m> <jeffro256> The RPC speedup PR is here: https://github.com/monero-project/monero/pull/10605
17:37:27 <br-m> <rucknium> More discussion about stressnet?
17:37:38 <br-m> <jeffro256> j-berman did some really interesting profiling of LMDB related to 10605. I think that I might try to really reduce the complexity of that PR
17:38:41 <br-m> <jeffro256> Then, in a separate PR, implement the separate pruned/prunable mempool database tables approach. The only thing I'm worried about is if it'll make normal daemon block processing slower 
17:39:36 <br-m> <jeffro256> After PR 9135, bulk block processing will skip the mempool, so it wouldn't apply their, but it would to top block propogation times (maybe)
17:40:18 <br-m> <jberman> I suspect impact to normal sync will be close to negligible
17:40:29 <br-m> <jeffro256> I hope so 
17:41:22 <br-m> <rucknium> I am excited for the speedup :)
17:41:41 <br-m> <rucknium> Thanks for all the work on it, including reviewers
17:41:50 <br-m> <jeffro256> If LMDB has a large readahead, I can see that once the blockchain code starts touching prunable blobs during top block propgation, then the reads will be in-memory, and then the only additional overhead would be the 2x key lookups 
17:42:06 <br-m> <jeffro256> So I can see it being negligible, but we'll see 
17:42:49 <br-m> <jeffro256> At a certain point, trying to theorize about performance, w/o a demo, and with so many moving parts is basically astrology 
17:43:24 <br-m> <rucknium> Does stressnet provide enough of a demo envionment?
17:43:39 <br-m> <jeffro256> Yeah I'd definitely say so 
17:43:45 <br-m> <jberman> It took 0.1s in that demo to read 20k keys and also the pruned blobs
17:44:13 <br-m> <jeffro256> I can't remember, was the 
17:44:43 <br-m> <jeffro256> keys read in series, or was it lookup from the root each time?
17:45:04 <br-m> <jeffro256> in the demo
17:45:32 <br-m> <rucknium> Crazy idea: Could I just apply that PR to the stressnet node code and hope it speeds up my spamming?
17:45:47 <br-m> <jberman> It's read in order, though I also tested locally with random read order and it was roughly equivalent
17:46:41 <br-m> <jeffro256> @Rucknium Yeah go for it, I don't think it should have any conflicts with other open PRs beside 10761
17:47:13 <br-m> <rucknium> Awesome. Thank you.
17:48:21 <br-m> <rucknium> More discussion of this item?
17:49:23 <br-m> <rucknium> 6. monerosim (https://github.com/Fountain5405/monerosim).
17:49:33 <br-m> <rucknium> Is @gingeropolous:monero.social  here?
17:49:50 <br-m> <gingeropolous> Hi! Yep, here
17:50:47 <br-m> <rucknium> I think you were doing a tedious grid search for network parameters that would get closest to mainnet behavior.
17:51:43 <br-m> <gingeropolous> Yes, your review encouraged me to investigate the delta and see if I could narrow it
17:52:08 <br-m> <rucknium> What are your findings so far?
17:52:34 <br-m> <gingeropolous> I think it has been narrowed. I'm remote so I can't really link things right now, but the detailed findings can be found on the repo
17:53:30 <br-m> <gingeropolous> But yeah, the general idea seemed to be the 100% reachable network has a different behavior than mainnet, and the always on network in the sim also modified things
17:53:58 <br-m> <gingeropolous> So, those parameters can be toggled and managed via the config files for sim generation
17:54:33 <br-m> <rucknium> Fantastic. How was the unreachable nodes implemented?
17:55:00 <br-m> <gingeropolous> Just adding the --hide-my-port.
17:55:37 <br-m> <rucknium> Do you think you would have different results if trying --in-peers=0?
17:55:50 <br-m> <gingeropolous> As I'm typing it, I realize I could also also do it from the host level, as in each shadow thing could function as a firewall for that virtual entity
17:55:52 <br-m> <rucknium> in-peers would probably be stricter. Or combining them
17:56:30 <br-m> <rucknium> @gingeropolous: Is that easy to do? That would probably mimic the actual network setup most closely
17:56:32 <br-m> <gingeropolous> Dude, yeah, it's a sim. We could test parameters for as long as the machines spin , and I look forward to doing so!
17:57:14 <br-m> <gingeropolous> Yeah, I could add that in.
17:57:30 <br-m> <rucknium> Because most unreachable are unreachable because of their NAT or similar external setup, not because of their monerod flag config options
17:59:07 <br-m> <gingeropolous> Indeed. I guess we could also mimic the ... Effective of that UPNP punch through or whatever? Because monero still tries, right? And sometimes it works.... Or just flat default firewall... Though I guess that can just get swallowed up in the config setting of % reachable ".....
18:00:12 <br-m> <rucknium> I don't know too much about the UPNP punch through, but maybe someone who does know could comment.
18:02:32 <br-m> <rucknium> Any more discussion of this agenda item?
18:03:39 <br-m> <gingeropolous> So I'm still not at the milestone? What do we think, 98%, 70%..... 🤗
18:03:58 <br-m> <rucknium> I think you are
18:04:34 <br-m> <sneedlewoods_xmr:matrix.org> I don't think we use upnp anymore https://github.com/monero-project/monero/pull/10012
18:10:20 <br-m> <rucknium> We can end the meeting here. Thanks everyone.
18:10:41 <br-m> <jeffro256> Thanks everyone 
18:10:51 <br-m> <gingeropolous> Thank you all!
18:12:24 <DataHoarder> 19:32:54 <br-m> <rucknium> DataHoarder set up a view key scanner on stressnet: https://stressnet.p2pool.observer/payments
18:12:24 <DataHoarder> FYI I support carrot-native scanning as well, if any of those were running. JSON is available in https://stressnet.p2pool.observer/payments.json which provides some further details, including TxProofV2 (InProof)
18:38:05 <br-m> <rucknium> I forgot to say that DataHoarder  has it for mainnet, too. Has the General Fund, CCS, Magic, and Bounties view keys at least: https://blocks.p2pool.observer/payments