Q token mark QUADPublic Accountability

Operational actors

Operator Guide

Validators, relayers, providers, and endpoint operators need public status labels, clean boundaries, and a route to the right surface without exposing private procedure.

This page is orientation. It does not publish keys, private topology, sensitive configuration, or private recovery steps.

Operator Experience Contract

Every operational role should know what it is responsible for, what state is visible, and which claims remain outside the role.

RoleWhat public pages should showWhat they must not imply
ValidatorChain id, public metadata, validator set posture, liveness labels, missed-signing visibility where public, readiness state, upgrade or governance slot, and slash-risk boundary.Validator coordination is not allocation, future privilege, guaranteed income, private governance, or custody authority.
RelayerRoute owner, source and destination surfaces, channel or route label where public, backlog, timeout, gas-float posture, stale state, and refund or recovery label.A relayer moving evidence does not force destination admission, Core worth, settlement, or redemption.
ProviderRegistration posture, accepted service class, quote or contract boundary, delivered receipt, challenge or dispute state, settlement record, and repair or refusal state.Provider capacity is not chain authority, validator status, raw compute earning, or automatic payment.
RPC / endpointEndpoint owner or class where public, freshness, degraded label, replacement status, fallback state, and what clients should downgrade.An endpoint answering requests is not proof of chain health, custody, admission, or final settlement by itself.
Emergency postureNormal, watch, degraded, paused, refused, quarantined, recovery, or restored labels with the owning surface named.A public emergency label should not reveal sensitive steps, private contacts, or exploitable timing.

Public Operator Map

Use the owning surface. Each actor has a different public job.

Core validatorsChain state, validator set posture, blocks, chain metadata, and Core readiness labels. Bridge relayer healthTransport observation, provider posture, backlog/gas labels, and activation boundaries when public. Infra providersAccepted work lanes, BIGHT-priced service posture, receipts, proof, challenge, repair, and public product labels. Liquid operatorsMotion, settlement-request posture, readiness, role separation, and market-closed labels. Main statusPublic state labels for live, test/rehearsal, planned, closed, stale, and not-yet-public surfaces. Integrator guideOwner, phase, proof, and boundary labels for downstream interfaces.

Validator Path

  • Read the owning chain metadata before using a wallet, explorer, or config file.
  • Confirm chain id, denom, address prefix, and public endpoint contract from the owning surface.
  • Track liveness, missed-signing, upgrade, governance, and readiness labels where published.
  • Keep keys, seed phrases, sentry layout, private endpoints, and recovery steps out of public reports.
  • Do not present coordination work as allocation, reward eligibility, or future control.

Relayer Path

  • Show the route owner, source surface, destination surface, route state, and timeout state.
  • Show gas-float posture as funded, low, paused, replenishing, exhausted, or not yet public.
  • Show backlog and freshness where route health affects action.
  • Show refund, surplus, recovery, refusal, or terminal state as separate labels.
  • Do not translate successful transport into destination admission or final settlement.

Provider Journey

Providers should see accepted work and settlement evidence without receiving open-ended authority.

1. Interest

Provider asks which public service class is open: storage, receipt memory, proof, retrieval, contract work, or route support.

2. Registration posture

Public label says open, waitlist, closed, paused, refused, or not yet public.

3. Accepted work

Work class, quote boundary, receipt expectation, proof class, and payload boundary are visible.

4. Delivery record

Receipt, verification path, challenge state, repair state, and refusal state are separated.

5. Settlement record

Actual denom, actual amount, receipt id, difference reason, and owner surface are shown where public.

Health Labels

Operational pages should make degraded states easy to read without exposing sensitive mechanics.

Normal

The route or actor is answering within its public contract.

Watch

The actor is still answering, but freshness, backlog, missed-signing, or gas posture needs attention.

Degraded

The route answers below normal; downstream interfaces should downgrade confidence and show last update time.

Paused

Action is intentionally stopped. Do not retry blindly or imply availability.

Refused

The owning surface rejected the action, route, provider state, or interpretation.

Quarantined

Delivered or observed material is held away from admitted state while review continues.

Recovery

The owning surface is restoring service or reconciling state. Private steps remain private.

Restored

The owning surface has returned to normal under its public contract.

Endpoint Replacement

  • Name the owning surface before replacing an endpoint in a UI or config.
  • Preserve chain id, endpoint class, freshness, and status labels.
  • Show whether replacement is candidate, active, fallback, degraded, or refused.
  • Do not publish private access details or sensitive routing details.
  • Do not treat a replacement endpoint as a stronger source of truth than the owning chain.

Emergency Boundary

  • Public pages may show paused, degraded, refused, quarantined, recovery, or restored state.
  • Public pages may link to the owning status page and receipt/proof route.
  • Public pages should not expose keys, private endpoints, private contacts, or sensitive timing.
  • Public pages should not create panic language, blame language, or unsupported financial claims.
  • Private recovery remains private until a public receipt or status update is intentionally published.

Must-Not-Infer List

Operational visibility proves less than people want it to prove. Keep the label narrow.

Node visible

Does not mean public sale, allocation, special privilege, or future reward eligibility.

Endpoint online

Does not mean the chain, route, custody, admission, or settlement is healthy by itself.

Provider listed

Does not mean endorsement, private authority, or automatic settlement.

Relayer active

Does not mean destination admission or final value movement.