Re:Decentralized Naming and Certificate Authority
by xur17 on Wednesday February 12, 2020 @02:46PM
(#22312089)
I have a longer answer here [0], but in short, Handshake does not control existing domain names. They are giving the top 100k existing domain name owners control of a gtld based on the domain they own. Ex `example.com` receives `example` in Handshake's system.
Re:Decentralized Naming and Certificate Authority
by Ajedi32 on Wednesday February 12, 2020 @02:51PM
(#22312133)
Okay, that's much better. Thanks for the clarification. I assume "com", "org", "net", "ninja", etc are also reserved then?
Re:Decentralized Naming and Certificate Authority
by xur17 on Wednesday February 12, 2020 @02:53PM
(#22312150)
Yes, they are. The list can be found here: https://raw.githubusercontent.com/handshake-org/hsd/1c2d1036...
> Existing TLDs and over 100,000 Alexa websites are reserved on the Handshake blockchain. Upon removing collisions, generic, and exclusions (e.g. 1 or 2 character names), approximately 80,000 names remain. Using the root key and DNSSEC, domain owners can cryptographically prove ownership to the Handshake blockchain to claim names.
Does Handshake control existing (`.com`, `.org`, etc.) domain names or don't they? If they do, then what happens when a DNS entry in Handshake's roots contradicts what's in the ICANN roots? If Handshake wins conflicts, then that breaks the internet for existing users.