Rm topology desc
This commit is contained in:
parent
1ccc0a9704
commit
ae38d247fb
|
@ -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.
|
||||
|
||||
|
|
Loading…
Reference in New Issue