nathanwoodburn/handypedia
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Compare commits

base: nathanwoodburn:0cafb9adb2d276e54484a36a2c1ec494cd77ed1d
Branches Tags
nathanwoodburn:main
...
compare: nathanwoodburn:4e334d4eb9f9ef4fd260579141d889f51914aec1
Branches Tags
nathanwoodburn:main

3 Commits
0cafb9adb2 ... 4e334d4eb9

Author SHA1 Message Date
Nathan Woodburn
4e334d4eb9 docs: update handshake 2024-02-09 04:09:03 +00:00
Nathan Woodburn
561b7f20af docs: update handshake 2024-02-09 04:08:39 +00:00
Nathan Woodburn
6f244dd341 docs: create hns_tokenomics 2024-02-09 04:07:11 +00:00
2 changed files with 30 additions and 3 deletions
Expand all files Collapse all files

3
handshake.md
View File

@@ -2,7 +2,7 @@
title: Handshake title: Handshake
description: description:
published: 1 published: 1
date: 2024-02-09T03:11:04.797Z date: 2024-02-09T04:08:59.896Z
tags: tags:
editor: markdown editor: markdown
dateCreated: 2024-02-09T03:11:04.797Z dateCreated: 2024-02-09T03:11:04.797Z
@@ -12,4 +12,3 @@ dateCreated: 2024-02-09T03:11:04.797Z
Handshake is a naming protocol that’s backwards compatible with the existing DNS system. It does not replace the DNS protocol, but instead expands the root zone file where TLD ownership information is stored and the root servers with a distributed and decentralized blockchain-based system, which nobody controls and anybody can use. This allows the root zone to be uncensorable, permissionless, and free of gatekeepers like ICANN. Handshake is a naming protocol that’s backwards compatible with the existing DNS system. It does not replace the DNS protocol, but instead expands the root zone file where TLD ownership information is stored and the root servers with a distributed and decentralized blockchain-based system, which nobody controls and anybody can use. This allows the root zone to be uncensorable, permissionless, and free of gatekeepers like ICANN.
Every peer in the Handshake network cryptographically validates and manages the root zone, which also removes the need for the Certificate Authority system (CAs) entirely. Names are logged on the Handshake blockchain, which is essentially one big distributed zone file that anyone has the right to add an entry in. Every peer in the Handshake network cryptographically validates and manages the root zone, which also removes the need for the Certificate Authority system (CAs) entirely. Names are logged on the Handshake blockchain, which is essentially one big distributed zone file that anyone has the right to add an entry in.

28
hns_tokenomics.md Normal file
View File

@@ -0,0 +1,28 @@
---
title: HNS Tokenomics
description:
published: 1
date: 2024-02-09T04:07:06.390Z
tags:
editor: markdown
dateCreated: 2024-02-09T04:07:06.390Z
---
# HNS Tokenomics
## Overview
HNS has a hard-cap of 2,040,000,000 coins. 66% of this was pre-mined and 46.6% of all HNS was aidropped to free and open source developers.
> ![hns_airdrop_graphic.png](/hns_airdrop_graphic.png){.align-center}
[https://medium.com/blockchannel/handshake-distribution-quadrants-f6199ff3cdcd](https://medium.com/blockchannel/handshake-distribution-quadrants-f6199ff3cdcd)
## Burning
At the end of a [TLD auction](/en/auction) all the money paid by the winner do not go to anyone, it is burned (locked away and never usable again).
According to [Shake Stats](https://shakestats.com/) the HNS analytics website, over 1% of the total HNS supply has already been burned in auctions.
Many Handshake community members have embraced the burn meme and incorporated burning HNS into their applications like [shakedex](https://shakedex.readthedocs.io/en/latest/community_burn.html)