CELESTIA / LIVE OBSERVATIONS
Infrastructure,
in plain sight.
Live evidence from Celestia infrastructure.
01 / CONSENSUS
Know your upstream.
Check freshness and reported history span. Earliest/latest timestamps do not prove continuous block availability.
02 / OPERATOR TOOLS
A clean start on Mocha-5.
StakeUs read-only RPC & REST
Served by our own synced Mocha-5 consensus node. Recent history only; older queries may be unavailable. GET/HEAD requests, 5 requests/second per client, and 16 MiB maximum responses. No transaction broadcast, JSON-RPC POST, WebSocket, or SLA.
RPC status ↗ · REST node information ↗
RPC base: https://mocha.stakeus.xyz/rpc REST base: https://mocha.stakeus.xyz/rest
Pruned bridge command
For an installed v0.34.4-mocha binary. Choose a new, empty node store. Serving data does not require funding a transaction wallet.
Community upstream; no SLA. Keep admin RPC local and allow P2P TCP/UDP 2121. Initial sync takes time.Storage headroom calculator
A planning estimate using your measurements; this is not an official Fibre requirement calculator.
02 / FIBRE REGISTRY
Registered is the beginning.
Inspect transport reachability and the observations behind each result.
| Provider / consensus address | Latest TLS probe | Latency | Observed success | Samples |
|---|
THE MEASUREMENT CONTRACT
Useful signals. Clear limits.
01 / Source
The registry comes from the chain’s valaddr module through a named HTTPS consensus provider. Cross-provider block comparisons detect disagreement; they are not independent consensus verification.
02 / Probe
A successful TLS handshake means the endpoint was reachable from this observer. It does not verify the validator-endorsed certificate, gRPC readiness, available capacity, or a successful blob upload/download.
03 / History
Scans run every five minutes. Success percentages use actual samples in the last 24 hours, beginning when this observer started. They are not historical uptime claims or an SLA. History is retained for 14 days.