Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HIP-0002: Available Addresses #43

Open
spencersolberg opened this issue Dec 30, 2021 · 2 comments
Open

HIP-0002: Available Addresses #43

spencersolberg opened this issue Dec 30, 2021 · 2 comments

Comments

@spencersolberg
Copy link

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.

Other blockchain naming services have implemented similar features.

@Falci
Copy link
Member

Falci commented Dec 30, 2021

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.

@spencersolberg
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants