[consensus] Enable checkpoint batching and leader schedule change for mysticeti mainnet #18564
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
arun-koshy
force-pushed
the
ak/leader-schedule-mainnet
branch
from
4afe8d6 to
64908fa
Compare
mystenmark
reviewed
Jul 11, 2024
|
|
||
| // Enable checkpoint batching on mainnet. | ||
| cfg.checkpoint_summary_version_specific_data = Some(1); | ||
| cfg.min_checkpoint_interval_ms = Some(200); | ||
| } | ||
| 53 => { |
There was a problem hiding this comment.
since 52 was reverted from testnet branch, do we need to introduce 53 right now? Or should we collapse them?
There was a problem hiding this comment.
Yeah good point, 52 & 53 would get released together anyways so I guess there is no harm in collapsing them into 52.
mystenmark
approved these changes
Jul 11, 2024
arun-koshy
force-pushed
the
ak/leader-schedule-mainnet
branch
from
a9532d3 to
ba4911f
Compare
tx-tomcat
pushed a commit
to tx-tomcat/sui-network
that referenced
this pull request
Jul 29, 2024
… mysticeti mainnet (MystenLabs#18564) ## Description Enable features in protocol config (v52) for Mysticeti mainnet launch - Checkpoint batching - Leader Scoring & Schedule Change --- ## Release notes Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required. For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates. - [ X ] Protocol: v52 -- Enable checkpoint batching in mainnet. -- Enable Leader Scoring & Schedule Change for Mysticeti consensus on mainnet.
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.
Description
Enable features in protocol config (v52) for Mysticeti mainnet launch
Removed v53 and moved feature changes to v52
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.
-- Enable checkpoint batching in mainnet.
-- Enable Leader Scoring & Schedule Change for Mysticeti consensus on mainnet.