Skip to content

FULL status card: distinguish "online but not pricing" oracles from inactive #34

Description

@BaumerCrypto

During mainnet launch (2026-07-17) I noticed the FULL status card's roster buckets don't cleanly account for all 35 operators.

The card has three buckets — software/version, stale, and inactive — but some oracles sit in a state none of them capture: fresh heartbeat and a valid version, but no live price feed and not signing.

At launch I saw GTO90 (16), Anthony (18), and medgboracle3452 (29) in exactly this state: online and version-compatible, counted correctly in the Fresh Heartbeats total, but absent from both the signing set and the inactive list. So the visible buckets don't sum to 35, and an operator who's online-but-not-pricing looks the same as one who never started.

This isn't a counting bug — the heartbeat total is accurate. It's a display gap: there's no bucket for "reachable but not contributing a price." I'd like a fourth category, something like "Online, no price feed (N)," listing these operators separately from truly inactive ones. It helps tell apart "started but price source stalled/misconfigured" from "never came online" — different operator problems needing different follow-up.

Refinement, not urgent. Deferred from launch day.

Version: oracle-network-status.sh v1.6.3

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions