Skip to content

feat(tests): peerdas tracking issue #1301

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

Open
danceratopz opened this issue Mar 12, 2025 · 1 comment
Open

feat(tests): peerdas tracking issue #1301

danceratopz opened this issue Mar 12, 2025 · 1 comment
Assignees
Labels
fork:osaka Osaka hardfork scope:tests Scope: Changes EL client test cases in `./tests` tracker Tracking issue for projects with sub-tasks type:feat type: Feature

Comments

@danceratopz
Copy link
Member

danceratopz commented Mar 12, 2025

Tracking issue for the required testing coverage for the EL for PeerDAS

Please add/describe sub-tasks as they get scoped!

Resources

@danceratopz danceratopz added fork:osaka Osaka hardfork scope:tests Scope: Changes EL client test cases in `./tests` tracker Tracking issue for projects with sub-tasks type:feat type: Feature labels Mar 12, 2025
@danceratopz danceratopz pinned this issue Mar 12, 2025
@marioevz
Copy link
Member

@felix314159

After talking to @ralexstokes, the main issue is validating the EL receiving the blob tx and generating the correct proof.

This is the place where we tested this for Cancun: https://github.com/ethereum/hive/blob/master/simulators/ethereum/engine/suites/cancun/tests.go

I think we could, as a starting point, update these for PeerDAS, we have a blob transaction creator and a blob sender inside of these tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fork:osaka Osaka hardfork scope:tests Scope: Changes EL client test cases in `./tests` tracker Tracking issue for projects with sub-tasks type:feat type: Feature
Projects
None yet
Development

No branches or pull requests

3 participants