Then let's take the ecency approach even though its a but complicated, ok? Then we have 3 apps following one format. I would see the social media links on the same level as tokens.
I think ecency approach seems a bit too complicated, too data intense, serves a different use-case in my opinion, i would prefer something simpler, just a simple association to the standard wallet address, a user can define in their profile for tips or donations.
ps. A list like in the tokens object, has also the drawback that is is more difficult to retrieve the address of a token. To retrieve lets say a BTC or LN address the whole list has to be searched, but in the proposed format the address can be directly accessed by its token name like profile.wallet.ln or profile.wallet.btc which is a more elegant solution. With a list you have to search the whole list whenever you want a token address.
I think ecency approach seems a bit too complicated, too data intense, serves a different use-case in my opinion, i would prefer something simpler, just a simple association to the standard wallet address, a user can define in their profile for tips or donations.
ps. A list like in the tokens object, has also the drawback that is is more difficult to retrieve the address of a token. To retrieve lets say a BTC or LN address the whole list has to be searched, but in the proposed format the address can be directly accessed by its token name like profile.wallet.ln or profile.wallet.btc which is a more elegant solution. With a list you have to search the whole list whenever you want a token address.
View more