Skip to content

feat: support amsterdam time#1187

Closed
jihoonsong wants to merge 2 commits intoethpandaops:mainfrom
jihoonsong:amsterdam-time
Closed

feat: support amsterdam time#1187
jihoonsong wants to merge 2 commits intoethpandaops:mainfrom
jihoonsong:amsterdam-time

Conversation

@jihoonsong
Copy link
Copy Markdown
Contributor

This PR supports Amsterdam time. Features for Glamsterdam such as BALs could use this.

@barnabasbusa
Copy link
Copy Markdown
Collaborator

What exactly do we use this for?

@jihoonsong
Copy link
Copy Markdown
Contributor Author

It's used for the EL to figure out which fork it's in to determine if current engine API call is allowed. For example, BALs adds two new versions of engine APIs and Geth could use Amsterdam time to figure out if a call to those APIs is made after Gloas.

@barnabasbusa
Copy link
Copy Markdown
Collaborator

Amserdam Time is already in genesis.json and geth should be able to read it from that, assuming you set gloas_fork_epoch.

@jihoonsong
Copy link
Copy Markdown
Contributor Author

jihoonsong commented Sep 19, 2025

Damn, you're right. There was some different issue and I was confused with that. Sorry about this, closing this PR.

@jihoonsong jihoonsong closed this Sep 19, 2025
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