An Alpha_context manager operation, packed so that the type is not parametrized by 'kind.

Information stored for each prechecked manager operation.

Note that this record does not include the operation hash because it is instead used as key in the map that stores this information in the state below.

Build a manager_op_weight from operation hash and manager_op_info.

Static information to store in the filter state.

State that tracks validated manager operations.

Returns the weight and resources consumption of an operation. The weight corresponds to the one implemented by the baker, to decide which operations to put in a block first (the code is largely duplicated). See Tezos_baking_alpha.Operation_selection.weight_manager

Return fee for an operation that consumes op_resources for its weight to be strictly greater than min_weight.

Check if an operation as a weight (fees w.r.t gas and size) large enough to be prechecked and return said weight. In the case where the prechecked mempool is full, return an error if the weight is too small, or return the operation to be replaced otherwise.

At a given level a consensus operation is acceptable if its earliest expected timestamp, op_earliest_ts is below the current clock with an accepted drift for the clock given by a configuration.

Check that an operation with the given op_round, at level op_level is likely to be correct, meaning it could have been produced before now (+ the safety margin from configuration).

Given an operation at level greater or equal than/to the current level, we compute the expected timestamp of the operation's round. If the operation is at a greater level, we assume that it is based on the proposal at round zero of the current level.

All operations whose (level, round) is lower than or equal to the current head are deemed valid. Note that in case where their is a high drift in the computer clock, they might not have been considered valid by comparing their expected timestamp to the clock.

This is a stricter than necessary filter as it will reject operations that could be valid in the current timeframe if the proposal they endorse is built over a predecessor of the current proposal that would be of lower round than the current one.

What can we do that would be smarter: get current head's predecessor round and timestamp to compute the timestamp t0 of a predecessor that would have been proposed at round 0.

Timestamp of round at current level for an alternative head that would be based on such proposal would be computed based on t0. For level higher than current head, compute the round's earliest timestamp if all proposal passed at round 0 starting from t0.

A quasi infinite amount of "valid" (pre)endorsements could be sent by a committee member, one for each possible round number.

This filter rejects (pre)endorsements that refer to a round that could not have been reached within the time span between the last head's timestamp and the current local clock.

We add config.clock_drift time as a safety margin.

Remove a manager operation hash from the ops_state. Do nothing if the operation was not in the state.

Remove a manager operation hash from the ops_state. Do nothing if the operation was not in the state.

Add a manager operation hash and information to the filter state. Do nothing if the operation is already present in the state.

If the provided operation is a manager operation, add it to the filter_state. If the mempool is full, either return an error if the operation does not have enough weight to be included, or return the operation with minimal weight that gets removed to make room.

Do nothing on non-manager operations.

If replace is provided, then it is removed from filter_state before processing op. (If replace is a non-manager operation, this does nothing since it was never in filter_state to begin with.) Note that when this happens, the mempool can no longer be full after the operation has been removed, so this function always returns `No_replace.

This function is designed to be called by the shell each time a new operation has been validated by the protocol. It will be removed in the future once the shell is able to bound the number of operations in the mempool by itself.

conflict_handler config returns a conflict handler for Mempool.add_operation (see Mempool.conflict_handler).

• For non-manager operations, we select the greater operation according to Operation.compare.

• A manager operation is replaced only when the new operation's fee and fee/gas ratio both exceed the old operation's by at least a factor of config.replace_by_fee_factor (see better_fees_and_ratio).

Precondition: both operations must be individually valid (because of the call to Operation.compare).