3 ms·
> If users choose to use Handshake as their DNS roots, they will no longer be able to access websites which only exist on ICANN's root zone. This is not true.
by xur17 7y ago
> If users choose to use Handshake as their DNS roots, they will no longer be able to access websites which only exist on ICANN's root zone.
This is not true. You can setup Handshake to be your resolver, and it will resolve both domains on handshake, and legacy domains from icann.
- Ajedi32 7y agoThen what's this paragraph in the FAQ about? > 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.
- xur17 7y agoI 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. [0] https://news.ycombinator.com/item?id=22312059 https://news.ycombinator.com/item?id=22312059
- Ajedi32 7y agoOkay, that's much better. Thanks for the clarification. I assume "com", "org", "net", "ninja", etc are also reserved then?
- xur17 7y agoYes, they are. The list can be found here: https://raw.githubusercontent.com/handshake-org/hsd/1c2d1036b262ecb767e71a73cd91ef11c940b230/lib/covenants/names.json https://raw.githubusercontent.com/handshake-org/hsd/1c2d1036...