From 5c41de2b85206783566188a375408068c25106d2 Mon Sep 17 00:00:00 2001 From: Sergio Mena Date: Fri, 14 Jan 2022 13:50:48 +0100 Subject: [PATCH] Update spec/abci++/abci++_app_requirements_002_draft.md Co-authored-by: Josef Widder <44643235+josef-widder@users.noreply.github.com> --- spec/abci++/abci++_app_requirements_002_draft.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spec/abci++/abci++_app_requirements_002_draft.md b/spec/abci++/abci++_app_requirements_002_draft.md index 8ceabd9a4..c74317e81 100644 --- a/spec/abci++/abci++_app_requirements_002_draft.md +++ b/spec/abci++/abci++_app_requirements_002_draft.md @@ -39,8 +39,8 @@ _AppHash_, _TxResults_, _ConsensusParams_, or _ValidatorUpdates_ (the values pro * Requirement 3 [`PrepareProposal`, timeliness] If $p$'s Application fully executes prepared blocks in `PrepareProposal` and the network is in a synchronous period while processes $p$ and $q$ are in $r_p$, - then the value of _TimeoutPropose_ at $q$ must be such that $q$ does not prevote _nil_ in $r_p$ due to - $q$'s propose timer timing out. + then the value of _TimeoutPropose_ at $q$ must be such that $q$'s propose timer does not time out (which would result in $q$ prevoting _nil_ in $r_p$). + . Full execution of blocks at `PrepareProposal` time stands on Tendermint's critical path. Thus, Requirement 3 ensures the Application will set a value for _TimeoutPropose_ such that the time it takes