3 ms·
> Query a DNS server (dnsdist) with an ENS domain and get a wallet address back, > Query a DNS server with a wallet address and get an ENS domain back, > Quer
by PragmaticPulp 5y ago
> Query a DNS server (dnsdist) with an ENS domain and get a wallet address back,
> Query a DNS server with a wallet address and get an ENS domain back,
> Query a DNS server with an ENS domain for specific metadata and get the requested information back.
> Spoiler: we only reach the first goal in this blog post
If I’m reading this right, this is just a proxy service that uses an existing Ethereum light client to take an ENS domain and get a wallet address back?
So this isn’t really a DNS service in the traditional sense, but rather a way to look up wallet addresses from friendly ENS names?
- rvz 5y agoDisappointingly yes.
- aerique 5y agoThis PoC indeed only returns a wallet address but this project was spawned by typing in `vitalik.eth` in my browser's address bar and expecting to end up on a website. If you check https://app.ens.domains/name/vitalik.eth/details https://app.ens.domains/name/vitalik.eth/details You see there's an `url` field as well so with a little extra work we could return the URL as a CNAME. Perhaps it would be better if the code would have returned that, but it is not a give that it has any contents. This is part of the question of what an ENS name even means. A browser would be interested in the URL and a wallet client in a wallet address, etc. My interest was in seeing how we can extend existing DNS infrastructure for accessing something new and similar. edit: Having just read the ICANN article linked by rasengan this would at least fix the issue with end users having to customize their browser or DNS resolver. (https://news.ycombinator.com/item?id=29343007 https://news.ycombinator.com/item?id=29343007)