Lightning Channel Management: How Routing Nodes Work

A Lightning routing node is a Lightning node that forwards other people's payments and charges small fees for it. To make that work it has to tend its channels: keep balances on both sides, set fees so that payments flow through it without draining it, and shift funds around when channels become lopsided. Hardly anyone gets rich doing this. A small node often earns less than its electricity costs; the appeal lies in learning and in contributing to the network.

What a routing node does in the Lightning Network

How the Lightning Network works in principle, with channels, balances and payments across other nodes, is covered in the basics article. This one is about the other side: you are not the payer but one of the nodes in the middle.

A routing node is a Lightning node with several public channels that runs around the clock. If Anna wants to pay the café and the best route runs through you, a payment promise arrives on one of your channels and you pass on an equal promise on another channel. As soon as the café accepts the payment, both promises settle. You now have more on one channel and less on the other, and the difference is your fee.

The promise is called an HTLC (Hashed Timelock Contract). What an HTLC looks like as a script is explained in Bitcoin Scripts and Smart Contracts. What matters to the operator: you cannot lose money doing this as long as your node is online and working correctly. But you earn nothing either if nobody pays through you.

Common software for this is LND, Core Lightning, Eclair and LDK-based nodes. Many home operators use ready-made node packages such as Umbrel, Start9 or RaspiBlitz, with a dashboard like Ride The Lightning or ThunderHub.

Inbound and outbound liquidity: the two sides of every channel

A channel with a capacity of 1’000’000 satoshis is like a balance scale with a fixed set of weights. If 700’000 sit on your side, that is your outbound liquidity: that much you can send or forward through this channel. The 300’000 on your partner's side are your inbound liquidity: that much can flow to you through this channel.

Every payment shifts the weights. If you forward 100’000 satoshis from channel A to channel B, you then have 100’000 more outbound on A and 100’000 less on B. Your total stays the same, plus the fee.

That gives the most important rule of channel management: a routing node needs room in both directions in every channel. A channel where everything sits on your side can no longer bring anything to you. A channel where everything sits with your partner can no longer pass anything on.

Whoever opens a channel puts in the capital. At the start everything is on your side: lots of outbound, zero inbound. New nodes can therefore send, but can hardly forward anything, because nothing can come in from outside. Getting inbound liquidity is the first real hurdle.

Where inbound liquidity comes from

• Others open channels to you. That rarely happens by itself while your node is unknown.
• Channel swaps between operators: on platforms such as Lightning Network+ operators agree to open equal-sized channels to each other, often in a triangle.
• Buying inbound: providers and marketplaces, such as Amboss's Magma or Lightning service providers, open a channel to you for a fee.
• Spending: if you pay for something yourself over a channel, balance moves to your partner and you gain inbound.
• Swapping out of Lightning: you send satoshis over Lightning to a swap service and get them back on the blockchain (see rebalancing).

Routing fees: base fee and ppm

Every node sets, for each of its channels, what it charges for forwarding. The fee has two parts:

• Base fee: a fixed amount per forward, stated in millisatoshis. 1’000 millisatoshis are 1 satoshi.
• Fee rate in ppm: a proportion of the forwarded amount in parts per million. 1 ppm is one millionth, 100 ppm is 0.01 %, 1’000 ppm is 0.1 %.

What matters is which channel charges: the fee applies to the channel through which the payment leaves your node. High fees on a channel make it unattractive for payments that want to flow out there. That protects scarce outbound. Low fees attract payments and drain the channel faster.

According to mempool.space, the median public channel at the end of August 2026 charged a 0.5 satoshi base fee and 0.01 % of the amount. Many channels to large merchants and exchanges are much pricier, because liquidity there is scarce. Newer LND versions also allow fees or discounts on the incoming channel; that is not yet widespread.

Besides the fee, every channel has further settings: the smallest and largest amount it forwards (min/max HTLC), and a time buffer in blocks (CLTV delta) that gives you time to react on the blockchain in a dispute.

Channels drain: rebalancing and swaps

In practice payments rarely flow evenly. If you have a channel to a large exchange, you often see money flowing only one way: users withdraw bitcoin via Lightning, so your outbound towards that exchange drains, or the reverse. A one-sided channel earns nothing more. There are four tools against that.

1. Adjust fees. If a channel runs empty, raise its fee. Fewer payments flow out, more take other routes. If it is overfull, lower it. Programs such as charge-lnd or LNDg do this automatically by rules.

2. Circular rebalancing. You pay yourself: satoshis leave your node through a full channel, travel through the network and come back through an empty one. You pay the other nodes' fees along the way. It only pays off if you later sell the shifted liquidity for more than shifting it cost.

3. Submarine swaps. A swap service exchanges Lightning balance for on-chain bitcoin or vice versa, secured like an HTLC. Lightning Labs' "Loop Out" and Boltz are examples. A swap out empties your side and creates inbound. It costs the service's fee plus an on-chain transaction.

4. Close and reopen, or splicing. The capital of a useless channel can go into a better one. Splicing, where the software supports it, lets you move money into or out of a running channel without closing it. Both cost on-chain fees, a lot in busy times.

What a routing node realistically earns

An honest calculation helps here. Income comes only from forwarded volume times fee rate. Capital alone earns nothing.

The assumptions in the second example are already generous. Reports from small and medium operators are mostly well below 1 % a year, and many earn nothing after costs. Higher returns go to nodes attached to real payment flows, such as exchanges or large wallets. Block, the company behind Cash App, stated at the Bitcoin 2025 conference in May 2025 that its Lightning nodes earned an annual yield of about 9.7 %. Those nodes have Cash App's payment traffic behind them and are no benchmark for a home computer.

For comparison: a bitcoin sitting cold in your hardware wallet earns 0 % interest, but carries no technical failure risk either. Why supposed yields on bitcoin are often more expensive than they look is described in The Staking Illusion.

Routing fees count as income for tax purposes. In Germany they are usually "other income" with a €256 annual exemption limit; details for Germany, Austria and Switzerland are in Lightning Network and taxes.

Risks: hot keys, force closes, outages

A routing node is a hot wallet: its keys sit on a computer that is always connected to the internet, and they have to, otherwise it cannot sign. Whoever gains access to that computer can drain the channels.

• Force close: if your partner is offline for long or your nodes disagree, a channel is closed unilaterally on the blockchain. Depending on settings, your money is then locked for up to about two weeks, and the close costs fees, a lot in busy times.
• Stale channel states: if your node restores an old channel state after a backup mistake, the partner can treat that as cheating and take the channel's entire balance. A Lightning backup is therefore not simply a copy of the database. Use your software's static channel backup and a watchtower.
• Outage during payments: if your node goes down in the middle of a forward and doesn't return in time, a payment may have to be settled on the blockchain.

How to start a small routing node

If you want to try it, you need little capital and some patience.

1. Set up a Bitcoin node. Lightning builds on your own Bitcoin node. A mini PC with an SSD is enough.
2. Install Lightning software. LND or Core Lightning, most easily through a node package. Set up backup and watchtower right away.
3. Open a few good channels. Better three to five channels of at least 1’000’000 satoshis each to well-connected nodes than twenty tiny ones. Small channels cannot carry large payments.
4. Get inbound. Through a channel swap or a purchased channel.
5. Watch fees, don't tweak daily. Adjust weekly, depending on which channels run dry.
6. Keep records. Export forwards, costs and channel fees, not least for tax.