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

[Merge] Kiln Meta-Issue 🔥🧱 #4972

Closed
23 of 24 tasks
ajsutton opened this issue Feb 11, 2022 · 1 comment
Closed
23 of 24 tasks

[Merge] Kiln Meta-Issue 🔥🧱 #4972

ajsutton opened this issue Feb 11, 2022 · 1 comment
Assignees

Comments

@ajsutton
Copy link
Contributor

ajsutton commented Feb 11, 2022

Description

Tracking issue for work required to fully support Kiln meta-spec (https://hackmd.io/@n0ble/kiln-spec)

M0 (Implementation started):

  • Create tracking issue (this one!)

M1 (Kiln v1 Spec implemented):

M2 (Kiln v2 Spec implemented):

M3 (Many-toMany Interop):

  • Run many:many devnet with transition (TTD occurring 8+ epochs in the beacon chain)
  • Send EL Txs that transfer ETH and deploy a contract which are successfully executed on chian

M4 (Weekly devnet):

  • Participate in EF led weekly devnet
  • Be on the devnet during the merge transition process and process EL TXs
  • Sync from genesis using Optimistic Sync

M5 (All-to-All persistent testnet):

M6 (Kiln code released)

  • Mainnet-compatibile sync support
  • Merge Kiln code into main branch
  • Add --network kiln CLI flag
  • Add basic documentation for public to connect to Kiln
  • Stable release with Kiln support
@ajsutton ajsutton self-assigned this Feb 21, 2022
@ajsutton
Copy link
Contributor Author

ajsutton commented Apr 4, 2022

Closing this as all the work is done on the teku side now. Making sure the kiln specification is feature complete for MainNet is a specs repo concern.

@ajsutton ajsutton closed this as completed Apr 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant