Refactor configuration to update epoch values for features and fixes#5058
Merged
Conversation
Frozen
force-pushed
the
feature/activate-features-devnet-2026.2
branch
from
b1eb1eb to
db4e50a
Compare
mur-me
approved these changes
Jun 24, 2026
|
Tick the box to add this pull request to the merge queue (same as
|
Collaborator
Author
|
@copilot resolve the merge conflicts in this pull request |
…res-devnet-2026.2 # Conflicts: # internal/params/config.go
Resolved the merge conflict in |
GheisMohammadi
approved these changes
Jun 29, 2026
This file contains hidden or 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
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 request updates the activation epochs for several protocol features in the
internal/params/config.gofile. Previously, these features were either set to zero or marked as "to be determined" (TBD); now, they are all set to activate at epoch 52050. This change helps coordinate the rollout of multiple protocol improvements at the same time.Protocol upgrade epoch alignment:
CXMerkleProofReplayFixEpoch,RejectShard0CrossLinkEpoch,DuplicateCrossLinkEpoch,ValidatorWrapperAddressBindEpoch,SlashExternalStakeDenomFixEpoch,RejectDuplicateSlashEvidenceEpoch, andSlashGroupOrderFixEpochto activate at epoch 52050, replacing previous placeholder values. [1] [2]