Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kiln 🔥🧱 (the merge) devnets 2022 tracker #3731

Closed
14 tasks done
g11tech opened this issue Feb 8, 2022 · 1 comment
Closed
14 tasks done

Kiln 🔥🧱 (the merge) devnets 2022 tracker #3731

g11tech opened this issue Feb 8, 2022 · 1 comment
Assignees
Labels
Epic Issues used as milestones and tracking multiple issues.

Comments

@g11tech
Copy link
Contributor

g11tech commented Feb 8, 2022

Kiln 🔥🧱

Kiln 🔥🧱 is the followup sprint of Kintsugi 🍵 with aim to move client implementations into the production readiness stage. This is the supposed to be last devnet before pre-production testsnets.

Kiln v1 spec: https://hackmd.io/@n0ble/kiln-spec
Kiln v2 spec: https://hackmd.io/@n0ble/kiln-spec#v2-change-set
Milestones tracker: https://notes.ethereum.org/@timbeiko/kiln-milestones
Engine API test vectors: https://notes.ethereum.org/rmVErCfCRPKGqGkUe89-Kg?view

CL Spec Tracker

Merge Tracker

Kiln v1:

  • Interface lodestar with the ELs on Kiln spec 1.0.0.alpha.6 Implement Kiln spec (v1) execution apis 1.0.0-alpha.6 #3736
  • basic interop with
    • nethermind
    • geth
  • Perform kurtosis runs for lodestar coupled with Kiln ready EL/Cl clients #3751
  • devnet4 participation https://notes.ethereum.org/D5xK4XrmTb6MKGudf_hcrg
    • setup of devnet by EL team
    • Merge transition
    • Issues/Observations
      • This devnet was important for the EL's beacon sync apart from the changed api semantics.
      • At the merge points, there were atleast 2 pow chains, and hence when the terminal block came in from the clients that were ahead, the lodestar node (whose EL - nethermind was on another fork), got accepted and didn't move ahead
      • Because of some issue (already being investigated by nethermind team), it didn't sync to right chain, with ACCEPTED status being rejected till the head of the chain (of synced ELs) move 128 slots ahead, after that it started syncing, and synced up to chain head with an execution status of syncing. Lodestar's behavior in this is as expected and as per the optimistic specs.

Kiln v2

Devnet -5

Kiln

  • kiln network config update

Kiln spec v2.1

@g11tech
Copy link
Contributor Author

g11tech commented Apr 22, 2022

Closed in favour of the merge tracker: #3945

@g11tech g11tech unpinned this issue Apr 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic Issues used as milestones and tracking multiple issues.
Projects
None yet
Development

No branches or pull requests

1 participant