From f404b2709351ee29ca287cd9fa3c502ae26a0d4c Mon Sep 17 00:00:00 2001 From: Daniel Cason Date: Wed, 9 Mar 2022 09:30:30 +0100 Subject: [PATCH] PBTS model: reinforcing alignment with UTC --- .../proposer-based-timestamp/pbts-sysmodel_002_draft.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/spec/consensus/proposer-based-timestamp/pbts-sysmodel_002_draft.md b/spec/consensus/proposer-based-timestamp/pbts-sysmodel_002_draft.md index 097089251..c98d47f73 100644 --- a/spec/consensus/proposer-based-timestamp/pbts-sysmodel_002_draft.md +++ b/spec/consensus/proposer-based-timestamp/pbts-sysmodel_002_draft.md @@ -4,13 +4,15 @@ #### **[PBTS-CLOCK-NEWTON.0]** -There is a reference Newtonian real-time `t` (UTC). +There is a reference Newtonian real-time `t`. No process has direct access to this reference time, used only for specification purposes. +The reference real-time is assumed to be aligned with the Coordinated Universal Time (UTC). ### Synchronized clocks -Processes are assumed to be equipped with synchronized clocks. +Processes are assumed to be equipped with synchronized clocks, +aligned with the Coordinated Universal Time (UTC). This requires processes to periodically synchronize their local clocks with an external and trusted source of the time (e.g. NTP servers). @@ -58,7 +60,7 @@ This allows us to adopt a relaxed version of the above `ACCURACY` definition: - At real time `t` there is at least one correct process `p` which clock marks `C_p(t)` with `|C_p(t) - t| <= ACCURACY` -Then, through [PBTS-CLOCK-PRECISION] we can extend this relation of clock times +Then, through [PBTS-CLOCK-PRECISION.0] we can extend this relation of clock times with real time to every correct process, which will have a clock with accuracy bound by `ACCURACY + PRECISION`. But, for the sake of simpler specification we can assume that the `PRECISION`,