* install `https://github.com/handshake-org/hsd` - run `./bin/hsd` and wait for wallet to sync
* install `https://github.com/handshake-org/hs-client` - run `./bin/hsw-cli account create` and `./bin/hsw-cli --account=default address` - copy address
* install `https://github.com/handshake-org/hs-airdrop` - follow instructions depending on how you whether you want to give the cli your key or sign manually - simplest way is something like `hs-airdrop <key-file> <address>`
* back in `hs-client` - run ./bin/hsd-rpc sendrawairdrop <base64-from-hs-airdrop>`
* leave the wallet running and wait for 20 or something blocks
* back in `hs-client` - `./bin/hsw-cli balance --account=default` should now have a balance.
Handshake is a decentralized naming and certificate authority [1]. It decentralizes the DNS root and allows for the people of the internet to own names instead of leasing from a TLD provider like Verisign [2] among other things like removing trust from the SSL equation, instead allowing for verification on the blockchain (right now, we simply trust CA providers who have issued rogue SSL certs [3]). It launched in early February, and since then, has gained a lot of momentum [4].
One name, crypto, sold for 588785 HNS, which at today's exchange rate of $.30 [5], would be $176,000.
The system is live and works with the legacy TLDs (eg, verisign continues to own "com" on Handshake and thus all existing domains continue to work). You can download hsd [6] or use an extension for chrome from Namebase [7] to start using the Handshake Naming System.
Hope this helps!
[2] Verisign controls .com
[3] https://arstechnica.com/information-technology/2017/01/alrea...
[5] https://www.coingecko.com/en/coins/handshake
[6] https://github.com/handshake-org/hsd
[7] https://chrome.google.com/webstore/detail/namebase-handshake...
The really important metric is how much traffic on the web is accessed using Handshake names, and how how many users can resolve those names. Are there any numbers on that?
HNS coins can be sold on Namebase Pro or on a few Chinese smaller exchanges. They can also be used for TLD auctions on Namebase. Hopefully many more use cases to come.
The top ~250,000 users on github have had their SSH keys and PGP added to a merkle tree. Out of those ~250,000 users, ~175,000 of them had valid SSH and PGP keys at the time of tree creation.
If you had 15 or more followers on github during the week of 2019-02-04, your github SSH & PGP keys are included in the merkle tree.
> As a final addition, Hacker News accounts which are linked with Keybase accounts are included in the tree provided they were ~1.5 years old during the crawl.
But it's not entirely clear to me how I find out whether I was included or not, or where I'd be able to sell it.
I don't understand. Is there a definition for 'open source developer', or is everyone in the definition you provided getting this?
When will it happen?
