<ofrnxmr> @tomdooley:matrix.org: They'll be or have been made

I got it running already on stressnet for go-p2pool and changed already for next beta

There were some questions and requests and some were implemented to benefit (or allow working) of p2pool and others to miners in general

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)

xmrig was updated for stress net already, but if mining via p2pool you had to do nothing to have it work for now

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

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.

oh right it was tomdooley. No that's a super specific field knowledge that AI will never do right

the "p2pool" changes are small, relatively. However they depend on bringing all the carrot crypto into p2pool ^ which I did on my project

(which is also a moving target)

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.

and carrot crypto, yes

it's all a moving target until final release after all

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

<rucknium> MRL meeting in this room in two hours.

<rucknium> Meeting time! monero-project/meta #1340

<rucknium> 1. Gtreetings

Hello

<jberman> waves

<articmine> Hi

<rucknium> 2. Updates. What is everyone working on?

<jberman> me: PR followup, set up a 4-phase plan to get the FCMP++ integration audited, got pre-fork multisig working / tests passing

<rucknium> 3. FCMP code integration audit prep.

<syntheticbird> Hi

<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

<jberman> Each subsequent phase essentially utilizes the building blocks of its preceding phase

<vtnerd> Hi

<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

<vtnerd> Sorry for late followup: me: testing changes to boost beast in lwsf. Getting monero_c/lwsf to work on macos should be completed

So with possible working-in of the results of one phase's audit results before going to the audit of the next phase?

<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

<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

I see.

Makes sense

Will be interesting to see how long the whole process takes, over all 4 phases

<jberman> Here are the specific sections I want to get audited: paste.debian.net/hidden/82c00500

<jberman> rbrunner: I think 3 months is a reasonable expectation. First 2 audit phases ~1 month, and the latter 2 ~two months

Sounds like a good sprint :)

Hopefully without burnout at the end ...

<rucknium> Do you have specific firm(s) in mind?

<jberman> Will probably start with CS if they have availability between the other work

<rucknium> Code auditing plan sounds good to me. I am no code auditing expert of course :)

<rucknium> Anything else on this agenda item?

<jberman> Nothing from me :)

<rucknium> 4. FCMP alpha stressnet (monero.town/post/6763165).

<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

<jberman> We're still going on beta tasks (scaling, finalizing code, awaiting kayaba's availability to open up as well)

<rucknium> Sounds good. Anything else about stressnet?

<jberman> Nothing from me

<rucknium> We can end the meeting here. Thanks everyone.

<articmine> Thanks

<jberman> thank you

<syntheticbird> A short meeting that's rare

<syntheticbird> thx