System status

Holds the spot websocket and writes live 24-hour tickers for the most liquid pairs as the venue sends them. The rest of the catalogue refreshes on a 60-second REST sweep even when everything is healthy — the socket carries the pairs people watch, the sweep carries the long tail.

When degraded — A socket silent for 45 seconds stops being trusted, and the sweep tightens to 15 seconds and carries every pair. On screen: spot prices step every 15 seconds instead of ticking continuously — current, but coarser, and the boards say so with a feed badge.

The same job for perpetuals, built differently because the venue’s futures ticker channel accepts a subscription and then delivers nothing — a measured behaviour, not an assumption. Perpetual prices are rebuilt from the live trade tape plus a REST 24-hour baseline, and the forming one-minute candle is folded from the same tape.

When degraded — Degraded looks the same as spot: the 15-second REST sweep carries every contract until the tape delivers again.

The last funding-and-liquidation pass skipped no contract for a stale mark price.

A second socket that opens depth, trade and candle channels for exactly the symbols open terminals are watching, and drops each one when its last watcher leaves. Idle is its healthy resting state — nothing subscribes until a terminal opens. The heartbeat reports what this socket has open, not proof it is delivering.

When degraded — When this path fails, an open terminal polls the venue directly: the order book refreshes every 3 seconds instead of ten times a second. Visibly coarser — and still current.

The servers rendering pages and relaying streams — including this one. It does not self-report, and does not need to: this reading arriving is the measurement. Were this tier down, you would be looking at an error page, not a status page.

When degraded — Its degraded mode is the fallback story below — with the worker’s cache empty or gone, every market read goes to the venue’s public REST API directly, request by request.

Scans its chain for transfers to issued deposit addresses and credits each one only once it is buried deep enough to trust — after re-reading the block at the deposit’s height, so a chain reorganisation orphans the record rather than paying it. With no address issued it idles, and idle is its healthy resting state.

The heartbeat reports it bound to chain id 56.

When degraded — Its chain endpoint stopped answering, or a scan step failed — which would otherwise look exactly like a chain with no deposits on it. Nothing is credited on a guess; the pass retries until its reads succeed.

Follows any payment already broadcast through to settlement, then starts approved ones — every transition behind an atomic claim, the signed transaction recorded before it is sent. It starts only when payouts are explicitly enabled, the faucet is closed and the configured signer is healthy. Every request reaches it only after one human approval. The pill names which refusal applies rather than reporting an idle it has not earned.

The heartbeat reports it bound to chain id 56.

When degraded — A payment already on the chain is being followed but a step is failing or waiting on an operator. Nothing is re-sent and nothing is released on the strength of an outage.