Default Token Address Linking

[wilwade]

Replaced by #5

[wesbiggs]

Looks good -- I just left a couple of naming questions (that you may have thought about already). I am still working through how this repo relates to the (forthcoming) DSNP schemas repo, but this all makes sense for walletAddresses.

[JoeCap08055]

Recommend we reference an issue with this PR, that describes the problem being solved & other points, such as why we can't simply use 'addPublicKeyToMsa' (presumably because they're not supported key types, ie sr15519). Could also enhance the "Goal" in the README with the same information.

[wilwade]

Recommend we reference an issue with this PR, that describes the problem being solved & other points, such as why we can't simply use 'addPublicKeyToMsa' (presumably because they're not supported key types, ie sr15519). Could also enhance the "Goal" in the README with the same information.

@JoeCap08055 Good points.

• Added issue Connecting MSAs to Additional External Non-Payment Addresses #2 (although didn't specifically address addPublicKeyToMsa, I think it is more clear)
• Updated the README a bunch

[enddynayn]

👍 awesome!

[saraswatpuneet]

Lgtm

[JoeCap08055]

Not trying to be picky, but I wonder if there's a better term than "payment address" that would be more clear that these are NOT (necessarily) FRQCY-holding wallets for paying transaction fees, but are simply for informational purposes

[wilwade]

Not trying to be picky, but I wonder if there's a better term than "payment address" that would be more clear that these are NOT (necessarily) FRQCY-holding wallets for paying transaction fees, but are simply for informational purposes

@JoeCap08055 I am 100% open to options. "Token Addresses" didn't feel right, but perhaps?

Some additional meh ideas:

• Payment Target
• Token Wallet
• Transfer Address
• Token Linked Address

[JoeCap08055]

@wilwade I'm similarly stumped as to a good name; here are some ChatGPT-generated options, maybe one will provide some inspiration:

1. Payment Address Registry: Emphasizes that the addresses are for receiving payments across different tokens and blockchains.

2. Cross-Chain Payment List: Highlights the chain-agnostic nature of the addresses.

3. Token-Agnostic Address Book: Focuses on the token-agnostic aspect of the list.

4. Receiver Address Pool: Suggests that the addresses are meant for receiving payments rather than sending.

5. Payment Destination Directory: Conveys that the addresses are destinations for payments, independent of the blockchain.

6. Universal Payment Address List: Emphasizes the universal applicability of the addresses.

7. External Payment Address List: Indicates that these addresses are external to the Frequency blockchain in terms of payment capability.

8. Token Receiver Address Book: Focuses on the role of these addresses as receivers of various tokens.

9. Interchain Payment Address List: Highlights the interoperability across different blockchains.

10. Wallet Destination Registry: Indicates that the addresses are associated with a wallet for receiving tokens.