Skip to content

Set altair/bellatrix fork epochs to zero in BTEC gossip tests#5346

Open
jtraglia wants to merge 4 commits into
ethereum:masterfrom
jtraglia:btec-tests-fix
Open

Set altair/bellatrix fork epochs to zero in BTEC gossip tests#5346
jtraglia wants to merge 4 commits into
ethereum:masterfrom
jtraglia:btec-tests-fix

Conversation

@jtraglia

@jtraglia jtraglia commented Jun 8, 2026

Copy link
Copy Markdown
Member

In the bls_to_execution_change gossip validation tests, we set CAPELLA_FORK_EPOCH to a non-FAR_FUTURE_EPOCH value but leave the previous fork epochs as-is. This is confusing for implementations since the capella epoch is lower. Let's hardcode the previous fork epochs to zero.

@jtraglia jtraglia requested a review from nflaig June 8, 2026 16:02
@github-actions github-actions Bot added the testing CI, actions, tests, testing infra label Jun 8, 2026
{
"ALTAIR_FORK_EPOCH": 0,
"BELLATRIX_FORK_EPOCH": 0,
"CAPELLA_FORK_EPOCH": 0,

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this list can become pretty large for later forks, maybe we can have an ordered list of forks in the spec helpers and pick the highest fork for epoch (in this case 0)? That's more or less how we do it in lodestar, so you don't need to set earlier fork epochs explicitly

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah wait. You just made me realize this solution is incomplete. Are you suggesting we do this ("maybe we can have an ordered list of forks in the spec helpers") here in the specs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

testing CI, actions, tests, testing infra

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants