-
Notifications
You must be signed in to change notification settings - Fork 251
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
rolls out chained Merkle shreds to ~5% of mainnet slots #4019
rolls out chained Merkle shreds to ~5% of mainnet slots #4019
Conversation
2b661b3
to
9098f79
Compare
Backports to the stable branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. |
Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis. |
(cherry picked from commit d3fe8f8)
(cherry picked from commit d3fe8f8) # Conflicts: # turbine/src/broadcast_stage/standard_broadcast_run.rs
(cherry picked from commit d3fe8f8)
(cherry picked from commit d3fe8f8) # Conflicts: # turbine/src/broadcast_stage/standard_broadcast_run.rs
Problem
Rolling out chained Merkle shreds to testnet.
Summary of Changes
The commit rolls out chained Merkle shreds to ~5% of mainnet slots.