From b1da70386edb15303fb8aa587b8a5da784a2d644 Mon Sep 17 00:00:00 2001
From: fryorcraken <110212804+fryorcraken@users.noreply.github.com>
Date: Mon, 15 Sep 2025 20:23:58 +1000
Subject: [PATCH] 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.
---
 vac/raw/sds.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/vac/raw/sds.md b/vac/raw/sds.md
index 15f0f8d..0082a2d 100644
--- a/vac/raw/sds.md
+++ b/vac/raw/sds.md
@@ -111,7 +111,7 @@ Its importance is expected to increase once a p2p retrieval mechanism is added t
 Each participant MUST maintain:
 
 * A Lamport timestamp for each channel of communication,
-initialized to current epoch time in nanosecond resolution.
+initialized to current epoch time in millisecond resolution.
 * A bloom filter for received message IDs per channel.
 The bloom filter SHOULD be rolled over and
 recomputed once it reaches a predefined capacity of message IDs.