Skip to content

Schedule Fusaka on Ethereum mainnet #17734

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.

Sign up for GitHub

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

Jump to bottom
Merged
yperbasis merged 4 commits into from
Oct 31, 2025
Merged

Schedule Fusaka on Ethereum mainnet #17734

yperbasis merged 4 commits into from
Oct 31, 2025

Conversation

@yperbasis
Copy link
Member

@yperbasis yperbasis commented Oct 31, 2025

on December 3, 2025, 09:49:11pm UTC
BPO1 December 9, 2025, 02:21:11pm UTC
BPO2 January 7, 2026, 01:01:11am UTC

See https://notes.ethereum.org/@bbusa/fusaka-bpo-timeline, ethereum/consensus-specs#4689 and eth-clients/mainnet#11.

DefaultOsakaBlobConfig was removed because it's the same as DefaultPragueBlobConfig, so there's no need to set it explicitly.

@yperbasis yperbasis enabled auto-merge (squash) October 31, 2025 13:53
@yperbasis yperbasis merged commit cfb2e0a into main Oct 31, 2025
17 checks passed
@yperbasis yperbasis deleted the yperbasis/fusaka_on_mainnet branch October 31, 2025 14:14
yperbasis added a commit that referenced this pull request Oct 31, 2025
@yperbasis
Schedule Fusaka on Ethereum mainnet (#17734)
fd41b19 
on December 3, 2025, 09:49:11pm UTC
BPO1 December 9, 2025, 02:21:11pm UTC
BPO2 January 7, 2026, 01:01:11am UTC

See https://notes.ethereum.org/@bbusa/fusaka-bpo-timeline,
ethereum/consensus-specs#4689 and
eth-clients/mainnet#11.

`DefaultOsakaBlobConfig` was removed because it's the same as
`DefaultPragueBlobConfig`, so there's no need to set it explicitly.
@yperbasis yperbasis mentioned this pull request Oct 31, 2025
Merged
yperbasis added a commit that referenced this pull request Oct 31, 2025
@yperbasis
[r32] Schedule Fusaka on Ethereum mainnet (#17736)
63a01b5 
Cherry pick #17734 into `release/3.2`
mh0lt pushed a commit that referenced this pull request Nov 4, 2025
@yperbasis @mh0lt
Schedule Fusaka on Ethereum mainnet (#17734)
1e81c18 
on December 3, 2025, 09:49:11pm UTC
BPO1 December 9, 2025, 02:21:11pm UTC
BPO2 January 7, 2026, 01:01:11am UTC

See https://notes.ethereum.org/@bbusa/fusaka-bpo-timeline,
ethereum/consensus-specs#4689 and
eth-clients/mainnet#11.

`DefaultOsakaBlobConfig` was removed because it's the same as
`DefaultPragueBlobConfig`, so there's no need to set it explicitly.
@yperbasis yperbasis mentioned this pull request Nov 17, 2025
Merged
@somnergy
Copy link
Member

somnergy commented Nov 27, 2025

(Ignore if already addressed, I only just saw this)

@taratorio
Copy link
Member

taratorio commented Nov 28, 2025

(Ignore if already addressed, I only just saw this)

What do you mean by missing? The test checks that the last fork_id is 0x07c9462e (as per the doc) - that is BPO2 which comes after BPO1 which comes after Osaka. Calculating the last fork id depends on the values for the previous fork ids so can't arrive at the same values if the previous ones are not correct. So correctness is proven. But would not hurt to add explicit tests for bpo1 and Osaka fork ids before bpo2.

getConfig API work is finished yes.

@taratorio taratorio mentioned this pull request Nov 28, 2025
Merged
@taratorio
Copy link
Member

taratorio commented Nov 28, 2025

@somnergy #18091

@somnergy
Copy link
Member

somnergy commented Nov 28, 2025

What do you mean by missing? The test checks that the last fork_id is 0x07c9462e (as per the doc) - that is BPO2 which comes after BPO1 which comes after Osaka. Calculating the last fork id depends on the values for the previous fork ids

Yeah, it's a valid argument. It's also always better to be very explicit, even unnecessarily explicit, when it comes to config.
Thanks for the added intermediate checks.

taratorio added a commit that referenced this pull request Dec 1, 2025
@taratorio
p2p/forkid: add clarity with separate tests for osaka, bpo1, bpo2 for…
fec58bb 
…kids (#18091)

follow up to
#17734 (comment)
to make it a bit clearer
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@antonis19 antonis19 antonis19 approved these changes

@taratorio taratorio Awaiting requested review from taratorio taratorio is a code owner

@mh0lt mh0lt Awaiting requested review from mh0lt mh0lt is a code owner

@domiwei domiwei Awaiting requested review from domiwei domiwei is a code owner

@Giulio2002 Giulio2002 Awaiting requested review from Giulio2002 Giulio2002 is a code owner

@canepat canepat Awaiting requested review from canepat

@somnergy somnergy Awaiting requested review from somnergy

Assignees

No one assigned

Labels

FUSAKA

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@yperbasis @somnergy @taratorio @antonis19