From 2de03e7969b32e5a3e98ec4ff3cea8d43eb08705 Mon Sep 17 00:00:00 2001 From: handshake-web Date: Sun, 9 May 2021 10:42:11 +0000 Subject: [PATCH 01/19] Added --bare flag for claim instructions and some descriptions on Handshake --- claim/index.html | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/claim/index.html b/claim/index.html index 5b38a62..353ebec 100644 --- a/claim/index.html +++ b/claim/index.html @@ -92,7 +92,7 @@

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 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 this creates significant security risk. The instructions on this page uses your key to sign a proof. 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).

System Setup

Please read through these instructions carefully, as using cryptographic blockchains are a bit unusual.

@@ -118,24 +118,30 @@

cd hs-airdrop-0.7.1/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

+

./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-0.0.8/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.

+

If you see the transaction, 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. We are dealing with scarce resources, 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's most fun for software engineers to register a name yourself.

Bidding on names

+

It takes about a day before you can do anything. This is a decentralized network without singular leaders or institutions in permanent control, so it will need time to confirm.

After about a day for the redemption to clear on the network, you can use your HNS to register top-level domains (which could also be useful for usernames on systems which use Handshake). Replace NAME with your desired name. Please see the documentation on auctions and protocol summary for more information.

Name status (week in which it will be released if not yet available): ./bin/hsd-cli rpc getnameinfo NAME

Open for bidding (if name is not being opened): ./bin/hsw-cli rpc sendopen NAME

-

Send bid (5 is an example bid amount and 10 is your blinding mask, see documentation): ./bin/hsw-cli rpc sendbid NAME 5 10

+

Send bid (5 is an example bid amount and 10 is your blinding mask, see documentation): ./bin/hsw-cli rpc sendbid NAME 50 500

+

You should set a very high blinding mask as it can dissuade people from using it.

Reveal bid (YOU MUST REVEAL AFTER BIDDING IS CLOSED WITHIN 10-BLOCK-DAYS OR YOU WILL LOSE YOUR COINS, SEE DOCUMENTATION): ./bin/hsw-cli rpc sendreveal NAME

If lost auction, refund coins back to yourself: ./bin/hsw-cli rpc sendredeem

Get a list of all names and the current state: ./bin/hsd-cli rpc getnames

See the documentation on more commands, such as renewals which must be made at least every two years.

Try googling/searching for hns block explorer or looking on an HNS Exchange for a list of bid blinds and bid status of names.

The state of auctions are as follows: OPEN (first ~six hours, cannot bid), BID (~five days, anyone can place bids), REVEAL (~ten days, you MUST reveal your bid or you lose your bid HNS), REDEEM/REGISTER (refund your money or update the DNS record, no time limit for REDEEM). This takes a long time to secure the network, while it is possible to make it fast, true decentralized systems must "confirm" chain states over time and therefore HNS biases towards security and correctness. Selecting instant redemption would be a foolish endeavor (as someone can claim high-value names cheaply) and fast auctions would prove inaccurate or increased vulnerability towards censorship attacks.

+

Handshake enables authenticated proofs, think SSH keys without needing to verify the fingerprint. Just type in the right name and the chain proof verifies the public key. Right now, the most common method is to trust a third party (SSL Cert Authorities) to sign off and one is trusting them to act honestly and competently. Handshake is an attempt to explore an alternative to these constructions. Decentralized authenticated connections require a secure decentralized root of trust which starts with names.

Summary

-

