waku-org
/
specs
mirror of https://github.com/waku-org/specs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

typos

This commit is contained in:
SionoiS 2024-09-06 11:15:18 -04:00
parent 1069535b9b
commit 10d07670b7
No known key found for this signature in database
GPG Key ID: C9458A8CB1852951
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
standards/core/store-sync.md
View File

@ -1,13 +1,13 @@
---
title: WAKU-STORE-SYNC
name: Waku Store Syncronization
name: Waku Store Synchronization
editor: Simon-Pierre Vivier <simvivier@status.im>
contributors:
---
## Abstract
This document describe the strategy Waku store node will employ to stay synchronized.
This document describe the strategy Waku Store node will employ to stay synchronized.
The goal being that all store nodes eventually archive the same set of messages.
## Background / Rationale / Motivation
@ -27,7 +27,7 @@ Various protocols and features that help with message consistency are described
### Store Resume
This feature allow a node to fill the gap in messages for the period it was offline.
This feature allow a node to fill the gap in messages for the period it was last offline.
At startup, a node use the Store protocol to query a random node for
the time interval since it was last online.
It is RECOMMENDED” to limit the time interval to a maximum of 6 hours.
@ -35,7 +35,7 @@ It is RECOMMENDED” to limit the time interval to a maximum of 6 hours.
### Waku Sync
Nodes that stay online can still miss messages.
Waku Sync is used to find those messages by periodically syncing with random node.
Waku Sync is used to find those messages by periodically syncing with random nodes.
It is RECOMMENDED to trigger a sync every 5 minutes for the time range of the last hour.
After both hash set are reconciled, the Store protocol is used to reciprocally query the other node with the hash differences found.