[State: done] → consento-org/hlc
TLDR; The local time of devices is not 100% in sync. Using timeservers requires a working internet connection and becomes a point of centralization. Vector clocks dont store a human readable time. The hybrid logical clock allows to have sorted, human readable time stamps for that are practically in-sync.
We need to have timestamps for any operation done with consento. These timestamps are relevant for log auditing and to make sure that operations done on two devices get processed in the correct order on sync.
The timestamps on devices can be changed and out-of-sync and as such are not reliable. Which is why we had to explore other solutions for this.
Trusted timestamps, as described in RFC3161, work well to make sure that entries are signed at a certain timestamp; but those take time to compute, require a persistent internet connection, and an outside service and what is more: an authority trusted by all parties involved to sign those entries.
A hybrid logical clock (hlc) is a clock based on the devices clock. If no sync happens it will always just use the local device time.
What makes it different from the device clock is that it will change the internal behavior if it encounters a timestamp created by another device that is in the future.
In this case, the hlc will use the latest received timestamp and start a logical counter that increments every time a new timestamp is requested.
To make sure that there is the lowest possible chance of equal timestamps, we have created bigint-time which will return the current time in nanoseconds.
And we published @consento/hlc that basically functions as the example below and can be reused for any sort of timestamp-syncing mechanism.
(Note: the configuration is rather complex, please refer to the documenation!)