Kiln 🔥🧱 Milestones

Following Kintsugi, Kiln 🔥🧱 incorporates the last major spec changes we expect for The Merge.

As with Kintsugi, we expect to have a few iterations of short-lived devnets before launching a longstanding testnet aimed for broader usage by application and infrastructure developers.

The Kiln Meta Spec lists the changes and associated commits for the EL, CL and Engine Api specifications.

• Kiln 🔥🧱 Milestones
  • Milestone tracker
    • Execution layer
    • Consensus layer
  • Milestones
  • Office Hours 🕰

Milestone tracker

To track progress across all clients, please create a Kiln 🔥🧱 tracking issue in your repo. We’ll link to those issues here as well as track high-level milestones at a glance.

As with Kintsugi, please do not waste other teams’ time prior to implementing core specs and running all test vectors (M1). The milestones are designed to help capture complexity and iterate toward stable interop and testnets.

Please link to your primary tracking issue against the name of your client (first column). See Kintugi links here.

Execution layer

Consensus layer

Milestones

• M0: Implementation started

  • Signify that implementation of the Kiln 🔥🧱 meta-spec has started by creating a tracking issue and linking in the above table

• M1: Kiln v1 Spec Implemented

  • EL/CL: pass all released consensus test vectors
  • Run against mergemock
  • Geth based Engine API test cases
  • EL: geth based EIP 4399 test cases
  • EL: additional 4399 test cases

• M2: Kiln v2 Spec Implemented

  • EL/CL: pass all released consensus test vectors
  • Run against mergemock
  • Geth based Engine API test cases
  • EL: geth based EIP 4399 test cases
  • EL: additional 4399 test cases

• M3: Many-to-Many Interop – 2 or more EL and CL teams perform interop testing

  • Run many:many devnet with transition (TTD occuring 8+ epochs in the beacon chain)
  • Send EL TXs that transfer ETH and deploy a contract which are successfully executed on chain
  • List teams you interop with in the table

• M4: Weekly devnet – Weekly devnet build for more in depth testing

  • Starting in the second week of February, EF devops (Pari, etc) will lead a devnet build on Thursdays. This devnet (if successful) will remain up until the following Thursday
  • Once passing M2, join the weekly devnet
  • To pass M4, client team must be on the devnet during the Merge transition process and process EL TXs
    • Note: Increasingly complex EL TXs will be sent on weekly devnets, testing EIPs and fuzzing the network
  • Addionally, CL clients must be able to sync from genesis using Optimistic Sync

• M5: All-to-All persistent testnet – All ready EL and CL teams create a long-lived devnet to replace Kintsugi

  • Kiln specification considered feature complete for mainnet Merge
  • Run many:many devnet with transition
  • Keep the devnet up until The Merge as a testing environment for applications
  • Create README for the public to connect

• M6: Kiln 🔥🧱 code released – clients release Kiln 🔥🧱 code for public consumption

  • Mainnet-compatible sync support (Optimistic, Snap, etc.)
  • Merge Kiln 🔥🧱 code into main branch
  • Create basic documentation, ideally with a CLI flag, for the public to connect to persistent testnet
  • Release Kiln 🔥🧱 for public consumption

Office Hours 🕰

Every week, we’ll hold Kiln 🔥🧱 office hours as part of the AllCoreDevs and Consensus Layer calls. The first 30-45 minutes of each call will be dedicated to team updates, issue/blocker discussion and next steps for Kiln 🔥🧱.

The calls are each held fortnightly on alternating weeks with the Consensus Layer call happening next, on February 10 (Thursday) 14:00 UTC, and the AllCoreDevs call happening the following week February 18 14:00 UTC.

Note that these calls are “fixed” in UTC and do not move with DST start/end. You can subscribe to them on Google Calendar here.