Namada · Shielded multichain infra

MASP Indexer Observatory

Live preview
Checking fleet…
connecting to MASP indexers
Neutral health monitoring for the public Namada MASP indexers that light & mobile wallets use for shielded sync — reachability, latency, and indexer freshness vs live RPC tip (the failure mode that can mask a drained shielded balance). Privacy-safe probes only. No keys, no addresses, no wallet data.
Namada · MASP · Shielded sync
Is your shielded sync reading a live indexer — or a stale one?
connecting…
Loading live data from the community MASP registry… first probe can take ~15–20s.

Indexer latency (now)?Round-trip to /api/v1/height. Reachable indexers first, then offline. Click a name for details.

reachable first · lower is better
Measuring indexer latency…

Fleet health over session?Stacked green/yellow/red counts per poll since you opened this page. History stays in your browser; durable multi-day history is a funded M1 deliverable.

—
fresh stale / slow (still answering) offline

Avg fleet latency?Average round-trip across reachable indexers, one point per poll this session.

per poll · ms
median now—
fastest / slowest—

Live MASP indexer status

≤50 blk · fresh stale / slow offline
IndexerOperator Height?Block height reported by /api/v1/height — the tip the wallet will sync shielded state to. Lag?Blocks behind the live RPC tip. Large lag = stale shielded state even if HTTP looks fine. Latency?Round-trip for /api/v1/height. Latency trend?This indexer's latency across polls this browser session. Status?green = fresh (≤50 blk). yellow = reachable but stale/slow. red = offline. Far-behind indexers stay yellow so they are not confused with dead hosts.
Probing community registry…
Shielded-sync freshness
The metric height-only monitors miss
Wallets run shielded-sync --with-indexer against these endpoints. An indexer can answer HTTP 200 yet serve a tip tens or hundreds of thousands of blocks behind — so a drained shielded balance still looks funded. We measure lag vs live RPC tip on every poll.

Lag behind RPC tip (blocks)

—
collecting…
Why this matters: in June 2026 a ~$600K shielded-pool drain went largely unnoticed while a stale MASP indexer kept showing balances that live RPC reported as zero. Generic uptime tools only check “is the host up?” — not “is the shielded tip current?”
Delivery plan
From prototype to production in one month
Funded via Namada Public Goods Funding / Fast Shielded Microgrants — $2,000 total, split 50/50. Work completes within a month. Everything MIT-licensed.
Now
Working prototype · live probes
Week 1
M1 · Production launch
Weeks 2–3
M2 · Durability & upstream
≤ 1 month
Complete & handed over
$2,000
Total ask
50 / 50 across milestones
~3 wks
Work duration
within 1 month of funding
MIT
License
fully open-source
Milestone 1 — Production launch · Week 1 · prepaid · incl. $200 hosting
$1,000
  • Public MIT GitHub repo (README, methodology, contribution guide)
  • Own domain + HTTPS + always-on VPS (12 months)
  • Production dashboard: reachability, height, lag vs RPC tip, latency, trends
  • Multi-source RPC reference tip + fleet-consensus fallback
  • Durable history → real 24h / 7d freshness uptime %
  • Public JSON API + Namada forum launch thread
Acceptance: live public URL; MIT repo; API returning real indexer data; continuous history recording.
Milestone 2 — Durability, alerting & upstream · Weeks 2–3 · on delivery
$1,000
  • Per-indexer detail pages + 24h / 7d / 30d charts
  • Staleness growth tracker (lag over time)
  • Opt-in alerting (Telegram / Discord / webhook) for red / stale indexers
  • Operator self-check (“add / verify your MASP indexer”)
  • Embeddable status badge for READMEs
  • At least 1 upstream PR / registry contribution + handover runbook
Acceptance: detail pages + charts live; alerting demonstrable; ≥1 upstream PR; handover published.

Budget · $2,000

paid in NAM / USDC equivalent at approval
M1 — production engineering + deploy$800
M1 — domain + VPS hosting (12 months)$200
M2 — detail pages, alerting, operator tooling, upstream$1,000
Total$2,000

What this is

A vendor-neutral freshness & uptime dashboard for the public Namada MASP indexers that light and mobile wallets depend on for shielded sync.

What it checks (privacy-safe only)

  • GET /api/v1/height — indexer tip height + latency
  • RPC /status (multi-source) — live chain tip for lag calculation
  • Freshness classification — green / yellow / red by lag thresholds

No viewing keys, spending keys, addresses, or wallet data is ever sent or stored. The reference tip is the highest height among responding RPC sources, with fleet-consensus fallback.

Status model

  • green — reachable, ≤50 blocks behind tip, <3s latency
  • yellow — reachable but stale or slow (including lag far beyond 5,000 — still answering)
  • red — unreachable / no height

Keeping “stale but answering” separate from “offline” is the point: wallets can finish sync against a host that looks healthy yet serves outdated shielded state.

Registry

Probes the full community MASP indexer list from the Luminara ecosystem registry (not a hand-picked subset).

Preview limits

This local preview polls live indexers and keeps session history in your browser. A funded build adds durable multi-day history, alerting, and always-on hosting.

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