From 64974242d2d0a3b349eba06992ee2ea740a4e614 Mon Sep 17 00:00:00 2001 From: Nicholas Dudfield Date: Fri, 18 Sep 2026 12:43:23 +0700 Subject: [PATCH] docs(consensus): distinguish rechecked alignment from terminal expiry --- src/xrpld/app/consensus/ConsensusExtensionsDesign.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/xrpld/app/consensus/ConsensusExtensionsDesign.md b/src/xrpld/app/consensus/ConsensusExtensionsDesign.md index 54be3b8fc8..e4bd5cc881 100644 --- a/src/xrpld/app/consensus/ConsensusExtensionsDesign.md +++ b/src/xrpld/app/consensus/ConsensusExtensionsDesign.md @@ -660,9 +660,10 @@ gate performs no alignment work and does not hold up the other. With both disabled, extensions add no acceptance delay. Each gate starts and measures its own bounded observation window independently. -Export can therefore align or expire while RNG is still progressing. Readiness -is re-evaluated against current peer positions and the ordinary transaction -set, not latched across changes in those inputs. An export-side convergence +Export can therefore align or expire while RNG is still progressing. Successful +alignment is rechecked against current peer positions and the ordinary +transaction set while the other gate is waiting; an expired Export decision +remains terminal for the round. An export-side convergence failure must not change RNG semantics; an RNG fallback must not make export unsafe.