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

Multichain support for ENS resolution #104

Open
Arachnid opened this issue Jul 5, 2021 · 4 comments
Open

Multichain support for ENS resolution #104

Arachnid opened this issue Jul 5, 2021 · 4 comments

Comments

@Arachnid
Copy link

Arachnid commented Jul 5, 2021

It'd be great if the ENS integration in kethereum supported resolving addresses other than Ethereum addresses, as per EIP 2304. At least Bitcoin and Bitcoin Cash support would be an amazing start.

We have a JS library that encodes and decodes different address types here, for reference: https://github.com/ensdomains/address-encoder

@brantlymillegan
Copy link

@ligi thanks tagging it so fast. Given your tag "help wanted", any objections to us putting this on Gitcoin with a bounty?

@ligi
Copy link
Member

ligi commented Jul 5, 2021

tbh I had some bad experiences with bounties in the past. If people just write code for the money it can be worse as when they actually write it with the intent to use it. This is also part of the reason why I tagged it with "help wanted". This is a functionality I do not see me using on my own - and Ideally the feature is done by someone actually having a use case for it. But I am also open to a bounty - just my 2cents here.

@brantlymillegan
Copy link

Got it. Background on our request: the Bitcoin.com Wallet requested a Kotlin library from us for their ENS integration, and they support BTC, BCH, and ETH, hence our request. (right now, they're using a library maintained by Unstoppable Domains to integrate ENS, which is bad given the conflict of interest, but it supports ENS wrong anyway)

@ligi
Copy link
Member

ligi commented Jul 5, 2021

Great to hear. So the ideal thing would be if they contribute the feature. Happy to review the PR and merge it. And if they do not want to do so I am also OK with a bounty. I just do not see myself doing it for reasons stated above and also time reasons.

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

No branches or pull requests

3 participants