MakeChannelHash is used for mapping ChannelDefinitionWithIDs.

TODO: Needs thorough unit testing of all paths including nil handling MERC-3524.

Protocol instances start in either the staging or production stage.

Protocol instances start in either the staging or production stage.

Protocol instances start in either the staging or production stage.

Additional limits so we can more effectively bound the size of observations NOTE: These are hardcoded because these exact values are relied upon as a property of coming to consensus, it's too dangerous to make these configurable on a per-node basis.

LLO-specific limits Maximum amount of channels that can be added per round (if more than this needs to be added, it will be added in batches until everything is up-to-date).

Maximum number of streams that can be observed per round.

Maximum amount of channels that can be removed per round (if more than this needs to be removed, it will be removed in batches until everything is up-to-date).

MaxOutcomeChannelDefinitionsLength is the maximum number of channels that can be supported.

Additional limits so we can more effectively bound the size of observations NOTE: These are hardcoded because these exact values are relied upon as a property of coming to consensus, it's too dangerous to make these configurable on a per-node basis.

OCR protocol limits NOTE: CAREFUL! If we ever accidentally exceed these e.g.

Additional limits so we can more effectively bound the size of observations NOTE: These are hardcoded because these exact values are relied upon as a property of coming to consensus, it's too dangerous to make these configurable on a per-node basis.

Enum value maps for LLOStreamValue_Type.

Enum value maps for LLOStreamValue_Type.

EVMOnchainConfigCodec provides a llo-specific implementation of OnchainConfigCodec.

WARNING Use extreme caution making changes in this file All changes MUST be backwards compatible If the format changes in a backwards incompatible way, active DONs can become stuck permanently.

NOTE: Outcome must serialize deterministically, hence use of repeated tuple instead of maps.

The predecessor protocol instance stores its attested retirement report in this cache (locally, offchain), so it can be fetched by the successor protocol instance.

Values for a set of streams, e.g.