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

Added cancun blob test vectors #52

Merged
merged 4 commits into from
Mar 6, 2025
Merged

Added cancun blob test vectors #52

merged 4 commits into from
Mar 6, 2025

Conversation

debjit-bw
Copy link
Member

@debjit-bw debjit-bw commented Mar 4, 2025

Added test vectors for generating blobs with nethermind and applying them to reth.

Changes

  • scripts/apply_test_vectors.sh: Added support for multiple versions of engine_newPayloadV_ and engine_forkchoiceUpdatedV_.
  • chainspec files: added config or changed variables for cancun and pectra forks (timestamps and fields like blobSchedule, eip4844TransitionTimestamp, etc.
  • scripts/run_nethermind.sh: Due to a change in nethermind's optimization, txs were being stuck in pending if sent locally. This image is a rollback of the change (hotfix) till they release the proper fix in an image release (soon).
  • scripts/generate_eip4844-cancun_vectors.sh: The main file which generates the test vectors. It first deploys the deposit contract, and in the second block sends a blob containing a "Hello World" text padded with zeros. The generation steps are mentioned here.
  • post-merge-run.yml: Adds the new test to CI.

@debjit-bw debjit-bw requested a review from dapplion March 4, 2025 17:56
@debjit-bw debjit-bw marked this pull request as ready for review March 4, 2025 18:30
@dapplion
Copy link
Member

dapplion commented Mar 6, 2025

Looks great!

@debjit-bw debjit-bw merged commit 9e1bfd6 into master Mar 6, 2025
7 checks passed
@debjit-bw debjit-bw deleted the cancun-blob-vectors branch March 6, 2025 10:31
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

Successfully merging this pull request may close these issues.

2 participants