Skip to content

Simplified validate_header func in post-merge forks#1135

Closed
Antrikshgwal wants to merge 9 commits intoethereum:forks/praguefrom
Antrikshgwal:master
Closed

Simplified validate_header func in post-merge forks#1135
Antrikshgwal wants to merge 9 commits intoethereum:forks/praguefrom
Antrikshgwal:master

Conversation

@Antrikshgwal
Copy link
Contributor

@Antrikshgwal Antrikshgwal commented Mar 3, 2025

Related to Issue #1133

How was it fixed?

Simplified the validate_header function in Cancun, shanghai and Paris forks in the forks.py file since they are the post-merge forks.
Added documentation in the function docstring clarifying that for post-merge forks, the parent header is always the last header in the chain.

Cute Animal Picture

image

enitrat and others added 9 commits January 25, 2025 13:35
* dev: change type of branch node subnodes

* Annotate tuple with 16

* add ellipsis to tuple

* explicit tuple

* use explicit 16-field tuple

* fmt

* remove Annotated import

* fix types

* Use assert_type alongside cast (#1)

* Import from typing_extensions instead of typing (#2)

---------

Co-authored-by: Sam Wilson <57262657+SamWilsn@users.noreply.github.com>
* dev: update storage trie type

* update type in state_db
* dev: stricter type for MessageCallOuput

* fix: build doc
- If ``trace`` is passed in the POST, turn on full trace in the T8N tool.

- Validate that ``output-basedir`` is also specified as EEST relies on a
  known location for the trace files. Raise a clarifying error if it is not
  specified.
@gurukamath
Copy link
Contributor

gurukamath commented Mar 4, 2025

Thanks for taking up the issue and for the PR. A couple of points here.

  • PR Refactor Environment #1131 re-factors the validate_header function a little bit. Perhaps making this PR on top of it (once Refactor Environment #1131 has been merged) is better
  • Would be nice to have this PR raised against the forks/prague branch as that is where most of the latest re-factoring updates are being merged. For context, forks/prague will be merged into master once Prague goes live on mainnet.

Let me know in case you have any other questions.

@gurukamath
Copy link
Contributor

#1131 has been merged. Could you re-base the PR on the latest forks/prague and raise the PR against that branch

@Antrikshgwal Antrikshgwal changed the base branch from master to forks/prague March 5, 2025 09:36
@Antrikshgwal
Copy link
Contributor Author

#1131 has been merged. Could you re-base the PR on the latest forks/prague and raise the PR against that branch

Hey @gurukamath !!
I re-based the PR. Do I still need to raise a PR against forks/prague?

@gurukamath
Copy link
Contributor

#1131 has been merged. Could you re-base the PR on the latest forks/prague and raise the PR against that branch

Hey @gurukamath !! I re-based the PR. Do I still need to raise a PR against forks/prague?

Yes. I see there are conflicts with forks/prague. Please rebase this to resolve.

@Antrikshgwal Antrikshgwal closed this by deleting the head repository Mar 19, 2025
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.

7 participants

Comments