Note: The original version of this issue tried to cover both payment and non-payment addresses. After some discussion and work, the issue was split. #3 now handles the payment schema, while this issue is for the non-payment related work.
Details
Writer: As a user with an MSA, I want to be able to connect my addresses on any chain to my MSA so they can be discovered by others
User Reader: As a user looking at my connections, I want to know what addresses to use for them on any chain
App Reader: As a application looking at a user, I want to know what other connected addresses they have on any chain to provide wider experiences to the user.
Options
Don't do it
No: Connecting additional data and structures to MSAs is a core part of Frequency
Custom MSA Pallet storage
No: Frequency does not need to read this information
Use an existing org.dsnp schema
No: Not structured and requires indexing to discover
Use up coming dsnp verified attributes
Both: This is a linking discovery need. It doesn't need verification and needs easy discoverability.
Use IPFS batched Data
No: Would still require indexing, and doesn't provide a signature required setup
Use Paginated Data
Maybe: Requires writing all each time, and these points of data are atomic
Use Itemized Data
Yes: Atomic data points, can require signature, easy to discover
Searched for Related Issues
[X] I have done a search for related issues and either found none, or noted them
Feature Description
Note: The original version of this issue tried to cover both payment and non-payment addresses. After some discussion and work, the issue was split. #3 now handles the payment schema, while this issue is for the non-payment related work.
Details
Options
org.dsnp
schemaSearched for Related Issues