Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Activate engine APIs even when genesis timestamp of hard fork is set to 0 #8135

Open
daniellehrner opened this issue Jan 17, 2025 · 0 comments · May be fixed by #8136
Open

Activate engine APIs even when genesis timestamp of hard fork is set to 0 #8135

daniellehrner opened this issue Jan 17, 2025 · 0 comments · May be fixed by #8136
Assignees
Labels
bug Something isn't working

Comments

@daniellehrner
Copy link
Contributor

The following or similar genesis config are used on testnets or rollups:

{
  "config": {
    "chainId": 2151908,
    "homesteadBlock": 0,
    "eip150Block": 0,
    "eip155Block": 0,
    "eip158Block": 0,
    "byzantiumBlock": 0,
    "constantinopleBlock": 0,
    "petersburgBlock": 0,
    "istanbulBlock": 0,
    "muirGlacierBlock": 0,
    "berlinBlock": 0,
    "londonBlock": 0,
    "arrowGlacierBlock": 0,
    "grayGlacierBlock": 0,
    "mergeNetsplitBlock": 0,
    "shanghaiTime": 0,
    "cancunTime": 0,
    "bedrockBlock": 0,
    "regolithTime": 0,
    "canyonTime": 0,
    "ecotoneTime": 0,
    "fjordTime": 0,
    "graniteTime": 0,
    ...
}

Besu currently flattens those milestones, which leads to some engine API endpoints not being activated. See details in the following issue:

Consensys/op-besu#4

We need to make sure that those endpoints work as expected with those configurations

@daniellehrner daniellehrner self-assigned this Jan 17, 2025
@daniellehrner daniellehrner added the bug Something isn't working label Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant