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 types.
Structs§
- Blob type returned in responses to
engine_getBlobsV1
: https://github.com/ethereum/execution-apis/pull/559 - This includes all bundled blob related data of an executed payload.
- Fields introduced in
engine_newPayloadV3
that are not present in theExecutionPayload
RPC object. - Claims in JWT are used to represent a set of information about an entity.
- Contains information which identifies a client implementation.
- This structure contains a body of an execution payload.
- This structure maps for the return value of
engine_getPayload
of the beacon chain spec, for V2. - This structure maps for the return value of
engine_getPayload
of the beacon chain spec, for V3. - This structure maps for the return value of
engine_getPayload
of the beacon chain spec, for V4. - This is the input to
engine_newPayloadV2
, which may or may not have a withdrawals field. - Container type for all available additional
newPayload
request parameters that are not present in theExecutionPayload
object itself. - This structure maps on the ExecutionPayload structure of the beacon chain spec.
- This structure maps on the ExecutionPayloadV2 structure of the beacon chain spec.
- This structure maps on the ExecutionPayloadV3 structure of the beacon chain spec.
- This structure encapsulates the fork choice state
- Represents a successfully processed forkchoice state update.
- Value-object holding a reference to a hex-encoded 256-bit secret key.
- A container type for CancunPayloadFields that may or may not be present.
- A container type for PraguePayloadFields that may or may not be present.
- This structure contains the attributes required to initiate a payload build process in the context of an
engine_forkchoiceUpdated
call. - And 8-byte identifier for an execution payload.
- This structure contains the result of processing a payload or fork choice update.
- Fields introduced in
engine_newPayloadV4
that are not present in theExecutionPayload
RPC object. - This structure contains configurable settings of the transition process.
Enums§
- 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.
- An execution payload, which can be either ExecutionPayloadV1, ExecutionPayloadV2, or ExecutionPayloadV3.
- This represents the
executionPayload
field in the return value ofengine_getPayloadV2
, specified as: - A standalone forkchoice update errors for RPC.
- The version of the engine api.
- Errors returned by the
JwtSecret
- Error that can occur when handling payloads.
- Represents the status response of a payload.
- Various errors that can occur when validating a payload or forkchoice update.
Constants§
- The list of all supported Engine capabilities available over the engine endpoint.
- invalid forkchoice state error code.
- invalid forkchoice state error message.
- invalid payload attributes error code.
- invalid payload attributes error message.
Type Aliases§
- The execution payload body response that allows for
null
values. - Represents possible variants of a processed forkchoice update.