Lightning Channel Lifecycle
Daily breakdown of channel opens, cooperative closes, and force-closes on the Lightning Network. Reveals the rhythm of network expansion, maintenance, and stress events.
What is it?
This chart compares three independent flows: channel opens, cooperative closes, and force-closes. Each line represents its own channel count per day. Comparing them helps assess network expansion, renewal, and stress episodes. The precision of this distinction depends on the collection method described in the methodological context.
How to read
The three lines share the same scale in channels per day: gold for opens, blue for cooperative closes, and red for force-closes. Read each flow at its own height without adding them together. Compare the pace of opens with both types of closes and observe force-close spikes. The legend lets you isolate each series.
Key zones
The Lightning Network typically counts tens of thousands of public channels. A normal pace is a few dozen to a few hundred opens and closes per day. Days with more than 500 opens or closes warrant investigation - they often mark a major capacity reallocation or a stress event.
What to observe
Massive opening waves (>300/day for multiple days) often precede network growth periods. Closure waves correlated with L1 fee spikes indicate 'cleaning up' of unprofitable channels. The 30-day opens/closes ratio is an excellent trend indicator.
Historical context
The Lightning Network grew from a few hundred channels in 2018 to tens of thousands across cycles. The strongest opening waves coincided with El Salvador adoption (2021), Cash App integration (2022), and volume spikes of subsequent bull cycles. 📌 Methodological note 2026-05-18: from this date, Trinity uses a different methodological source for this metric. The real opens/closes breakdown (on-chain channel transaction parsing) is temporarily replaced by a proxy based on net channel count difference between daily snapshots (mempool /statistics/3y). This means recent values may no longer faithfully separate cooperative opens from force-closes - full reconstruction is planned for when the self-hosted Lightning indexer is ready. Pre/post-2026-05-18 absolute comparisons must be interpreted with this nuance in mind.
Expert notes
Data combines on-chain heuristics (P2WSH) for opens and timelocked script patterns for force-closes. Cooperative closes are estimated by subtraction (total P2WSH closes minus identified force-closes). This method introduces an error margin of about 20-25%, mainly on cooperatives.
Common mistakes to avoid
Channel count does not equal network health. A network with fewer but larger and better-connected channels is more efficient than one with many fragmented small channels. Look at total capacity in parallel.
Programmatic access
REST API
curl -sS \
'https://api.trinityinsights.io/api/v1/onchain/metrics/ln-channel-lifecycle/data?timeframe=90d' \
-H 'X-API-Key: $TRINITY_API_KEY'MCP server
{
"tool": "get_chart_value",
"metric_id": "ln-channel-lifecycle",
"timeframe": "1y"
}Required tier: pro. See the pricing grid for the tier list and the MCP documentation for multi-client configuration.
Related metrics
Institutional disclaimer
Trinity Insights is an educational and analytical tool. The metric above does not constitute investment advice. Trinity Insights is not a Crypto-Asset Service Provider (CASP) registered under MiCA Regulation (EU) 2023/1114. See the full disclaimer.