v2.1: rolls out chained Merkle shreds to ~21% of mainnet slots (backport of #4431) #4435
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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
|
@mergify rebase |
(cherry picked from commit 9d09787)
✅ Branch has been successfully rebased |
behzadnouri
force-pushed
the
mergify/bp/v2.1/pr-4431
branch
from
e9489c8 to
de3f00e
Compare
behzadnouri
added
the
automerge
t-nelson
approved these changes
Jan 14, 2025
AshwinSekar
approved these changes
Jan 14, 2025
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.
Problem
Incrementally rolling out chained Merkle shreds to mainnet.
Summary of Changes
The commit rolls out chained Merkle shreds to ~21% of mainnet slots.
This is an automatic backport of pull request #4431 done by Mergify.