docs(consensus): explain why seq=3 may mirror seq=2

Clarify inline that seq=3 publish can carry unchanged txSetHash while still providing extra entropySetHash delivery/fetch opportunity under packet loss or reordering.
This commit is contained in:
Nicholas Dudfield
2026-03-03 17:41:55 +07:00
parent 8fcb2ed336
commit c2209b4472

View File

@@ -1731,6 +1731,12 @@ Consensus<Adaptor>::phaseEstablish(
// Publish entropySetHash before accepting so lagging peers
// can fetch/merge reveal sets in ConvergingReveal.
//
// This can look redundant in healthy rounds because txSetHash may
// be unchanged versus the prior proposal (for example, seq=2 and
// seq=3 showing the same tx summary in monitors). We still publish
// to create an additional delivery window for entropySetHash and
// to trigger fetch/merge on peers that missed earlier packets.
if (mode_.get() == ConsensusMode::proposing)
adaptor_.propose(result_->position);