fryorcraken
b1da70386e
fix: use milliseconds for Lamport timestamp initialization ( #179 )
...
Changed Lamport timestamp initialization from nanoseconds to
milliseconds. The current time in nanoseconds exceeds JavaScript's
Number.MAX_SAFE_INTEGER, making nanosecond precision unsuitable for
JavaScript implementations. Milliseconds provide sufficient precision
while remaining well within safe integer bounds for decades to come.
2025-09-15 20:23:58 +10:00
Jimmy Debe
3505da6bd6
sds lint fix ( #177 )
...
Fix lint issue in sds.md
2025-08-22 14:53:34 +02:00
Hanno Cornelius
536d31b5b7
docs: re-add sender ID to messages ( #170 )
...
Re-added the concept of a participant ID and the corresponding
`sender_id` field in each SDS message.
This is useful to filter "self-triggered" messages as described in
https://github.com/waku-org/js-waku/pull/2528
However, this will also be a necessary part of the protocol once p2p
message exchange is added.
---------
Co-authored-by: fryorcraken <110212804+fryorcraken@users.noreply.github.com >
Co-authored-by: shash256 <111925100+shash256@users.noreply.github.com >
2025-08-19 16:38:42 +01:00
Arseniy Klempner
8ee2a6d6b2
docs: add optional retrieval hint to causal history in sds ( #130 )
2025-03-07 18:32:46 -08:00
Hanno Cornelius
235c1d5aa6
docs: clarify receiving sync messages ( #131 )
...
Minor adds to "Receive message" procedure to reflect changes introduced
in https://github.com/vacp2p/rfc-index/pull/129
2025-02-20 11:03:49 +00:00
Arseniy Klempner
718245979f
docs: update sds sync message requirements ( #129 )
2025-02-18 21:10:31 -08:00
Arseniy Klempner
7a01711ffc
fix(sds): remove optional from causal history field in Message protobuf ( #123 )
2025-01-28 12:02:54 +02:00
Jimmy Debe
08b363d67e
Update SDS.md: Remove Errors ( #115 )
...
Remove markdown error from the SDS rfc.
2024-12-18 03:16:50 +01:00
Hanno Cornelius
bee78c40b9
docs: add SDS protocol for scalable e2e reliability ( #108 )
...
Introduces the "Scalable Data Sync" protocol, based on the e2e
reliability mechanisms discussed in the [Vac forum
post](https://forum.vac.dev/t/end-to-end-reliability-for-scalable-distributed-logs/293/10 ).
The initial aim is to provide an end-to-end reliability protocol for
Status chat protocols, specifically within the context of Status
Communities.
---------
Co-authored-by: fryorcraken <110212804+fryorcraken@users.noreply.github.com >
Co-authored-by: Jimmy Debe <91767824+jimstir@users.noreply.github.com >
2024-11-28 16:22:36 +00:00
