Status

Live health per subsystem. Any non-green pill means shares may be delayed or block templates may be stale — miners keep hashing, but a block found while degraded may not propagate cleanly.

Values refresh every 30 seconds. Last-known-good is shown if the aggregator can't reach the source; the freshness line at the bottom marks the page stale after 90 s.

Subsystems

bitcoind

Bitcoin Core (ECX alphanet branch, or testnet4 during scaffold). Serves block templates via RPC, tracks the tip, maintains peers.

enforcer

BIP-300/301 enforcer. Wraps bitcoind's getblocktemplate with drivechain-aware BMM logic. No-op during the testnet4 scaffold — drivechain rules do not apply to BTC testnet4.

ckpool

Con Kolivas's CKpool in solo mode. Fetches templates from the enforcer, distributes work to connected miners, submits found blocks back to bitcoind.

stratum

Stratum V1 listener on stratum.solofork.com:3333. Green means the port is accepting connections and CKpool is issuing work.

Network

Tip height

—

Difficulty

—

Peers

—

bitcoind's outbound + inbound peer count. Falling below 3 for more than a few minutes means the node may be partitioned.

Network hashrate

— H/s

Pool

Workers

—

— idle · — distinct addresses

Pool hashrate · 1h

— H/s

Share of network

—

Effort on current block

—

100% = at expected finding time · higher = overdue

Reading the pill colors

Green — OK. Subsystem is responding within expected timings. Nothing to do.
Amber — degraded. Subsystem responds but with delays, low peer count, or a stale tip. Keep mining; a block found now still counts, but expect a slightly higher stale-share rate. Check /stats for the rejected-share counter.
Red — down. Subsystem is unreachable, crashed, or has been failing for more than 60 s. Shares in flight will still be accepted once the subsystem recovers, but new templates are not being issued. If your backup pool is configured, the miner has already failed over. Email [email protected] if the red persists beyond a few minutes.

Machine-readable

Everything on this page is derived from a couple of JSON endpoints. CORS is open — poll them from anywhere.

/api/network.status — tip, difficulty, peers, and the per-subsystem ok / degraded / down flags. Refresh cadence 60 s server-side.
/api/pool.status — CKpool's own three-line JSON: worker counts, hashrates, share statistics. Refresh cadence ~10 s server-side.
/api/blocks.json — blocks found by this pool, most recent first.
/health — trivial 200 ok, for uptime pings.

loading…