<elongated:matrix.org> What’s the timeline for fcmp++ testnet/mainnet ?

<elongated:matrix.org> EoQ2 testnet ?

we still need to have the next beta stressnet, and alpha one has gone for longer than estimated (while handling other found issues not intrinsic to FCMP++, just old monero ones)

<ofrnxmr:xmr.mx> I imagine beta stressnet will finish with "production quality" sw, which will be deployed on testnet

<ofrnxmr:xmr.mx> Changes after that would probably be issues found by the greater ecosystem while adapting their software for the hardfork

<ofrnxmr:xmr.mx> What i mean is, testnet will be more like a release candidate

<ofrnxmr:xmr.mx> I dont see testnet being an overly long period, and i honestly dont see a reason for longer than 2 month lead-in after setting hard fork dates for mainnet. Especially with supportxmr having 88% (/s) of the global hashrate, we only need 1 mining pool to fork for the majority of security

<elongated:matrix.org> Still any eta on timeline? Like is everything needed for fcmp++ is already coded?

FCMP++ is working

plumbing to external utilities, details, proofs, wallet commands and stuff like that is what's left, and performance

<elongated:matrix.org> DataHoarder: Yes the needed things for next hf

<elongated:matrix.org> Even ramdomxv2

but v2 is not done lol

respectively TODO list for beta stressnet, TODO list for launch

many of these were done or are in PRs and are not marked done on the checklist

<elongated:matrix.org> Carrot and relayv2 are done ?

see linked PRs and discussion

that has been tested back and forth

Carrot was tweaked a couple of times, specially recently for future PQ turnstile support if needed

gist.github.com/jeffro256/146bfd5306ea3a8a2a0ea4d660cd2243 -> seraphis-migration/monero #250

not all carrot features are needed when it releases, btw, that doesn't need a hardfork (or a fork at all) to support. the derivations already exist, carrot-native wallets can come in later (but afaik they want to release that as well)