Feat: Cancun EIPs #3
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…header validation for Cancun hardfork in Taiko
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's new
This PR activates Cancun hardfork for taiko Shasta hardfork. This PR is part of #217
Key changes:
parent_block_beacon_rootis alwaysNoneTaikoTxEnvelope, which doesn't include EIP4844 transaction, thus this type of transaction is just doesn't existnot_activatederror as before cancunTests used for checking consistency between block outputs of alethia-reth and nethermind clients
Changes in default deployed smartcontracts
Due to EIP-4788(Beacon block root in the EVM) is disabled in this PR, it means that alethia-reth won't call smartcontract containing list of parents consensus block roots. So EIP-4788 smartcontract for storing block roots is unneeded and should be removed