From ae38d247fbac907bc5029fe8962ec9c1ec8b23e0 Mon Sep 17 00:00:00 2001 From: Jay Graber Date: Fri, 12 Jun 2020 15:40:43 -0700 Subject: [PATCH] Rm topology desc --- protocols/IPFS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/protocols/IPFS.md b/protocols/IPFS.md index 43d38f9..4fb3958 100644 --- a/protocols/IPFS.md +++ b/protocols/IPFS.md @@ -12,7 +12,7 @@ IPFS can serve as a content addressed storage system for decentralized identity ### Network Architecture & Connectivity -IPFS is a distributed protocol. Every node gets to participate in the network in any configuration, enabling different kinds of network topologies to emerge (Distributed, Decentralized, Federated, Centralized, Full Mesh, etc.). Nodes can connect to each other independently of the client (browser, mobile, desktop, command line). +IPFS is a distributed protocol. Every node gets to participate in the network in any configuration, enabling different kinds of network topologies to emerge. Nodes can connect to each other independently of the client (browser, mobile, desktop, command line). When nodes join the network, they bootstrap off of long-lived peers or those in their local area network. IPFS comes with a [default list of trusted peers](https://docs.ipfs.io/how-to/modify-bootstrap-list/), which can be modified. A node can opt-in to be part of the main public network and/or an alternative network. Nodes joining the main public network will join the [DHT](https://docs.ipfs.io/concepts/dht/) as either clients (consumers) or servers (providers of the content routing service). Nodes can also directly connect to peers they’re interested in either through peer ID or through subscribing to relevant pubsub channels.