About Handshake Airdrop
Handshake Airdrop is a decentralized, permissionless naming protocol where every peer is validating and in charge of managing the root DNS naming zone with the goal of creating an alternative to existing Certificate Authorities and naming systems. Names on the internet (top level domains, social networking handles, etc.)
Ultimately rely upon centralized actors with full control over a system which are relied upon to be honest, as they are vulnerable to hacking, censorship, and corruption. Handshake aims to experiment with new ways the internet can be more secure, resilient, and socially useful with a peer-to-peer system validated by the network’s participants.
Handshake is 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
Handshake Airdrop.Centralization exists because there is a need to manage spam, griefing, and sockpuppet/sybil attacks. 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.
| Platform | Token Per Claim | KYC | Website |
|---|---|---|---|
| Own chain | Free HNS To Top 100k Domain Owners+ 4,246 HNS | KYC for users is NOT a requirement | Click Here To Visit |
The Handshake Protocol
By running Handshake, one can participate in a decentralized open naming platform secured by a decentralized peer-to-peer network.
A base layer for the decentralized internet.
The internet is arranged in layers, to decentralize the internet, we 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 we 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. Handshake is an experimental structure for reaching that agreement via software.
True decentralization, no official singular Foundation, Committee, Corporation, or entities in permanent unitary control of the protocol.
Economic incentives
Economic incentives enable decentralized agreements to form via a transparent name auction process. Without some kind of economic cost function, one person could register all names. Economic incentives enable decentralized sybil resistance which would otherwise be centralized and corrupted.
Alternative to certificate authorities,
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.
Light clients
Light clients via merkelized proofs and proof-of-work allow for lightweight name resolutions and certificates. The initial protocol enables cryptographic name proofs, with the potential for decentralized proof lookups to be usually within the MTU limit.
A platform for sybil resilience.
WoT can/should be used as an augmentation, but it is often not a global agreement of resources for individual decentralized services. By using Handshake names, one can know that some kind of economic limits exist for the use of the name. This can be leveraged whenever one is concerned about resource exhaustion, and reaching global agreement on moderation alone is too costly.