From e0b7a2c01021fd174619e8bf879c788c73eb197b Mon Sep 17 00:00:00 2001 From: William Banfield Date: Wed, 11 Aug 2021 17:32:02 -0400 Subject: [PATCH] may -> will --- 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 7bbcb143b..e72e0095c 100644 --- a/docs/architecture/adr-071-proposer-based-timestamps.md +++ b/docs/architecture/adr-071-proposer-based-timestamps.md @@ -264,7 +264,7 @@ Block timestamps must be monotonically increasing. In `BFTTime`, if a validator’s clock was behind, the [validator added 1 millisecond to the previous block’s time and used that in its vote messages](https://github.com/tendermint/tendermint/blob/e8013281281985e3ada7819f42502b09623d24a0/internal/consensus/state.go#L2246). A goal of adding proposer-based timestamps is to enforce some degree of clock synchronization, so having a mechanism that completely ignores the validator’s local time no longer works. -Validator clocks may not be perfectly in sync. +Validator clocks will not be perfectly in sync. Therefore, the proposer’s local time may be less than the `LastCommit.Timestamp`. If the proposer’s local time is less than the `LastCommit.Timestamp`, the proposer will sleep until its local time exceeds it.