Re:Decentralized DNS with the Handshake Naming System
by oauea on Tuesday August 06, 2019 @01:02PM
(#20627122)
> Handshake TLDs need to be renewed every two years or the names go back up for auction. Renewals must include a recent block hash to prove that the name owner is still active and has _recently_ signed the renewal transaction.
Can't this just be automated?
Re:Decentralized DNS with the Handshake Naming System
by troquerre on Tuesday August 06, 2019 @02:54PM
(#20628297)
Yes! Another comment mentioned that you’ll need to keep keys online to do this, which is not completely true. You can also create a key that can only be used renew your names that’s separate from your master key.
- Yes, names are rolled out over 52 weeks based on the hash of the name (modulo 52), which was designed to prevent squatting. The auction & renewals processes should help as well.
- Yes, Handshake uses proof-of-work. It's a different algorithm (Blake2b keyed with KMAC256) than Bitcoin but still essentially relies on energy consumption for security.
- I'm not aware of any other major integrations. But it is easy for users to run their OWN local light client and use it as the DNS resolver for their OS: https://github.com/handshake-org/hnsd