# Kiln Spec v2.1 ***Kiln spec v2.1 released on March 10. See [v2.1 change set](#v2.1-change-set) for details.*** [toc] This document defines the version of the Merge specification that is considered to be implemented for Kiln🔥🧱 -- the last Merge sprint before launching pre-production testnets. Kiln aims to move client implementations into the production readiness stage. ## Spec versions The following is Kiln Spec v2.1: | Specification | Release / Commit | Reference | | - | - | - | | Consensus spec | `v1.1.10` + `PR#2844` | [`v1.1.10`](https://github.com/ethereum/consensus-specs/tree/v1.1.10/specs/bellatrix) + [`#2844`](https://github.com/ethereum/consensus-specs/pull/2844) | | Consensus spec tests | `v1.1.10` | [`v1.1.10`](https://github.com/ethereum/consensus-spec-tests/tree/v1.1.10) | | EIP-3675 | `d896145678bd65d3eafd8749690c1b5228875c39` | [`d8961456`](https://github.com/ethereum/EIPs/blob/d896145678bd65d3eafd8749690c1b5228875c39/EIPS/eip-3675.md) | | EIP-4399 | `6fe18dc5cc287c5ed690c29b4092a0a2f8873be4` | [`6fe18dc5`](https://github.com/ethereum/EIPs/blob/6fe18dc5cc287c5ed690c29b4092a0a2f8873be4/EIPS/eip-4399.md) | | Engine API | `v1.0.0-alpha.8` | [`v1.0.0-alpha.8`](https://github.com/ethereum/execution-apis/blob/v1.0.0-alpha.7/src/engine/specification.md) | *Note*: There might be minor updates to this specification during the sprint. The updates will be reflected by bumping the Kiln spec number (e.g. to v2), bumping the version of the respective document in this table, and announcing in the [Interop](https://discord.gg/3aFPzzU9) channel on Discord. Stay tuned. ### v2.1 change set **Date**: March 10, 2022 | Specification | Changes | Comments | | - | - | - | | Engine API | updated to [`v1.0.0-alpha.8`](https://github.com/ethereum/execution-apis/releases/tag/v1.0.0-alpha.8) | | | Consensus spec | PR [#2844](https://github.com/ethereum/consensus-specs/pull/2844) | Optimistically import any post-merge block | ### v2 change set **Date**: February 22, 2022 | Specification | Changes | Comments | | - | - | - | | Engine API | updated to [`v1.0.0-alpha.7`](https://github.com/ethereum/execution-apis/releases/tag/v1.0.0-alpha.7) | | | EIP-4399 | updated to [`6fe18dc5`](https://github.com/ethereum/EIPs/blob/6fe18dc5cc287c5ed690c29b4092a0a2f8873be4/EIPS/eip-4399.md) | PR [#4836](https://github.com/ethereum/EIPs/pull/4836) | | Engine API | PR [#180](https://github.com/ethereum/execution-apis/pull/180) | Renaming related to EIP-4399 update | | Consensus spec | PR [#2835](https://github.com/ethereum/consensus-specs/pull/2835) | Renaming related to EIP-4399 update | *Note*: Renamings introduced by PRs [#180](https://github.com/ethereum/execution-apis/pull/180) and [#2835](https://github.com/ethereum/consensus-specs/pull/2835) into Engine API and Consensus specs respectively are part of the Kiln v2 specification and must be implemented alongside with other v2 changes. These renamings are considered for inclusion in the next releases of Engine API and Consensus specs. ## Consensus layer Changes to Consensus layer spec introduced in Kiln v1: * Optimistic Sync [#2770](https://github.com/ethereum/consensus-specs/pull/2770), [#2820](https://github.com/ethereum/consensus-specs/pull/2820) * Rename "Merge" -> "Bellatrix" [#2774](https://github.com/ethereum/consensus-specs/pull/2774) * Rename `execute_payload` to `notify_new_payload` [#2817](https://github.com/ethereum/consensus-specs/pull/2817) * Rename `receipt_root` -> `receipts_root` [#2808](https://github.com/ethereum/consensus-specs/pull/2808) ## Execution layer Changes to Execution layer spec introduced in Kiln v1: * Extend semantics of `executePayload` and `forkchoiceUpdated` methods [#165](https://github.com/ethereum/execution-apis/pull/165) * Replace terminal block error with `INVALID_TERMINAL_BLOCK` status [#170](https://github.com/ethereum/execution-apis/pull/170) * Refine message ordering. Take 2 [#148](https://github.com/ethereum/execution-apis/pull/148) *Note:* Authentication for engine api [#167](https://github.com/ethereum/execution-apis/pull/167) is a pending change to the Engine API and will be added in a subsequent version of the Kiln specification.
Last changed by  
 
Mikhail Kalinin
7549

Read more

Kintsugi Spec v3

Kintsugi spec updated to v3 on November 30. See v3 change set for details. [toc] This document defines the version of the Merge specification that is considered to be implemented for Kintsugi🍵 -- the Merge sprint for November 2021 -- and provides additional guidance to client developers. Spec versions The following is Kintsugi Spec v3. Specification

11/30/2021
Merge Interop Spec

[toc] This document defines the version of the Merge specification that should be implemented as a prerequisite for the Interop and provides additional guidance to client developers. Spec versions The Merge specification has a number of different sources that should be aligned with each other to avoid incompatibility issues between consensus and execution client implementations. We define the following versions for each of these documents to be used during the Interop: Specification

10/5/2021
Engine API design space

The purpose of this document is to frame the design space of the Consensus API. It starts with the minimally required set of methods and gradually increases the complexity of the design by adding asynchrony, consistency checkpoints and some methods that might increase UX and aid for faster recovery after failures but are not required for the core functionality. The end goal is to come up with the solution that would not restrict future extensibility of the protocol and on the other hand would re-use as much of the existing JSON-RPC implementation over HTTP and websockets that we already have across clients. The security of this API is critical, thus we propose that implementations expose this API at an independent port from standard JSON-RPC user API and to put the new set of methods into a new namespace. With this progressive idea in mind we prefix engine_ as the namespace as a working prototype to be able to generalize API between L1 and L2 in the future, though, the name is debatable and doesn't matter that much at this stage. Previous work: Rayonism consensus JSON-RPC Some thoughts on API improvements

9/15/2021
Executable beacon chain spec

Beacon chain Configuration Execution Name Value MAX_BYTES_PER_TRANSACTION_PAYLOAD 2**20

2/25/2021
Read more from Mikhail Kalinin
Published on HackMD