Firo Spark Sync Monitor

Where delivery stands

Live probes, Spark setHash health, durable history, and the public JSON API run on firostatus.com (always-on Node). Domain + HTTPS is live. Public MIT GitHub and the forum launch write-up stay pending until their URLs are posted (honesty for CFC). Scorecard / compare / diagnose already ship as early decision surfaces.

M1 acceptance checklist · live

CFC verifies product signals here plus the public gates. Prefer /api/ci spark_ok over green-count / early uptime %.

• …
  anonset_source = live

  Continuous always-on sweeps
• …
  Anon-set fields populated

  ms / MB / setHash on endpoints
• …
  /api/history recording

  sample_count + uptime %
• ok
  Own domain + HTTPS

  firostatus.com · always-on
• pend
  Public MIT GitHub

  README · methodology · CONTRIBUTING
• pend
  Forum launch write-up

  point at live URL + API curls

# Verifier cheatsheet (pass when live)
curl -sS ORIGIN/api/status | jq '{anonset_source, spark_ok:(.endpoints|map(select(.spark_consistent==false or (.anonset.consistent==false)))|length==0), sample_hint:(.endpoints|map(.anonset.ms)|map(select(.!=null))|length)}'
curl -sS ORIGIN/api/history?hours=24 | jq '{sample_count, fleet_pct_24h:.uptime.fleet_pct_24h, fleet_n:(.fleet|length)}'
curl -sS -f ORIGIN/api/ci | jq '{ok,spark_ok,max_lag,reasons}'

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

curl -sS 'ORIGIN/api/history?hours=24&limit=200' \
  | jq '{storage, db, sample_count, recording_since, uptime_note,
         uptime:.uptime.fleet_pct_24h,
         fleet_n:(.fleet|length), events:(.events.sethash|length)}'

Verifier curls also live in /docs/VERIFY.md. Prefer /api/ci spark_ok over early uptime %.

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 ORIGIN/api/status \
  | jq '[.endpoints[]
      | select(.spark_consistent == false
          or (.anonset != null and .anonset.consistent == false))
      | {name, lag, spark_consistent, anonset}]'

Example: spark_ok-first CI (recommended for Spark sync)

# Prefer spark_ok for Spark path health (tip lag / ops-yellow alone should not fail Spark CI)
curl -sS ORIGIN/api/ci | jq -e '.spark_ok == true'
# Strict tip+Spark gate (HTTP 503 when ok=false); notes explain yellow when ok=true:
curl -sS -f ORIGIN/api/ci | jq '{ok, spark_ok, max_lag, yellow, notes, reasons}'

ok requires spark_ok and max_lag ≤ 2. Mild lag alone can yield spark_ok: true with ok: false. Ops-yellow (RTT outlier, TLS <14d) can leave ok: true with non-empty notes. Use spark_ok for Spark-only gates; use -f + ok when tip freshness is also required.

Example: compact consensus poll

curl -sS ORIGIN/api/spark \
  | jq '{checked_at, spark_consensus, spark_sethash_consensus, summary, inconsistent}'

Pin / audit fleet setHash

# Consensus fingerprint
curl -sS ORIGIN/api/status | jq -r '.spark_sethash_consensus'
# Hosts that disagree
curl -sS ORIGIN/api/status | jq '[.endpoints[] | select(.anonset.consistent==false) | {id,name,setHash:.anonset.setHash}]'
# Divergence windows (always-on)
curl -sS 'ORIGIN/api/history?hours=168' | jq '.events.sethash[-5:]'

Embed kit

<!-- README / status page -->
![Spark fleet](ORIGIN/api/badge)

<!-- Deep links (path routes) -->
Overview: ORIGIN/overview
Backends: ORIGIN/backends
Spark health: ORIGIN/spark
Backend detail: ORIGIN/backend/mathnodes
Developers: ORIGIN/developers
Health JSON: ORIGIN/api/health

Registry ids and deep links also ship in /api/docs (registry, deep_links). Production origin: https://firostatus.com.

ElectrumX method → JSON field

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.

Not for

• In-wallet server picker / user-device RTT ranking
• Authoritative chain state (full nodes remain authoritative)
• Replacing Campfire / Stack / Electrum-Firo Spark sync itself

Start here: /api/docs · /api/ci · /api/status · /docs/VERIFY.md

What this is

FiroStatus (firostatus.com) 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 and TLS. The dashboard and the API show the same probe data. See Developers for integration details.

How to read the Overview in 30 seconds

1. Spark / tip gates — prefer /api/ci spark_ok (and ok) over green-count alone.
2. Durable charts + fleet at a glance — lag, fleet mix, anon-set cost, who agrees on setHash.
3. Scorecard / compare / diagnose — decision aids; early history can keep “Reliable?” false even when Spark PASSes.

What it checks (privacy safe)

• server.version: reachability, TLS, software version, cert expiry
• 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 / setHash consensus is the modal value across the fleet.

Status model

• green: reachable, ≤2 blocks behind, Spark id + setHash match fleet, TLS ≥14 days, probe RTT not a fleet outlier (band = max(5s, 2.5× median RTT))
• yellow: tip lag >2, RTT outlier, missing Spark id, coin id / setHash mismatch, or TLS <14d — see status_reasons. Yellow is ops; spark_ok can still PASS
• red: unreachable, more than 100 blocks behind, or TLS certificate expired

Production vs preview

Privacy statement

Probes are public Electrum methods only. No addresses, keys, transactions, wallet traffic, or personal data are collected. This board is ops health for the curated fleet — not a wallet and not a privacy guarantee for funds.

Scoring (short)

Reference tip = highest height ≥2 backends agree on. Uptime = strict green % (yellow/red count as down) — not a wallet-availability SLA; interpret with /api/ci. Anon-set ms/MB are from this monitor’s single region. Full write-up: /docs/METHODOLOGY.md · verifier curls: /docs/VERIFY.md.

Funding

FCS proposal by panagot — ~$2,000 (in FIRO), paid after verification. Funding page · Forum thread · Roadmap.

Public JSON: /api/status · /api/ci · /api/history · /api/health · /api/docs · badge: /api/badge