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

EIP-4844 Implementers' Call #20 #755

Closed
timbeiko opened this issue Apr 6, 2023 · 8 comments
Closed

EIP-4844 Implementers' Call #20 #755

timbeiko opened this issue Apr 6, 2023 · 8 comments

Comments

@timbeiko
Copy link
Collaborator

timbeiko commented Apr 6, 2023

Meeting Info

📆 Subscribe to the Ethereum Protocol Call calendar for calendar invites

Agenda

@protolambda
Copy link

PSA: the Unknown Payload error code used in the 4844 engine API changed to match the regular engine API unknown payload error code again (we missed an update last year). See https://github.com/ethereum/execution-apis/pull/399/files

@mkalinin
Copy link
Contributor

If we have a time it would be great to discuss merging getPayloadV3 with getBlobsBundleV1 Engine API methods

@terencechain
Copy link
Contributor

Traveling so unlikely to make this. Update: we have tested the following on devnet with multiple prsym nodes:

  • State transition passes spec tests
  • Validators signing and broadcasting blobs
  • Nodes Syncing blocks and blobs by range
  • Blobs by root on special cases

We should be ready for multiclient devnet

@timbeiko
Copy link
Collaborator Author

Added @protolambda @mkalinin, and noted @terencechain - TY for the update!

@realbigsean
Copy link

I'm also not going to be able to make it but here is a Lighthouse update:

  • Jimmy has been working on testing locally https://hackmd.io/@jimmygchen/H1XUtBIfn
  • We're passing deneb EF tests for spec release v1.3.0-rc.5, but this doesn't include the TX type update, it would be good if we could get a CL spec release candidate with all changes we intend to include in the devnet so we can make sure we are passing EF tests
  • We're still working on ironing out single block + blob lookups as well as fixing some gossip verification
  • We could make 1 week for a devnet target, would prefer 2 weeks

@g11tech
Copy link

g11tech commented Apr 17, 2023

Traveling so unlikely to make this. Update: we have tested the following on devnet with multiple prsym nodes:

* State transition passes spec tests

* Validators signing and broadcasting blobs

* Nodes Syncing blocks and blobs by range

* Blobs by root on special cases

We should be ready for multiclient devnet

if prysm is ready with the following proposed spec for devnet 5: https://hackmd.io/@inphi/HJZo4vQGn, lodestar/ethereumjs can do devnet with prsym / any other EL

Talking of spec tests, are the new spec tests with 0x03 type version out?

cc @Inphi

@g11tech
Copy link

g11tech commented Apr 17, 2023

Talking of devnet 5 specs, it would be nice if these PRs could be reviewed/merged:

I also propose optional inclusion of this PR for devnet5:

@timbeiko
Copy link
Collaborator Author

closed in favor of #760

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

6 participants