4 ms·

If this gains traction, you will be able to pay a service provider a fee to update DNS entries for you. This is like the current system used by registrars. Yo

• mugsie 7y ago
  > you will be able to pay a service provider a fee to update DNS entries for you. So every time I add a new LB, or cycle out an environment I have to pay someone? And then wait for them to process the chain to publish the result? Remind me, what did etherium get to for transactons to clear? 20 something hours? That is not something I want when I am trying to redirect traffic from either a set of NS records that are broken, or if I host the full zone in the chain, a broken AWS / Azure region. Combine the time to wait for caches to refresh on the internets (better these days, but still longer than people would like), with waiting for a blockchain to publish my new records, and you have ops people in pain. DNS is already one of the largest fault tolerant, eventually consistent, cachable, federated, and globally distributed key value databases ever to exist - we don't need to add blockchain to the mix.
  • tynes 7y ago
    Handshake is for top level domains. You can do quick updates using traditional DNS infrastructure at a domain underneath a Handshake top level domain. The benefit is that you have a cryptographic asset representing the top level domain, the root of trust comes from you, value can accrue in the asset itself, its tradable with non interactive atomic swaps and is censorship resistant.