-
Notifications
You must be signed in to change notification settings - Fork 782
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
Tests and misc updates for L2 withdrawals root #399
Conversation
f790bbd
to
d4998b0
Compare
8d2f6ac
to
823e2d9
Compare
d4998b0
to
f56b4ca
Compare
@protolambda In order to update the genesis handling when reading from superchain-registry: https://github.com/ethereum-optimism/op-geth/blob/optimism/core/superchain.go#L30-L46 , I will need to make a change to SCR to:
Going to work on that PR, so there's a TBD in |
This comment is not relevant. Because |
383b923
to
14164f9
Compare
823e2d9
to
91c2f21
Compare
de78b7b
to
8ff4f17
Compare
…thdrawals storage root
and update checks for l2 withdrawal root to be gated on Isthmus instead of Holocene
* To check whether Isthmus is active within NewBlock(), to appropriately handle withdrawalRoot, we need to pass in chainConfig. * Also added a Block RLP encode/decode test.
...of L2ToL1MessagePasser contract
ExecutableDataToBlockNoHash() needs to know whether Isthmus is active to determine the correct treatment of withdrawalsRoot
regenerating binding with go1.22 results in different unmarshalling code that fails existing tests
they were mainly to address vscode warnings, will move it to a separate PR
also removed usage of a 3rd party package and custom json tags in header.
* remove extra public api * change equality check for encode/decode roundtrip test * remove extra test which is covered already in fuzz test
* remove earlier hardcoded test added in block_test and revert other helper changes in block_test
6f1be75
to
700b1fd
Compare
to avoid import cycle and include all fuzz tests in a single place
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One change to make, then good to merge into the base branch. Will do another review there, and then with the monorepo side ready (don't want to block updates to latest op-geth due to breaking changes in block-construction signatures) we can merge it optimism
branch.
Targeted to be merged into: #383
for TODO work items in
op-geth
documented in: ethereum-optimism/optimism#12044