What Is Handshake.org?
Handshake.org is a decentralized permission less system that is intended to incentivize a distributed network of computers to operate a system for domain name ownership. Under , every peer is tasked with validating and managing the root DNS naming zone, with the objective of providing an alternative to current certificate authorities and naming systems. Different participants across the internet such as social networking handles and domains rely on a centralized approach. This means the systems depend on a system of honesty — and are still prone to cyber attacks and fraud.
They aims to eradicate this problem by creating a decentralized internet that relies on a peer-to-peer system. The an experiment which seeks to explore those new ways in which the necessary tools to build a more decentralized internet. Services on the internet have become more centralized beginning in the 1990s, but do not fulfill the original decentralized vision of the internet. Email became Gmail, usenet became reddit, blog replies became facebook and Medium, pingbacks became twitter, squid became Cloudflare, even gnutella became The Pirate Bay. Centralization exists because there is a need to manage spam, griefing, and sockpuppet/sybil attacks.
Handshake Coin previous decentralized systems largely stopped working due to spam. If it were more costly to grief on the internet using decentralized systems, the need for trusted centralized corporations to manage these risks decrease. Internet services and platforms may benefit from building on top of a decentralized system which is specifically designed for resilience against sybil attacks. As they may redecentralize.
Handshake.org Storage Key Points
|Circulating Supply||385,319,721.49 HNS|
|Source Code||Click Here To View Source Code|
|Explorers||Click Here To View Explorers|
|Twitter Page||Click Here To Visit Twitter Group|
|Whitepaper||Click Here To View|
|Official Project Website||Click Here To Visit Project Website|
How to Claim a Name
Handshake.org If you own a name in the existing root zone, or the Alexa top 100k, or you reserved your name through a trademark claim, it is waiting for you on the blockchain. You are able to claim it by publishing a DNSSEC ownership proof – a cryptographic proof that you own the name on ICANN’s system. Your name must have a valid DNSSEC setup in order for the claim to be created. If you do not have DNSSEC set up, don’t worry – you can set it up after the blockchain launches and proofs will still be accepted retroactively. Here’s some useful guides for setting DNSSEC up on popular DNS services:
Events and Sockets
To listen for and react to events in hsd, a listener must be added in the runtime script. If you are running a full node (for example) you might already be familiar with the hsd full node launch script, which instantiates a object, adds a wallet, and begins the connection and synchronization process. The script ends with an function that actually starts these processes, and this is a good place to add event listeners. Using the table below you can discover which object needs to be listened for each event type.
Setting up a Handshake Wallet
Handshake Coin this guide is heavily copied from Wallets and Accounts and Keys, Oh My! by Daniel McNally with edits specific to . If you’re a seasoned bitcoiner, you can probably skim this section or skip straight ahead to the Examples section. Or if you already have a wallet and are looking to buy and manage names on check out the Name Auctions Guide. But if you’re relatively new or just want a refresher, this section will help you understand how wallets actually work.
The Handshake Protocol
A base layer for the decentralized internet. The internet is arranged in layers, to decentralize the internet, they need to start at the lowest layers of the stack. Secure naming ensures user agents are talking to the right endpoints. The place for minimal global consensus. Decentralization is most successful if they have minimal areas to reach complete global agreement. Names and signing certificates may be one of the few (if only) places of global agreement for a decentralized web. They experimental structure for reaching that agreement via software. Alternative to certificate authorities, using a decentralized trust anchor to prove domain ownership Distributed and permissionless zone file to which any participant has the right to add an entry or serve as host and validator
Internet Name Transfer Using Coin To Prevent Sybil Attacks
Handshake.org is a piece of software (and a loose consensus on agreement of the software itself). This software’s primary function is for people to come to agreement on names and cryptographic keys authorized to represent that names in a decentralized way. To do this in a decentralized way, they need to prevent a single party from claiming all the names. Therefore, a unit of account is needed to prevent that single party from claiming all names. Handshake uses