Handshake is a decentralized naming network with the majority ownership of initial coins are distributed to open source developers with available scrapeable keys. Certain kinds of decentralized systems were not historically possible as some entities could overwhelm the network and claim all the resources (in this case, register all names). Handshake is an experiment in distributing majority ownership to the open source community of this network as a method to bootstrap a decentralized network with limited resources, to prevent griefers taking up all the resources. It is hoped that this system could be used as a method wherever decentralized key authentication of names is needed (e.g. decentralized web applications where an association between a name and a cryptographic key proving ownership of that name). In other words, an association between keys and names create the potential for the decentralized web by allocating cryptographically provable resources to names. This could be used to prove the owner of a name published a document, and distributed across a decentralized network. The more applications using this system to secure/prove documents in a decentralized way, the higher the useful aggregate economic/social value of registered names on Handshake (Metcalfe's Law).

+

Handshake is rooted in the culture of open source and distributed the USD funding it raised to the open source community (over $10,000,000 dollars, not tokens, actual bank wires). Additionally, the majority ownership of initial coins are claimable by open source developers with available scrapeable keys. Certain kinds of decentralized systems were not historically possible as some entities could overwhelm the network and claim all the resources (in this case, register all names). Handshake is an experiment in distributing majority ownership to the open source community of this network as a method to bootstrap a decentralized network with limited resources, to prevent griefers taking up all the resources. It is hoped that this system could be used as a method wherever decentralized key authentication of names is needed (e.g. decentralized web applications where an association between a name and a cryptographic key proving ownership of that name). In other words, an association between keys and names create the potential for the decentralized web by allocating cryptographically provable resources to names. This could be used to prove the owner of a name published a document, and distributed across a decentralized network. The more applications using this system to secure/prove documents in a decentralized way, the higher the useful aggregate economic/social value of registered names on Handshake (Metcalfe's Law).

+

The Handshake community is in active development of authenticated proof of names/resources, decentralized social coordination tooling, and developing for decentralized web efforts.

+

IRC: #handshake-dev@freenode

From de4bcbb052f5b687752976fc27c41d679a8c8aa5 Mon Sep 17 00:00:00 2001 From: handshake-web Date: Sun, 9 May 2021 10:50:57 +0000 Subject: [PATCH 02/19] Typo fix --- claim/index.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/claim/index.html b/claim/index.html index 353ebec..2ef1612 100644 --- a/claim/index.html +++ b/claim/index.html @@ -123,14 +123,14 @@

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

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.

-

If you see the transaction, 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. We are dealing with scarce resources, 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's most fun for software engineers to register a name yourself.

+

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. We are dealing with scarce resources, 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's most fun for software engineers to register a name yourself.

Bidding on names

It takes about a day before you can do anything. This is a decentralized network without singular leaders or institutions in permanent control, so it will need time to confirm.

After about a day for the redemption to clear on the network, you can use your HNS to register top-level domains (which could also be useful for usernames on systems which use Handshake). Replace NAME with your desired name. Please see the documentation on auctions and protocol summary for more information.

Name status (week in which it will be released if not yet available): ./bin/hsd-cli rpc getnameinfo NAME

Open for bidding (if name is not being opened): ./bin/hsw-cli rpc sendopen NAME

-

Send bid (5 is an example bid amount and 10 is your blinding mask, see documentation): ./bin/hsw-cli rpc sendbid NAME 50 500

-

You should set a very high blinding mask as it can dissuade people from using it. +

Send bid (150 is an example bid amount and 500 is your blinding mask, see documentation): ./bin/hsw-cli rpc sendbid NAME 150 500

+

You should set a very high blinding mask as it can dissuade people from outbiddig you, the blinding mask is public, you will reveal your actual bid after bidding closes. Choose whatever bid and blinding mask you think makes sense for you. Note that the bid is a "Second-Price Auction", meaning setting a higher value will not result in higher payment unless there is someone else willing to pay that amount.

Reveal bid (YOU MUST REVEAL AFTER BIDDING IS CLOSED WITHIN 10-BLOCK-DAYS OR YOU WILL LOSE YOUR COINS, SEE DOCUMENTATION): ./bin/hsw-cli rpc sendreveal NAME

If lost auction, refund coins back to yourself: ./bin/hsw-cli rpc sendredeem

Get a list of all names and the current state: ./bin/hsd-cli rpc getnames

From cf021bff46ac225b1bb3a622b1d8c5ebe5484ed2 Mon Sep 17 00:00:00 2001 From: handshake-web Date: Sun, 9 May 2021 10:52:21 +0000 Subject: [PATCH 03/19] Fixed directory names on claim page --- claim/index.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/claim/index.html b/claim/index.html index 2ef1612..7e1f047 100644 --- a/claim/index.html +++ b/claim/index.html @@ -99,12 +99,12 @@

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

-

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.4.0/hsd 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.

Install

-

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

+

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

. +

In the second window, change into the hs-client directory and install cd hs-client-0.0.9/hs-client 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

@@ -115,12 +115,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

Claim your HNS

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-0.10.0/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 --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-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-0.0.9/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.

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. We are dealing with scarce resources, 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's most fun for software engineers to register a name yourself.

From b0eddd6be8825a5ff8f65c88c3ec5f38ccc360ed Mon Sep 17 00:00:00 2001 From: handshake-web Date: Sun, 9 May 2021 10:57:54 +0000 Subject: [PATCH 04/19] Another typo fix in claim page. --- claim/index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/claim/index.html b/claim/index.html index 7e1f047..2100530 100644 --- a/claim/index.html +++ b/claim/index.html @@ -123,14 +123,14 @@

If you have a base64 string, you can broadcast it to the network by going back to hs-client (cd hs-client-0.0.9/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.

-

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. We are dealing with scarce resources, 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's most fun for software engineers to register a name yourself.

+

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. We are dealing with scarce resources, 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's could be interesting for software engineers to go through the process of register a name for oneself.

Bidding on names

It takes about a day before you can do anything. This is a decentralized network without singular leaders or institutions in permanent control, so it will need time to confirm.

After about a day for the redemption to clear on the network, you can use your HNS to register top-level domains (which could also be useful for usernames on systems which use Handshake). Replace NAME with your desired name. Please see the documentation on auctions and protocol summary for more information.

Name status (week in which it will be released if not yet available): ./bin/hsd-cli rpc getnameinfo NAME

Open for bidding (if name is not being opened): ./bin/hsw-cli rpc sendopen NAME

Send bid (150 is an example bid amount and 500 is your blinding mask, see documentation): ./bin/hsw-cli rpc sendbid NAME 150 500

-

You should set a very high blinding mask as it can dissuade people from outbiddig you, the blinding mask is public, you will reveal your actual bid after bidding closes. Choose whatever bid and blinding mask you think makes sense for you. Note that the bid is a "Second-Price Auction", meaning setting a higher value will not result in higher payment unless there is someone else willing to pay that amount.

+

You should set a very high blinding mask as it can dissuade people from outbidding you, the blinding mask is public, you will reveal your actual bid after bidding closes. Choose whatever bid and blinding mask you think makes sense for you. Note that the bid is a "Second-Price Auction", meaning setting a higher value will not result in higher payment unless there is someone else willing to pay that amount.

Reveal bid (YOU MUST REVEAL AFTER BIDDING IS CLOSED WITHIN 10-BLOCK-DAYS OR YOU WILL LOSE YOUR COINS, SEE DOCUMENTATION): ./bin/hsw-cli rpc sendreveal NAME

If lost auction, refund coins back to yourself: ./bin/hsw-cli rpc sendredeem

Get a list of all names and the current state: ./bin/hsd-cli rpc getnames

From fa60fdef1a182b735a20996db0e4d5eb0ea2f01d Mon Sep 17 00:00:00 2001 From: handshake-web Date: Sun, 9 May 2021 11:04:43 +0000 Subject: [PATCH 05/19] Typo correction and cleanup of intro --- claim/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/claim/index.html b/claim/index.html index 2100530..c37b3a0 100644 --- a/claim/index.html +++ b/claim/index.html @@ -92,7 +92,7 @@

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 this creates significant security risk. The instructions on this page uses your key to sign a proof. 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 generates a signed proof of ownership of a public key. Please consider against sending your private keys to third parties to do this process on your behalf, as that results in significant risks. Handshake is an experiment in decentralized allocation of ownership of the network to the open source community. 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).

System Setup

Please read through these instructions carefully, as using cryptographic blockchains are a bit unusual.

From d322779bcc0c9ae852fc08a08283c87d4099b900 Mon Sep 17 00:00:00 2001 From: handshake-web Date: Sun, 9 May 2021 11:07:44 +0000 Subject: [PATCH 06/19] Replaced ambiguous 'we' from claim page --- claim/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/claim/index.html b/claim/index.html index c37b3a0..ca700c8 100644 --- a/claim/index.html +++ b/claim/index.html @@ -123,7 +123,7 @@

If you have a base64 string, you can broadcast it to the network by going back to hs-client (cd hs-client-0.0.9/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.

-

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. We are dealing with scarce resources, 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's could be interesting for software engineers to go through the process of register a name for oneself.

+

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's could be interesting for software engineers to go through the process of register a name for oneself.

Bidding on names

It takes about a day before you can do anything. This is a decentralized network without singular leaders or institutions in permanent control, so it will need time to confirm.

After about a day for the redemption to clear on the network, you can use your HNS to register top-level domains (which could also be useful for usernames on systems which use Handshake). Replace NAME with your desired name. Please see the documentation on auctions and protocol summary for more information.

From 27f5423fa1138e75e2a47460f5e9163e013ccccf Mon Sep 17 00:00:00 2001 From: handshake-web Date: Sun, 9 May 2021 11:10:23 +0000 Subject: [PATCH 07/19] Clarify claim page --- claim/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/claim/index.html b/claim/index.html index ca700c8..1908ebf 100644 --- a/claim/index.html +++ b/claim/index.html @@ -137,7 +137,7 @@

See the documentation on more commands, such as renewals which must be made at least every two years.

Try googling/searching for hns block explorer or looking on an HNS Exchange for a list of bid blinds and bid status of names.

The state of auctions are as follows: OPEN (first ~six hours, cannot bid), BID (~five days, anyone can place bids), REVEAL (~ten days, you MUST reveal your bid or you lose your bid HNS), REDEEM/REGISTER (refund your money or update the DNS record, no time limit for REDEEM). This takes a long time to secure the network, while it is possible to make it fast, true decentralized systems must "confirm" chain states over time and therefore HNS biases towards security and correctness. Selecting instant redemption would be a foolish endeavor (as someone can claim high-value names cheaply) and fast auctions would prove inaccurate or increased vulnerability towards censorship attacks.

-

Handshake enables authenticated proofs, think SSH keys without needing to verify the fingerprint. Just type in the right name and the chain proof verifies the public key. Right now, the most common method is to trust a third party (SSL Cert Authorities) to sign off and one is trusting them to act honestly and competently. Handshake is an attempt to explore an alternative to these constructions. Decentralized authenticated connections require a secure decentralized root of trust which starts with names.

+

Handshake enables authenticated proofs, think SSH keys without needing to verify the fingerprint. Just type in the right name and the chain proof provides verified association between the public key and the name/server. Right now, the most common method is to trust a third party (SSL Cert Authorities) to sign off and one is trusting them to act honestly and competently. Handshake is an attempt to explore an alternative to these constructions. Decentralized authenticated connections require a secure decentralized root of trust which starts with names.

Summary

Handshake is rooted in the culture of open source and distributed the USD funding it raised to the open source community (over $10,000,000 dollars, not tokens, actual bank wires). Additionally, the majority ownership of initial coins are claimable by open source developers with available scrapeable keys. Certain kinds of decentralized systems were not historically possible as some entities could overwhelm the network and claim all the resources (in this case, register all names). Handshake is an experiment in distributing majority ownership to the open source community of this network as a method to bootstrap a decentralized network with limited resources, to prevent griefers taking up all the resources. It is hoped that this system could be used as a method wherever decentralized key authentication of names is needed (e.g. decentralized web applications where an association between a name and a cryptographic key proving ownership of that name). In other words, an association between keys and names create the potential for the decentralized web by allocating cryptographically provable resources to names. This could be used to prove the owner of a name published a document, and distributed across a decentralized network. The more applications using this system to secure/prove documents in a decentralized way, the higher the useful aggregate economic/social value of registered names on Handshake (Metcalfe's Law).

The Handshake community is in active development of authenticated proof of names/resources, decentralized social coordination tooling, and developing for decentralized web efforts.

From 435cd0837800656e420eeb529fc277250e8b9e5b Mon Sep 17 00:00:00 2001 From: handshake-web Date: Sun, 9 May 2021 11:17:41 +0000 Subject: [PATCH 08/19] IRC in claim page --- claim/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/claim/index.html b/claim/index.html index 1908ebf..3fd781b 100644 --- a/claim/index.html +++ b/claim/index.html @@ -141,7 +141,7 @@

Summary

Handshake is rooted in the culture of open source and distributed the USD funding it raised to the open source community (over $10,000,000 dollars, not tokens, actual bank wires). Additionally, the majority ownership of initial coins are claimable by open source developers with available scrapeable keys. Certain kinds of decentralized systems were not historically possible as some entities could overwhelm the network and claim all the resources (in this case, register all names). Handshake is an experiment in distributing majority ownership to the open source community of this network as a method to bootstrap a decentralized network with limited resources, to prevent griefers taking up all the resources. It is hoped that this system could be used as a method wherever decentralized key authentication of names is needed (e.g. decentralized web applications where an association between a name and a cryptographic key proving ownership of that name). In other words, an association between keys and names create the potential for the decentralized web by allocating cryptographically provable resources to names. This could be used to prove the owner of a name published a document, and distributed across a decentralized network. The more applications using this system to secure/prove documents in a decentralized way, the higher the useful aggregate economic/social value of registered names on Handshake (Metcalfe's Law).

The Handshake community is in active development of authenticated proof of names/resources, decentralized social coordination tooling, and developing for decentralized web efforts.

-

IRC: #handshake-dev@freenode

+

IRC: #handshake@freenode

From c4637e0912e387704ff6ebd92ebd12ebd927010b Mon Sep 17 00:00:00 2001 From: handshake-web Date: Mon, 10 May 2021 11:44:43 +0000 Subject: [PATCH 09/19] Clarify bidding. --- claim/index.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/claim/index.html b/claim/index.html index 3fd781b..8c879ab 100644 --- a/claim/index.html +++ b/claim/index.html @@ -127,8 +127,9 @@

Bidding on names

It takes about a day before you can do anything. This is a decentralized network without singular leaders or institutions in permanent control, so it will need time to confirm.

After about a day for the redemption to clear on the network, you can use your HNS to register top-level domains (which could also be useful for usernames on systems which use Handshake). Replace NAME with your desired name. Please see the documentation on auctions and protocol summary for more information.

-

Name status (week in which it will be released if not yet available): ./bin/hsd-cli rpc getnameinfo NAME

-

Open for bidding (if name is not being opened): ./bin/hsw-cli rpc sendopen NAME

+

Name status (check a name is available): ./bin/hsd-cli rpc getnameinfo NAME

+

Open for bidding: ./bin/hsw-cli rpc sendopen NAME

+

After sending an open transaction, it will take around 6 hours for bidding to open. You will have around 5 days to submit a bid before bidding closes.

Send bid (150 is an example bid amount and 500 is your blinding mask, see documentation): ./bin/hsw-cli rpc sendbid NAME 150 500

You should set a very high blinding mask as it can dissuade people from outbidding you, the blinding mask is public, you will reveal your actual bid after bidding closes. Choose whatever bid and blinding mask you think makes sense for you. Note that the bid is a "Second-Price Auction", meaning setting a higher value will not result in higher payment unless there is someone else willing to pay that amount.

Reveal bid (YOU MUST REVEAL AFTER BIDDING IS CLOSED WITHIN 10-BLOCK-DAYS OR YOU WILL LOSE YOUR COINS, SEE DOCUMENTATION): ./bin/hsw-cli rpc sendreveal NAME

From bdb1b1fa4fb6a99be62a1f5e54aa0e1b262de4a5 Mon Sep 17 00:00:00 2001 From: handshake-web Date: Tue, 11 May 2021 03:48:12 +0000 Subject: [PATCH 10/19] Updated backup instructions and summary --- claim/index.html | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/claim/index.html b/claim/index.html index 8c879ab..506e616 100644 --- a/claim/index.html +++ b/claim/index.html @@ -92,7 +92,7 @@

Detailed information available in the hs-airdrop README.md file.

-

These instructions generates a signed proof of ownership of a public key. Please consider against sending your private keys to third parties to do this process on your behalf, as that results in significant risks. Handshake is an experiment in decentralized allocation of ownership of the network to the open source community. 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 generates a signed proof of ownership of a public key. Please consider against sending your private keys to third parties to do this process on your behalf, as that results in significant risks. Handshake is an experiment in decentralized allocation of ownership of the network to the open source community, it is believed that open source developers should be one of the primary long-term beneficiaries by owning a necessary resource as the network utility increases. 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).

System Setup

Please read through these instructions carefully, as using cryptographic blockchains are a bit unusual.

@@ -139,9 +139,14 @@

Try googling/searching for hns block explorer or looking on an HNS Exchange for a list of bid blinds and bid status of names.

The state of auctions are as follows: OPEN (first ~six hours, cannot bid), BID (~five days, anyone can place bids), REVEAL (~ten days, you MUST reveal your bid or you lose your bid HNS), REDEEM/REGISTER (refund your money or update the DNS record, no time limit for REDEEM). This takes a long time to secure the network, while it is possible to make it fast, true decentralized systems must "confirm" chain states over time and therefore HNS biases towards security and correctness. Selecting instant redemption would be a foolish endeavor (as someone can claim high-value names cheaply) and fast auctions would prove inaccurate or increased vulnerability towards censorship attacks.

Handshake enables authenticated proofs, think SSH keys without needing to verify the fingerprint. Just type in the right name and the chain proof provides verified association between the public key and the name/server. Right now, the most common method is to trust a third party (SSL Cert Authorities) to sign off and one is trusting them to act honestly and competently. Handshake is an attempt to explore an alternative to these constructions. Decentralized authenticated connections require a secure decentralized root of trust which starts with names.

+

Backing Up

+

If you want to store your coins in the event Handshake's utility and valuation increases in the future via greater development in the open, then you should back up your keys to maintain access to your coins and name for the future.

+

Write down the 12 or 24 words on a piece of paper. These words can recover your names and funds at any time. There is no other backup and no third party can restore it on your behalf without these words. You are interacting with a p2p network, and hence there is no recovery functionality built-in (as this would requiring updating all nodes on the p2p network):

+

./bin/hsw-cli master

Summary

-

Handshake is rooted in the culture of open source and distributed the USD funding it raised to the open source community (over $10,000,000 dollars, not tokens, actual bank wires). Additionally, the majority ownership of initial coins are claimable by open source developers with available scrapeable keys. Certain kinds of decentralized systems were not historically possible as some entities could overwhelm the network and claim all the resources (in this case, register all names). Handshake is an experiment in distributing majority ownership to the open source community of this network as a method to bootstrap a decentralized network with limited resources, to prevent griefers taking up all the resources. It is hoped that this system could be used as a method wherever decentralized key authentication of names is needed (e.g. decentralized web applications where an association between a name and a cryptographic key proving ownership of that name). In other words, an association between keys and names create the potential for the decentralized web by allocating cryptographically provable resources to names. This could be used to prove the owner of a name published a document, and distributed across a decentralized network. The more applications using this system to secure/prove documents in a decentralized way, the higher the useful aggregate economic/social value of registered names on Handshake (Metcalfe's Law).

+

Handshake is rooted in the culture of open source and the majority ownership of initial coins are claimable by open source developers with available scrapeable keys. The original intent was that the free and open source community has inufficient recognition in the long-term benefit in systems. When systems become more popular, the FOSS community does not receive the benefits. If Hanshake becomes more popular with better toolig and applications, members of the FOSS community benefits. It's believed that this aligned incentive creates benefit for all, with recogition via higher network valuation and utility in the future if this method works. Certain kinds of decentralized systems were not historically possible as some entities could overwhelm the network and claim all the resources (in this case, register all names). Handshake is an experiment in distributing majority ownership to the open source community of this network as a method to bootstrap a decentralized network with limited resources, to prevent griefers taking up all the resources. It is hoped that this system could be used as a method wherever decentralized key authentication of names is needed (e.g. decentralized web applications where an association between a name and a cryptographic key proving ownership of that name). In other words, an association between keys and names create the potential for the decentralized web by allocating cryptographically provable resources to names. This could be used to prove the owner of a name published a document, and distributed across a decentralized network. The more applications using this system to secure/prove documents in a decentralized way, the higher the useful aggregate economic/social value of registered names on Handshake (Metcalfe's Law).

The Handshake community is in active development of authenticated proof of names/resources, decentralized social coordination tooling, and developing for decentralized web efforts.

+

If you have questions or are looking to see how to contribute to improve the usability of the network, get in touch with the wider community. There is no official foundation or organization, on HNS you aren't connected to a central server in full control of the network, so there are many community groups. For starting, you can try one of the IRC or telegram channels.

IRC: #handshake@freenode

From fc9510431d2a49199305d52e40349f49d0ec09b4 Mon Sep 17 00:00:00 2001 From: handshake-web Date: Tue, 11 May 2021 03:51:35 +0000 Subject: [PATCH 11/19] typo fix --- claim/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/claim/index.html b/claim/index.html index 506e616..dfe1940 100644 --- a/claim/index.html +++ b/claim/index.html @@ -146,7 +146,7 @@

Summary

Handshake is rooted in the culture of open source and the majority ownership of initial coins are claimable by open source developers with available scrapeable keys. The original intent was that the free and open source community has inufficient recognition in the long-term benefit in systems. When systems become more popular, the FOSS community does not receive the benefits. If Hanshake becomes more popular with better toolig and applications, members of the FOSS community benefits. It's believed that this aligned incentive creates benefit for all, with recogition via higher network valuation and utility in the future if this method works. Certain kinds of decentralized systems were not historically possible as some entities could overwhelm the network and claim all the resources (in this case, register all names). Handshake is an experiment in distributing majority ownership to the open source community of this network as a method to bootstrap a decentralized network with limited resources, to prevent griefers taking up all the resources. It is hoped that this system could be used as a method wherever decentralized key authentication of names is needed (e.g. decentralized web applications where an association between a name and a cryptographic key proving ownership of that name). In other words, an association between keys and names create the potential for the decentralized web by allocating cryptographically provable resources to names. This could be used to prove the owner of a name published a document, and distributed across a decentralized network. The more applications using this system to secure/prove documents in a decentralized way, the higher the useful aggregate economic/social value of registered names on Handshake (Metcalfe's Law).

The Handshake community is in active development of authenticated proof of names/resources, decentralized social coordination tooling, and developing for decentralized web efforts.

-

If you have questions or are looking to see how to contribute to improve the usability of the network, get in touch with the wider community. There is no official foundation or organization, on HNS you aren't connected to a central server in full control of the network, so there are many community groups. For starting, you can try one of the IRC or telegram channels.

+

If you have questions or are looking to see how to contribute to improve the usability of the network, get in touch with the wider community. There is no official foundation or organization, on HNS you aren't connected to a central server in full control of the network, so there are many community groups. For starters, you can try one of the IRC or telegram channels.

IRC: #handshake@freenode

From 6fedc5f9da80c6278b20aec577561c75041addd8 Mon Sep 17 00:00:00 2001 From: handshake-web Date: Tue, 11 May 2021 03:52:52 +0000 Subject: [PATCH 12/19] clarify bidding --- claim/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/claim/index.html b/claim/index.html index dfe1940..15b7c0e 100644 --- a/claim/index.html +++ b/claim/index.html @@ -132,7 +132,7 @@

After sending an open transaction, it will take around 6 hours for bidding to open. You will have around 5 days to submit a bid before bidding closes.

Send bid (150 is an example bid amount and 500 is your blinding mask, see documentation): ./bin/hsw-cli rpc sendbid NAME 150 500

You should set a very high blinding mask as it can dissuade people from outbidding you, the blinding mask is public, you will reveal your actual bid after bidding closes. Choose whatever bid and blinding mask you think makes sense for you. Note that the bid is a "Second-Price Auction", meaning setting a higher value will not result in higher payment unless there is someone else willing to pay that amount.

-

Reveal bid (YOU MUST REVEAL AFTER BIDDING IS CLOSED WITHIN 10-BLOCK-DAYS OR YOU WILL LOSE YOUR COINS, SEE DOCUMENTATION): ./bin/hsw-cli rpc sendreveal NAME

+

Reveal bid (YOU MUST REVEAL AFTER BIDDING IS CLOSED WITHIN 10-BLOCK-DAYS OR YOU WILL LOSE THE COINS YOU ALLOCATED TO BID FROM THE sendbid TRANSACTION, SEE DOCUMENTATION): ./bin/hsw-cli rpc sendreveal NAME

If lost auction, refund coins back to yourself: ./bin/hsw-cli rpc sendredeem

Get a list of all names and the current state: ./bin/hsd-cli rpc getnames

See the documentation on more commands, such as renewals which must be made at least every two years.

From 525888eada8dec28237445fd6b38cd08bfc67a55 Mon Sep 17 00:00:00 2001 From: handshake-web Date: Tue, 11 May 2021 03:55:26 +0000 Subject: [PATCH 13/19] Remoed getnames command as it times out nowadays --- claim/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/claim/index.html b/claim/index.html index 15b7c0e..8faa264 100644 --- a/claim/index.html +++ b/claim/index.html @@ -128,13 +128,13 @@

It takes about a day before you can do anything. This is a decentralized network without singular leaders or institutions in permanent control, so it will need time to confirm.

After about a day for the redemption to clear on the network, you can use your HNS to register top-level domains (which could also be useful for usernames on systems which use Handshake). Replace NAME with your desired name. Please see the documentation on auctions and protocol summary for more information.

Name status (check a name is available): ./bin/hsd-cli rpc getnameinfo NAME

+

If it says "info": null, then the name is available

Open for bidding: ./bin/hsw-cli rpc sendopen NAME

After sending an open transaction, it will take around 6 hours for bidding to open. You will have around 5 days to submit a bid before bidding closes.

Send bid (150 is an example bid amount and 500 is your blinding mask, see documentation): ./bin/hsw-cli rpc sendbid NAME 150 500

You should set a very high blinding mask as it can dissuade people from outbidding you, the blinding mask is public, you will reveal your actual bid after bidding closes. Choose whatever bid and blinding mask you think makes sense for you. Note that the bid is a "Second-Price Auction", meaning setting a higher value will not result in higher payment unless there is someone else willing to pay that amount.

Reveal bid (YOU MUST REVEAL AFTER BIDDING IS CLOSED WITHIN 10-BLOCK-DAYS OR YOU WILL LOSE THE COINS YOU ALLOCATED TO BID FROM THE sendbid TRANSACTION, SEE DOCUMENTATION): ./bin/hsw-cli rpc sendreveal NAME

If lost auction, refund coins back to yourself: ./bin/hsw-cli rpc sendredeem

-

Get a list of all names and the current state: ./bin/hsd-cli rpc getnames

See the documentation on more commands, such as renewals which must be made at least every two years.

Try googling/searching for hns block explorer or looking on an HNS Exchange for a list of bid blinds and bid status of names.

The state of auctions are as follows: OPEN (first ~six hours, cannot bid), BID (~five days, anyone can place bids), REVEAL (~ten days, you MUST reveal your bid or you lose your bid HNS), REDEEM/REGISTER (refund your money or update the DNS record, no time limit for REDEEM). This takes a long time to secure the network, while it is possible to make it fast, true decentralized systems must "confirm" chain states over time and therefore HNS biases towards security and correctness. Selecting instant redemption would be a foolish endeavor (as someone can claim high-value names cheaply) and fast auctions would prove inaccurate or increased vulnerability towards censorship attacks.

From 7050c7b5d15003811611406373c0ad98309aeb39 Mon Sep 17 00:00:00 2001 From: handshake-web Date: Tue, 11 May 2021 03:56:56 +0000 Subject: [PATCH 14/19] typo fixes --- claim/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/claim/index.html b/claim/index.html index 8faa264..b300993 100644 --- a/claim/index.html +++ b/claim/index.html @@ -144,7 +144,7 @@

Write down the 12 or 24 words on a piece of paper. These words can recover your names and funds at any time. There is no other backup and no third party can restore it on your behalf without these words. You are interacting with a p2p network, and hence there is no recovery functionality built-in (as this would requiring updating all nodes on the p2p network):

./bin/hsw-cli master

Summary

-

Handshake is rooted in the culture of open source and the majority ownership of initial coins are claimable by open source developers with available scrapeable keys. The original intent was that the free and open source community has inufficient recognition in the long-term benefit in systems. When systems become more popular, the FOSS community does not receive the benefits. If Hanshake becomes more popular with better toolig and applications, members of the FOSS community benefits. It's believed that this aligned incentive creates benefit for all, with recogition via higher network valuation and utility in the future if this method works. Certain kinds of decentralized systems were not historically possible as some entities could overwhelm the network and claim all the resources (in this case, register all names). Handshake is an experiment in distributing majority ownership to the open source community of this network as a method to bootstrap a decentralized network with limited resources, to prevent griefers taking up all the resources. It is hoped that this system could be used as a method wherever decentralized key authentication of names is needed (e.g. decentralized web applications where an association between a name and a cryptographic key proving ownership of that name). In other words, an association between keys and names create the potential for the decentralized web by allocating cryptographically provable resources to names. This could be used to prove the owner of a name published a document, and distributed across a decentralized network. The more applications using this system to secure/prove documents in a decentralized way, the higher the useful aggregate economic/social value of registered names on Handshake (Metcalfe's Law).

+

Handshake is rooted in the culture of open source and the majority ownership of initial coins are claimable by open source developers with available scrapeable keys. The original intent was that the free and open source community has inufficient recognition in the long-term benefit in systems. When systems become more popular, the FOSS community does not receive the benefits. If Hanshake becomes more popular with better tooling and applications, members of the FOSS community benefits. It's believed that this aligned incentive creates benefit for all, with recognition via higher network valuation and utility in the future if this method works. Certain kinds of decentralized systems were not historically possible as some entities could overwhelm the network and claim all the resources (in this case, register all names). Handshake is an experiment in distributing majority ownership to the open source community of this network as a method to bootstrap a decentralized network with limited resources, to prevent griefers taking up all the resources. It is hoped that this system could be used as a method wherever decentralized key authentication of names is needed (e.g. decentralized web applications where an association between a name and a cryptographic key proving ownership of that name). In other words, an association between keys and names create the potential for the decentralized web by allocating cryptographically provable resources to names. This could be used to prove the owner of a name published a document, and distributed across a decentralized network. The more applications using this system to secure/prove documents in a decentralized way, the higher the useful aggregate economic/social value of registered names on Handshake (Metcalfe's Law).

The Handshake community is in active development of authenticated proof of names/resources, decentralized social coordination tooling, and developing for decentralized web efforts.

If you have questions or are looking to see how to contribute to improve the usability of the network, get in touch with the wider community. There is no official foundation or organization, on HNS you aren't connected to a central server in full control of the network, so there are many community groups. For starters, you can try one of the IRC or telegram channels.

IRC: #handshake@freenode

From df5484d4bb50b9aba23f47dcf6712ac91f334621 Mon Sep 17 00:00:00 2001 From: handshake-web Date: Tue, 11 May 2021 03:58:13 +0000 Subject: [PATCH 15/19] more typo fixes, maybe squash later --- claim/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/claim/index.html b/claim/index.html index b300993..c5ab446 100644 --- a/claim/index.html +++ b/claim/index.html @@ -141,7 +141,7 @@

Handshake enables authenticated proofs, think SSH keys without needing to verify the fingerprint. Just type in the right name and the chain proof provides verified association between the public key and the name/server. Right now, the most common method is to trust a third party (SSL Cert Authorities) to sign off and one is trusting them to act honestly and competently. Handshake is an attempt to explore an alternative to these constructions. Decentralized authenticated connections require a secure decentralized root of trust which starts with names.

Backing Up

If you want to store your coins in the event Handshake's utility and valuation increases in the future via greater development in the open, then you should back up your keys to maintain access to your coins and name for the future.

-

Write down the 12 or 24 words on a piece of paper. These words can recover your names and funds at any time. There is no other backup and no third party can restore it on your behalf without these words. You are interacting with a p2p network, and hence there is no recovery functionality built-in (as this would requiring updating all nodes on the p2p network):

+

Write down the 12 or 24 words on a piece of paper. These words can recover your names and funds at any time. There is no other backup and no third party can restore it on your behalf without these words. You are interacting with a p2p network, and hence there is no recovery functionality built-in (as this would require updating all nodes on the p2p network):

./bin/hsw-cli master

Summary

Handshake is rooted in the culture of open source and the majority ownership of initial coins are claimable by open source developers with available scrapeable keys. The original intent was that the free and open source community has inufficient recognition in the long-term benefit in systems. When systems become more popular, the FOSS community does not receive the benefits. If Hanshake becomes more popular with better tooling and applications, members of the FOSS community benefits. It's believed that this aligned incentive creates benefit for all, with recognition via higher network valuation and utility in the future if this method works. Certain kinds of decentralized systems were not historically possible as some entities could overwhelm the network and claim all the resources (in this case, register all names). Handshake is an experiment in distributing majority ownership to the open source community of this network as a method to bootstrap a decentralized network with limited resources, to prevent griefers taking up all the resources. It is hoped that this system could be used as a method wherever decentralized key authentication of names is needed (e.g. decentralized web applications where an association between a name and a cryptographic key proving ownership of that name). In other words, an association between keys and names create the potential for the decentralized web by allocating cryptographically provable resources to names. This could be used to prove the owner of a name published a document, and distributed across a decentralized network. The more applications using this system to secure/prove documents in a decentralized way, the higher the useful aggregate economic/social value of registered names on Handshake (Metcalfe's Law).

