Skip to content

Nethermind rolling expiry keeps 33_024 epochs - #2763

Draft
yorickdowne wants to merge 1 commit into
ethstaker:mainfrom
yorickdowne:nm-rolling-shorter
Draft

Nethermind rolling expiry keeps 33_024 epochs#2763
yorickdowne wants to merge 1 commit into
ethstaker:mainfrom
yorickdowne:nm-rolling-shorter

Conversation

@yorickdowne

Copy link
Copy Markdown
Collaborator

What I did

There appears to be rough consensus for 33_024 epochs for rolling expiry. Set Nethermind to that

In draft until NethermindEth/nethermind#12808 is in a release

@yorickdowne
yorickdowne marked this pull request as draft August 18, 2026 09:47
@kevaundray

Copy link
Copy Markdown

fyi In the next ACDC call, I added an agenda item to potentially revisit this and make it 8192 (roughly 2x the WSP and exactly 2x the blob retention period)

Not sure it has much relevance to this PR being merged or not since if we decide to go lower, it's "just" a constant change

@yorickdowne

Copy link
Copy Markdown
Collaborator Author

@kevaundray Interesting. Let's see how that goes! Execution layer clients appear to have converged on 33_024 for now. As you say, this can be changed again to 8_192 easily.

@kevaundray

Copy link
Copy Markdown

Yeah exactly, perhaps we do 8192 in H* alongside 8252!

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants