Skip to Content

Changes for page Networks

Last modified by Zenna Elfen on 2025/11/24 12:07
From version 13.1
edited by Zenna Elfen
on 2025/11/24 11:47
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
... ... @@ -12,6 +12,8 @@
12 12  
13 13  
14 14  
15 +
16 +
15 15  == Building Blocks of P4P Networks ==
16 16  
17 17  
... ... @@ -23,7 +23,7 @@
23 23  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.
24 24  
25 25  
26 -##### 9. **Data Synchronization**
28 +==== **Data Synchronization** ====
27 27  
28 28  > 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.
29 29  
... ... @@ -33,7 +33,7 @@
33 33  *Relevant links or documentation:*
34 34  
35 35  
36 -##### 10. **Collaborative Data Structures & Conflict Resolution**
38 +==== **Collaborative Data Structures & Conflict Resolution** ====
37 37  
38 38  > 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.
39 39  
... ... @@ -43,7 +43,7 @@
43 43  *Relevant links or documentation:*
44 44  
45 45  
46 -##### 11. **Data Storage & Replication**
48 +==== **Data Storage & Replication** ====
47 47  
48 48  > 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.
49 49  
... ... @@ -52,7 +52,7 @@
52 52  
53 53  *Relevant links or documentation:*
54 54  
55 -##### 12. **Peer & Content Discovery**
57 +==== **Peer & Content Discovery** ====
56 56  
57 57  > Discovery occurs in two phases:
58 58  > 1. **Peer Discovery** → finding _any_ nodes
... ... @@ -65,7 +65,7 @@
65 65  
66 66  *Relevant links or documentation:*
67 67  
68 -##### 13. **Identity & Trust**
70 +# **Identity & Trust**
69 69  
70 70  > Identity systems ensure reliable mapping between peers and cryptographic keys. They underpin authorization, federated trust, and secure overlays.
71 71