web(d-web): V36 share-version crossing widget on embedded dashboard - #430
Merged
Conversation
Surfaces ratchet state at a glance from the existing /v36_status JSON (VOTING/ACTIVATED, vote %, work-weighted signaling, current->target share version) -- the same internal state debug.log uses, never a stub. Charter #3 (crossing visibility): makes the live V35->V36 cross legible to the operator directly in the dashboard, serving LTC prod #288. Static drop-in to the on-disk --dashboard-dir; card defaults hidden and renders only on a successful fetch, so it degrades gracefully on coins or nodes where /v36_status is empty. Non-consensus web layer only.
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.
Surfaces ratchet/crossing state at a glance in the embedded dashboard, consuming the existing real
/v36_statusJSON endpoint (no new backend; the data is already truthful, sourced from the same internal state debug.log uses).What it shows (new "Share-Version Crossing" stat-card):
Charter #3 (crossing visibility): makes the live V35->V36 cross legible to the operator directly in the dashboard — serves LTC prod #288 network-upgrade coordination.
Scope/safety:
--dashboard-dir(no rebuild needed to deploy)./v36_statusis empty._loadedrender gate, so it cannot stall the main stats render.