Skip to content

op-e2e/actions: add L1 Osaka activation test#17522

Closed
DenseDenise wants to merge 8 commits intoethereum-optimism:developfrom
DenseDenise:FusakaTest
Closed

op-e2e/actions: add L1 Osaka activation test#17522
DenseDenise wants to merge 8 commits intoethereum-optimism:developfrom
DenseDenise:FusakaTest

Conversation

@DenseDenise
Copy link
Copy Markdown
Contributor

closes #17500

@DenseDenise DenseDenise requested review from a team as code owners September 18, 2025 18:15
@DenseDenise DenseDenise requested a review from Inphi September 18, 2025 18:15
@geoknee geoknee self-requested a review September 18, 2025 19:35
@geoknee geoknee added the H-l1-fusaka-defense Soft fork for being compatible with an L1 which has activated Fusaka label Sep 18, 2025
@geoknee
Copy link
Copy Markdown
Contributor

geoknee commented Sep 23, 2025

/ci authorize d591144

@DenseDenise DenseDenise requested a review from geoknee September 23, 2025 15:49
@DenseDenise
Copy link
Copy Markdown
Contributor Author

@geoknee Hi should be good now

@geoknee geoknee requested a review from a team as a code owner September 24, 2025 17:31
@geoknee geoknee changed the title op-e2e: add Fusaka activation test op-e2e/actions: add Fusaka activation test Sep 24, 2025
@geoknee geoknee changed the title op-e2e/actions: add Fusaka activation test op-e2e/actions: add L1 Osaka activation test Sep 24, 2025
@geoknee
Copy link
Copy Markdown
Contributor

geoknee commented Sep 24, 2025

/ci authorize ad87c6f

@DenseDenise
Copy link
Copy Markdown
Contributor Author

WOW thanks for the additional fixing, and the ci looks good @geoknee

@geoknee
Copy link
Copy Markdown
Contributor

geoknee commented Sep 25, 2025

/ci authorize 93271d9

Comment on lines +74 to +76
// Build L1 blocks to trigger Fusaka activation
// TODO in the current version of op-geth, the blob parameters don't change between Prague and Osaka.
// So this test is no useful until we can activate different blob parameters.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Highlighting this. We should be able to override the blob schedule for osaka and trigger a test failure (currently it passes).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Got it, should we create a issue or draft-PR for hint? or its okay and just keep it in mind?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm going to keep working on this branch (if that's ok with you) and try to get the test to fail with a custom blob schedule. Then we will get a review from another teammate and look to merge the PR (potentially with the test skipped).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This bug may be preventing us from installing a custom blob schedule ethereum-optimism/op-geth#685

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Got around that with a custom op-geth build here #17666

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I'm going to keep working on this branch (if that's ok with you) and try to get the test to fail with a custom blob schedule. Then we will get a review from another teammate and look to merge the PR (potentially with the test skipped).

Its 100% fine with me, sorry for slow respond, stuck in some personal task recently.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Got around that with a custom op-geth build here #17666

Looks like this has been merged, should I close this PR now?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yep I will close it. Thanks for kicking this off, you are attributed on the merged PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

H-l1-fusaka-defense Soft fork for being compatible with an L1 which has activated Fusaka

Projects

None yet

Development

Successfully merging this pull request may close these issues.

op-e2e/actions/proofs: Fusaka activation test

2 participants