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

more typo fixes, maybe squash later

pull/15/head
handshake-web 2021-05-11 03:58:13 +00:00
parent 7050c7b5d1
commit df5484d4bb
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
claim/index.html
View File

@ -141,7 +141,7 @@
<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>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):</p>
<p><b>./bin/hsw-cli master</b></p>
<h2>Summary</h2>
<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 tooling and applications, members of the FOSS community benefits</b>. 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). <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>