Skip to content

Add EIP 7594 fixtures#590

Merged
mratsim merged 1 commit intomasterfrom
eip-7594-fixtures
Mar 16, 2026
Merged

Add EIP 7594 fixtures#590
mratsim merged 1 commit intomasterfrom
eip-7594-fixtures

Conversation

@mratsim
Copy link
Owner

@mratsim mratsim commented Mar 16, 2026

This is a purely preparatory PR for PeerDAS support. No logic/code added, only over 22k lines of test vectors to avoid polluting the future main contribution.

Sources:

I explicitly downloaded the latest release which is from v1.6.0-beta0.

Summary by CodeRabbit

  • Documentation

    • Added README with Ethereum EIP-7594 test vector documentation and reference links.
  • Tests

    • Added comprehensive test data for EIP-7594 protocol verification scenarios including KZG proof validation, cell recovery, and batch processing with various edge cases (empty inputs, duplicate cells, invalid data, and valid scenarios).

@mratsim mratsim enabled auto-merge (squash) March 16, 2026 08:21
@coderabbitai
Copy link

coderabbitai bot commented Mar 16, 2026

📝 Walkthrough

Walkthrough

This pull request adds comprehensive test vectors and data files for Ethereum EIP-7594 FuLu PeerDAS protocol testing. The changes include a README documenting the test suite and numerous YAML data files containing test cases for KZG cell proof verification operations across multiple scenarios.

Changes

