-
m-relay<moneromatrix:matrix.org> Is this true?
-
m-relay<moneromatrix:matrix.org> "Carrot could be implemented today without FCMP, it does not require a hardfork."
-
m-relay<vtnerd:monero.social> Maybe? there's a new output type that's needed to prevent the janus attack, so if we dropped that from carrot then I think it would be possible
-
m-relay<vtnerd:monero.social> But the sender doesn't know whether the address is carrot or legacy
-
DataHoarderThis is in the context of the carrot addressing scheme (not output format)
-
DataHoarderBasically it could generate addresses and be sent funds there, but no one has bothered to define it in spec
-
DataHoarderSo yeah you wouldn't gain a bunch of features but you could have the addressing scheme for it
-
m-relay<jeffro256:monero.social> Not really without losing benefits. If you send XMR over CARROT, it wouldn't be spendable under RingCT without modifications. If you modified it to work under RingCT, you would lose OVKs and quantum forward secrecy.
-
m-relay<jeffro256:monero.social> You could have Janus protection with CARROT on RingCT by simply stuffing that data into tx_extra
-
m-relay<vtnerd:monero.social> Ah yes tx_extra, that great perpetual stew
-
DataHoardermany reasons why making a new output format and derivations for it was done indeed
-
m-relay<user5864:matrix.org> The whole fud with carrot getting out of hand
-
m-relay<ofrnxmr:xmr.mx> dev channel, not fud discussion channel
-
m-relay<syntheticbird:monero.social> this
-
m-relay<syntheticbird:monero.social> with all respect