logos-messaging/specs
1
0
Fork 0
mirror of https://github.com/logos-messaging/specs.git synced 2026-01-03 06:33:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

new impl. section

Browse Source
This commit is contained in:
SionoiS 2024-09-03 11:52:48 -04:00
parent 7d7cbc0338
commit bf5564851f
No known key found for this signature in database
GPG Key ID: C9458A8CB1852951
1 changed files with 24 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
standards/core/sync.md
View File

@ -91,6 +91,30 @@ Further refinements to the protocol are planned
to reduce the trust level required to operate.
Notably by verifing messages RLN proof at reception.
# Implementation
The following is not part of the specifications but good to know implementation details.
### Interval
Ad-hoc syncing can be useful in some cases but continueous periodic sync
minimise the differences in messages stored across the network.
Syncing early and often is the best strategy.
The default used in nwaku is 5 minutes interval between sync with a range of 1 hour.
### Range
We also offset the sync range by 20 seconds in the past.
The actual start of the sync range is T-01:00:20 and the end T-00:00:20
This is to handle the inherent jitter of GossipSub.
In other words, it is the amount of time needed to confirm if a message is missing or not.
### Storage
The storage implementation should reflect the Waku context.
Most messages that will be added will be recent and
all removed messages will be older ones.
When differences are found some messages will have to be inserted randomly.
It is expected to be a less likely case than time based insertion and removal.
Last but not least it must be optimized for sequential read
as it is the most often used operation.
# Copyright
Copyright and related rights waived via