Module valid_payload 

This is an extension trait for any provider that implements the engine API, to wait for a VALID response. This is useful for benchmarking, as it allows us to wait for a payload to be valid before sending additional calls.

Structs

NewPayloadTimingBreakdown 🔒

Server-side timing breakdown from reth_newPayload endpoint.

RethPayloadStatus 🔒

Response from reth_newPayload endpoint, which includes server-measured latency.

Traits

EngineApiValidWaitExt

An extension trait for providers that implement the engine API, to wait for a VALID response.

Functions

block_to_new_payload 🔒

Converts an RPC block into versioned engine API params and an [ExecutionData].

call_forkchoice_updated 🔒

Calls the correct engine_forkchoiceUpdated method depending on the given EngineApiMessageVersion, using the provided forkchoice state and payload attributes for the actual engine api message call.

call_forkchoice_updated_with_reth 🔒

Calls either reth_forkchoiceUpdated or the standard engine_forkchoiceUpdated* depending on use_reth.

call_new_payload 🔒

Calls the correct engine_newPayload method depending on the given [ExecutionPayload] and its versioned variant. Returns the EngineApiMessageVersion depending on the payload’s version.

call_new_payload_with_reth 🔒

Calls either engine_newPayload* or reth_newPayload depending on whether version is provided.

payload_to_new_payload 🔒

Converts an execution payload and sidecar into versioned engine API params and an [ExecutionData].