Installation Lap

v1.0.0-alpha.3 is a pre-release of the Execution API.

eth Namespace

No changes were made in this release.

engine Namespace

There were many changes to the engine API based on feedback from the Amphora event. This release is intended to be a stable target for clients planning to participate in the November merge sprint.

• Created a mainnet target for the engine API based on the interop version #81
• Removed engine_consensusValidated in accordance with it's removal from EIP-3675 #82
• Removed engine_preparePayload and instead combined the functionality as an extension of engine_forkchoiceUpdated via an additional parameter #83
• Added validAncestorHash to engine_executePayload return data #84
• Renumbered error codes to use more standard JSON-RPC codes #85
• Made a note of advanced usage of the API #86
• Enforced strict message ordering #89
• Added safeBlockHash to engine_forkchoiceUpdated #93
• Implemented method-level versioning #94
• Required clients to also expose the eth namespace on the same port as the engine namespace #97
• Versioned payloadId computation and specified collision-resistant calculation #104

Please note that there is an open discussion regarding how EL should respond when CL request a massive reorg that will cause it revert to syncing status.

Thank you @djrtwo, @mkalinin, @holiman, @protolambda, and others for their contributions on this release!

--

Full specification here.

Valve Replacement

Release

v1.0.0-alpha.2 is a breaking update to the engine method preparePayload. Previously the method returned a QUANTITY value. Now it returns an object with one field payloadId, which is a QUANTITY.

See #77 for the discussion around the change.

--

Full specification here.

Roaring Engine

Release

v1.0.0-alpha.1 is the first pre-release of the Execution API.

eth Namespace

The eth specification is a full rewrite, under CC0, of ETC Labs' JSON-RPC specification. It aims to be the canonical source for the standard eth methods implemented in execution clients. The specification is still under active development and testing against clients, so its correctness is not guaranteed.

Many people contributed to this work in significant ways, so a few shout outs are due:

• @shanejonas, @BelfordZ, et al. for developing the Open RPC standard
• @tkstanczak and @shanejonas for pushing for more rigorous definitions of the API
• @shanejonas for being available to help with questions regarding Open RPC and the JSON Schema standard, and for reviewing much of the work that went into the rewrite
• @alita-moore and @DockBoss for their efforts over the past few months to document the edge cases in the API

engine Namespace

The initial engine methods for the Merge Interop has been specified in #74 by @mkalinin. It introduces the following methods:

engine_executePayload
engine_preparePayload
engine_getPayload
engine_consensusValidated
engine_forkchoiceUpdated

Full specification here.

--

Αυτό είναι μόνο η αρχή.