<f​ede:xmr.mx> with FCMP++ the address will change if i understand correctly. Does anybody have an example of how addresses will look like? Are they going to be longer or shorter?

<s​yntheticbird:monero.social> Quoting [FCMP++ latest document](raw.githubusercontent.com/kayabaNer…cmp-ringct/develop/fcmp%2B%2B.pdf):

<s​yntheticbird:monero.social> > Addresses do not need modifications. All existing addresses will continue to

<s​yntheticbird:monero.social> work as-is. Wallets will work without modifying their keys at all

<s​yntheticbird:monero.social> FCMP++ is a new *"transaction protocol"*. Addresses changes will be caused by new addressing protocols such as [JamtisRCT](gist.github.com/tevador/d3656a217c0177c160b9b6219d9ebb96) and/or [Carrot](github.com/jeffro256/carrot/blob/master/carrot.md)

<s​yntheticbird:monero.social> Carrot will preserve backwards compatibility with existing addresses.

<s​yntheticbird:monero.social> Examples of new addresses:

<s​yntheticbird:monero.social> - **JamtisRCT**: `xmra1mm95tp74ihjcu244xt4hpw1smcg5cdhdubfbmk3iyyw16ned1tu70hys0r3784af7r8515f2p9xtrx58akjtwb0cft00ari8jecrighji8aqaexwsh2475q3e1bay734kuhicey8bck5wwfbbp2yi4e4qn9h8dst5aaq8qnbyj0xrweamt1jwq5m0j1anh5srpm6fkhm6s76s3udi6xi0rm0jwf884j2exgg3t0ebxdcc3k`

<s​yntheticbird:monero.social> - **Carrot**: no example found on the document but format is explained here: github.com/jeffro256/carrot/blob/ma…rot.md#71-transaction-global-fields

<f​ede:xmr.mx> so it's going to be 64+8 = 72 bytes long? 96 characters if the address is encoded using base36 (without checksum)

<s​yntheticbird:monero.social> Isn't Monero using Base58? I'm usnsure now.

<s​yntheticbird:monero.social> cc: jeffro256 kayabanerve

<s​yntheticbird:monero.social> What is Carrot address format ?

<f​ede:xmr.mx> yes, monero is using base58, but i'm not sure how long 72 bytes would be with base58

<f​ede:xmr.mx> definitely less than 96 chars

<k​ayabanerve:matrix.org> FCMP++ is compatible with the existing address protocol and Carrot, which reuses the same address format (despite a distinct one-time address derivation/TX data protocol).