15:33:44

Could the powers that be that control the @monero twitter account please share Magic Monero’s new fundraising push to build fuzzing harnesses around fcmp? 🙏 15:33:44

https://x.com/MagicGrants/status/2081875763914068446 15:33:44

https://donate.magicgrants.org/monero/projects/fuzzing-monero-2 15:53:02 This might be a stupid question, but my searches haven't turned up anything concrete: How do I run a FCMP++-enabled regtest node? It looks like the FCMP code is already in master, but no real help docs-wise on how to run it. I'm guessing you have to build from source with some ENVARS set or something? 16:14:50 @loop.ster:matrix.org: you download the binaries from the fcmp++-stage ci, or build it 16:16:02 @ofrnxmr:xmr.mx: translation: is it our fault or your fault 16:17:00 https://github.com/seraphis-migration/monero/actions/runs/30333902356 16:41:56 @syntheticbird: Closest CI I see that's relevant is https://github.com/monero-project/monero/actions/workflows/stagex.yml ? 16:42:49 i sent the link 16:43:01 he sent the link 16:43:07 she* 16:43:09 (dont mind me im just trolling) 16:43:17 ok ok. no harm done 16:43:25 @ofrnxmr:xmr.mx: MINOR MISGENDERING MISTAKE 16:43:27 Ak oh, got it. Thanks 16:43:32 im not a minor 16:43:40 np. lmk if any issues 16:43:44 @ofrnxmr:xmr.mx: nor is Mistake in the chat with us 16:44:35 tldr: the full fcmp code does not live in monero-project/monero yet. if it did, we'd be able to fork testnet already 16:45:16 it is being moved from seraphis-migration/fcmp++-stage to monero-project/monero in pieces, as audits complete and reviews are done 16:45:23 That explains why I couldn't find any way to build it, I guess. 16:46:10 yea. you need to build the seraphis-migration/ fcmp++-stage branch. you can also build the fcmp++-beta-stressnet branch for more bleeding edge changes 16:46:38 you'll need rust installed before building btw 16:46:49 unless you just download the binaries from the CI 16:47:00 iirc the pinned tweet about the stress test didn't give the seraphis-migration repo link. 16:47:14 where is the tweet pinned? 16:47:30 The fcmp++-beta-stressnet branch is what you want if you want to run on the current stressnet. You can also go the releases page in seraphis-migration, or use https://gist.github.com/jeffro256/543932a8b9de3a42ce474e7aa9184c86 16:48:02 i think he jsut wants regtest 16:48:22 Ah, yeah for regtest, I would use fcmp++-stage 16:48:38 That's the FCMP++ development branch 16:51:19 You will need to update the HF table if you use fcmp++-stage, though, because otherwise v17 isn't enabled 16:53:42 think it is enabled 16:53:44 Good to know. What is in Rust btw? 16:54:22 https://github.com/seraphis-migration/monero/blob/450c789fbe47e3c8847bf928fad9e7c5ccf39d16/src/hardforks/hardforks.cpp#L78 16:54:33 @loop.ster:matrix.org: fcmp++ is in rust 16:56:00 @ofrnxmr:xmr.mx: only the beginning 16:56:07 monerod will be oxidized 16:56:22 you are being rescued. stop resisting. 16:59:23 You're speaking to the choir man. I'm a Rust guy through and through 17:00:05 Oh, so it's pulling the code in from monero-oxide as an ffi library right now? 17:00:20 yea 17:00:28 Isaw fcmp code there and thought it was a 2nd impl 17:01:08 noice 17:01:51 Well, thank you for the assist. I consider myself enlightened 18:53:34 Do we need to convert our XMR to FCMP++ XMR after HF? 18:53:47 need to? no 18:53:47 No 18:54:15 You will need to run the updated software unless you want to stay on the old fork with few other people 18:54:35 hehe 18:55:40 its been a while since our last hard fork, but no, your old wallet and coins will keep working. you will just need to run updted wallet software 18:55:55 @jeffro256: I can do transactions with the same wallet using new updated software and it will use FCMP++. Are there any traceability risks using the old wallet? Is moving the XMR to a new wallet recommended? 18:56:49 correct, and CARROT wallets have better protections, so you may want to transfer the funds to a CARROT seed 18:57:23 but that is quantum traceability protections, not about on chain ones 18:58:04 Ok 18:58:55 @earthman:unredacted.org: Yes, your wallet software will use FCMP++ automatically when it is the right time, assuming that you keep it updated. What do you mean by "old wallet"? Old wallet software, or old wallet files? Old software, yes. Old wallet files get automatially updated to use FCMP++. 18:58:55 > Is moving the XMR to a new wallet recommended? 18:58:55 > Depends on what you mean. Moving to a new key hierarchy? Yes. Just any regular new wallet? NO 19:01:31 > Moving to a new key hierarchy? 19:01:33 ^ this means moving from legacy (current) to Carrot-native hierarchy, there are a few pluses https://github.com/jeffro256/carrot/blob/master/carrot.md#2-new-features 19:01:46 "These features are only available to wallets generated with the newly defined account key hierarchy. Existing Monero wallets will not inherit these features, unfortunately." 19:03:58 jeffro256: what happened with the comments on https://gist.github.com/jeffro256/146bfd5306ea3a8a2a0ea4d660cd2243, were they addressed elsewhere? I remember there were a few PQ turnstile tests on some of the codebases for carrot out there too 19:04:04 I was afraid that we had to convert the XMR of a legacy seed to something new and doing that at for all subaddresses at same time same time could link subaddressees to each other 19:04:38 old wallets will keep working fine and you can do changes or migrate as you wish 19:04:52 but even old ones can transact fine. 19:05:04 Nope, if in doubt, just don't try to do anything special, and keep using Monero normally exactly as you were before. No churning, no new keys, no migrating wallet files, etc. Just download the FCMP++/Carrot software when it gets published and move on 19:05:35 @jeffro256: Ok 19:05:36 We are trying to make the user experience as seamless as possible during the upgrade 19:11:25 DataHoarder: They aren't solved in the sense that Schnorr signatures are secure from DLP solvers in perpetuity. It remains unsolved in that sense, but that is out of scope of this scheme. To make spending authority somewhat secure in a practical system, you need some kind of pre-commit scheme, finalization layer, etc. This is [... too long, see https://mrelay.p2pool.observer/e/jbqLnZsLd1RvR24x ] 19:14:42 afaik some did indeed something similar with signatures that can be used once for a migration, but that'd require changes ofc 19:15:27 and doesn't work as well without "account/address-based" systems 19:16:37 I'll leave it as-is on my existing code/tests as it then also checks completeness with the other libraries, but I might then not expose it and keep it as an internal test 19:31:34 Yes, that's probbaly the best course of action