web(dashboard): relabel /local_stats DOA meter honestly (stale-shares != lost work) - #713
Merged
Merged
Conversation
The c2pool Hash Rate card labeled pool_stale_prop as "DOA+Orphan". At low share-difficulty that value is dominated by benign sharechain orphan churn (observed 0.959 on contabo LTC prod while true dead_hashrate = 0, reward = 100%), so operators misread it as ~100% lost work (DOA). Relabel it "Stale shares" and add truthful tooltips: the pool stale-share rate is share-count-based and does not reduce miner reward; the true lost-work signal is the hashrate-based local DOA meter (dead_hashrate/hashrate). Also clarify that share Efficiency is share-count based and orphan churn lowers it without cutting PPLNS payout. Label/tooltip only -- no computation change. Static drop-in (--dashboard-dir), reversible. Charter #1: a dashboard must never lie about prod health.
frstrtr
force-pushed
the
dash/local-stats-doa-relabel
branch
from
July 15, 2026 21:04
7719b1b to
db5e43e
Compare
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
Relabels the DOA/stale surface on the embedded dashboard so it stops reading as "~100% lost work" when the node is healthy.
The c2pool Hash Rate card labeled
global_stats.pool_stale_propas "DOA+Orphan". That value is the sharechain stale-share rate (orphan + dead shares, share-count based). At low share-difficulty it is dominated by benign orphan churn — observed 0.959 on contabo LTC prod while the truedead_hashratewas 0 and rewarded hashrate was 100% of actual. Operators read "DOA+Orphan: 95.9%" as catastrophic dead-on-arrival loss. It is not.Change (label/tooltip only — no computation change)
pool_stale: "DOA+Orphan" → "Stale shares", tooltip clarifies it is share-count based, expected-high at low vardiff, and does not reduce miner reward.local_doa(already hashrate-baseddead_hashrate/hashrate= true lost work): tooltip makes provenance explicit so it reads as the authoritative unrewarded-work signal.efficiency(share-count): tooltip clarifies orphan churn lowers share-efficiency without cutting PPLNS payout.Why this is the right layer
The underlying "sharechain dead-share count conflated with DOA" is the #467-class semantics issue, but at the
m_sharechain_stats_fnsource (consensus/sharechain owned). This PR is the web-layer honest relabel — reversible static drop-in served from--dashboard-dir, no rebuild, no binary cutover required. Charter #1: a dashboard must never lie about prod health.