Decentralized DNS with the Handshake Naming System

Re:Decentralized DNS with the Handshake Naming System by troquerre on Tuesday August 06, 2019 @12:31PM (#20626722)

I work at Namebase.The other comments address most of your questions, but just to add on: the 52 week rollout will help significantly with preventing squatters. Handshake has designed some other mechanisms that prevent squatting. The first is that the Alexa top 100k domains have been pre-registered (only facebook.com can register .facebook on Handshake). This ensures that existing domain stakeholders can transition to Handshake without worrying about their name being squatted on.

Second, Handshake is airdropping 70% of the mainnet coins to open-source developers. If you have over 15 followers on GitHub, you can claim around $400-800 of Handshake coins (HNS) with no strings attached. Not only will this give developers an incentive to check Handshake out, but also this ensures that the bidding power is spread out at launch. Without this mechanism, a whale could spend $10mm on HNS at launch and outbid everyone.

[ Parent | on HN ]

Re:Decentralized DNS with the Handshake Naming System by thinkmassive on Tuesday August 06, 2019 @04:09PM (#20629014)

Is there a way to be included if we have fewer than 15 followers? I've open sourced some personal projects, and I'm interested in claiming my domain (already did this on ENS), but after visiting handshake.org I did not see a way to participate without being included in the automated airdrop. Thanks!

[ Parent | on HN ]

Re:Decentralized DNS with the Handshake Naming System by LyndsySimon on Tuesday August 06, 2019 @01:40PM (#20627526)

> If you have over 15 followers on GitHub, you can claim around $400-800 of Handshake coins (HNS) with no strings attached.

How will one go about this? I'm interested, if only for the purpose of claiming a few domains that I have a personal interest in.

[ Parent | on HN ]

Re:Decentralized DNS with the Handshake Naming System by SkyMarshal on Tuesday August 06, 2019 @01:54PM (#20627674)

Go to https://handshake.org/ and click the top link under Developer Airdrop.

[ Parent | on HN ]

Re:Decentralized DNS with the Handshake Naming System by troquerre on Tuesday August 06, 2019 @02:52PM (#20628270)

You can use https://github.com/handshake-org/hs-airdrop to claim your coins on the testnet. You’ll have to repeat the process once the mainnet launches.

If you want an easier way to claim and use your coins I can also add you to our private beta for Namebase.io. Just ping me at tieshun at namebase.io.

[ Parent | on HN ]

Re:Decentralized DNS with the Handshake Naming System by xur17 on Tuesday August 06, 2019 @03:29PM (#20628622)

There was a post on HN about a year ago announcing Handshake, with an option to signup for the airdrop with your github account, irc account, etc.

Do you know if these users will still receive the tokens they signed up for? Should these tokens show up on testnet?

[ Parent | on HN ]

Re:Decentralized DNS with the Handshake Naming System by troquerre on Tuesday August 06, 2019 @03:40PM (#20628711)

You should have received a seed phrase as part of that airdrop. You'll be able to use that seed phrase to claim your tokens on the testnet and mainnet. Ping me at tieshun at namebase.io if you want to try things out on testnet — I'm happy to walk you through it.

[ Parent | on HN ]

Re:Decentralized DNS with the Handshake Naming System by ishanjain28 on Tuesday August 06, 2019 @01:21PM (#20627331)

Hey! So, I thought this was cool and wanted to try it out.

Compiled hnsd and tried to run it on local machine and an ec2 spot instance but it keeps failing to connect to it's (hardcoded?) peers.

I keep seeing this,

peer 354 (172.104.177.177:13038): failed connecting: connection refused peer 354 (172.104.177.177:13038): closing peer peer 354 (172.104.177.177:13038): closed peer peer 355 (139.162.183.168:13038): failed connecting: connection refused peer 355 (139.162.183.168:13038): closing peer peer 355 (139.162.183.168:13038): closed peer peer 353 (172.104.214.189:13038): failed connecting: connection refused peer 353 (172.104.214.189:13038): closing peer peer 353 (172.104.214.189:13038): closed peer peer 352 (173.255.209.126:13038): failed connecting: connection refused peer 352 (173.255.209.126:13038): closing peer peer 352 (173.255.209.126:13038): closed peer peer 357 (172.104.177.177:13038): failed connecting: connection refused peer 357 (172.104.177.177:13038): closing peer peer 357 (172.104.177.177:13038): closed peer peer 359 (139.162.183.168:13038): failed connecting: connection refused peer 359 (139.162.183.168:13038): closing peer peer 359 (139.162.183.168:13038): closed peer peer 358 (172.104.214.189:13038): failed connecting: connection refused peer 358 (172.104.214.189:13038): closing peer peer 358 (172.104.214.189:13038): closed peer peer 356 (173.255.209.126:13038): failed connecting: connection refused peer 356 (173.255.209.126:13038): closing peer peer 356 (173.255.209.126:13038): closed peer peer 363 (172.104.177.177:13038): failed connecting: connection refused peer 363 (172.104.177.177:13038): closing peer peer 363 (172.104.177.177:13038): closed peer peer 361 (139.162.183.168:13038): failed connecting: connection refused peer 361 (139.162.183.168:13038): closing peer peer 361 (139.162.183.168:13038): closed peer peer 362 (172.104.214.189:13038): failed connecting: connection refused peer 362 (172.104.214.189:13038): closing peer peer 362 (172.104.214.189:13038): closed peer peer 360 (173.255.209.126:13038): failed connecting: connection refused peer 360 (173.255.209.126:13038): closing peer peer 360 (173.255.209.126:13038): closed peer

Also, These IP address are either blocking ICMP ping messages or outright unreachable because ping fails to talk to them.

[ Parent | on HN ]

Re:Decentralized DNS with the Handshake Naming System by tynes on Tuesday August 06, 2019 @01:31PM (#20627439)

Unfortunately the seeder peers aren't up right now, see here for a fresh peers list

https://hnscan.com/peers

[ Parent | on HN ]

Re:Decentralized DNS with the Handshake Naming System by drexlspivey on Tuesday August 06, 2019 @04:43PM (#20629422)

502 Bad Gateway

[ Parent | on HN ]

Re:Decentralized DNS with the Handshake Naming System by ishanjain28 on Tuesday August 06, 2019 @04:49PM (#20629474)

I tried it right after he suggested doing that.

Try this command, It contains a list of peers that were working few hours back. Maybe they are still online.

  ./hnsd -r 127.0.0.1:53  -s ajgkxfe47u6wwyvyh7qixbdddvjxcqbs2oxwr5attq45yj72s5pcs@54.201.46.33:13038,akudgzg2wntfjucsodyvz44h76qae7xrtuix6wc6fc22cx5jll6fe@165.227.52.206:13038,ajaqq7jwqrwixmvl64tzi3qfi7ynj3hmmtzmkyubtrljh4mwmh7ie@165.22.151.242:13038,ap77bve4acntajehkvqc33bvlsi27ka6l2xte4fhn2ghuwx44fsxc@18.236.58.201:13038

[ Parent | on HN ]