You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe HIP-0002 should be expanded and an endpoint listing available addresses should be implemented.
For example, a GET request to https://<domain>/.well-known/wallets could retrieve a list of supported currencies.
The response could simply be a comma-separated plain-text list. The currencies could either be represented with their symbol, such as BTC,ETH,HNS, or with their SLIP-0044 coin type, such as 0,60,5353.
This is interesting but I don't see a use case other than listing all the coins supported by a particular address.
HIP2 main usage is for wallet clients to resolve domain in address. Each wallet should resolve the symbols the wallet supports (eg: Bob Wallet will only resolve HNS)
About using coin type from SLIP-0044, I don't like this idea since HIP2 is not limited to cryptocurrency and could be used even by fiat currencies.
About using coin type from SLIP-0044, I don't like this idea since HIP2 is not limited to cryptocurrency and could be used even by fiat currencies.
Good call, I agree with you on this.
Each wallet should resolve the symbols the wallet supports
Some wallets (Exodus, exchange wallets, hardware wallets) support lots of coins. I think it'd be more efficient to query what coins are accepted, as opposed to trial and error. This makes sense to me, because some wallets ask to choose a recipient before choosing the coin.
I also think this idea could be neat for services integrating tips. Imagine connecting your Twitter handle to your domain and your tip jar is automatically populated with your addresses.
NFT galleries could use this for displaying collectibles across different chains.
I believe HIP-0002 should be expanded and an endpoint listing available addresses should be implemented.
For example, a GET request to
https://<domain>/.well-known/wallets
could retrieve a list of supported currencies.The response could simply be a comma-separated plain-text list. The currencies could either be represented with their symbol, such as
BTC,ETH,HNS
, or with their SLIP-0044 coin type, such as0,60,5353
.Other blockchain naming services have implemented similar features.
The text was updated successfully, but these errors were encountered: