Crate engine
Expand description
§alloy-rpc-types-engine
Types for the engine
Ethereum JSON-RPC namespace.
Engine API types: https://github.com/ethereum/execution-apis/blob/main/src/engine/authentication.md and https://eips.ethereum.org/EIPS/eip-3675, following the execution specs https://github.com/ethereum/execution-apis/tree/6709c2a795b707202e93c4f2867fa0bf2640a84f/src/engine.
Modules§
- payload
- Payload types.
Structs§
- Blob
AndProof V1 - Blob type returned in responses to
engine_getBlobsV1
: https://github.com/ethereum/execution-apis/pull/559 - Blobs
Bundle V1 - This includes all bundled blob related data of an executed payload.
- Cancun
Payload Fields - Fields introduced in
engine_newPayloadV3
that are not present in theExecutionPayload
RPC object. - Claims
- Claims in JWT are used to represent a set of information about an entity.
- Client
Version V1 - Contains information which identifies a client implementation.
- Execution
Data - Struct aggregating
ExecutionPayload
andExecutionPayloadSidecar
and encapsulating complete payload supplied for execution. - Execution
Payload Body V1 - This structure contains a body of an execution payload.
- Execution
Payload Envelope V2 - This structure maps for the return value of
engine_getPayload
of the beacon chain spec, for V2. - Execution
Payload Envelope V3 - This structure maps for the return value of
engine_getPayload
of the beacon chain spec, for V3. - Execution
Payload Envelope V4 - This structure maps for the return value of
engine_getPayload
of the beacon chain spec, for V4. - Execution
Payload Input V2 - This is the input to
engine_newPayloadV2
, which may or may not have a withdrawals field. - Execution
Payload Sidecar - Container type for all available additional
newPayload
request parameters that are not present in theExecutionPayload
object itself. - Execution
Payload V1 - This structure maps on the ExecutionPayload structure of the beacon chain spec.
- Execution
Payload V2 - This structure maps on the ExecutionPayloadV2 structure of the beacon chain spec.
- Execution
Payload V3 - This structure maps on the ExecutionPayloadV3 structure of the beacon chain spec.
- Forkchoice
State - This structure encapsulates the fork choice state
- Forkchoice
Updated - Represents a successfully processed forkchoice state update.
- JwtSecret
- Value-object holding a reference to a hex-encoded 256-bit secret key.
- Maybe
Cancun Payload Fields - A container type for CancunPayloadFields that may or may not be present.
- Maybe
Prague Payload Fields - A container type for PraguePayloadFields that may or may not be present.
- Payload
Attributes - This structure contains the attributes required to initiate a payload build process in the
context of an
engine_forkchoiceUpdated
call. - Payload
Id - And 8-byte identifier for an execution payload.
- Payload
Status - This structure contains the result of processing a payload or fork choice update.
- Prague
Payload Fields - Fields introduced in
engine_newPayloadV4
that are not present in theExecutionPayload
RPC object. - Transition
Configuration - This structure contains configurable settings of the transition process.
Enums§
- Client
Code - This enum defines a standard for specifying a client with just two letters. Clients teams which have a code reserved in this list MUST use this code when identifying themselves.
- Execution
Payload - An execution payload, which can be either ExecutionPayloadV1, ExecutionPayloadV2, or ExecutionPayloadV3.
- Execution
Payload Field V2 - This represents the
executionPayload
field in the return value ofengine_getPayloadV2
, specified as: - Forkchoice
Update Error - A standalone forkchoice update errors for RPC.
- Forkchoice
Update Version - The version of the engine api.
- JwtError
- Errors returned by the
JwtSecret
- Payload
Error - Error that can occur when handling payloads.
- Payload
Status Enum - Represents the status response of a payload.
- Payload
Validation Error - Various errors that can occur when validating a payload or forkchoice update.
Constants§
- CAPABILITIES
- The list of all supported Engine capabilities available over the engine endpoint.
- INVALID_
FORK_ CHOICE_ STATE_ ERROR - invalid forkchoice state error code.
- INVALID_
FORK_ CHOICE_ STATE_ ERROR_ MSG - invalid forkchoice state error message.
- INVALID_
PAYLOAD_ ATTRIBUTES_ ERROR - invalid payload attributes error code.
- INVALID_
PAYLOAD_ ATTRIBUTES_ ERROR_ MSG - invalid payload attributes error message.
Type Aliases§
- Execution
Payload Bodies V1 - The execution payload body response that allows for
null
values. - Fork
Choice Update Result - Represents possible variants of a processed forkchoice update.