Skip to content

Conversation

@joshklop
Copy link
Contributor

@joshklop joshklop commented Sep 19, 2025

No description provided.

@joshklop joshklop requested a review from geoknee September 19, 2025 06:06
@geoknee
Copy link
Contributor

geoknee commented Sep 19, 2025

This is great, thanks @joshklop.

I ran the new test and watched the output. It's clear that op-geth does not support running an Osaka L1 yet.

I am working on an upstream merge here ethereum-optimism/op-geth#684, but that still won't allow us to run an Osaka L1. There is only unreleased upstream code which should let us do it.

@geoknee
Copy link
Contributor

geoknee commented Sep 19, 2025

Another observation from the logs: the batcher in this test environment apparently uses calldata, not blobs.

That will give us a false sense of security since we expect blob submission in prod, and for this to break with Fusaka. Can we force the batcher to use blobs at least in the new test (and probably all the others too)?

@joshklop joshklop force-pushed the joshklop/osaka-override branch 4 times, most recently from 4d064ab to b42ddb1 Compare September 24, 2025 19:34
@codecov
Copy link

codecov bot commented Sep 24, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.31%. Comparing base (59b7d71) to head (9f3c38c).
⚠️ Report is 11 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop   #17529      +/-   ##
===========================================
- Coverage    74.62%   74.31%   -0.32%     
===========================================
  Files          172      172              
  Lines        10955    10955              
===========================================
- Hits          8175     8141      -34     
- Misses        2634     2670      +36     
+ Partials       146      144       -2     
Flag Coverage Δ
cannon-go-tests-64 66.03% <ø> (-0.72%) ⬇️
contracts-bedrock-tests 80.72% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 5 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@joshklop joshklop force-pushed the joshklop/osaka-override branch 5 times, most recently from ed50480 to 2587788 Compare September 25, 2025 18:24
@joshklop joshklop marked this pull request as ready for review September 25, 2025 18:27
@joshklop joshklop requested review from a team as code owners September 25, 2025 18:27
@joshklop joshklop force-pushed the joshklop/osaka-override branch from 2587788 to 27d5316 Compare September 25, 2025 20:27
@joshklop joshklop changed the base branch from develop to joshklop/l1-subprocess September 25, 2025 20:28
@joshklop joshklop changed the title sysgo: add ability to configure osaka offset sysgo: add Osaka activation test Sep 25, 2025
@joshklop joshklop force-pushed the joshklop/l1-subprocess branch from 2936d73 to 8417a3d Compare September 25, 2025 20:41
@joshklop joshklop force-pushed the joshklop/osaka-override branch from 27d5316 to b6a99a3 Compare September 25, 2025 20:41
@joshklop joshklop force-pushed the joshklop/l1-subprocess branch from 8417a3d to e961c6c Compare September 26, 2025 18:02
@joshklop joshklop force-pushed the joshklop/osaka-override branch 2 times, most recently from ed4267c to 263e480 Compare September 26, 2025 18:46
@joshklop joshklop force-pushed the joshklop/l1-subprocess branch from e961c6c to 09f1a75 Compare September 26, 2025 19:11
@joshklop joshklop force-pushed the joshklop/osaka-override branch from 263e480 to f368540 Compare September 26, 2025 19:11
@geoknee geoknee added the H-l1-fusaka-defense Soft fork for being compatible with an L1 which has activated Fusaka label Sep 27, 2025
@joshklop joshklop force-pushed the joshklop/l1-subprocess branch from 09f1a75 to 94841db Compare September 29, 2025 21:43
@joshklop joshklop force-pushed the joshklop/osaka-override branch from 1107a12 to 9f3c38c Compare October 6, 2025 04:23
@joshklop
Copy link
Contributor Author

joshklop commented Oct 6, 2025

Probably easiest to review commit-by-commit.

Copy link
Contributor

@geoknee geoknee left a comment

Choose a reason for hiding this comment

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

LGTM

@joshklop
Copy link
Contributor Author

joshklop commented Oct 6, 2025

As discussed out-of-band: pre-emptively resolving all comments to allow for merging. Will address comments in follow-ups.

@joshklop joshklop added this pull request to the merge queue Oct 6, 2025
Merged via the queue into develop with commit 4e726c6 Oct 6, 2025
69 checks passed
@joshklop joshklop deleted the joshklop/osaka-override branch October 6, 2025 14:06
joshklop added a commit that referenced this pull request Oct 20, 2025
joshklop added a commit that referenced this pull request Oct 20, 2025
Before, we merely waited for the blob base fee to rise above 1 before assuming
that the blob parameters would have a visible impact on the fee.

