Updated backup instructions and summary

claim/index.html

@@ -92,7 +92,7 @@
 
 <section class="light claim"><div class="section-wrapper"><div>
   <p><a href="https://github.com/handshake-org/hs-airdrop">Detailed information available in the hs-airdrop README.md file.</a></p>
-  <p><b>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).</b></p>
+  <p><b>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).</b></p>
   <p>This page explains how <b>github developers with over 15 followers on February 2019</b>, or in the <b>PGP WoT Strong Set</b> 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).</p>
   <h2>System Setup</h2>
   <p>Please read through these instructions carefully, as using cryptographic blockchains are a bit unusual.</p>
@@ -139,9 +139,14 @@
   <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>
   <p><b>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.</b></p>
+  <h2>Backing Up</h2>
+  <p>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.</p>
+  <p>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):</p>
+  <p><b>./bin/hsw-cli master</b></p>
   <h2>Summary</h2>
-  <p>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). <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>
+  <p>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. <b>If Hanshake becomes more popular with better toolig and applications, members of the FOSS community benefits</b>. 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). <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>
   <p>The Handshake community is in active development of authenticated proof of names/resources, decentralized social coordination tooling, and developing for decentralized web efforts.</p>
+  <p><b>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.</b></p>
   <p><b>IRC: #handshake@freenode</b></p>
 </div></div></section>