<c​haser:monero.social> how much of monero-serai and monero-wallet (repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/518) will need to be rewritten and re-audited for feature parity under FCMP++? I gather that Kayaba generously implemented a multisig for FCMP++, currently unaudited.

<k​ayabanerve:matrix.org> chaser @chaser:monero.social: monero-serai just needs to be extended with the new RCT type. My FCMP++ development already defined monero-fcmp-plus-plus for it to hook into, as we have monero-clsag.

<k​ayabanerve:matrix.org> monero-wallet needs:

<k​ayabanerve:matrix.org> - CARROT

<k​ayabanerve:matrix.org> - Adjusting to support the new RCT type

<k​ayabanerve:matrix.org> Both should be fine.

<k​ayabanerve:matrix.org> To have parity with wallet2, it needs a client-side merkle tree impl. The version I'm currently planning to ship at launch will only include ring-level privacy to the node connected to if using a pure Rust stack (a wallet2 impl could export its tree info).

<k​ayabanerve:matrix.org> Also, I wasn't generous by doing the FCMP++ multisigs. It was part of my CCS.

<k​ayabanerve:matrix.org> Both wallet2 and monero-wallet will have notable work when they move to the new FCMP++ wallets (outgoing view keys, a slightly more efficient multisig, and the PQ-migratable key derivation scheme).

<k​ayabanerve:matrix.org> Also, cc jeffro256, does Carrot define an OutputAuxData struct and extra as the serialization of a list of them or are we adding a new output type for the aux data?

<c​haser:monero.social> noted, thank you very much. this is good news.