Lightning capacity: public channels do not reveal payment room
Public Lightning channel capacity is not a direct measure of how much a particular participant can pay or receive. Channel direction, balance allocation, route bottlenecks and unobserved channels matter. Research should label the public capacity series as a covered funding measure rather than a guaranteed payment-success measure.
Lightning Labs’ liquidity documentation explains the contextual and directional nature of liquidity. The worksheet uses a simplified route to illustrate the distinction. It does not claim that public network data exposes every channel balance or that a hypothetical route will execute.
Separate three questions
First ask which funding capacity is observed. Record announced channels, data source, observation time and duplicate-channel treatment. Public announcements describe a visible part of the network. Private or otherwise unobserved channels make that coverage incomplete.
Second ask about direction. A channel can hold value while most of its balance is on the opposite side from the desired payment direction. Total channel capacity does not reveal the amount available in each direction. Preserve unknown balances rather than assigning half of every channel to each participant as if observed.
Third ask about a complete route. Even when several channel balances are known in an authorized dataset, the route must have enough directional capacity at every hop. Additional constraints, fees, reservations and operating conditions may reduce feasibility. A topology map alone cannot supply all these inputs.
Hypothetical route bottleneck
Assume a fictional route A → B → C. Channel A-B has total capacity 1,000,000 satoshis, with 100,000 available from A toward B under this simplified example. Channel B-C has total capacity 800,000, with 500,000 available toward C.
| Channel | Total capacity | Assumed forward room |
|---|---|---|
| A-B | 1,000,000 sats | 100,000 sats |
| B-C | 800,000 sats | 500,000 sats |
| Route | Not an additive limit | At most 100,000 sats before other constraints |
Adding the two capacities gives 1,800,000 sats, but does not mean A can send that amount to C. The simplified forward bottleneck is the minimum of 100,000 and 500,000, not their sum. A proposed 200,000-sat payment fails this necessary condition on the specified route.
This does not prove the payment cannot succeed anywhere in the network. Another route or a supported multi-part arrangement might change the result. Conversely, passing the simplified minimum test is not sufficient to guarantee success after fees and other constraints. Every balance and route here is hypothetical.
Interpret capacity growth carefully
If public capacity rises, separate new observed channels, larger channels, closures and coverage revisions. A larger visible total may increase potential funding while leaving a particular receiver short of inbound room. The payment question needs its own direction, sender, receiver, timestamp and explicitly covered endpoint conditions.
Do not infer transaction volume from capacity. The same funds can support repeated payments and channel rebalancing. Conversely, a funded channel can be idle. Capacity is a stock under a coverage rule; payments are flows over an interval. There is no universal multiplier converting one into the other.
For a public memo, report observed capacity, known directional evidence, unknown balance coverage and the selected payment question separately. Avoid probing payments merely to fill gaps; published documentation and authorized records may be sufficient to describe the limitation.
Recheck after channel-state changes, source coverage changes or a different payment direction. The deliverable is a coverage-and-bottleneck analysis, not spot exchange depth, a customer census or a forecast of network payment throughput.
Use account-level balances only when they are legitimately available and clearly mark which side of the channel they describe. A balance observation can become stale after subsequent payments, so save its time rather than attaching it permanently to a public channel identifier. A successful small payment, if already recorded, demonstrates that outcome at that time; it does not reveal the maximum feasible payment size.
FAQ
Can public capacity be called spendable payment liquidity?
Only with direction, route and coverage qualifications. Total funding alone does not establish room for a particular payment.
Does one route’s bottleneck prove network-wide failure?
No. It describes the stated route under specified assumptions. Other routes, payment arrangements and current conditions need separate evidence.