Live data from Hacker News

Handshake: An experimental peer-to-peer root DNS

handshake.org

11–20 of 62 posts

Re: Handshake: An experimental peer-to-peer root DNS

#11
post #5

This looks like a really cool premise. Decentralized signatures for certs seems like a no-brainer solution to cert/DNS hijacking (maybe I'm missing something?).

Cool technical premise. Not the first implementation of the idea. My guess? Business is hard.

Re: Handshake: An experimental peer-to-peer root DNS

#13

This definitely looks interesting! (I hope a project contributor is reading/commenting) Q: Let's say I'm a representative of a company that wants to buy their name "example.com" to be resolved via Handshake. Assuming things are live and running well, what's the process by which we'd get www.example.com resolving to 123.123.123.123? (keeping it simple, not worrying about mx and srv records yet) How stable and safe is…

This provides a replacement for the root zone and not does not directly include subdomains. In DNS terms this is like registering a TLD. So if you own "companyx.com" domain, you could register "companyx" on handshake. Once you own this domain you can use your private key associated to set your name servers / other DNS settings, so subdomains could fallback to using existing DNS resolution, or this could resolve directly to a website.

With your private key you can also do interesting things like verify your subdomains with signatures ala DNSSEC or verify your own SSL certs without CAs.

The paper also mentions future improvements that could see each TLD using a side-chain (like plasma) to manage and possibly sell their own subdomains. This could also give each TLD owner more control over their own "consensus rules" for their particular TLD.

There are a lot more possibilities here, some are covered in the paper, many more are still to be explored.

Super excited for this project!

Re: Handshake: An experimental peer-to-peer root DNS

#15
Compared to other crypto projects, what really excites me is there is already a fully functioning testnet, SPV resolver, and C bindings available on day of announcement!

Main-net launch only 1 month away.

Other crypto projects should take note. This is how to prove you're serious.

Re: Handshake: An experimental peer-to-peer root DNS

#17
post #13

This definitely looks interesting! (I hope a project contributor is reading/commenting) Q: Let's say I'm a representative of a company that wants to buy their name "example.com" to be resolved via Handshake. Assuming things are live and running well, what's the process by which we'd get www.example.com resolving to 123.123.123.123? (keeping it simple, not worrying about mx and srv records yet) How stable and safe is…

This provides a replacement for the root zone and not does not directly include subdomains. In DNS terms this is like registering a TLD. So if you own "companyx.com" domain, you could register "companyx" on handshake. Once you own this domain you can use your private key associated to set your name servers / other DNS settings, so subdomains could fallback to using existing DNS resolution, or this could resolve direc…

I'm curious how this would work out at scale. Would everyone just get a long descriptive TLD and then use that directly? While that would technically work I imagine it would confuse people who are used to treat the address bar of the browser primarily as the search box. So I'd enter "flowers" and expect a Google search for flowers, but since the TLD flowers exists and resolves to something you end up on some dude's blog. The alternative would be to use the www subdomain, but apart from looking odd (www.flowers? Something my mom could accidentally come up with, forgetting the .com - so maybe not that bad after all...) since we're not used to that now, it also reverses the current trend of dropping the www.

So of looks like this could also mean some changes in how we actually use the web, not just how DNS is managed.

Re: Handshake: An experimental peer-to-peer root DNS

#20

This definitely looks interesting! (I hope a project contributor is reading/commenting) Q: Let's say I'm a representative of a company that wants to buy their name "example.com" to be resolved via Handshake. Assuming things are live and running well, what's the process by which we'd get www.example.com resolving to 123.123.123.123? (keeping it simple, not worrying about mx and srv records yet) How stable and safe is…

"If you own a name in the existing root zone or the Alexa top 100k, your name is waiting for you on the blockchain. You are able to claim it by publishing a DNSSEC ownership proof – a cryptographic proof that you own the name on ICANN’s system. Your name must have a valid DNSSEC setup in order for the claim to be created. If you do not have DNSSEC set up, don’t worry – you can set it up after the handshake blockchain launches and proofs will still be accepted retroactively."

https://handshake-org.github.io/guides/claims.html

Post reply on HN