Skip to content

fix(spec-specs): read blob gas fields from any parent header - #3845

Open
AhmethanKalenderoglu wants to merge 1 commit into
ethereum:forks/bogotafrom
AhmethanKalenderoglu:fix/amsterdam-bpo2-parent-blob-gas
Open

AhmethanKalenderoglu wants to merge 1 commit into
ethereum:forks/bogotafrom
AhmethanKalenderoglu:fix/amsterdam-bpo2-parent-blob-gas

Conversation

@AhmethanKalenderoglu

Copy link
Copy Markdown
Contributor

Fixes #3840.

calculate_excess_blob_gas in amsterdam only read the blob gas fields if the parent was an amsterdam or bpo5 header, so with a bpo2 parent (BPO2ToAmsterdamAtTime15k) the excess blob gas was reset to 0. All the forks that can come before amsterdam have these fields, so the check is dropped. Same change in bogota to keep the two in sync.

Added a test with bpo2 and bpo5 parents, the bpo2 case fails without the fix.

@AhmethanKalenderoglu

Copy link
Copy Markdown
Contributor Author

@spencer-tb could you take a look when you get a chance? It's a follow-up to #3352 for the bpo2 → amsterdam case. CI needs approval to run.

This branch has not been deployed

No deployments
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.

Amsterdam may ignore BPO2 parent blob-gas fields at the fork boundary

1 participant