Skip to Content

Changes for page Networks

Last modified by Zenna Elfen on 2026/01/05 21:51
From version 37.1
edited by Zenna Elfen
on 2026/01/05 19:54
Change comment: There is no comment for this version
To version 14.1
edited by Zenna Elfen
on 2025/11/24 11:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,12 +1,9 @@
1 -(% class="jumbotron" %)
1 +(% class="box" %)
2 2  (((
3 -(% class="container" %)
4 -(((
5 -= Peer-for-Peer Networks =
3 +This page contains an overview of all P4P Networks in this wiki and their building blocks.
6 6  
7 -P4P, short for Peer-4-Peer (which in turn is short for Peer-for-Peer) are a family of networks which build on principles of local-first, peer-2-peer, open-source, routing agnostic (offline-first) and mutual-aid principles. The above is a lot of terms which in and of themselves carry a lot of meaning, yet when combined they enable censorship-resistant, resilient and adaptive, sustainable and energy-efficient communication infrastructures.
5 +You can also [[add a P4P Network>>doc:Projects.WebHome]] or have a look at the [[P4P Applications>>doc:P4P.Applications.WebHome]].
8 8  )))
9 -)))
10 10  
11 11  
12 12  
... ... @@ -17,189 +17,78 @@
17 17  
18 18  
19 19  
17 +== Building Blocks of P4P Networks ==
20 20  
21 21  
22 -(% class="col-xs-12 col-sm-8" %)
20 +(% class="box" %)
23 23  (((
24 -{{box title="==== Contents ====
25 -
26 -====== ======"}}
27 -{{toc depth="5"/}}
28 -{{/box}}
22 +Lost in translation? Take a look at the [[terminology>>doc:P4P.Definitions.WebHome]].
29 29  )))
30 30  
25 +To fully assemble a P4P network one needs a few different building blocks. The following is an overview of the building blocks needed for P4P networks.
31 31  
32 32  
28 +==== **Data Synchronization** ====
33 33  
34 -
35 -
36 -
37 -
38 -
39 -(% class="row" %)
40 -(((
41 -
42 -== Building Blocks of P4P Networks ==
43 -To fully assemble a P4P network one needs a few different building blocks, below is an overview of 15 of those building blocks. Lost in translation? Take a look at the [[terminology>>doc:P4P.Definitions.WebHome]].
44 -)))
45 -
46 -(((
47 -==== ====
48 -
49 -==== **1. Data Synchronization** ====
50 -
51 51  > Synchronization answers **how updates flow between peers** and how they determine what data to exchange. This layer is about **diffing, reconciliation, order, causality tracking, and efficient exchange**, not persistence or user-facing collaboration semantics.
52 52  
53 -* //How do peers detect differences and synchronize state?//
54 -* Examples: Range-Based Set Reconciliation, RIBLT, Gossip-based sync, State-based vs op-based sync, Lamport/Vector/HLC clocks, Braid Protocol
32 +- _How do peers detect differences and synchronize state?_
33 +- Examples: Range-Based Set Reconciliation, RIBLT, Gossip-based sync, State-based vs op-based sync, Lamport/Vector/HLC clocks, Braid Protocol
55 55  
35 +*Relevant links or documentation:*
56 56  
57 57  
58 -==== **2. Collaborative Data Structures & Conflict Resolution** ====
38 +==== **Collaborative Data Structures & Conflict Resolution** ====
59 59  
60 60  > This layer defines **how shared data evolves** when multiple peers edit concurrently. It focuses on **conflict-free merging, causality, and consistency of meaning**, not transport or storage. CRDTs ensure deterministic convergence, while event-sourced or stream-driven models maintain a history of all changes and derive consistent state from it.
61 61  
62 -* //How do peers collaboratively change shared data and merge conflicts?//
63 -* Examples: CRDTs (Yjs, Automerge), OT, Event Sourcing, Stream Processing, Version Vectors, Peritext
42 +- _How do peers collaboratively change shared data and merge conflicts?_
43 +- Examples: CRDTs (Yjs, Automerge), OT, Event Sourcing, Stream Processing, Version Vectors, Peritext
64 64  
45 +*Relevant links or documentation:*
65 65  
66 66  
67 -==== **3. Data Storage & Replication** ====
48 +==== **Data Storage & Replication** ====
68 68  
69 69  > This layer focuses on **durability, consistency, and redundancy**. It handles write-paths, crash-resilience, and replication semantics across nodes. It is the “database/storage engine” layer where **data lives and survives over time**, independent of sync or merging logic.
70 70  
71 -* //How is data persisted locally and replicated between peers?//
72 -* Examples: SQLite, IndexedDB, LMDB, Hypercore (append-only logs), WALs, Merkle-DAGs (IPFS/IPLD), Blob/media storage
52 +- _How is data persisted locally and replicated between peers?_
53 +- Examples: SQLite, IndexedDB, LMDB, Hypercore (append-only logs), WALs, Merkle-DAGs (IPFS/IPLD), Blob/media storage
73 73  
55 +*Relevant links or documentation:*
74 74  
57 +==== **Peer & Content Discovery** ====
75 75  
76 -==== **4. Peer & Content Discovery** ====
77 -
78 78  > Discovery occurs in two phases:
79 79  > 1. **Peer Discovery** → finding _any_ nodes
80 80  > 2. **Topic Discovery** → finding _relevant_ nodes or resources
81 81  > These mechanisms enable decentralized bootstrapping and interest-based overlays.
82 82  
83 -* //How do peers find each other, and how do they discover content in the network?//
84 -* Examples: DHTs (Kademlia, Pastry), mDNS, DNS-SD, Bluetooth scanning, QR bootstrapping, static peer lists, Interest-based routing, PubSub discovery (libp2p), Rendezvous protocols
85 85  
65 +- _How do peers find each other, and how do they discover content in the network?_
66 +- Examples: DHTs (Kademlia, Pastry), mDNS, DNS-SD, Bluetooth scanning, QR bootstrapping, static peer lists, Interest-based routing, PubSub discovery (libp2p), Rendezvous protocols
86 86  
68 +*Relevant links or documentation:*
87 87  
88 -==== **5. Identity & Trust** ====
70 +# **Identity & Trust**
89 89  
90 90  > Identity systems ensure reliable mapping between peers and cryptographic keys. They underpin authorization, federated trust, and secure overlays.
91 91  
92 -* //How peers identify themselves, authenticate, and establish trustworthy relationships?//
93 -* Examples: PKI, Distributed Identities (DIDs), Web-of-Trust, TOFU (SSH-style), Verifiable Credentials (VCs), Peer key fingerprints (libp2p PeerIDs), Key transparency logs
74 +- _How peers identify themselves, authenticate, and establish trustworthy relationships?_
75 +- Examples: PKI, Distributed Identities (DIDs), Web-of-Trust, TOFU (SSH-style), Verifiable Credentials (VCs), Peer key fingerprints (libp2p PeerIDs), Key transparency logs
94 94  
95 95  
96 96  
97 -==== **6. Transport Layer** ====
98 98  
99 -> This layer provides logical connections and flow control. QUIC and WebRTC bring modern congestion control and encryption defaults; Interpeer explores transport beyond IP assumptions.
100 100  
101 -* //How do peers establish end-to-end byte streams and reliable delivery?//
102 -* Examples: TCP, UDP, QUIC, SCTP, WebRTC DataChannels, Interpeer transport stack
103 103  
104 -
105 -
106 -==== **7. Underlying Transport (Physical/Link Layer)** ====
107 -
108 -> Highly relevant for **offline-first / edge networks**, device-to-device communication, and mesh networks and relates to the hardware which facilitates connections.
109 -
110 -* //How does data move across the medium?//
111 -* Examples: Ethernet, Wi-Fi Direct / Wi-Fi Aware (post-AWDL), Bluetooth Mesh, LoRa, NFC, Cellular, CSMA/CA, TDMA, FHSS
112 -
113 -
114 -
115 -==== **8. Session & Connection Management** ====
116 -
117 -> Manages **connection lifecycle**, including authentication handshakes, reconnection after drops, and session continuation—especially important in lossy or mobile networks.
118 -
119 -* //How are connections initiated, authenticated, resumed, and kept alive?//
120 -* Examples: TLS handshake semantics, Noise IK/XX patterns, session tokens, keep-alive heartbeats, reconnection strategies, session resumption tickets
121 -
122 -
123 -
124 -==== **9. Content Addressing** ====
125 -
126 -> Content addressing ensures **immutability, verifiability, and deduplication**. Identity of data = cryptographic hash, enabling offline-first and tamper-evident systems.
127 -
128 -* //How is data addressed and verified by content, not location?//
129 -* Examples: IPFS CIDs, BitTorrent infohashes, Git hashes, SHA-256 addressing, Named Data Networking (NDN)
130 -
131 -
132 -
133 -==== **10. P2P Connectivity** ====
134 -
135 -> Connectivity ensures peers bypass NATs/firewalls to reach each other. 
136 -
137 -* //How can two peers connect directly across networks, firewalls, and NATs?//
138 -* Examples: IPv6 direct, NAT Traversal, STUN, TURN, ICE (used in WebRTC), UDP hole punching, UPnP
139 -
140 -
141 -
142 -==== **11. Session & Connection Management** ====
143 -
144 -> Manages **connection lifecycle**, including authentication handshakes, reconnection after drops, and session continuation.
145 -
146 -* //How are connections initiated, authenticated, resumed, and kept alive?//
147 -* Examples: TLS handshake semantics, Noise IK/XX patterns, session tokens, keep-alive heartbeats, reconnection strategies, session resumption tickets
148 -
149 -
150 -
151 -==== **12. Message Format & Serialization** ====
152 -
153 -> Serialization ensures **portable data representation**, forward-compatible schemas, and efficient messaging. IPLD provides content-addressed structuring for P2P graph data.
154 -
155 -* //How is data encoded, structured, and made interoperable between peers?//
156 -* Examples: CBOR, Protocol Buffers, Cap’n Proto, JSON, ASN.1, IPLD schemas, Flatbuffers
157 -
158 -
159 -
160 -==== **13. File / Blob Synchronization** ====
161 -
162 -> Bulk data syncing has **different trade-offs** than small collaborative state (chunking, deduplication, partial transfer, resume logic). Critical for media and archival P2P use-cases.
163 -
164 -//How are large objects transferred and deduplicated efficiently across peers?//
165 -Examples: BitTorrent chunking, IPFS block-store, NDN segments, rsync-style delta sync, ZFS send-receive, streaming blob transfers
166 -
167 -
168 -==== **14. Local Storage & Processing Primitives** ====
169 -
170 -> Provides durable on-device state and local computation (event sourcing, materialization, compaction). Enables offline-first writes and deterministic replay.
171 -
172 -* //How do nodes persist, index, and process data locally—without external servers?//
173 -* Examples: RocksDB, LevelDB, SQLite, LMDB, local WALs/append-only logs, embedded stream processors (NATS Core JetStream mode, Actyx-like edge runtimes), Kafka-like libraries
174 -
175 -
176 -
177 -==== **15. Crash Resilience & Abortability** ====
178 -
179 -> Ensures P2P apps don’t corrupt state on crashes. Tied to **local storage & stream-processing**, and critical in offline-first and distributed update pipelines. Abortability is the updated term for Atomicity as part of the ACID abbreviation.
180 -
181 -* //How do nodes recover and maintain correctness under failure?//
182 -* Examples: WALs, idempotent ops, partial log replay, transactional journaling, write fences
183 -
184 -
185 -
186 -
187 187  == Distributed Network Types ==
188 188  
189 189  
190 190  [[Flowchart depicting distributed network variants, under development. Building on work from Z. Elfen, 2024: ~[~[https:~~~~/~~~~/doi.org/10.17613/naj7d-6g984~>~>https://doi.org/10.17613/naj7d-6g984~]~]>>image:P4P_Typology.png||alt="Flowchart depicting typologies of distributed networks, such as Friend-2-Friend, Grassroots Networks, Federated Networks, Local-First, P2P and P4P Networks" data-xwiki-image-style-alignment="center" height="649" width="639"]]
191 191  
192 -== ==
193 193  
88 +
194 194  == Overview of P4P Networks ==
195 195  
196 196  {{include reference="Projects.WebHome"/}}
197 -)))
198 -
199 -
200 -
201 -
202 -
203 -
204 -
205 -~)~)~)