# 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
8281

Read more

In-Protocol deposits PoC sync calls

Call 5 Meeting Date/Time: Thursday 2023/4/6 at 15:30 UTC Meeting Duration: 45 minutes Agenda Client updatesEL CL Devnet/Testing updates

3/30/2023
In-Protocol deposits PoC scope

Specification Execution Layer EIP-6110 Conensus Layer #3177 Engine API eip6110.md Specification work [x] Explore design space without pending_queue in the beacon state, #08c728, #23c10c. [ ] Rebase spec with Deneb/Cancun [ ] Confirm that a significant increase of a number of top ups per epoch is fine wrt WS period computation. [ ] Confirm that CL client devs are fine with taking the (pubkey, index) cache complexity in favour of complexity related to pending_queue.

3/30/2023
Engine API: Shanghai checks

Source: https://github.com/ethereum/execution-apis/blob/main/src/engine/shanghai.md [x] Paris payloads MUST be processed by newPayloadV2 and forkchoiceUpdatedV2[x] case with forkchoiceUpdatedV2 and payloadAttributes == null, and Paris block data [x] case with forkchoiceUpdatedV2 and payloadAttributes == null, and Shanghai block data [x] case with forkchoiceUpdatedV2 and payloadAttributes = {data of the first Capella slot} etc [x] EL MUST return -32602: Invalid params in the following cases: [x] newPayloadV2ExecutionPayloadV1 passed with timestamp >= SHANGHAI_TIMESTAMP

2/2/2023
In-Protocol Deposits breakout

Next steps Explore design space without pending_queue in the beacon stateTransition: process block.body.deposits and block.body.execution_payload.deposits in parallel instead of queuing the latter and waiting for the former to fill the gap (proposed by Peter Davies) WS period: confirm that a significant increase of a number of top ups per epoch is fine (pubkey, index) cache: confirm that CL client devs are fine with taking this engineering complexity in favour of complexity related to pending_queuedata complexity of two queues is higher than of one because of top ups, each top up would take a separate record in the pending_queue while all top ups for the same validator are accumulated in a single record in the validator registry sig verification complexity: limited by a size of EL block, worth re-evaluating Evaluate a number of deposits per 30M gas block that advanced attacker can induce by making multiple deposits in one transaction (reduced cost by removing base tx fee and re-using warmed up state slot reads/writes) -- Peter Davies to do the evaluation one deposit per transaction consumes 50-60k gas and results in 500-600 deposits per 30M gas block at max; this number can be doubled with the tricks

1/26/2023
Read more from Mikhail Kalinin
Published on HackMD