docs(consensus): clarify validation sidecar signing rule

Remove the stale TMValidation exportSignatures field from the draft proto path now that export signatures ride signed proposal sidecars. Document that any future validation-carried ConsensusExtensions data must be covered by the signed validation payload and duplicate/replay identity, not an unsigned wrapper field.
This commit is contained in:
Nicholas Dudfield
2026-04-27 15:45:27 +07:00
parent a61f334ca2
commit f13233b00a
2 changed files with 14 additions and 11 deletions

View File

@@ -225,11 +225,6 @@ message TMValidation
// Number of hops traveled
optional uint32 hops = 3 [deprecated = true];
// Legacy export signature gossip field retained for wire compatibility.
// Current proposal-based export signatures use
// TMProposeSet.exportSignatures.
repeated bytes exportSignatures = 4;
}
// An array of Endpoint messages