Skip to content

Propose Glamsterdam activation times for Sepolia and Hoodi - #2205

Open
parithosh wants to merge 3 commits into
masterfrom
glamsterdam-testnet-timings
Open

Propose Glamsterdam activation times for Sepolia and Hoodi#2205
parithosh wants to merge 3 commits into
masterfrom
glamsterdam-testnet-timings

Conversation

@parithosh

@parithosh parithosh commented Aug 28, 2026

Copy link
Copy Markdown
Member

Proposes activation times for Glamsterdam (Gloas + Amsterdam) on the public testnets, for client team review.

Network Epoch Start slot Unix UTC
Sepolia 353024 11296768 1791294816 Tue, 06 Oct 2026, 13:53:36
Hoodi TBD TBD TBD TBD

The Sepolia value is epoch-aligned and consistent with the network's beacon genesis:

  • Sepolia: 1655733600 + 11296768 * 12 = 1791294816

Hoodi and mainnet timings are left TBD. Once agreed, the timings get scheduled in eth-clients/sepolia and eth-clients/hoodi and filled into the EIP-7773 activation table.

@parithosh

parithosh commented Sep 3, 2026

Copy link
Copy Markdown
Member Author

Alternate time proposal in case we want a later fork for Sepolia:

Network Epoch Start slot Unix UTC
Sepolia 353024 11296768 1791294816 Tue, 06 Oct 2026, 13:53:36

@dgusakov

dgusakov commented Sep 3, 2026

Copy link
Copy Markdown

If we move Sepolia, I suggest moving Hoodi as well. Just to have more time for testing and ensure we do not nuke Hoodi like we did with Holesky...

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants