Editor changes for 13, 2, 4
This commit is contained in:
parent
53dc1e6372
commit
8b84fe868e
|
@ -3,10 +3,10 @@ slug: 13
|
||||||
title: 13/WAKU2-STORE
|
title: 13/WAKU2-STORE
|
||||||
name: Waku v2 Store
|
name: Waku v2 Store
|
||||||
status: draft
|
status: draft
|
||||||
editor: Oskar Thorén <oskar@status.im>
|
editor: Sanaz Taheri <sanaz@status.im>
|
||||||
contributors:
|
contributors:
|
||||||
- Dean Eigenmann <dean@status.im>
|
- Dean Eigenmann <dean@status.im>
|
||||||
- Sanaz Taheri <sanaz@status.im>
|
- Oskar Thorén <oskar@status.im>
|
||||||
---
|
---
|
||||||
|
|
||||||
This specification explains the Waku `WakuStore` protocol which enables querying of messages received through relay protocol and stored by other nodes. It also supports pagination for more efficient querying of historical messages.
|
This specification explains the Waku `WakuStore` protocol which enables querying of messages received through relay protocol and stored by other nodes. It also supports pagination for more efficient querying of historical messages.
|
||||||
|
|
|
@ -3,9 +3,10 @@ slug: 2
|
||||||
title: 2/MVDS
|
title: 2/MVDS
|
||||||
name: Minimum Viable Data Synchronization
|
name: Minimum Viable Data Synchronization
|
||||||
status: stable
|
status: stable
|
||||||
editor: Oskar Thorén <oskar@status.im>
|
editor: Sanaz Taheri <sanaz@status.im>
|
||||||
contributors:
|
contributors:
|
||||||
- Dean Eigenmann <dean@status.im>
|
- Dean Eigenmann <dean@status.im>
|
||||||
|
- Oskar Thorén <oskar@status.im>
|
||||||
---
|
---
|
||||||
|
|
||||||
In this specification, we describe a minimum viable protocol for data synchronization inspired by the Bramble Synchronization Protocol[^1]. This protocol is designed to ensure reliable messaging between peers across an unreliable peer-to-peer (P2P) network where they may be unreachable or unresponsive.
|
In this specification, we describe a minimum viable protocol for data synchronization inspired by the Bramble Synchronization Protocol[^1]. This protocol is designed to ensure reliable messaging between peers across an unreliable peer-to-peer (P2P) network where they may be unreachable or unresponsive.
|
||||||
|
|
|
@ -3,10 +3,11 @@ slug: 4
|
||||||
title: 4/MVDS-META
|
title: 4/MVDS-META
|
||||||
name: MVDS Metadata Field
|
name: MVDS Metadata Field
|
||||||
status: draft
|
status: draft
|
||||||
editor: Oskar Thorén <oskar@status.im>
|
editor: Sanaz Taheri <sanaz@status.im>
|
||||||
contributors:
|
contributors:
|
||||||
- Dean Eigenmann <dean@status.im>
|
- Dean Eigenmann <dean@status.im>
|
||||||
- Andrea Maria Piana <andreap@status.im>
|
- Andrea Maria Piana <andreap@status.im>
|
||||||
|
- Oskar Thorén <oskar@status.im>
|
||||||
---
|
---
|
||||||
|
|
||||||
In this specification, we describe a method to construct message history that will aid the consistency guarantees of [2/MVDS](/spec/2). Additionally, we explain how data sync can be used for more lightweight messages that do not require full synchronization.
|
In this specification, we describe a method to construct message history that will aid the consistency guarantees of [2/MVDS](/spec/2). Additionally, we explain how data sync can be used for more lightweight messages that do not require full synchronization.
|
||||||
|
|
Loading…
Reference in New Issue