Opening Lightning channels on your Bitcoin node requires the right peers, enough capacity, and realistic expectations about routing income. Here's how to do it right in 2026.
Running a Bitcoin node is one thing. Running a Lightning node that routes real payments and earns routing fees is another. Most people set up Umbrel or Start9, see the Lightning wallet, and stop there. This guide walks you through actually opening useful Lightning channels — understanding capacity, peer selection, routing strategy, and what to realistically expect from running a routing node in 2026.
You need:
If you''re still deciding on node software, our Bitcoin Node Software Comparison covers Umbrel, Start9, RaspiBlitz, and myNode side by side.
A Lightning channel is a two-way payment tunnel between your node and a peer. When you fund a channel with 1,000,000 sats:
For your node to route payments, you need both inbound and outbound liquidity. Initially, all your capacity is outbound. To receive payments, either your peers push sats your way (by routing through you) or you open channels where peers fund their side.
Inbound liquidity strategies:
Bad peer selection is why most routing nodes fail to earn meaningful fees. Good peers are:
Well-connected: Nodes with many channels and high capacity have more routing paths through them. Connect to central hubs.
Online consistently: A peer that''s offline 30% of the time makes your channels useless during those periods. Check uptime on Amboss or 1ML before connecting.
Fee-competitive: Peers who charge very high routing fees route fewer payments — and yours may not route through them.
Strategically positioned: Connecting to nodes that serve different parts of the network than you do (exchanges, large wallets, specific regions) creates more routing paths.
Don''t connect to random small nodes or yourself. The Lightning network is scale-free — a few giant hubs move most of the volume.
pubkey@host:port)Start9''s Embassy OS supports both LND and Core Lightning. The interface differs slightly:
For LND:
lncli connect <pubkey>@<host>:<port>
lncli openchannel --node_key <pubkey> --local_amt 1000000
For Core Lightning:
lightning-cli connect <pubkey> <host> <port>
lightning-cli fundchannel <pubkey> 1000000
Minimum viable routing channel: 500,000 sats (0.005 BTC). Smaller channels struggle to route even moderate payments.
Good routing channels: 1,000,000-5,000,000 sats. This allows routing most Lightning payments (typical payments are 10,000-100,000 sats).
Large institutional channels: 10M+ sats. These position you to route large volume but require significant capital commitment.
How many channels? Start with 3-5 quality channels rather than 10 cheap ones. Three channels to well-connected nodes will route more than ten channels to poor nodes.
Routing fees have two components:
Competitive fee settings for a new node:
Set fees too high and no payments route through you. Set them too low and you''re giving away routing for free. Most successful routing nodes start low (1-5 ppm) to attract flow, then adjust based on channel utilization.
Let''s be direct: routing fees from a small home Lightning node are modest.
A node with 10M sats in channels at 1 ppm fees might route 500M sats per month if well-positioned — earning 500 sats (~$0.50). A large, well-positioned node with 1 BTC+ in channels might earn 50,000-200,000 sats per month.
Routing income is not the primary reason to run a Lightning node in 2026. The reasons are:
For in-depth analysis, see our Lightning Node Profitability Guide.
Rebalancing: As you route payments, channels become unbalanced (all liquidity on one side). Rebalance by:
Channel health monitoring: Check:
Closing channels: Close unproductive channels (poor uptime, zero routing) and redeploy capital to better peers. Closing is an on-chain transaction — wait for low-fee periods.
| Feature | Umbrel | Start9 | RaspiBlitz |
|---|---|---|---|
| Lightning UI | Good | Good | Advanced |
| Thunderhub integration | Yes | Yes | Built-in |
| CLN support | LND only | Both | Both |
| Routing tools | Basic | Basic | Advanced |
| Best for | Beginners | Privacy-focused | Serious routing |
See our Umbrel vs Start9 vs RaspiBlitz comparison for the full breakdown.
Minimum 0.005 BTC (500,000 sats) per channel for useful routing. Ideally 0.01-0.05 BTC per channel. Having at least 0.1 BTC total to deploy across 3-5 channels gives you a meaningful routing node.
Yes — when payments route through your channels, you earn routing fees automatically. Fees accumulate in your local channel balance. But income is modest for small nodes.
Opening a channel requires 3 Bitcoin block confirmations, typically 30-60 minutes. The on-chain transaction must confirm before the channel is active.
Yes, but closing is an on-chain transaction that costs fees. Cooperative closes (both parties agree) are faster and cheaper. Force closes (one party closes unilaterally) take longer due to time locks.
Inbound liquidity is capacity on your peer''s side of the channel — it''s how much you can receive via Lightning. When you first open a channel, all capacity is outbound (you can only send). To receive payments, you need peers to send liquidity your way or purchase inbound liquidity.
Explore node software in our Bitcoin Node Directory. See also: How to Run a Bitcoin Node and Bitcoin Node Privacy Benefits.
Get our free Beginners Guide to Buying Bitcoin plus weekly insights for long-term holders.
A Bitcoin full node downloads 600+ GB during initial sync and uses 200+ GB/month ongoing. This guide covers exact bandwidth requirements by connection type, how to manage upload costs, and whether pruning helps.
Running your own Bitcoin node protects your financial privacy in ways most users never consider. This guide explains exactly what threats a personal node defends against and how to set it up correctly.
How much bandwidth does a Bitcoin node use? Complete breakdown of IBD data, ongoing monthly usage, pruned vs full node differences, and how to limit bandwidth.