Activate peerDAS at Electra. #14734
Merged
Activate peerDAS at Electra. #14734
Conversation
This file contains 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
nalepae
force-pushed
the
peerdas-at-electra-fork
branch
2 times, most recently
from
40b9490 to
a45fed3
Compare
nalepae
requested review from
saolyn,
nisdas and
james-prysm
and removed request for
a team
nalepae
force-pushed
the
peerdas-at-electra-fork
branch
from
a45fed3 to
3917b28
Compare
nalepae
force-pushed
the
peerdas-at-electra-fork
branch
from
3917b28 to
3dc1dd6
Compare
nisdas
approved these changes
Dec 27, 2024
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.
This pull requests is a step before activating peerDAS at Fulu.
Before this pull request, Prysm was only able to manage peerDAS at genesis.
With this pull request, Prysm is able to start (for example) at Deneb, then fork at Electra, with the peerDAS feature activated at Electra.
The next step is to create the Fulu boilerplate, and to activate peerDAS at Fulu.
Tested on kurtosis:
For this last task, we had to de-activate some rate limiting for blobs, since with this rate limiting activated, Prysm was not able to sync at all.
Note: This issue is totally orthogonal to peerDAS, and is reproducible with the latest Prysm release, with Deneb (blobs) only.