From f01578982713a792ddaeae2bdb09c4db25b5c26a Mon Sep 17 00:00:00 2001 From: handshake-web Date: Wed, 12 May 2021 15:14:36 +0000 Subject: [PATCH 16/19] Add notice on top --- claim/index.html | 1 + 1 file changed, 1 insertion(+) diff --git a/claim/index.html b/claim/index.html index c5ab446..2b7e8de 100644 --- a/claim/index.html +++ b/claim/index.html @@ -92,6 +92,7 @@

Detailed information available in the hs-airdrop README.md file.

+

UPDATE: Please be careful about using other software, giving away your private key to others, or following instructions on random websites who are not HNS community members. Those websites may incorrectly state that these instructions are currently outdated; those instructions have not been validated by the Handshake community.

These instructions generates a signed proof of ownership of a public key. Please consider against sending your private keys to third parties to do this process on your behalf, as that results in significant risks. Handshake is an experiment in decentralized allocation of ownership of the network to the open source community, it is believed that open source developers should be one of the primary long-term beneficiaries by owning a necessary resource as the network utility increases. 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).

System Setup

From 42f59145950551a539bae5cf6922af35930517d8 Mon Sep 17 00:00:00 2001 From: handshake-web Date: Wed, 12 May 2021 15:15:37 +0000 Subject: [PATCH 17/19] s/websites/instructions/ --- claim/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/claim/index.html b/claim/index.html index 2b7e8de..f836f3b 100644 --- a/claim/index.html +++ b/claim/index.html @@ -92,7 +92,7 @@

