From 67264420d276192db67b9276f5cb90f9988c391c Mon Sep 17 00:00:00 2001 From: Sergey Alekseev Date: Wed, 27 Apr 2022 22:27:12 +0300 Subject: [PATCH] simplify claim steps rm unnecessary hs-client installation (see https://github.com/handshake-org/hsd/issues/638#issuecomment-931253002) --- claim/index.html | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/claim/index.html b/claim/index.html index a66b645..132e2af 100644 --- a/claim/index.html +++ b/claim/index.html @@ -100,27 +100,25 @@

Make sure you have nodejs and npm installed first. On MacOS, please install homebrew and run "brew install node unbound". On debian/ubuntu, you can run "sudo apt-get install nodejs npm build-essential libunbound-dev". If you run other distributions or OSes, you can probably figure this part out.

Next, install node-gyp: npm install node-gyp

Download

-

Download hsd, hs-client, and hs-airdrop from https://handshake.org/download/. If downloaded from github, the directory structure is slightly different (hsd-2.4.0/hsd should be replaced with just hsd in these instructions).

-

Extract hsd, hs-client, and hs-airdrop: tar xvf hs*

+

Download hsd and hs-airdrop from https://handshake.org/download/. If downloaded from github, the directory structure is slightly different (hsd-*/hsd should be replaced with just hsd in these instructions).

+

Extract hsd and hs-airdrop: tar xvf hs*

You may also verify the asc file if desired.

Install

-

In one window, change into the hsd directory cd hsd-*/hsd and then run npm install --production

. -

In a second window, change into the hs-client directory cd hs-client-*/hs-client and then run npm install --production

+

In one window, change into the hsd directory cd hsd-*/hsd and then run npm install --production.

+

In a second window, change into the hs-airdrop directory cd hs-airdrop-*/hs-airdrop and then run npm install --production

Run hsd

hsd is the handshake fullnode and will sync with the network

To connect, in the first window run: ./bin/hsd --log-level info

Get your address

-

To claim your airdrop, you need an HNS address to send the coins to. To generate one, in the second window run:

+

To claim your airdrop, you need an HNS address to send the coins to. To generate one, in a third window, change into the hsd directory cd hsd-*/hsd and then run:

./bin/hsw-cli account get default | grep receiveAddress

You should see a string of random looking characters beginning with hs1. The entire string inside the quotes is your public address (this address is public and can be shared). Copy this address and save it

Claim your HNS

-

In the second window, go to the hs-airdrop directory and install hs-airdrop:

-

cd hs-airdrop-*/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 private key you want to check and the hs1XXXX string with the public address you generated earlier. This will prompt for your key's passphrase if encrypted. Please see the hs-airdrop README.md file for more information.

+

In the second window, in the hs-airdrop directory run:

./bin/hs-airdrop --bare ~/.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-*/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 the third window and running (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 propagate 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.

You did it! Please read on! Handshake provides tooling on secure naming and by owning the HNS tokens you can use it to bid on names. You can try bidding on some names before playing around with transfers. Handshake deals with scarce resources, namespaces are unique, consider registering a username/handle you like. Many good names are being registered, apologies if your preferred names are taken -- it's hard to mitigate this in a decentralized way. On the principle of understanding the protocol, it could be interesting for software engineers to go through the process of registering a name for themselves.