20:06:23 <Guest72> Hi
22:34:56 <m-relay> <k​iersten5821:matrix.org> how will addresses/subaddresses change during the new fcmp upgrade
22:35:26 <m-relay> <k​iersten5821:matrix.org> the differentiation of these has always been somewhat of an annoying ux complication relative to other coins
22:38:02 <m-relay> <v​tnerd:monero.social> Existing addresses will continue to work (called legacy) and users can create carrot addresses with new features
22:38:34 <m-relay> <v​tnerd:monero.social> The primary benefit will be post-quantum turnstile which only works with new carrot addresses afaik
22:41:16 <DataHoarder> also https://github.com/jeffro256/carrot/blob/master/carrot.md#22-new-wallets-only
23:05:17 <m-relay> <j​effro256:monero.social> There will still be main addresses, subaddress, and integrated address, and at its most basic, you would use them just like you normally would today.
23:06:19 <m-relay> <j​effro256:monero.social> But no "new" types of addresses in the sense that wallet code interacts with ~other people's~ addresses exactly the same, regardless of whether it's a Carrot-derived address or a legacy address
23:20:04 <m-relay> <k​iersten5821:matrix.org> i see, it would be nice at some point to have a uniform address type, instead of having so many, i can't even remember what an integrated address is. the ux is pretty difficult 
23:20:04 <m-relay> <k​iersten5821:matrix.org> will the seed phrase change if i instantiate a new wallet under the new fcmp scheme for the benefits in that carrot.md? or will it be like bitcoin's "derivation paths", and require some path for the same seed?
23:20:09 <m-relay> <k​iersten5821:matrix.org> i see, it would be nice at some point to have a uniform address type, instead of having so many, i can't even remember what an integrated address is. the ux is pretty difficult 
23:20:10 <m-relay> <k​iersten5821:matrix.org> will the seed phrase change if i instantiate a new wallet under the new fcmp scheme for the benefits in that carrot. md? or will it be like bitcoin's "derivation paths", and require some path for the same seed?
23:31:23 <m-relay> <j​effro256:monero.social> > the ux is pretty difficult
23:31:24 <m-relay> <j​effro256:monero.social> TLDR; don't use integrated addresses unless you're a merchant and really need it. Use a different address for each person you interact with, just like disposable email addresses.
23:31:26 <m-relay> <j​effro256:monero.social> HW wallets and other wallets which use derivations paths from their seed won't need to migrate. However, the default seeds used in the CLI wallet and GUI wallet will need to migrate