Live data from Hacker News

Handshake: An experimental peer-to-peer root DNS

handshake.org

21–30 of 62 posts

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

#22
It looks like the dev team has already anticipated a SHA3 based ASIC design as a threat to monopolize control over the Handshake protocol.

Guessing an insider on is hoping to exploit this for financial gain and control of this isolated DNS pool.

and why would users want to participate in a protocol which inherently relinquishes centralized accountability and responsibility, in favor of a security model that allows any of these mining warehouse operations run by anonymous robber barrons with enough excess capital to fill up an entire building with random number generating electricity wasting heaters?

Who thinks this is seriously a good idea for anything other then exploiting greater fools to sell digital beanie babies to?

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

#24
post #16

How do you get coins if you're not an open source project? Is the idea that, when the mainnet launches, private individuals and the for-profit sector will buy coins from open source projects?

or you could mine your own

what happens when one of these large mining operations in China/South pacific/etc target this network and begin accumulating all the handshake "coins".

How would someone 3 years from now have access to generate coins/tokens after the protocol increases the difficulty and stops generating coins so easily?

Wouldn't it be cheaper just to run a normal DNS server? What's the use case?

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

#25
post #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.

What are the other implementation of the idea?

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

#30

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…

I’m confused, and after skimming through the paper I’m still not sure.

How does this work after the handshake network launches?

If I register a new domain with ICANN, but do not register it with Handshake, can someone else? And if not, doesn’t that mean ICANN is still the central authority for domain names? (Including transfers)

It seems like the existing root zone & handshake will immediately fork, and then how will 3rd parties determines which root zone is correct? Doesn’t that still mean existing CA’s could simply update the root zone (regardless of handshake) (which is the existing problem with bad actor CA’s).

I’m probably missing something here, could anyone elaborate?

Post reply on HN