Bridge Radar

About Bridge Radar

Bridge Radar is a real-time bridge-health intelligence layer for Solana. It monitors every bridge with a Solana leg and exposes a single answer for users, dApps, and Foundation reviewers: is this bridge healthy right now?

Building an integration? Jump straight to Developer Tools for the SDK, REST/WebSocket API, embeddable widget, and on-chain oracle docs — this page covers what Bridge Radar is and how it's built.

What's live right now

A snapshot of what's real and running today, not aspirational — full detail in PROGRESS.md.

  • Bridge count unavailable right now — the registry API didn't respond.
  • 5 independent detectors feeding one weighted Health Score, real since 2026-08-01 (parity, outflow, signer, frontend, oracle).
  • Postgres + TimescaleDB in production — deployed on Render, real hypertables, not the SQLite dev default.
  • @bridge-radar/sdk@0.2.0 published on npm, including Finality Watch's getFinalityHealth().
  • REST + WebSocket API live and publicly reachable — see /developers for real curl examples.
  • On-chain oracle live on Solana Devnet — not mainnet yet, a deliberate real-funds decision not made.

Detectors

Five independent detectors, weighted and composed into one real-time score.

Lock / mint parity

Flags imbalance between origin-chain locks and Solana-side mints.

— weight

Outflow anomaly

Z-score over a rolling 30-day baseline catches unusual withdrawal volume.

— weight

Signer set drift

Watches guardian / DVN signer sets for unexpected rotations.

— weight

Frontend integrity

Hashes the live bundle to catch a hijacked front end before users do.

— weight

Oracle staleness

Checks that the price feeds a bridge depends on are still fresh.

— weight

Surfaces

Four real ways to consume Bridge Radar's data.

This dashboard — bridge list, comparisons, live event feed, personal activity.
REST + WebSocket API — free, open, no rate limiting currently enforced. Full docs, real curl examples, and an embeddable health badge on /developers.
On-chain Anchor program radar-oracle on Solana Devnet. Program ID, real account layout, and a PDA-read example on /developers.
Telegram + Discord + webhook alerter for anomaly events, plus a real Telegram bot (@bruhalert_bot) answering /start, /status, and /help by long-polling Telegram's getUpdates, plus a real automated weekly digest to every wallet linked via a real /start deep link. Both outbound alert delivery (Discord: real HTTP 204; Telegram: a real reply with a real message_id) and inbound bot commands are live-confirmed (2026-08-08).

Architecture

Rust cargo workspace for ingestion + scoring + attestation; pnpm workspace for API + dashboard; Anchor program for the on-chain oracle. Storage has two implementations behind the same interface on both sides — a Rust trait (SQLite / Postgres +Timescale) and a matching TypeScript interface in the API — with SQLite as the zero-setup dev default. Both backends are wired end-to-end and selected by DATABASE_URL: Postgres was verified live on 2026-08-08 (real indexed events, real computed health scores, real API responses, all off a running Timescale container). See ARCHITECTURE.md for the full breakdown.

Finality & Alpenglow

Solana is mid-transition from its current consensus (TowerBFT — a real, documented ~12.8s finality time) to a new consensus mechanism called Alpenglow, built around a new voting protocol called Votor, targeting ~150ms finality — roughly an 80-100x improvement. As of this writing, Alpenglow is not live on Solana mainnet: per Solana's own official upgrade page, it's being tested on a community cluster, with mainnet activation targeted for Q3 2026 — not yet confirmed live. Our own real observed data below is consistent with that: finality is still measuring in the ~12-second TowerBFT range, not the ~150ms Alpenglow target.

This matters for bridges specifically: any bridge with a hardcoded assumption about how long finality takes (e.g. "wait for N confirmations before minting on the destination chain") could see that assumption become stale once Alpenglow activates — either unnecessarily conservative, or, during a mixed-validator-set transition period, genuinely inconsistent. Finality Watch tracks this directly: it polls Solana's own documented getSlot RPC method at both confirmed and finalized commitment, records the real elapsed time between them, and flags a real anomaly only when an observation deviates 3x from a real trailing-hour baseline — relative to observed data, never a hardcoded assumption about which consensus version is currently active. See the live panel on the homepage, or GET /v1/network/finality for the real current numbers.

This is descriptive infrastructure context, not a claim that Bridge Radar detects or prevents any specific incident — same rule as every other signal on this site.

Open source, public good

MIT (code), CC-BY 4.0 (docs). No token. No equity.