ls ./projects

project // Lightning · Infrastructure

Lightning Routing Ops Desk

Channel health, forwarding history, fee revenue, offline peers, and alerts for forced closes.

Advanced10 days
./submit./open-lessonls ./roadmap

Overview

Lightning operators need situational awareness. This dashboard turns node RPCs (and optional Prometheus exporters) into a live ops console.

An ops dashboard can drain funds if compromised. Least-privilege macaroons/RPC ACLs and auth in front of the UI are not optional for production.

Learning objectives

  • Aggregate channel, peer, and balance metrics from a Lightning node
  • Visualize routing revenue and liquidity health
  • Alert on offline peers, disabled channels, or stalled payments

Prerequisites

  • Lightning Retail POS
  • Liquidity
  • Routing

Required skills

LND or CLN metricsLiquidity opsAlert design

Part of the lightning roadmap.

Architecture diagram

UI ──► Ops API ──► LND/CLN RPC (+ Prometheus)

Requirements

  • Node health panel (alias, pubkey, synced, version)
  • Per-channel local/remote liquidity view
  • Peer connected/disconnected status
  • Forwarding / fee summary
  • Credentials stay server-side; UI is auth-protected

Stretch goals

  • Liquidity health score per channel (ratio + uptime + failures)
  • Prometheus metrics + alert rules
  • High unpaid HTLC warning
  • Historical forwarding charts

Recommended resources

Example repositories

Submission instructions

  • Docker-friendly demo README
  • Screenshots of liquidity and alert panels
  • Document least-privilege macaroon / ACL choices
  • Describe any health-score formula you invented