Cohort / File(s) Summary
Protocol Documentation
tests/protocol_ethereum_eip7594_fulu_peerdas/README.md
Adds protocol overview with links to test vectors, releases, reference implementation, and audit documentation.
compute_verify_cell_kzg_proof_batch_challenge Test Cases
tests/protocol_ethereum_eip7594_fulu_peerdas/compute_verify_cell_kzg_proof_batch_challenge/kzg-mainnet/*/data.yaml
Introduces 8 test data files covering scenarios: empty input, single/multiple cells, duplicate cells, non-sequential/max cell indices, and mixed commitment indices with detailed KZG commitment, coset evaluation, and proof vectors.
recover_cells_and_kzg_proofs Test Cases
tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/*/data.yaml
Adds test case for invalid scenario where all cells are missing with null output.
verify_cell_kzg_proof_batch Test Cases
tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/*/data.yaml
Adds 30+ test data files covering valid cases (multiple blobs, unsorted, regression, same cell multiple times, zero cells) and invalid cases (incorrect cell/commitment/proof, invalid cells, missing cell/commitment/proof, invalid cell index).

Estimated Code Review Effort

🎯 2 (Simple) | ⏱️ ~15 minutes

Poem

🐰 A warren of proofs, so shiny and new,
Test vectors arranged in every hue,
From valid to invalid, each case we explore,
EIP-7594 testing, there's always more!
Our cells are verified, our KZGs supreme,
PeerDAS data dreams!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Add EIP 7594 fixtures' directly and clearly describes the main change: addition of test fixtures for EIP-7594 protocol support.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch eip-7594-fixtures
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request integrates a substantial collection of test fixtures for EIP 7594, laying the groundwork for future PeerDAS support. The added data, primarily in YAML format, covers diverse test cases for KZG proof verification and cell recovery, ensuring robust validation for upcoming protocol changes. The focus is solely on providing essential test infrastructure.

Highlights

  • EIP 7594 Test Fixtures: Added a comprehensive set of test vectors for Ethereum Improvement Proposal (EIP) 7594, which is crucial for PeerDAS support.
  • Preparatory Work: This pull request is purely preparatory, focusing on providing necessary test data without introducing any new logic or code.
  • Extensive Test Coverage: Included over 22,000 lines of test vectors, covering various scenarios for KZG proof batch challenges and cell recovery.
  • External Sources: The test vectors were sourced from official Ethereum consensus-spec-tests releases and reference implementations, ensuring accuracy and reliability.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • tests/protocol_ethereum_eip7594_fulu_peerdas/README.md
    • Added a README file detailing the sources for the Ethereum Data Availability Sampling test vectors.
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_verify_cell_kzg_proof_batch_challenge/kzg-mainnet/
    • Added numerous YAML test data files for compute_verify_cell_kzg_proof_batch_challenge covering cases such as duplicate cells, empty inputs, maximum cell indices, mixed commitment indices, multiple cells with multiple blobs, multiple cells with a single blob, non-sequential indices, and single cells.
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/
    • Added YAML test data for recover_cells_and_kzg_proofs specifically for scenarios where all cells are missing.
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/
    • Added various YAML test data files for verify_cell_kzg_proof_batch covering incorrect cells, incorrect commitments, incorrect proofs, invalid cells (multiple cases), invalid cell indices, invalid commitments (multiple cases), missing cells, missing commitments, missing proofs, valid multiple blobs, valid unsorted inputs, valid same cell multiple times, and valid zero cells.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
tests/protocol_ethereum_eip7594_fulu_peerdas/README.md (1)

1-7: Good provenance documentation.

The README clearly documents the official Ethereum sources for these test vectors, which is valuable for traceability and future updates.

Consider adding a trailing newline at the end of the file (POSIX convention).

📝 Suggested improvement
   - Generator: https://github.com/ethereum/consensus-specs/tree/v1.7.0-alpha.3/tests/core/pyspec/eth_consensus_specs/test/fulu/kzg
   - Reference audited impl: https://github.com/ethereum/c-kzg-4844/tree/v2.1.7/tests
+
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@tests/protocol_ethereum_eip7594_fulu_peerdas/README.md` around lines 1 - 7,
The README.md for the Ethereum Data Availability Sampling test vectors is
missing a trailing newline; edit the README.md (the file containing the "#
Ethereum Data Availability Sampling test vectors" header) and ensure the file
ends with a single POSIX newline character so the file has a trailing newline at
EOF.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@tests/protocol_ethereum_eip7594_fulu_peerdas/README.md`:
- Around line 1-7: The README.md for the Ethereum Data Availability Sampling
test vectors is missing a trailing newline; edit the README.md (the file
containing the "# Ethereum Data Availability Sampling test vectors" header) and
ensure the file ends with a single POSIX newline character so the file has a
trailing newline at EOF.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1c352991-7818-4198-a2b7-0b382df85f52

📥 Commits

Reviewing files that changed from the base of the PR and between 17eb597 and 96ed31f.

📒 Files selected for processing (83)
  • tests/protocol_ethereum_eip7594_fulu_peerdas/README.md
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells/kzg-mainnet/compute_cells_case_valid_0/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells/kzg-mainnet/compute_cells_case_valid_1/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells/kzg-mainnet/compute_cells_case_valid_2/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells/kzg-mainnet/compute_cells_case_valid_3/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells/kzg-mainnet/compute_cells_case_valid_4/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells/kzg-mainnet/compute_cells_case_valid_5/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells/kzg-mainnet/compute_cells_case_valid_6/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells/kzg-mainnet/compute_cells_invalid_blob_0/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells/kzg-mainnet/compute_cells_invalid_blob_1/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells/kzg-mainnet/compute_cells_invalid_blob_2/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells/kzg-mainnet/compute_cells_invalid_blob_3/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells_and_kzg_proofs/kzg-mainnet/compute_cells_and_kzg_proofs_case_invalid_blob_0/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells_and_kzg_proofs/kzg-mainnet/compute_cells_and_kzg_proofs_case_invalid_blob_1/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells_and_kzg_proofs/kzg-mainnet/compute_cells_and_kzg_proofs_case_invalid_blob_2/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells_and_kzg_proofs/kzg-mainnet/compute_cells_and_kzg_proofs_case_invalid_blob_3/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells_and_kzg_proofs/kzg-mainnet/compute_cells_and_kzg_proofs_case_valid_0/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells_and_kzg_proofs/kzg-mainnet/compute_cells_and_kzg_proofs_case_valid_1/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells_and_kzg_proofs/kzg-mainnet/compute_cells_and_kzg_proofs_case_valid_2/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells_and_kzg_proofs/kzg-mainnet/compute_cells_and_kzg_proofs_case_valid_3/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells_and_kzg_proofs/kzg-mainnet/compute_cells_and_kzg_proofs_case_valid_4/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells_and_kzg_proofs/kzg-mainnet/compute_cells_and_kzg_proofs_case_valid_5/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_cells_and_kzg_proofs/kzg-mainnet/compute_cells_and_kzg_proofs_case_valid_6/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_verify_cell_kzg_proof_batch_challenge/kzg-mainnet/compute_verify_cell_kzg_proof_batch_challenge_case_all_cells/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_verify_cell_kzg_proof_batch_challenge/kzg-mainnet/compute_verify_cell_kzg_proof_batch_challenge_case_duplicate_cells/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_verify_cell_kzg_proof_batch_challenge/kzg-mainnet/compute_verify_cell_kzg_proof_batch_challenge_case_empty/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_verify_cell_kzg_proof_batch_challenge/kzg-mainnet/compute_verify_cell_kzg_proof_batch_challenge_case_many_cells/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_verify_cell_kzg_proof_batch_challenge/kzg-mainnet/compute_verify_cell_kzg_proof_batch_challenge_case_max_cell_indices/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_verify_cell_kzg_proof_batch_challenge/kzg-mainnet/compute_verify_cell_kzg_proof_batch_challenge_case_mixed_commitment_indices/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_verify_cell_kzg_proof_batch_challenge/kzg-mainnet/compute_verify_cell_kzg_proof_batch_challenge_case_multiple_cells_multiple_blobs/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_verify_cell_kzg_proof_batch_challenge/kzg-mainnet/compute_verify_cell_kzg_proof_batch_challenge_case_multiple_cells_single_blob/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_verify_cell_kzg_proof_batch_challenge/kzg-mainnet/compute_verify_cell_kzg_proof_batch_challenge_case_non_sequential_indices/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/compute_verify_cell_kzg_proof_batch_challenge/kzg-mainnet/compute_verify_cell_kzg_proof_batch_challenge_case_single_cell/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/recover_cells_and_kzg_proofs_case_invalid_all_cells_are_missing/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/recover_cells_and_kzg_proofs_case_invalid_cell_0/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/recover_cells_and_kzg_proofs_case_invalid_cell_1/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/recover_cells_and_kzg_proofs_case_invalid_cell_2/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/recover_cells_and_kzg_proofs_case_invalid_cell_3/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/recover_cells_and_kzg_proofs_case_invalid_cell_index/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/recover_cells_and_kzg_proofs_case_invalid_duplicate_cell_index/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/recover_cells_and_kzg_proofs_case_invalid_more_cell_indices_than_cells/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/recover_cells_and_kzg_proofs_case_invalid_more_cells_than_cell_indices/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/recover_cells_and_kzg_proofs_case_invalid_more_cells_than_cells_per_ext_blob/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/recover_cells_and_kzg_proofs_case_invalid_more_than_half_missing/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/recover_cells_and_kzg_proofs_case_invalid_shuffled_half_missing/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/recover_cells_and_kzg_proofs_case_invalid_shuffled_no_missing/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/recover_cells_and_kzg_proofs_case_invalid_shuffled_one_missing/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/recover_cells_and_kzg_proofs_case_valid_half_missing_every_other_cell/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/recover_cells_and_kzg_proofs_case_valid_half_missing_first_half/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/recover_cells_and_kzg_proofs_case_valid_half_missing_second_half/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/recover_cells_and_kzg_proofs/kzg-mainnet/recover_cells_and_kzg_proofs_case_valid_no_missing/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_incorrect_cell/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_incorrect_commitment/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_incorrect_proof/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_invalid_cell_0/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_invalid_cell_1/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_invalid_cell_2/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_invalid_cell_3/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_invalid_cell_index/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_invalid_commitment_0/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_invalid_commitment_1/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_invalid_commitment_2/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_invalid_commitment_3/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_invalid_missing_cell/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_invalid_missing_cell_index/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_invalid_missing_commitment/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_invalid_missing_proof/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_invalid_proof_0/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_invalid_proof_1/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_invalid_proof_2/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_invalid_proof_3/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_valid_0/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_valid_1/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_valid_2/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_valid_3/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_valid_4/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_valid_5/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_valid_6/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_valid_multiple_blobs/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_valid_not_sorted/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_valid_regression1/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_valid_same_cell_multiple_times/data.yaml
  • tests/protocol_ethereum_eip7594_fulu_peerdas/verify_cell_kzg_proof_batch/kzg-mainnet/verify_cell_kzg_proof_batch_case_valid_zero_cells/data.yaml

@mratsim mratsim disabled auto-merge March 16, 2026 08:26
@mratsim mratsim merged commit 024534f into master Mar 16, 2026
17 checks passed
@mratsim mratsim deleted the eip-7594-fixtures branch March 16, 2026 08:27
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a comprehensive set of EIP 7594 test fixtures, primarily consisting of YAML files containing various test vectors for PeerDAS support. A README.md file has also been added to provide context for these new test vectors. The changes are purely preparatory, adding no new logic or code, which aligns with the PR's stated objective to avoid polluting future main contributions. No issues of medium, high, or critical severity were identified in the added test data or the README file.

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.

1 participant