Conversation
CHAIN_VERSION 4.1.1 -> 4.1.2 so validators running the #176 rules are distinguishable on chain from 4.1.1 before HF15; hardfork_version masks the patch component, so the HF15 hardfork version and date stay unchanged.
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
1 participant
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.
#176 changes HF15 consensus rules relative to 4.1.1. Bumping
CHAIN_VERSIONto 4.1.2 lets operators and the network tell the two builds apart viarunning_versionbefore HF15 (2026-10-05 00:00 UTC).hardfork_versionmasks the patch component, so the HF15 hardfork version and activation time are unchanged. No schema change (#176 keeps the storage layout), so 4.1.1 → 4.1.2 does not wipe shared memory.🤖 Generated with Claude Code