Detailed information available in the hs-airdrop README.md file.
-These instructions generates a signed proof of ownership of a public key. Please be careful about using other software or giving away your private key to others, as they would be able to generate proofs on your behalf. Handshake is an experiment in decentralized allocation of ownership of the network to the open source community. If this model is successful, people may replicate this distribution model in distribution of ownership to Open Source Developers and Organizations, giving away your private key prevents you from claiming on other systems. This HNS airdrop is a native limited resource used to register top-level domains and usernames (a limited resource is needed in decentralized naming systems, as a single bad actor would register all useful names in existence if no limited resources existed).
+These instructions generate a signed proof of ownership of a public key. Please be careful about using other software or giving away your private key to others, as they would be able to generate proofs on your behalf. Handshake is an experiment in decentralized allocation of ownership of the network to the open source community. If this model is successful, people may replicate this distribution model in distribution of ownership to Open Source Developers and Organizations, giving away your private key prevents you from claiming on other systems. This HNS airdrop is a native limited resource used to register top-level domains and usernames (a limited resource is needed in decentralized naming systems, as a single bad actor would register all useful names in existence if no limited resources existed).
This page explains how github developers with over 15 followers on February 2019, or in the PGP WoT Strong Set can claim HNS. Being able to claim does NOT imply that one is a "top open source developer", this system was optimized for a list of previously scrapeable keys (and could not be modified after the Handshake network launches without a hard fork).
Please read through these instructions carefully, as using cryptographic blockchains are a bit unusual.
Make sure you have nodejs and npm installed first. On MacOS, please install homebrew and run "brew install node". On debian/ubuntu, you can run "sudo apt-get install nodejs npm build-essential". If you run other distributions or OSes, you can probably figure this part out.
Next, install node-gyp: npm install node-gyp
Download hsd, hs-client, and hs-airdrop from https://handshake.org/download/. If downloaded from github, the directory structure is slightly different (hsd-2.0.2/hsd should be replaced with just hsd in these instructions).
+Download hsd, hs-client, and hs-airdrop from https://handshake.org/download/. If downloaded from github, the directory structure is slightly different (hsd-2.0.2/hsd or other version number direcory should be replaced with just hsd in these instructions).
Extract hsd, hs-client, and hs-airdrop: tar xvf hs*
You may also verify the asc file if desired.
In one window, change into the hsd directory and install cd hsd-2.0.2/hsd and then run npm install --production
. -In the second window, change into the hs-client directory and install cd hs-client-0.0.8/hs-client and then run npm install --production
+(Please note, x.x.x = version number below)
+In one window, change into the hsd directory cd hsd-x.x.x/hsd and then install by running npm install --production
. +In the second window, change into the hs-client directory and install cd hs-client-x.x.x/hs-client and then run npm install --production
hsd is the handshake fullnode and will sync with the network
To connect, in the first window run: ./bin/hsd --log-level info
@@ -115,12 +116,12 @@To save a copy of your private key, write down the output of the 12 word phrase on a piece of paper (do not save it in the cloud anywhere): ./bin/hsw-cli master | grep phrase
In the second window, go to the hs-airdrop directory and install hs-airdrop:
-cd hs-airdrop-0.7.1/hs-airdrop
+cd hs-airdrop-x.x.x/hs-airdrop
Then install the dependencies: npm install --production
Check if your key is in the airdrop. Replace id_rsa with the location of your key you want to check and the hs1XXXX string with the public address you generated earlier. Please see the hs-airdrop README.md file for more information.
./bin/hs-airdrop ~/.ssh/id_rsa hs1XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
This may take a while, as it is trying to find and decrypt a message to your key. If successful you should see a base64 string. A NonceError means your key was not included, you can try another key.
-If you have a base64 string, you can broadcast it to the network by going back to hs-client (cd hs-client-0.0.8/hs-client) and typing (replace BASE64_STRING with the string dumped from hs-airdrop): ./bin/hsd-cli rpc sendrawairdrop BASE64_STRING
+If you have a base64 string, you can broadcast it to the network by going back to hs-client (cd hs-client-x.x.x/hs-client) and typing (replace BASE64_STRING with the string dumped from hs-airdrop): ./bin/hsd-cli rpc sendrawairdrop BASE64_STRING
You should see it return a hex hash if successful. In an hour or two you should see it propogate over the network. You can see the updated balance by running: ./bin/hsw-cli balance
You can also try searching for your hs1 address balance by googling/searching: hns block explorer in your web browser and pasting in your hs1 address.