ryan
/
handshake
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Typo fix

pull/1/head
handshake-web 2020-02-23 01:36:13 +00:00
parent 2adfbc27e1
commit bd7360317b
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
claim/index.html
View File

@ -120,7 +120,7 @@
<p>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.</p>
<p><b>./bin/hs-airdrop ~/.ssh/id_rsa hs1XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</b></p>
<p>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.</p>
<p>If you have a base64 string, you can broadcast it to the network by going back to hs-client (<b>cd hs-client-0.0.8/hs-client</b>) and typing (replace BASE64_STRING with the string dumped from hs-airdrop: <b>./bin/hsd-cli rpc sendrawairdrop BASE64_STRING</b></p>
<p>If you have a base64 string, you can broadcast it to the network by going back to hs-client (<b>cd hs-client-0.0.8/hs-client</b>) and typing (replace BASE64_STRING with the string dumped from hs-airdrop): <b>./bin/hsd-cli rpc sendrawairdrop BASE64_STRING</b></p>
<p>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: <b>./bin/hsw-cli balance</b></p>
<p>You can also try searching for your hs1 address balance by googling/searching: <b>hns block explorer</b> in your web browser and pasting in your hs1 address.</p>
<h2>Bidding on names</h2>
@ -135,7 +135,7 @@
<p>Try googling/searching for <b>hns block explorer</b> or looking on an HNS Exchange for a list of bid blinds and bid status of names.</p>
<p>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.</p>
<h2>Summary</h2>
<p>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). <b>In other words, an association between keys and names create the potential for the decentralized web by allocating cyrptographically provable resources to names.</b> 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).</p>
<p>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). <b>In other words, an association between keys and names create the potential for the decentralized web by allocating cryptographically provable resources to names.</b> 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).</p>
</div></div></section>
</div>