Repository navigation
feat(sepolia): schedule gloas at epoch 353024 - #111
Conversation
Sepolia activates Glamsterdam at epoch 353024 (2026-10-06 13:53:36 UTC), per eth-clients/sepolia#126. Min client versions cover the Sepolia-ready CL releases shipped so far: prysm v7.2.0, lodestar v1.49.0, teku 26.9.1.
![redpandabot[bot]](https://avatars.githubusercontent.com/in/3749543?s=60&v=4){kind=small}
There was a problem hiding this comment.
Adds the Sepolia gloas fork at epoch 353024 to the static production config. Every claim checks out: the epoch matches eth-clients/sepolia's metadata config (GLOAS_FORK_EPOCH: 353024, no glamsterdam scheduled), the fork lands 2026-10-06T13:53:36Z per the genesis/slot math, and each listed minClientVersions release (prysm v7.2.0, lodestar v1.49.0, teku 26.9.1) bakes Sepolia gloas at 353024 into its network configs. Omitted clients genuinely have no Sepolia-ready release — Lighthouse v8.2.2's built-in Sepolia config still carries FAR_FUTURE_EPOCH for gloas. No blob-schedule changes were needed; upstream has no further BPO entries.
Reviewed 1 changed file(s) @ 0d1b180d — no blocking issues found.
"If debugging is the process of removing software bugs, then programming must be the process of putting them in." — Edsger Dijkstra
Adds the Sepolia Gloas fork (epoch 353024, 2026-10-06 13:53:36 UTC, per eth-clients/sepolia#126) so it shows up as an upcoming fork on lab's fork readiness page.
minClientVersionslists the Sepolia-ready CL releases published so far: prysm v7.2.0, lodestar v1.49.0, teku 26.9.1. Lighthouse, nimbus, grandine and tysm get added as their Sepolia releases land.Only
gloasis added (noglamsterdamalias): lab derives the combined name from its fork registry, and a second key would render a duplicate fork section.