Repository navigation
Schedule Sepolia Glamsterdam activation - #126
Merged
Merged
Conversation
This was referenced Sep 17, 2026
terencechain
approved these changes
Sep 17, 2026
nflaig
approved these changes
Sep 17, 2026
StefanBratanov
approved these changes
Sep 17, 2026
ilitteri
approved these changes
Sep 18, 2026
4 tasks
1 task
This was referenced Sep 21, 2026
MariusVanDerWijden
approved these changes
Sep 21, 2026
2 of 4 tasks
MegaRedHand
approved these changes
Sep 21, 2026
prestonvanloon
approved these changes
Sep 21, 2026
Member
|
@ralexstokes is this waiting on anything or is it ready to merge? |
ilitteri
added a commit
to zemse/ethrex
that referenced
this pull request
Sep 21, 2026
**Motivation** Glamsterdam (Gloas on the consensus layer, Amsterdam on the execution layer) has a date on Sepolia: epoch **353024**, timestamp **1791294816**, **2026-10-06 13:53:36 UTC**. Decided in [ethereum/pm#2205](ethereum/pm#2205) (merged 2026-09-15) and recorded in the EIP-7773 activation table by [ethereum/EIPs#12355](ethereum/EIPs#12355) (merged 2026-09-17). The client configuration is [eth-clients/sepolia#126](eth-clients/sepolia#126), still open at the time of writing but reflecting the merged decision. **Description** - `amsterdamTime: 1791294816` added to the Sepolia preset, after the Osaka and BPO times, exactly as eth-clients/sepolia#126 does in `metadata/genesis.json`. `1655733600 + 353024 * 32 * 12 = 1791294816`. - No blob-schedule change. Upstream leaves it unchanged, Amsterdam inherits the BPO2 parameters, and the preset carries no Amsterdam blob entry, the same shape as the Plataberget preset. - The EIP-2124 fork ID changes with the new scheduled fork: the Sepolia fork-ID test rows after BPO2 now advertise `next = 1791294816`, and a head at or past Amsterdam gets fork hash `0x6c1d9423` (CRC32 continued from BPO2's `0x268956b6` over the big-endian timestamp; the same method reproduces `0x268956b6` from BPO1's hash). The usual just-before/at pair was added for the new fork. - A test pins the activation timestamp on the parsed preset so it cannot drift silently. The Sepolia genesis-hash test is unaffected, since the chain config is not part of the genesis header. - The forks roadmap claimed Amsterdam timestamps were already wired into the Sepolia and Hoodi presets; neither was true. It now states the Sepolia schedule and that Hoodi and mainnet are still TBD upstream, which pm#2205 confirms. Hoodi is not scheduled here because pm#2205 leaves its date TBD. **How to Test** ```sh cargo test -p ethrex-config ``` Nine preset tests pass; `cargo test -p ethrex-common --lib fork_id` passes 8/8, including `test_sepolia_amsterdam_activation` and the unchanged `test_sepolia_genesis_block_hash`. **Checklist** - [ ] Updated `STORE_SCHEMA_VERSION` (crates/storage/lib.rs) if the PR includes breaking changes to the `Store` requiring a re-sync. (Not needed: no schema change.)
Sahil-4555
pushed a commit
to Sahil-4555/erigon
that referenced
this pull request
Sep 22, 2026
Schedule Glamsterdam on Sepolia for **6 October 2026, 13:53:36 UTC**, following [ethereum/pm#2205](ethereum/pm#2205). - Set Amsterdam to timestamp `1791294816`. - Set Caplin's Gloas epoch to `353024` and fork version to `0x90000076`, matching [eth-clients/sepolia#126](eth-clients/sepolia#126). - Update the existing Sepolia fork-ID cases before, at, and after activation; the Amsterdam fork hash is `0x6c1d9423`.
ralexstokes
marked this pull request as ready for review
September 22, 2026 15:39
prestonvanloon
pushed a commit
to OffchainLabs/prysm
that referenced
this pull request
Sep 22, 2026
Set GloasForkEpoch to 353024 (2026-10-06 13:53:36 UTC), matching eth-clients/sepolia#126 and the schedule from ethereum/pm#2205. The other Gloas values eth-clients#126 adds to config.yaml all match Prysm's mainnet defaults, which SepoliaConfig() inherits, so no Sepolia override is needed for them. The WORKSPACE sepolia_testnet pin is left alone until eth-clients#126 merges. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
pull Bot
pushed a commit
to wsnchristopher/prysm
that referenced
this pull request
Sep 22, 2026
**What type of PR is this?** > Other **What does this PR do? Why is it needed?** Set GloasForkEpoch to 353024 (2026-10-06 13:53:36 UTC), matching eth-clients/sepolia#126. Note that this PR is blocked until the upstream PR merges, as we need to bump the pin for `WORKSPACE`. (So we don't need a separate PR like [this](OffchainLabs#15733)) **Which issue(s) does this PR fix?** N/A **Other notes for review** **Acknowledgements** - [ ] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [ ] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [ ] I have added a description with sufficient context for reviewers to understand this PR. - [ ] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable). --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: Preston Van Loon <pvanloon@offchainlabs.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Schedule Sepolia's Glamsterdam upgrade (Gloas + Amsterdam) at epoch 353024, timestamp 1791294816 (October 6, 2026 at 13:53:36 UTC), following the merged schedule in ethereum/pm#2205 and the activation-table update in ethereum/EIPs#12355.
amsterdamTimein the Geth-style and Besu configurations.0x6ac4fd60).The Sepolia Gloas fork version
0x90000076matches Lighthouse's configuration. Additional Gloas values match consensus-specs; execution fields were checked against Besu's configuration parser and Nethermind's Sepolia chainspec.Validation:
1655733600 + 353024 * 32 * 12 = 1791294816, the UTC conversion, and hexadecimal timestamp.git diff --checkpassed.No client startup or live fork-transition test was run; validation covers configuration structure and agreement with upstream settings.