A Practical Guide to Opening Lightning Channels and Managing Liquidity
A channel management guide for anyone running their own Lightning node. Covers the concrete steps and numbers behind opening channels, acquiring inbound capacity, and optimizing routing revenue.
Many people have installed a Lightning wallet and made a payment. Far fewer take the next step: running their own node and managing channels directly. The barrier between those two stages almost always comes down to one topic - how to handle liquidity.
This article assumes the reader is already running a full node such as LND or Core Lightning, or plans to do so soon. The focus is less on conceptual explanation and more on the practical choices you encounter during real operation.
The Two Directions of a Channel: Outbound and Inbound Capacity
A Lightning channel is a structure in which two parties lock bitcoin into a multisig UTXO and exchange balances within it. When you open a channel first, you start with only your own bitcoin. That entire amount is your outbound capacity. The counterparty's balance is zero, so your inbound capacity - the amount you can receive - is also zero.
A payment is the act of moving a balance from one side to the other. Every time you send a payment, your outbound capacity decreases and your inbound capacity increases. Conversely, when you receive a payment, your inbound capacity decreases and your outbound capacity increases.
This asymmetry is the first wall beginners run into. You cannot receive payments over a channel you opened yourself. To receive your first Lightning payment, you must acquire inbound capacity beforehand.
Three Ways to Acquire Inbound Capacity
1) Buy an inbound channel
Services such as Lightning Pool, LNBIG, and Amboss Magma sell channels where the counterparty provides the funds. Typically, securing 1,000,000 sat of inbound capacity for one month costs a fee in the range of 20,000 to 50,000 sat. This is the fastest and most predictable method.
2) Use a swap service
Services like Loop Out, Boltz, and Peerswap move Lightning balances to on-chain bitcoin. Because you spend your outbound capacity and receive on-chain bitcoin in return, your inbound capacity recovers by the same amount. This is a way to redistribute balances while keeping the channel open.
3) Send to an exchange
If you already use an exchange that supports Lightning, such as Kraken or River, you can send a small amount there. The outbound capacity you spend creates an equivalent amount of inbound capacity. This has the lowest fees, but it requires trusting the exchange.
Where Should You Open a Channel?
There is no single rule for choosing a good peer. However, three metrics are useful.
- Centrality: Check a node's betweenness centrality on an explorer such as Amboss or 1ML. The higher it is, the more likely payments are to route through that node.
- Uptime: Only choose nodes that have been close to 100% uptime over the past month. Channels connected to an offline peer cannot route payments during that time.
- Fee policy: If the routing fee (ppm) charged by a large node is too high, that path will be too expensive to be routed through. Below 100 ppm is typical.
For beginners, a good starting point is three to five channels: one or two with large nodes like LNBIG, ACINQ, or Bitrefill, and one or two with counterparties you actually expect to pay or receive from.
What Is the Right Channel Size?
Too small, and a single payment may not fit. Too large, and capital sits idle and on-chain closing fees become expensive. A general sense of scale:
- Personal spending (shopping, tips): 500,000 to 2,000,000 sat per channel
- Merchant or payment-receiving use: 2,000,000 to 10,000,000+ sat per channel
- Routing node operators: 10,000,000 to 100,000,000 sat per channel
A channel is opened with a single on-chain transaction. Opening many small channels when fees are high is uneconomical. When possible, it is better to open a few larger channels when fees are below 20 sat/vB.
The Reality of Routing Revenue
The idea that running a routing node is a profitable business circulates frequently, but the actual numbers deserve a conservative reading. As of 2024, a well-operated node earns an annual return (routing fees relative to locked capital) of roughly 1 to 3%. After accounting for electricity, internet, and time, most operators are at a loss or barely breaking even.
If routing revenue is your goal, you need automation tools like Charge-LND, balanceofsatoshis (bos), and lnd-manageJ to dynamically adjust fees, automate rebalancing, and quickly drop underperforming peers. Manual operation is nearly impossible to make work.
If your goal is self-sovereignty and personal spending, it is more honest to treat routing revenue as a side effect rather than the objective.
Rebalancing: Maintaining Bidirectional Liquidity
When payments flow heavily in one direction, either outbound or inbound capacity on a given channel becomes depleted. At that point you can no longer send or receive in that direction. This is when rebalancing is needed.
The simplest approach is circular rebalancing. This means sending a payment to yourself. You construct a route of the form: your node A - external path - back to your node A. This consumes outbound capacity on the departure channel and restores inbound capacity on the arrival channel.
Using the rebalance command in bos or the rebalance-lnd script, you can set conditions (fee cap, path exclusion, etc.) and run it automatically. Be careful not to exceed the fee cap you have calculated yourself. For most nodes, if the rebalancing fee exceeds the routing fees earned, the operation becomes unsustainable.
The Risk of Going Offline
A Lightning channel is safest when both parties are online. If your node goes offline for several days and your counterparty attempts to close the channel using an outdated state, a Watchtower must detect this and broadcast a penalty transaction. LND's built-in Watchtower is limited, so it is safer to register with an external Watchtower such as LNBIG WT or Sleepyarks.
Summary
Lightning channel operations reduce to five recurring tasks:
- Open channels when fees are low.
- Acquire inbound capacity (buy or swap).
- Evaluate peers by uptime and centrality each quarter and close low-activity channels.
- Automate rebalancing to maintain bidirectional liquidity.
- Register with a Watchtower and store backups (
channel.backup) off-site.
Once these habits are internalized, Lightning becomes part of your everyday payment infrastructure. The first three months involve many mistakes, and those mistakes are best accepted as the cost of learning.