[barnabasbusa]

Following #1505, which keeps blob throughput per second constant across the EIP-8198 slot duration change, this keeps gas per second constant too: when slot_duration_ms_heze differs from slot_duration_ms and Heze is not at genesis, a gas_limit_schedule entry is added at heze_fork_epoch with the preceding gas limit (the last entry before Heze, else gas_limit/genesis_gaslimit) scaled by the slot ratio, so shorter slots lower the gas limit and longer slots raise it at that same epoch (e.g. 200000000 at 6000ms → 133333333 at 4000ms, verified in the rendered GAS_LIMIT_SCHEDULE). Entries after Heze are kept as-is, an entry already at heze_fork_epoch disables the auto entry, and with an unchanged slot duration nothing changes.

[redpandabot]

Summary

Adds a gas-limit entry at heze_fork_epoch scaled by the slot-duration ratio, mirroring #1505's BPO scheduling. Logic, rounding, default-setting order, and README claims all check out; the only gap is that the auto-inserted entry skips the >= gloas_fork_epoch validation that user entries must pass, which surfaces on out-of-order fork configs.

Issues

• 🟡 src/package_io/input_parser.star:228 — Auto entry can land below gloas_fork_epoch, bypassing the schedule validation — see the thread on that line

---

_{Reviewed @ 5f079188
"In theory, there is no difference between theory and practice. In practice, there is." — attributed to Yogi Berra}