Hacker News Reader

Comment by danShumway | Hacker News Reader

I'm not affiliated with Handshake in any way.

But my assumption is that there would still be registrars that can handle this sort of thing for you, in the same way that a service like Netlify can handle setting up a static site server and renewing LetsEncrypt certificates. It's just that if you wanted to do it manually, you could.

View on HN

Exactly. We built a registrar for Handshake (https://namebase.io) and our service will automatically handle renewal transactions. That said, anyone can still manage their keys and submit renewal transactions on their own if they want to do that, similar to how you can use Coinbase vs a desktop wallet for Bitcoin.

Thanks. I’m still wary of the bi-annual renewal requirement. If I register a name today, can I renew it one year later from today to stretch it to two years from then (which would be three years from now) or would I be able to renew it for two years only near the end of the two year period? In other words, can I perpetually have it renewed to approximately two years in the future at all times? If not, that brings the same risk I talked about in my comment above (where families may not have enough time to figure things out and handle it).

It's not even that. It reads like it's a cliff. Currently under ICANN, if you fail to renew a domain, you have ~90 days to figure out that you didn't renew it before it's lost forever. Even if it's scripted to renew, it could fail for any number of reasons (lack of fiat currency, transient network failures, lack of crypto-currency, etc).

Thanks. That makes sense. For some reason I didn’t think of concentrated service providers because I was too focused on decentralization (and to think of it, such concentrated providers are everywhere in decentralized platforms).

Reply on news.ycombinator.com