Skip to Content

Changes for page Networks

Last modified by Zenna Elfen on 2025/11/24 12:07
From version 14.1
edited by Zenna Elfen
on 2025/11/24 11:48
Change comment: There is no comment for this version
To version 13.1
edited by Zenna Elfen
on 2025/11/24 11:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -12,8 +12,6 @@
12 12  
13 13  
14 14  
15 -
16 -
17 17  == Building Blocks of P4P Networks ==
18 18  
19 19  
... ... @@ -25,7 +25,7 @@
25 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.
26 26  
27 27  
28 -==== **Data Synchronization** ====
26 +##### 9. **Data Synchronization**
29 29  
30 30  > 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.
31 31  
... ... @@ -35,7 +35,7 @@
35 35  *Relevant links or documentation:*
36 36  
37 37  
38 -==== **Collaborative Data Structures & Conflict Resolution** ====
36 +##### 10. **Collaborative Data Structures & Conflict Resolution**
39 39  
40 40  > 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.
41 41  
... ... @@ -45,7 +45,7 @@
45 45  *Relevant links or documentation:*
46 46  
47 47  
48 -==== **Data Storage & Replication** ====
46 +##### 11. **Data Storage & Replication**
49 49  
50 50  > 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.
51 51  
... ... @@ -54,7 +54,7 @@
54 54  
55 55  *Relevant links or documentation:*
56 56  
57 -==== **Peer & Content Discovery** ====
55 +##### 12. **Peer & Content Discovery**
58 58  
59 59  > Discovery occurs in two phases:
60 60  > 1. **Peer Discovery** → finding _any_ nodes
... ... @@ -67,7 +67,7 @@
67 67  
68 68  *Relevant links or documentation:*
69 69  
70 -# **Identity & Trust**
68 +##### 13. **Identity & Trust**
71 71  
72 72  > Identity systems ensure reliable mapping between peers and cryptographic keys. They underpin authorization, federated trust, and secure overlays.
73 73