Handshake

Frequently asked questions

What is Handshake?

Handshake is an experiment in creating a decentralized network that allows for a global allocation of names. It aims to provide an alternative to the current centralized systems that control handles, usernames, and domain names on the internet. Handshake enables decentralized web services to experiment by offering key management, server/service authentication, and decentralized lookup of name records. It seeks to explore new ways to build a more decentralized internet and reduce the reliance on trusted third parties and certificate authorities. The Handshake community is decentralized, and forking and maintaining separate distributions is encouraged. It is important to note that Handshake does not have an official foundation, entity, or team page.

How does Handshake aim to make the internet more secure?

Handshake aims to make the internet more secure by replacing the current centralized trusted internet infrastructure with a decentralized Certificate Authority (CA) and globally unique namespace. Currently, the internet relies on a single trust root DNS zone and trusted CAs to secure connections. However, this creates a reliance on a few trusted actors, many of whom are for-profit corporations with potential conflicts of interest. If any one of these trusted CAs fails, the entire security of the internet is compromised.

Handshake proposes a decentralized network where cryptoeconomic incentives are used to establish consensus on the association between names and certificates. By providing a decentralized lookup of name records and using cryptographic proofs backed by cryptoeconomic mechanisms, Handshake aims to eliminate the need for a trusted CA corporation. This would reduce the risk of centralized control and potential vulnerabilities.

In summary, Handshake aims to make the internet more secure by decentralizing the trust anchor and providing a secure association between names and servers without relying on a single trusted entity or a handful of trusted CAs.

Where can I find the Handshake project on GitHub?

The Handshake project can be found on GitHub at github.com/handshake-org.

What are the risks associated with sharing private keys for the claiming process?

Sharing private keys for the claiming process can result in significant risks. Private keys are used to generate a signed proof of ownership of a public key. By sharing private keys with third parties, individuals expose themselves to potential security breaches and unauthorized access to their digital assets. Handshake, being an experiment in decentralized ownership, emphasizes the importance of open source developers benefiting from the network utility. The HNS airdrop, which is a limited resource used for registering top-level domains and usernames, requires the careful handling of private keys. It is advised not to send private keys to third parties for the claiming process to mitigate the associated risks.

How does Handshake ensure unique names within a namespace?

Handshake ensures unique names within a namespace by utilizing a decentralized blockchain and cryptographic proofs backed by cryptoeconomic mechanisms. It aims to replace centralized trusted internet infrastructure, such as the current DNS system, with a decentralized Certificate Authority and globally unique namespace. By decentralizing the allocation of ownership of the network to the open-source community, Handshake aims to prevent a single bad actor from registering all useful names in existence. This is achieved by introducing a limited resource, called HNS, which is used to register top-level domains and usernames. The cryptoeconomic incentives established by Handshake coordinate consensus on the association between names and certificates, ensuring uniqueness within the namespace.

What are the available files for download and their requirements?

The available files for download and their requirements are as follows:

1. hsd-6.1.0.tar.gz (asc) - Requires node-gyp to build. Execute hsd-6.1.0/build.
2. hs-client-6.0.0.tar.gz (asc) - Requires Node.js version 14+ to run. Execute hsd-6.1.0/hsd/bin/hsd.
3. hs-airdrop-0.10.0.tar.gz (asc) - No specific requirements mentioned.
4. hs-miner-0.0.10.tar.gz (asc) - No specific requirements mentioned.

Please note that the tarball signers list can be checked in the SECURITY file. Additionally, SHA256 checksums are provided for each file:

• hsd-6.1.0.tar.gz: 33bd61711c06319a0b3487ff68363fbd3a43fec49bb776754242924a0acae38b
• hs-airdrop-0.10.0.tar.gz: b2dd2438f8552c880a4659cacb41ce59108d07bce08c291c6a690abe4f7bdfdc
• hs-miner-0.0.10.tar.gz: 67ff3517f24194b4e1375c565634d07e263ddcbee1c744e82592b6cb8e31f780
• hs-client-6.0.0.tar.gz: ae4135b26bc2adab9dc1868d57aa3211eb26a77b20ffaa2aee7528cd08d99be3