Due to rounding, it is possible that different parameters still result in the same
base fee even above the minimum (either 1 or the reserve price set by EIP-7918).

Calculating the precise intersections between different blob base fee formulae, so
we opt for the simpler but maximally robust approach: calculate both the BPO1 base
fee and the Osaka base fee, and only proceed when they differ.

This resolves a nit on a previous PR that was merged due to time pressure:
#17529 (comment)
joshklop added a commit that referenced this pull request Oct 20, 2025
Before, we merely waited for the blob base fee to rise above 1 before assuming
that the blob parameters would have a visible impact on the fee.

Due to rounding, it is possible that different parameters still result in the same
base fee even above the minimum (either 1 or the reserve price set by EIP-7918).

Calculating the precise intersections between different blob base fee formulae, so
we opt for the simpler but maximally robust approach: calculate both the BPO1 base
fee and the Osaka base fee, and only proceed when they differ.

This resolves a nit on a previous PR that was merged due to time pressure:
#17529 (comment)
joshklop added a commit that referenced this pull request Oct 21, 2025
Before, we merely waited for the blob base fee to rise above 1 before assuming
that the blob parameters would have a visible impact on the fee.

Due to rounding, it is possible that different parameters still result in the same
base fee even above the minimum (either 1 or the reserve price set by EIP-7918).

Calculating the precise intersections between different blob base fee formulae is
complicated, so we opt for the simpler but maximally robust approach: calculate
both the BPO1 base fee and the Osaka base fee, and only proceed when they differ.

This resolves a nit on a previous PR that was merged due to time pressure:
#17529 (comment)
joshklop added a commit that referenced this pull request Oct 21, 2025
joshklop added a commit that referenced this pull request Oct 21, 2025
Before, we merely waited for the blob base fee to rise above 1 before assuming
that the blob parameters would have a visible impact on the fee.

Due to rounding, it is possible that different parameters still result in the same
base fee even above the minimum (either 1 or the reserve price set by EIP-7918).

Calculating the precise intersections between different blob base fee formulae is
complicated, so we opt for the simpler but maximally robust approach: calculate
both the BPO1 base fee and the Osaka base fee, and only proceed when they differ.

This resolves a nit on a previous PR that was merged due to time pressure:
#17529 (comment)
joshklop added a commit that referenced this pull request Oct 21, 2025
Before, we merely waited for the blob base fee to rise above 1 before assuming
that the blob parameters would have a visible impact on the fee.

Due to rounding, it is possible that different parameters still result in the same
base fee even above the minimum (either 1 or the reserve price set by EIP-7918).

Calculating the precise intersections between different blob base fee formulae is
complicated, so we opt for the simpler but maximally robust approach: calculate
both the BPO1 base fee and the Osaka base fee, and only proceed when they differ.

This resolves a nit on a previous PR that was merged due to time pressure:
#17529 (comment)
joshklop added a commit that referenced this pull request Oct 21, 2025
Before, we merely waited for the blob base fee to rise above 1 before assuming
that the blob parameters would have a visible impact on the fee.

Due to rounding, it is possible that different parameters still result in the same
base fee even above the minimum (either 1 or the reserve price set by EIP-7918).

Calculating the precise intersections between different blob base fee formulae is
complicated, so we opt for the simpler but maximally robust approach: calculate
both the BPO1 base fee and the Osaka base fee, and only proceed when they differ.

This resolves a nit on a previous PR that was merged due to time pressure:
#17529 (comment)
joshklop added a commit that referenced this pull request Oct 21, 2025
Before, we merely waited for the blob base fee to rise above 1 before assuming
that the blob parameters would have a visible impact on the fee.

Due to rounding, it is possible that different parameters still result in the same
base fee even above the minimum (either 1 or the reserve price set by EIP-7918).

Calculating the precise intersections between different blob base fee formulae is
complicated, so we opt for the simpler but maximally robust approach: calculate
both the BPO1 base fee and the Osaka base fee, and only proceed when they differ.

This resolves a nit on a previous PR that was merged due to time pressure:
#17529 (comment)
joshklop added a commit that referenced this pull request Oct 21, 2025
Before, we merely waited for the blob base fee to rise above 1 before assuming
that the blob parameters would have a visible impact on the fee.

