03:17:01 <br-m> <ofrnxmr> @tomdooley:matrix.org: They'll be or have been made
04:39:35 <DataHoarder> I got it running already on stressnet for go-p2pool and changed already for next beta
04:40:17 <DataHoarder> There were some questions and requests and some were implemented to benefit (or allow working) of p2pool and others to miners in general
04:41:37 <DataHoarder> C p2pool is not updated but that'd be simpler with changes known (and documented). Schemes that use FCMP++ ability to chain transactions to aggregate outputs automatically are in research (but don't necessarily are required for the upgrade)
04:42:14 <DataHoarder> xmrig was updated for stress net already, but if mining via p2pool you had to do nothing to have it work for now
05:16:30 <DataHoarder> the only change that was made to p2pool (C-p2pool) ahead of time and is live now is checking for torsion on wallet addresses and bailing out client-side, for the upgrade ahead of time they will be refused network-wide
08:59:53 <sech1> It will be updated for FCMP++ when the time is right. Right now it's too early. Updating for FCMP++ is no small feat, in fact it's a massive change. Definitely not something for AI to do, no matter how good it is.
09:29:50 <DataHoarder> oh right it was tomdooley. No that's a super specific field knowledge that AI will never do right
09:30:53 <DataHoarder> the "p2pool" changes are small, relatively. However they depend on bringing all the carrot crypto into p2pool ^ which I did on my project
09:31:01 <DataHoarder> (which is also a moving target)
09:33:18 <sech1> FCMP++ changes must be tied together with RandomX v2 changes which are also part of the next upgrade, and both of those changes will require a block template/header format change. This is not finalized yet, so why I said it's too early.
09:34:20 <sech1> and carrot crypto, yes
10:54:29 <DataHoarder> it's all a moving target until final release after all
10:55:07 <DataHoarder> I make the changes myself for early sanity checks (hey, we got a few tips of things to modify) but I had to change that code several times as the target indeed moves and shifts
15:05:44 <br-m> <rucknium> MRL meeting in this room in two hours.
17:00:44 <br-m> <rucknium> Meeting time! https://github.com/monero-project/meta/issues/1340
17:00:47 <br-m> <rucknium> 1. Gtreetings
17:01:10 <rbrunner> Hello
17:02:32 <br-m> <jberman> waves
17:02:46 <br-m> <articmine> Hi
17:04:00 <br-m> <rucknium> 2. Updates. What is everyone working on?
17:06:16 <br-m> <jberman> me: PR followup, set up a 4-phase plan to get the FCMP++ integration audited, got pre-fork multisig working / tests passing
17:07:25 <br-m> <rucknium> 3. FCMP code integration audit prep.
17:08:52 <br-m> <syntheticbird> Hi
17:09:30 <br-m> <jberman> My current plan on the table is to have the fcmp++-stage in the seraphis-migration repo ready for auditing. I'd like to audit the integration code in 4 phases: 1) Crypto, 2) Crypto Integration, 3) Tree building / prove / verify, 4) Consensus integration
17:10:37 <br-m> <jberman> Each subsequent phase essentially utilizes the building blocks of its preceding phase 
17:10:55 <br-m> <vtnerd> Hi
17:11:42 <br-m> <jberman> So right now, I have PR's prepped (and am working with jeffro to get those PR's merged), and then would like to get started with auditing on a specific commit of fcmp++-stage
17:12:07 <br-m> <vtnerd> Sorry for late followup: me: testing changes to boost beast in lwsf. Getting monero_c/lwsf to work on macos should be completed 
17:12:37 <rbrunner> So with possible working-in of the results of one phase's audit results before going to the audit of the next phase?
17:12:44 <br-m> <jberman> Of note, I've already opened a couple PR's upstream, which jeffro and vtnerd reviewed. I'm proposing we get that code + other related building block crypto audited as well
17:13:38 <br-m> <jberman> rbrunner: Yes. I'm thinking about a distinct CCS like kayaba's where I raise funds for the audits in advance, to minimize downtime between each phase 
17:14:07 <rbrunner> I see.
17:14:13 <rbrunner> Makes sense
17:15:07 <rbrunner> Will be interesting to see how long the whole process takes, over all 4 phases
17:15:21 <br-m> <jberman> Here are the specific sections I want to get audited: https://paste.debian.net/hidden/82c00500
17:16:53 <br-m> <jberman> rbrunner: I think 3 months is a reasonable expectation. First 2 audit phases ~1 month, and the latter 2 ~two months
17:17:26 <rbrunner> Sounds like a good sprint :)
17:17:51 <rbrunner> Hopefully without burnout at the end ...
17:21:13 <br-m> <rucknium> Do you have specific firm(s) in mind?
17:21:55 <br-m> <jberman> Will probably start with CS if they have availability between the other work
17:23:26 <br-m> <rucknium> Code auditing plan sounds good to me. I am no code auditing expert of course :)
17:23:35 <br-m> <rucknium> Anything else on this agenda item?
17:25:13 <br-m> <jberman> Nothing from me :)
17:25:19 <br-m> <rucknium> 4. FCMP alpha stressnet (https://monero.town/post/6763165).
17:26:50 <br-m> <jberman> It seems @ofrnxmr:monero.social has identified a new issue to work through when blocks increase in size that I'll look into today. Tx relay v2 appears to be running smoothly
17:28:20 <br-m> <jberman> We're still going on beta tasks (scaling, finalizing code, awaiting kayaba's availability to open up as well)
17:31:23 <br-m> <rucknium> Sounds good. Anything else about stressnet?
17:31:50 <br-m> <jberman> Nothing from me
17:33:08 <br-m> <rucknium> We can end the meeting here. Thanks everyone.
17:34:31 <br-m> <articmine> Thanks 
17:34:55 <br-m> <jberman> thank you
17:44:47 <br-m> <syntheticbird> A short meeting that's rare
17:44:50 <br-m> <syntheticbird> thx