A PerasEpochContext that is valid only in a given range of round numbers

Check whether a given PerasRoundNo is within the bounds of a BoundedPerasEpochContext.

Returns the corresponding PerasEpochContext if the round number is within the bounds, or Nothing otherwise.

A two-epoch window of Peras epoch contexts, which can be used to resolve round numbers into their corresponding Peras contexts.

An error indicating that a PerasEpochContext could not be found for a given PerasRoundNo in a PerasEpochContextResolver.

Resolve a PerasRoundNo into its corresponding PerasEpochContext using a PerasEpochContextResolver.

Fails with PerasEpochContextNotFoundForRound if the round number is not within the bounds of either the current or previous epoch context, or if the resolver is in an error state.

Compute the bounds of the Peras round numbers that are covered by the given PerasEpochContextResolver.

NOTE: the upper bound is exclusive, thus we return an empty range [0,0) when the resolver doesn't cover any Peras round.

A handle to a PerasEpochContextResolver that can be used in STM to resolve round numbers into their corresponding PerasEpochContexts.

A mocked PerasEpochContextResolverHandle that always succeeds by resolving every round number to a fixed given (fixed) PerasEpochContext.

Helper to resolve the epoch context for a given round a pass it to a continuation for further processing.

NOTE: this function will throw an STM exception if round number cannot be resolved, or if the continuation fails.

Type-class for blocks that support constructing a Peras epoch contexts from their corresponding ledger and chain-dep states.

Helper to build a BoundedPerasEpochContext using a function that produces a PerasVotingCommitteeInput from a ledger and chain-dep state.

NOTE: this is useful to define instances for StateSupportsPerasEpochContext where mkBoundedPerasEpochContext is instantiated to either: * mkBoundedPerasEpochContextWith mkMockPerasVotingCommitteeInput for test types with limited Peras support, and * mkBoundedPerasEpochContextWith V1.mkPerasVotingCommitteeInput for production types.

Initialize a PerasEpochContextResolver from a ledger and header state.

NOTES: 1. We may later decide that a PerasEpochContextResolver is always initiated with empty/error value, and rely on the first ticking to properly initialize it. In the current architecture, however, that would work only if the first ticking happens when the previous slot is either Origin, or a slot from a previous epoch compared to the target slot. 2. Given that we have no assumption that (1) would work, we made a polymorphic system where a BoundedEpochContext can be created from either a ticked or unticked ledger+header state (see LedgerStateSupportsPeras and ChainDepStateSupportsPeras helper classes). This way, a PerasEpochContextResolver can be initialized from unticked LedgerState and HeaderState, but then ticked by using the 'Ticked LedgerState' and 'Ticked HeaderState'. 3. If in the future we move on to a system where the resolver is always initialized with empty/error value, we can remove the polymorphic system and only create a BoundedPerasEpochContext from 'Ticked LedgerState' and 'Ticked HeaderState'.

Tick a PerasEpochContextResolver to a target SlotNo.

NOTES: 1. To avoid circular dependencies, this function uses a deconstructed ExtLedgerState instead of the ExtLedgerState itself. 2. It doesn't seem to bring much to differentiate a PerasEpochContextResolver from a ticked one at type level, since they need to carry exactly the same information. We tried, and it didn't improve readability.

Data needed to run time-dependent queries.

NOTE: this is existential on the MapKind of the ledger state, as we really don't care about it for the purpose of time resolution.

Wrapper over runQuery that uses a TimeResolutionContext to build a Summary.

Wrapper over runQueryEraIndexed that uses a TimeResolutionContext to build a Summary.

A handle to an STM action that returns a TimeResolutionContext.

Helper to run a time-dependent query using a TimeResolutionContextHandle.

The outcome of comparing the epoch of a previous slot with the epoch of a target slot when ticking the ledger, discriminated by how many epoch boundaries were crossed. This drives how the Peras epoch-context resolver is updated.

Errors that can occur when detecting whether a target slot is in the next epoch compared to a previous slot.

Determine whether a target slot is in the next epoch compared to a previous slot, and if so, how many epoch boundaries were crossed.