Due to rounding, it is possible that different parameters still result in the same
base fee even above the minimum (either 1 or the reserve price set by EIP-7918).

Calculating the precise intersections between different blob base fee formulae is
complicated, so we opt for the simpler but maximally robust approach: calculate
both the BPO1 base fee and the Osaka base fee, and only proceed when they differ.

This resolves a nit on a previous PR that was merged due to time pressure:
#17529 (comment)
joshklop added a commit that referenced this pull request Oct 21, 2025
Before, we merely waited for the blob base fee to rise above 1 before assuming
that the blob parameters would have a visible impact on the fee.

Due to rounding, it is possible that different parameters still result in the same
base fee even above the minimum (either 1 or the reserve price set by EIP-7918).

Calculating the precise intersections between different blob base fee formulae is
complicated, so we opt for the simpler but maximally robust approach: calculate
both the BPO1 base fee and the Osaka base fee, and only proceed when they differ.

This resolves a nit on a previous PR that was merged due to time pressure:
#17529 (comment)
joshklop added a commit that referenced this pull request Oct 21, 2025
Before, we merely waited for the blob base fee to rise above 1 before assuming
that the blob parameters would have a visible impact on the fee.

Due to rounding, it is possible that different parameters still result in the same
base fee even above the minimum (either 1 or the reserve price set by EIP-7918).

Calculating the precise intersections between different blob base fee formulae is
complicated, so we opt for the simpler but maximally robust approach: calculate
both the BPO1 base fee and the Osaka base fee, and only proceed when they differ.

This resolves a nit on a previous PR that was merged due to time pressure:
#17529 (comment)
joshklop added a commit that referenced this pull request Oct 21, 2025
Before, we merely waited for the blob base fee to rise above 1 before assuming
that the blob parameters would have a visible impact on the fee.

Due to rounding, it is possible that different parameters still result in the same
base fee even above the minimum (either 1 or the reserve price set by EIP-7918).

Calculating the precise intersections between different blob base fee formulae is
complicated, so we opt for the simpler but maximally robust approach: calculate
both the BPO1 base fee and the Osaka base fee, and only proceed when they differ.

This resolves a nit on a previous PR that was merged due to time pressure:
#17529 (comment)
joshklop added a commit that referenced this pull request Oct 28, 2025
Before, we merely waited for the blob base fee to rise above 1 before assuming
that the blob parameters would have a visible impact on the fee.

Due to rounding, it is possible that different parameters still result in the same
base fee even above the minimum (either 1 or the reserve price set by EIP-7918).

Calculating the precise intersections between different blob base fee formulae is
complicated, so we opt for the simpler but maximally robust approach: calculate
both the BPO1 base fee and the Osaka base fee, and only proceed when they differ.

This resolves a nit on a previous PR that was merged due to time pressure:
#17529 (comment)
joshklop added a commit that referenced this pull request Oct 28, 2025
…17953)

Before, we merely waited for the blob base fee to rise above 1 before assuming
that the blob parameters would have a visible impact on the fee.

Due to rounding, it is possible that different parameters still result in the same
base fee even above the minimum (either 1 or the reserve price set by EIP-7918).

Calculating the precise intersections between different blob base fee formulae is
complicated, so we opt for the simpler but maximally robust approach: calculate
both the BPO1 base fee and the Osaka base fee, and only proceed when they differ.

This resolves a nit on a previous PR that was merged due to time pressure:
#17529 (comment)
github-merge-queue bot pushed a commit that referenced this pull request Oct 28, 2025
…st (#17944)

* split out helpers and initialization to a separate file

* fix comment in mise.toml

* rename osaka test

* rename to fusaka

* txplan: support non-cell proof blob txs

* also verify the l1 blob base fee in the l1 block contract

* optimization

#17529 (comment)

* op-acceptance-tests: harden the BPO blob base fee calculation test (#17953)

Before, we merely waited for the blob base fee to rise above 1 before assuming
that the blob parameters would have a visible impact on the fee.

Due to rounding, it is possible that different parameters still result in the same
base fee even above the minimum (either 1 or the reserve price set by EIP-7918).

Calculating the precise intersections between different blob base fee formulae is
complicated, so we opt for the simpler but maximally robust approach: calculate
both the BPO1 base fee and the Osaka base fee, and only proceed when they differ.

This resolves a nit on a previous PR that was merged due to time pressure:
#17529 (comment)

* add log
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.

3 participants