From 57452a69be18baeaec9c4928fc4d4b8a6b2b3274 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tom=C3=A1s=20Gr=C3=BCner?=
 <47506558+MegaRedHand@users.noreply.github.com>
Date: Thu, 22 Oct 2026 11:49:55 -0300
Subject: [PATCH] chore(beacon): unschedule Hoodi Glamsterdam

eth-clients/hoodi#33 calls off the Gloas activation planned for epoch
132352 (2026-10-26 17:42:48 UTC): GLOAS_FORK_EPOCH goes back to far
future and the Gloas-epoch GAS_LIMIT_SCHEDULE entry is removed. The
built-in Hoodi config is eth-clients' file byte for byte, so it follows.

A gloas build still carrying the old schedule would fork off Hoodi at
that epoch. Its existing directories resume on the new file, since both
the old and the new Gloas epoch are ahead of anything processed, which
first_config_difference accepts since #677.
---
 bin/ethlambda/assets/hoodi/config.yaml | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/bin/ethlambda/assets/hoodi/config.yaml b/bin/ethlambda/assets/hoodi/config.yaml
index 72149b8d5..092ab4eda 100644
--- a/bin/ethlambda/assets/hoodi/config.yaml
+++ b/bin/ethlambda/assets/hoodi/config.yaml
@@ -46,7 +46,7 @@ FULU_FORK_EPOCH: 50688
 
 # Gloas
 GLOAS_FORK_VERSION: 0x80000910
-GLOAS_FORK_EPOCH: 132352
+GLOAS_FORK_EPOCH: 18446744073709551615
 
 # Time parameters
 # ---------------------------------------------------------------
@@ -215,10 +215,3 @@ BLOB_SCHEDULE:
     MAX_BLOBS_PER_BLOCK: 15
   - EPOCH: 54016
     MAX_BLOBS_PER_BLOCK: 21
-
-# Gas limit scheduling
-# ---------------------------------------------------------------
-
-GAS_LIMIT_SCHEDULE:
-  - EPOCH: 132352
-    GAS_LIMIT: 200000000