You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: multinode/node.go
+8-2Lines changed: 8 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -39,11 +39,13 @@ type ChainConfig interface {
39
39
}
40
40
41
41
// FinalizedStateCheckConfig is an optional interface for enabling finalized state availability checking.
42
+
// It is optional (not part of NodeConfig) so non-EVM multinode consumers are not forced to extend their config types; see aliveLoop in node_lifecycle.go.
42
43
typeFinalizedStateCheckConfiginterface {
43
44
FinalizedStateCheckFailureThreshold() uint32
44
45
}
45
46
46
47
// FinalizedStateChecker is an optional interface for RPCClients that support finalized state checks.
48
+
// It is optional (not part of RPCClient) so non-EVM multinode consumers avoid boilerplate and review churn; see aliveLoop in node_lifecycle.go.
// Finalized state availability check via optional interfaces
106
+
// Finalized-state availability is for EVM-style stacks, but multinode is a shared framework package: mandatory RPCClient/NodeConfig APIs would make every consumer (e.g. Solana)
107
+
// inherit stubs or real implementations trigger unrelated security review. Optional interfaces keep the feature opt-in—only callers that need it implement FinalizedStateCheckConfig and FinalizedStateChecker; everyone else stays untouched.
0 commit comments