From 561b7f20afdbefc54d1576a037de5cb9570471b7 Mon Sep 17 00:00:00 2001 From: Nathan Woodburn Date: Fri, 9 Feb 2024 04:08:39 +0000 Subject: [PATCH] docs: update handshake --- handshake.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/handshake.md b/handshake.md index c1f86c6..ce69c1a 100644 --- a/handshake.md +++ b/handshake.md @@ -2,7 +2,7 @@ title: Handshake description: published: 1 -date: 2024-02-09T03:11:04.797Z +date: 2024-02-09T04:08:35.406Z tags: editor: markdown dateCreated: 2024-02-09T03:11:04.797Z @@ -11,5 +11,4 @@ dateCreated: 2024-02-09T03:11:04.797Z # Handshake 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. \ No newline at end of file