Static internal information needed by pre_filter.

It depends on the head block upon which a mempool is built.

Create an info based on the head block.

Should be called only once when a new prevalidator is started for a new protocol. Subsequent infos should be created using flush.

Create a new info based on the head block.

Parts of the old info (which may have been built on a different block) are recycled, so that this function is more efficient than init and does not need a Tezos_protocol_environment.Context.t argument.

Perform some syntactic checks on the operation.

To be used mostly as an exceptional mechanism to prevent ill-formed operations to block block application.

Note that the functions exposed in the output of proto_with_validation_plugin already call syntactic_check when appropriate.

Perform some light preliminary checks on the operation.

If successful, return `Passed_prefilter with the priority of the operation, based on the operation kind and potentially its fee, gas, and size. If not, return a classification containing the encountered error.

Should be called on arrival of an operation and after a flush of the prevalidator.

Return a conflict handler for Mempool.add_operation.

See the documentation of type Mempool.conflict_handler in e.g. lib_protocol_environment/sigs/v8/updater.mli.

Precondition: both operations must be individually valid (required by the protocol's operation comparison on which the implementation of this function relies).

The purpose of this module is to provide the fee_needed_to_replace_by_fee function. For this function to be correct, the caller must maintain the state of type t by calling update on each successfully validated operation and its induced replacements.

Compute the minimal fee (expressed in mutez) that candidate_op would need to have in order to be strictly greater than op_to_overtake according to compare_operations.

Return None when at least one operation is not a manager operation.

Also return None if both operations are manager operations but there was an error while computing the needed fee. However, note that this cannot happen when both manager operations have been successfully validated by the protocol.