From 534c1faf31fa58a438775825b3954c3c038008fd Mon Sep 17 00:00:00 2001 From: Jay Graber Date: Tue, 9 Jun 2020 21:58:27 -0700 Subject: [PATCH] edit --- protocols/gun.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/protocols/gun.md b/protocols/gun.md index a34be92..94d0a02 100644 --- a/protocols/gun.md +++ b/protocols/gun.md @@ -2,7 +2,7 @@ Gun is a distributed database with a graph structure. Related libraries include a constellation of tools for merging conflicting data and handling routing and security. -In GunDB's graph store, entries are [JSON objects under UUID keys](https://gun.eco/docs/Porting-GUN). Data is stored in browser localStorage by default, with backup "supernode" servers to ensure persistence. Peers connect over websockets to other peers, and choose what data to synchronize and persist. +In GunDB's graph store, entries are [JSON objects under UUID keys](https://gun.eco/docs/Porting-GUN). Data is stored in browser localStorage by default, with backup "supernode" servers to ensure persistence. Peers connect to other peers, and choose what data to synchronize and persist. ### Identity @@ -10,7 +10,7 @@ Gun's SEA module provides the capability to create a [public/private keypair](ht ### Network structure -Gun uses websockets to transfer data between peers. When a client puts something in a graph, a message is sent to the network and other clients that have subscribed to that data pick it up and update their state. Those who are offline will eventually receive those updates. +Gun transfers data between peers. When a client puts something in a graph, a message is sent to the network and other clients that have subscribed to that data pick it up and update their state. Those who are offline will eventually receive those updates. Gun uses a flooding algorithm for message propagation, called [DAM](https://gun.eco/docs/DAM) (Daisy-chain ad-hoc mesh-network). DAM's API allows for the swapping out of transport layers (websockets, WebRTC, etc). A proposed future [routing](https://gun.eco/docs/Routing) protocol, the [AXE protocol](https://web.stanford.edu/~nadal/A-Decentralized-Data-Synchronization-Protocol.pdf), includes a mechanism for monetization through bandwidth-based payments.