Detailed information available in the hs-airdrop README.md file.

-

UPDATE: Please be careful about using other software, giving away your private key to others, or following instructions on random websites who are not HNS community members. Those websites may incorrectly state that these instructions are currently outdated; those instructions have not been validated by the Handshake community.

+

UPDATE: Please be careful about using other software, giving away your private key to others, or following instructions on random websites who are not HNS community members. Those instructions may incorrectly state that these instructions are currently outdated; those instructions have not been validated by the Handshake community.

These instructions generates a signed proof of ownership of a public key. Please consider against sending your private keys to third parties to do this process on your behalf, as that results in significant risks. Handshake is an experiment in decentralized allocation of ownership of the network to the open source community, it is believed that open source developers should be one of the primary long-term beneficiaries by owning a necessary resource as the network utility increases. 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).

System Setup

From 19a4ff28b411ed89a7e67b501ed0164d0dd8b575 Mon Sep 17 00:00:00 2001 From: handshake-web Date: Wed, 12 May 2021 16:19:26 +0000 Subject: [PATCH 18/19] Remove duplicate section on backing up seed --- claim/index.html | 1 - 1 file changed, 1 deletion(-) diff --git a/claim/index.html b/claim/index.html index f836f3b..08a93d8 100644 --- a/claim/index.html +++ b/claim/index.html @@ -113,7 +113,6 @@

