bch(node): align local predicate name v36 -> v36_active (cosmetic, version-gate consistency) - #301
Merged
Merged
Conversation
…ate consistency (no-op, cosmetic)
frstrtr
added a commit
that referenced
this pull request
Jun 23, 2026
…ate consistency (no-op, cosmetic) (#301) Co-authored-by: frstrtr <frstrtr@users.noreply.github.com>
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.
Cosmetic no-op rename of a local predicate in src/impl/bch/node.hpp (v36 -> v36_active) for naming consistency with the core::version_gate::is_v36_active SSOT.
Scope: src/impl/bch/node.hpp only, +2/-2. No v36 surface change, no behavior change — pure rename. Per-coin isolation invariant respected (single file, BCH-only). Single-coin smoke gate suffices.
NOT conformance-crossing work — this is code hygiene, independent of the bch-conformance LTC-soak fence. Merge operator-gated as always.