A daily digest to provide snapshots on the overall network data. Check latest editions.
⚡ Biggest Channel Opened Today
Capacity: (5.0 BTC)
Between: LNBiG [Hub-1] ↔ cyberdyne.sh (maintenance)
Transaction: 974714x1801x1
Window: block 974,572–974,848 (since the previous edition)
Details:
- https://mempool.space/lightning/channel/1071709376874086401
- https://1ml.com/channel/1071709376874086401
✨ New Node Spotlight
Name: production2 - View profile
Capacity: (50.0M sats)
Transaction: 974719x485x1
💥 Biggest Channel Closed
Capacity (last known): (2.5 BTC)
Between: lndus0.zaphq.io ↔ Strike
Funding tx: 973860x1486x1
Closed since: 2026-11-05 (UTC)
Details:
- https://mempool.space/lightning/channel/1070770393923321857
- https://1ml.com/channel/1070770393923321857
📈 Network Snapshot
| # | Total[1] | Active[2] |
| Nodes | 12,497 (−55, -0.44%) | 13,482 (−1, -0.01%) |
| Channels | 32,112 (−723, -2.20%) | 33,527 (+54, +0.16%) |
| Capacity | 3215 BTC (−221 BTC, -6.43%) | 3258 BTC (+32 BTC, +1.00%) |
⭐ Today's featured node
wintermute (rank #451, 21.7M sats, 14 chans, —)
Centrality Bridge: Betweenness centrality rank #8: lies on many shortest payment paths between other nodes.
📅 See Yesterday's Biggest Channel
Sourced from bitcoindatalabs' weekly Lightning report — BDL's own census of the network, taken for the most recent completed week because their daily graph file is not current. The change shown is against the previous week's report, not against yesterday. Both columns crawl the same gossip network independently, so they differ and shouldn't be compared directly. ↩
Sourced from amboss.space: only nodes and channels Amboss observed as active (recently online or announcing). Updated daily. ↩
221 BTC capacity drop against 5 BTC opens tells the real story. 86% cooperative closes is healthy. What closure size triggers your alerting?
🥳🥳🥳
For anyone accepting Lightning invoices rather than running a routing node, the useful read of a big close like the 2.5 BTC Strike channel is narrower: does your own receive side still have inbound liquidity along paths payers actually use?
The aggregate capacity number can drop a lot without changing that, or it can stay flat while your single upstream channel goes away. The checks that protect an invoice are local: invoice expiry long enough for the payer, a reference in the description that matches your records, and marking the bill paid only when the invoice shows settled, not when the payer says they sent it. A failed or expired invoice is not a partial payment.