To claim your airdrop, you need an HNS address to send the coins to. To generate one, in the second window 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

-

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

Claim your HNS

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

cd hs-airdrop-0.10.0/hs-airdrop

From 5b84714b31f35c81651af3192e126eb87f6ab01f Mon Sep 17 00:00:00 2001 From: handshake-web Date: Wed, 12 May 2021 16:24:38 +0000 Subject: [PATCH 19/19] update --- claim/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/claim/index.html b/claim/index.html index 08a93d8..5f53faa 100644 --- a/claim/index.html +++ b/claim/index.html @@ -92,7 +92,7 @@

Detailed information available in the hs-airdrop README.md file.

-

UPDATE: Please be careful about using other software, giving away your private key to others, or following instructions on random websites who are not HNS community members. Those instructions may incorrectly state that these instructions are currently outdated; those instructions have not been validated by the Handshake community.

+

UPDATE: Please be careful about using other software or giving away your private key to others. In addition, one should be careful about following instructions on random websites who are not HNS community members as those instructions may incorrectly state that this page is currently outdated or contain other errors; instructions made by those who are not active users or community participants in Handshake likely have not been validated by the Handshake community.

These instructions generates a signed proof of ownership of a public key. Please consider against sending your private keys to third parties to do this process on your behalf, as that results in significant risks. Handshake is an experiment in decentralized allocation of ownership of the network to the open source community, it is believed that open source developers should be one of the primary long-term beneficiaries by owning a necessary resource as the network utility increases. 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).

System Setup