The article and Namebase faq go into some details, but just so I understand, what are the practical effects of this beyond decentralization? - If I buy a TLD, will I own it in perpetuity, even after I die? - If we're encouraging people to register their own TLDs, won't we run into the same limited-name/squatter problems as normal domains? I get that names are being released at a trickle, but that seems like it would…
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 t…
Decentralized DNS with the Handshake Naming System
71–75 of 75 posts
Re: Decentralized DNS with the Handshake Naming System
#72Earlier quoted context omitted.
> Good luck with that. If there is no way to have a US court take ownership of a domain (or force someone to handover a bad faith registration), someone will either end up in jail for contempt, or it will just be banned. This same argument applies to bitcoin and it has not (yet) been banned in much of the free world.
We don't see them trying to change anything on the chain with bitcoin - just trace people (and law enforcement has gotten pretty good at that to be fair). They seize wallets from people they arrest, like normal cash / assets, or get a court order to get companies holding the coin to hand them over, if the accused used a hosted wallet.
Re: Decentralized DNS with the Handshake Naming System
#73Earlier quoted context omitted.
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…
Unfortunately the seeder peers aren't up right now, see here for a fresh peers list https://hnscan.com/peers
Re: Decentralized DNS with the Handshake Naming System
#74Earlier quoted context omitted.
Unfortunately the seeder peers aren't up right now, see here for a fresh peers list https://hnscan.com/peers
502 Bad Gateway
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:13038Re: Decentralized DNS with the Handshake Naming System
#75As an FYI for HN, many of y'all are probably eligible for $400-800 of Handshake coins (HNS). Handshake is airdropping coins to open-source developers to incentivize them to check out the project. If you have over 15 followers on GitHub you can use this tool to claim coins. This is a no-strings-attached giveaway so if you want to you can also sell your coins but it'd be worth it to bid on your name before you do. You…