Firo Spark Sync Monitor

Past the prototype — what funding unlocks

The Vercel preview already proves the Spark signal. What’s left is always-on community infrastructure (continuous anon-set sweeps, durable history, own domain), then tools so wallet teams and operators can decide, not only watch a status wall.

Who this is for

Primary: wallet / SDK / mobile teams reviewing default Electrum hosts, and Electrumx operators watching Spark serve cost. Secondary: public transparency when Spark sync stalls. The dashboard and the JSON feed show the same probe data.

Where this sits in the Firo stack

Public JSON routes

Fields that matter in /api/status

Height only checks vs Spark path

Concrete jobs this API supports

1. CI or ops alert. Fail a job or page someone when any default host has spark_consistent === false or anonset.consistent === false.
2. Incident triage. Separate an app bug from an Electrum host that is serving a slow or divergent Spark set.
3. Default list review. Compare anonset.mb and anonset.ms across operators before publishing recommended backends (same setHash can still mean different bytes on the wire).
4. Docs transparency. Embed /api/badge or poll /api/ci from a status page.

Example: list Spark inconsistent hosts

curl -sS https://firo-spark-sync-monitor.vercel.app/api/status \
  | jq '[.endpoints[]
      | select(.spark_consistent == false
          or (.anonset != null and .anonset.consistent == false))
      | {name, lag, spark_consistent, anonset}]'

Example: CI gate with /api/ci

# Exit non zero when tip+Spark gate fails (HTTP 503)
curl -sS -f https://firo-spark-sync-monitor.vercel.app/api/ci \
  | jq '{ok, spark_ok, max_lag, reasons, green, yellow, red}'

ok requires spark_ok and max_lag ≤ 2. Mild lag alone can yield spark_ok: true with ok: false — see reasons. -f fails curl on HTTP 503. For Spark-only CI, assert spark_ok.

Example: compact consensus poll

curl -sS https://firo-spark-sync-monitor.vercel.app/api/spark \
  | jq '{checked_at, spark_consensus, spark_sethash_consensus, summary, inconsistent}'

Privacy and probe surface

Probes are public Electrum methods only: server.version, blockchain.headers.subscribe, spark.getsparklatestcoinid, and spark.getsparkanonymityset. No addresses, keys, transactions, or wallet traffic are sent or stored. CORS is open (*) so browser tools and dashboards can read the feed.

Start here: /api/docs · /api/status · /api/ci

What this is

A community health board and JSON feed for the public Firo Electrum backends that light and mobile wallets depend on. Flagship focus: Spark sync health (anon set fetch and setHash), plus tip lag. The dashboard and the API show the same data. See Developers for integration details.

How to read the Overview in 30 seconds

1. Spark sync signal — coins, MB, median fetch time, setHash agreement (the flagship).
2. CI / tip gates — spark_ok vs strict tip band (ok / max lag ≤2).
3. Fleet at a glance — which host is lagging or slow on anon-set; open a row for detail.

What it checks (privacy safe)

• server.version: reachability, TLS, software version
• blockchain.headers.subscribe: chain height and lag vs fleet reference tip
• spark.getsparklatestcoinid: active Spark coin group id, cross checked across backends
• spark.getsparkanonymityset: full anon set fetch time, size, and setHash consistency

No addresses, keys, transactions, or wallet data are sent or stored. The reference tip is the highest height at least two backends agree on. Spark consensus is the modal value across the fleet.

Status model

• green: reachable, ≤2 blocks behind, Spark id and setHash match fleet, probe RTT under 3s from this monitor
• yellow: lagging, slow RTT, missing Spark id, or Spark coin id / setHash mismatch — tip can be 0 blk with Spark id matching and still yellow on setHash ✗
• red: unreachable or more than 100 blocks behind

What funding unlocks

This preview already probes the live fleet and ships a Developers JSON guide. Funding moves it to always-on hosting with continuous anon-set sweeps, durable multi-day history, alerting, operator tooling, wallet scorecard / compare views, Spark incident log, deeper ElectrumX method docs, and a proper community domain. Details on the Roadmap.

Public JSON API: /api/status · field docs: /api/docs · badge: /api/badge