From d39d8e18344dcc95d7b01c9a394d15fe60dbe6c4 Mon Sep 17 00:00:00 2001 From: William Banfield Date: Wed, 11 Aug 2021 11:52:17 -0400 Subject: [PATCH] update alternatives section --- docs/architecture/adr-071-proposer-based-timestamps.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/architecture/adr-071-proposer-based-timestamps.md b/docs/architecture/adr-071-proposer-based-timestamps.md index 0911bfec6..ba46719c3 100644 --- a/docs/architecture/adr-071-proposer-based-timestamps.md +++ b/docs/architecture/adr-071-proposer-based-timestamps.md @@ -48,7 +48,8 @@ Using timestamps in our protocol means either accepting the timestamps as not re This design requires impacting the protocol’s liveness in order to make the timestamps more reliable. An alternate approach is to remove timestamps altogether from the block protocol. `BFTTime` is deterministic but may be arbitrarily inaccurate. -This approach was not selected because a reliable source of time is quite useful for blockchain applications. +However, having a reliable source of time is quite useful for blockchain applications. +We therefore decided not to remove the timestamp. Time is much more meaningful to humans than block height. Applications may wish for some transactions to occur on a certain day, on a regular period, or after some time following a different event. All of these require some meaningful representation of agreed upon time.