Skip to content

feat(l1) Check withdrawals is not missing or null on v2 engine payloads. #1606

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

Merged
merged 7 commits into from
Jan 3, 2025

Conversation

fkrause98
Copy link
Contributor

Description
The difference between a v1 vs a v2 engine payload is the fact that v2 has a withdrawal field, this PR adds
a check on V2 fork & engine endpoints to check this field is not missing.

Closes #1605

@fkrause98 fkrause98 requested a review from a team as a code owner January 3, 2025 15:49
@fkrause98 fkrause98 changed the title feat(l1): Check withdrawals is not missing or null on v2 engine payloads. feat(l1) Check withdrawals is not missing or null on v2 engine payloads. Jan 3, 2025
Copy link
Contributor

@fmoletta fmoletta left a comment

Choose a reason for hiding this comment

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

🚀


match payload {
ExecutionPayload {
withdrawals: None, ..
Copy link
Contributor

@ElFantasma ElFantasma Jan 3, 2025

Choose a reason for hiding this comment

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

I don't think it is ok to check this here, as this code is run for both V1 and V2 🤔

@fkrause98 fkrause98 added this pull request to the merge queue Jan 3, 2025
Merged via the queue into main with commit c2c106f Jan 3, 2025
17 checks passed
@fkrause98 fkrause98 deleted the quick_fix_empty_withdrawals branch January 3, 2025 19:38
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.

Empty Withdrawals
5 participants