From f738fe6e86bd7b312d1ecfa88a13d114f70607dc Mon Sep 17 00:00:00 2001 From: William Banfield <4561443+williambanfield@users.noreply.github.com> Date: Thu, 3 Feb 2022 09:47:02 -0500 Subject: [PATCH] Update docs/architecture/adr-071-proposer-based-timestamps.md Co-authored-by: M. J. Fromberger --- docs/architecture/adr-071-proposer-based-timestamps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/architecture/adr-071-proposer-based-timestamps.md b/docs/architecture/adr-071-proposer-based-timestamps.md index d13697b32..1443eab85 100644 --- a/docs/architecture/adr-071-proposer-based-timestamps.md +++ b/docs/architecture/adr-071-proposer-based-timestamps.md @@ -133,7 +133,7 @@ These parameters are `PRECISION`, and `MSGDELAY`. The `PRECISION` and `MSGDELAY` parameters are used to determine if the proposed timestamp is acceptable. A validator will only Prevote a proposal if the proposal timestamp is considered `timely`. A proposal timestamp is considered `timely` if it is within `PRECISION` and `MSGDELAY` of the Unix time known to the validator. -More specifically, a proposal timestamp is `timely` if `proposalTimestamp - PRECISION <= validatorLocalTime <= proposalTimestamp + PRECISION + MSGDELAY`. +More specifically, a proposal timestamp is `timely` if `proposalTimestamp - PRECISION ≤ validatorLocalTime ≤ proposalTimestamp + PRECISION + MSGDELAY`. Because the `PRECISION` and `MSGDELAY` parameters must be the same across all validators, they will be added to the [consensus parameters](https://github.com/tendermint/tendermint/blob/master/proto/tendermint/types/params.proto#L13) as [durations](https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#google.protobuf.Duration).