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 tracking #2852

Closed
7 tasks
protolambda opened this issue Mar 14, 2022 · 0 comments
Closed
7 tasks

EIP-4844 tracking #2852

protolambda opened this issue Mar 14, 2022 · 0 comments
Assignees
Labels

Comments

@protolambda
Copy link
Contributor

This issue tracks open TODOs for EIP-4844 integration into the consensus-specs.

  • Fork-choice spec
    • Define "dependency" system in fork-choice and testing. (need help from @djrtwo or @adiasg)
    • Move download-requirement of blobs from validator spec to fork-choice spec doc
  • KZG commitments in BeaconState
    • Register the KZG commitments that are included in beacon-blocks in the BeaconState.
      This is optional, but provides more direct merkle proofs / access. Indirectly, through the beacon-block latest_header and history accumulators we already include them though.
  • Update configs / presets files with new EIP-4844 variables
  • Enable pyspec generation from EIP-4844 feature dir
  • Update test-generators & py-tests to output beacon-chain test-vectors for this feature

And there's an option to move the process_blob_kzgs to under the is_execution_enabled if-statement, but it's a no-op on empty payloads (when execution is not enabled), and ideally we remove the if-statement in the next hardfork after Bellatrix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants
@hwwhww @protolambda and others