Monitoring

Current implementation, supported use and explicit qualification limits.

Experimental Feature

This feature is experimental and may change significantly in future versions.

Current release status

Public document hashing and exact integer aggregation are live with signed results. Native consensus, mining, issuance, COMPUTE payments and rewards are inactive. Independent operation is not yet demonstrated.

What can be observed

HTTP gateway reachability and client round-trip time are limited observations. Check actual job completion, policy/signatures, source identity and known error states. They do not establish worker uptime, global validator count or consensus health.

Native operator qualification

On consenting off-mainnet hosts, collect accepted work, resource throughput, independently validated history, peer/WAN measurements, restart/restore results and actual cost/resource commitments. Keep sensitive logs private; share only public signed/redacted evidence.

Safety

Local financial acceptance must stop on source/account drift, conflicting views, corruption/capacity or failure of the agreed resource/peer assumptions. No founder global override or automatic refunds are provided.

Observe without inventing telemetry

A gateway request has a time and round trip. That measurement is useful, but it is not global peer latency, validator uptime or consensus health.

BoundaryImplementation / evidenceMeaning
Gateway observationActual health/policy response + browser timestampAvailability of that request only
Workload observationActual job ID and signed resultNo fabricated throughput or global daily total
Configured host metadataKnown Seed/Gamma recordsNot independently measured online operators
Independent resource evidenceConsenting hosts / own keys / WAN tracesNot yet supplied by local identities or containers

Practical procedure

  1. 1Record source, timestamp, scope and actual response.
  2. 2Separate configured addresses from measured reachability.
  3. 3Retain errors and missing measurements as unavailable.
  4. 4For outside qualification, measure resource throughput, propagation, recovery and actual costs.
Technical reference · scope is explicit
Observation = source + time + actual measurement + limitation
Gateway RTT ≠ validator latency
Signing keys ≠ independently controlled operators
Historical height ≠ advancing production consensus

Limits and failure cases

  • No invented uptime percentage, eight-region map, 47-peer total or confidence score.
  • A resource benchmark is not a guaranteed attacker-cost lower bound.
  • No arbitrary outside-operator count proves founder-independent security.