core(web): re-source /v36_status crossing counter from desired-version tally (not format flag) - #608
Merged
Conversation
…n tally
The /v36_status share_chain.{v35_shares,v36_shares,v36_percentage} fields
bucketed by the per-share FORMAT flag (overall_v36_shares). During the graded
g2 ratchet the .157 seed relays V35-FORMAT shares over p2p even while their
miners vote V36, so the format count reads 0 v36 straight through a real
crossing -- the founding-charter class of lie, in the exact fields the operator
curls to watch the vote climb.
Re-source from the desired-version data the AutoRatchet keys on
(get_desired_version_weights), the same swap #288 made for the ratchet mint
gate: the headline v36_percentage is now the work-weighted sampling signal --
the exact "N% old version" figure the journal logs and the integrator reads to
fire the crossing-event ping -- and v36_shares/v35_shares are the flat
desired-version vote counts over the chain. Both climb with the cross; neither
is the format-flag stub. Fenced to the .157 web layer; overall_v36_shares stays
available on the parent version_signaling object for the format breakdown.
Adds SAFE-ADDITIVE honesty-regression KAT: a snapshot whose FORMAT is 100% V35
yet whose desired-version tally is ~33% V36 (rig #1 flipped) asserts the
crossing counter tracks the vote (132 shares / 33.33%), never the frozen format
zero. Full suite 22/22 green.
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.
What
/v36_statusshare_chain.{v35_shares,v36_shares,v36_percentage}bucketed by the per-share FORMAT flag (overall_v36_shares). During the graded g2 ratchet, the.157seed relays V35-format shares over p2p even while their miners vote V36, so the format count reads 0 v36 straight through a real crossing — the founding-charter class of lie, in the exact fields the operator curls to watch the vote climb.This re-sources those three fields from the desired-version data the AutoRatchet keys on (
get_desired_version_weights) — the same swap #288 made for the ratchet mint gate:v36_percentage→ the work-weighted sampling signal (sampling_signaling) — the exact "N% old version" complement the.157journal logs and the integrator reads to fire the[crossing-event]ping.v36_shares/v35_shares→ the flat desired-version vote counts over the chain.Both climb with the cross; neither is the format-flag stub. Fenced to the
.157web layer (rest_v36_status);overall_v36_sharesstays available on the parentversion_signalingobject for anyone wanting the format breakdown. The dashboard crossing card already surfacedsampling_signaling/overall_v36_vote_pctcorrectly — this fixes the raw API contract the operator/integrator query directly.Test
SAFE-ADDITIVE honesty-regression KAT (
V36StatusShareChainTracksDesiredVersionNotFormatFlag): a sharechain snapshot whose FORMAT is 100% V35 yet whose desired-version tally is ~33% V36 (rig #1 flipped, others on V35) asserts the crossing counter tracks the vote (132 shares / 33.33%), never the frozen format 0. Guard pins that the format-flag source genuinely reads 0 for this snapshot, so a revert to the format tally is caught.test_web_honesty_regression22/22 green locally (built on workstation).Charter #3 (crossing visibility). Non-consensus web layer.