<m​etaflipnocap:matrix.org> greetings—i go by GOB_RECURSOR.

<m​etaflipnocap:matrix.org> i offer recursive clarity engineering:

<m​etaflipnocap:matrix.org> editing not for style, but for information integrity + transmission logic.

<m​etaflipnocap:matrix.org> i work peer-to-peer. crypto preferred (XMR ideal).

<m​etaflipnocap:matrix.org> happy to refine any draft or spec you’d like eyes on.

<m​etaflipnocap:matrix.org> one pass free, to calibrate sync. just drop the file or DM.

<a​ntilt:we2.ee> oscillatory behavior is a typical "bad" marker. And the trust-me-bro PR stunt is annoying

<m​onerobull:matrix.org> So silver bullet means the FCMP "delay" was all fud?

<m​onerobull:matrix.org> btw, absolutely cooked on the naming there

<c​haser:monero.social> monerobull @monerobull:matrix.org: from where I stand, the delay was FUD from the very beginning. no one involved in FCMP++ development talked about a serious delay. it was even said that, if work on a conservative drop-in starts now, it won't shift the timeline considerably. however, people like drama from random Twitter accounts and LLM-hallucinated summaries of MRL meeting logs better, so...

<m​onerobull:matrix.org> to be fair i flew over the logs and the ai summary appeared to check out

<m​onerobull:matrix.org> might have been bcs i went in biased looking for the messages talking about a delay

<m​onerobull:matrix.org> might have been bcs i went in biased, looking for the messages talking about a delay

<m​onerobull:matrix.org> i flew over the logs and the ai summary appeared to check out

<o​frnxmr:monero.social> EP-159 is delayed

<o​frnxmr:monero.social> monero-project/monero #9941

<f​reeman:cypherstack.com> Thank you thank you, we had maybe a dozen different draft named until we finally found the right one! The working name was Project Schnorrt and Schweet

<o​frnxmr:monero.social> I think it's fair to say that no one talked about _any_ delay to fcmp

<o​frnxmr:monero.social> The only "delay" was the may 21 alpha-testnet

<m​onerobull:matrix.org> im glad we got silver bullet instead of schnorrt xD

<o​frnxmr:monero.social> And the testnet delay isnt a real one, more of a stress test delay (though i spun up and began a low-effort stress test anyway)

<a​nestheticbliss:matrix.org> So when is the fcmp release rough estimate then

<a​nestheticbliss:matrix.org> End of 25? Beginning of 26? Or later than that?

<o​frnxmr:monero.social> After the implementation is tested, reviewed, tweaked, etc

<o​frnxmr:monero.social> Nioc has xmr bet for july 2026

<o​frnxmr:monero.social> i think it wholly depends on how the review and testing goes

<p​reland:monero.social> Is there a testnet yet?

<o​frnxmr:monero.social> i have one, yes

<o​frnxmr:monero.social> the monero-project testnet wont be forked until after the code is merged to monero-project

ofrnxmr the bet was not finalized :)

<d​iego:cypherstack.com> Math work, roughly 2 hours.

<d​iego:cypherstack.com> Naming work, roughly 3 weeks.

<d​iego:cypherstack.com> Time well spent.

<r​ucknium:monero.social> I suppose "delay" is a charged word, but the original FCMP research CCS schedule assumed that divisors were a solved problem in 2022. The work of Veridise last year and Cypher Stack this year were just supposed to verify that it was in fact solved. Cypher Stack found that the problem was not solved and have proposed a new solution. That proposed solution has to be checked by someo<clipped message

<r​ucknium:monero.social> ne else, which is a new piece of work. And some of the FCMP code has to be re-written to implement the proposed solution, as I understand it. That seems to at least add _some_ time to FCMP implementation and deployment.

<r​ucknium:monero.social> The mathematical work and the coding work are being done by different people and has been (and will continue to be) done in parallel.

<r​ucknium:monero.social> MRL isn't going to catch a case of "go fever", and I don't mean the programming language: en.wikipedia.org/wiki/Go_fever

<r​ucknium:monero.social> > In the US space industry, "go fever" (also "launch fever") is an informal term used to refer to the overall attitude of being in a rush or hurry to get a project or task done while overlooking potential problems or mistakes.[1] The term was coined after the Apollo 1 fire in 1967 and has been referred to in subsequent NASA incidents such as the Space Shuttle Challenger disaster i<clipped message

<r​ucknium:monero.social> n 1986 and the Space Shuttle Columbia disaster in 2003.

<r​ucknium:monero.social> From MRL Research Road-map 2: github.com/monero-project/research-…ions/roadmaps/MRL-R002/MRL-R002.tex

<r​ucknium:monero.social> > The Monero Research Lab wishes to state emphatically that our concern is to report our findings on Monero, which is an open source project, as honestly and transparently as possible. Our goal is not to persuade, re-assure, or enrich speculators or investors; our goal is to assist the Monero community and the Monero Core Team in the design of a robust and strong cryptocurrency wi<clipped message

<r​ucknium:monero.social> th an emphasis on user privacy.

:)

<o​frnxmr:monero.social> if divisors were, in fact, a solved problem in january, it doesnt change where we are today

<o​frnxmr:monero.social> The implementation work being done atm, aiui, is not reliant on divisors or non-divisors. If the implementation is completed and the math is _still_ not a solved problem, then you can say that the math added time to the launch

<o​frnxmr:monero.social> To me, its like saying we wont internally test-drive the car until it is certified for public roadways

<o​frnxmr:monero.social> [@rucknium:monero.social](https://matrix.to/#/@rucknium:monero.social) are you running a testnet?

<a​ntilt:we2.ee> @surae : grateful for today :)

<b​randon:cypherstack.com> Deep cut

<r​ucknium:monero.social> No, I'm not running a testnet