Running a Lightning Node: Earning Sats and Supporting the Network

A lightning node is software that takes part in the Lightning Network: it opens channels, sends and receives payments, and can forward other people’s payments for a small fee. Running your own means no company holds your Lightning payments or sees all of them, and teaches you how Bitcoin’s payment layer works from the inside. It also gives you new duties: staying online, keeping backups and installing updates.

In the previous lessons you saw why running a Bitcoin node matters, compared node platforms and set up your own full node, including installing Lightning and making the right channel backup. This lesson is about running that Lightning node well: for your own payments first, and for routing if you want to go further.

What Is a Lightning Node?

A lightning node manages payment channels. It talks to other Lightning nodes to find routes, forwards payments between its channels and keeps track of every channel’s balance. It works alongside your Bitcoin full node: it uses the blockchain to open and close channels, and handles payments off-chain in between.

What a Lightning Node Actually Does

• Manages payment channels: opens, maintains and closes channels with other nodes
• Sends and receives payments directly, without a wallet company in between
• Routes payments: forwards other people’s payments when your channels sit on a useful path
• Earns routing fees: usually a few sats per forwarded payment
• Watches for cheating: checks the blockchain for a channel partner publishing an old balance, but only while it is online, unless a watchtower helps (see below)

For how channels and routing work, review Lesson 4.1: Lightning Network Explained and Lesson 4.2: Lightning Channels and Routing.

Lightning Node Implementations

Several teams have written independent Lightning software. Which one you run affects setup, features and which tools work with your node.

LND (Lightning Network Daemon)

Built by Lightning Labs in the Go language, LND is the most widely used implementation and the default Lightning software on most node platforms, including Umbrel’s Lightning Node app, myNode and RaspiBlitz. It has a full API, extensive documentation and the largest set of third-party tools. The steps and settings in this lesson use LND.

CLN / Core Lightning

Built by Blockstream in C, Core Lightning (formerly c-lightning) is designed around plugins, so advanced users can extend what their node does. It tends to use fewer resources. Umbrel, Start9 and RaspiBlitz all offer it as an alternative to LND.

Eclair

ACINQ’s server node software, written in Scala. ACINQ’s own large node runs it, and that is the node Phoenix users have their channel with. Phoenix itself runs ACINQ’s separate mobile library, lightning-kmp. Eclair is aimed at operators of large nodes and is rarely found on home node platforms.

LDK (Lightning Dev Kit)

LDK isn’t a standalone node; it is a library, written in Rust, that developers use to build Lightning into their own apps and wallets. Unless you build software, you won’t use it directly.

Implementation	Language	Best For	Where You Find It
LND	Go	General use, most platforms	Umbrel, Start9, myNode, RaspiBlitz
CLN	C	Plugins, low resources	Umbrel, Start9, RaspiBlitz
Eclair	Scala	Large server nodes	ACINQ’s node (Phoenix’s channel partner)
LDK	Rust	Building Lightning into apps	Inside wallets and apps

Setting Up a Lightning Node

Lesson 4.7 walks through installing Lightning on Umbrel. In outline:

1. Wait until your Bitcoin node is fully synced. Lightning needs it to check channel transactions. The first sync takes a few days on a Raspberry Pi.
2. Install the Lightning software. On Umbrel, install the Lightning Node app (LND) from the App Store; Core Lightning is also available. On Start9 you choose between LND and CLN. Without a platform, you download it and configure it to talk to your Bitcoin node.
3. Write down the recovery words. LND gives you 24 words. They restore your node’s on-chain funds. They do not, on their own, restore money in channels: that also needs the static channel backup file, channel.backup, which the words only decrypt (LND recovery guide). See “Backups and Updates” below.
4. Fund the node. Send bitcoin to its on-chain address; channels are opened from there. While you learn, use an amount you could afford to lose to a mistake.
5. Open your first channel. See the steps below.

Opening a Channel, Step by Step

1. Find a peer’s address. Every node has a node ID, its public key: a long string of letters and numbers. To connect, you need its full address, written pubkey@host:port: the node ID, an @, and where it can be reached on the internet or Tor. Explorers such as Amboss list it on each node’s page.
2. Paste it into your node. In Umbrel’s Lightning Node app, use the option to open a channel and paste the address. On the command line, lncli connect pubkey@host:port followed by lncli openchannel --node_key=pubkey --local_amt=amount.
3. Choose the amount and the on-chain fee. Opening a channel is an on-chain transaction, so you pay a mining fee, and closing it later costs another. A higher fee rate confirms faster.
4. Wait for confirmations. The channel becomes usable once the funding transaction has a few confirmations (LND asks for 3 to 6, depending on size).
5. Copy a fresh channel.backup off the node. Do this after every channel you open or close.

If the peer refuses, nothing is lost: many nodes set a minimum channel size (LND’s minchansize, 20,000 sats by default) and reject smaller requests before any bitcoin moves.

Use Your Node for Your Own Payments

Before thinking about routing for profit, use the node for what most people set it up for: paying and being paid without a company in the middle.

• Pay from your phone. Connect Zeus to your node (Lesson 4.7 shows how). Your phone becomes a remote control: payments leave from your node instead of a wallet company’s.
• Get inbound liquidity so you can receive. A channel you open yourself can only send at first. Spend through it, ask another node to open a channel to you, buy inbound liquidity from a Lightning Service Provider, or swap part of your balance out on-chain. Lesson 4.2 explains each option.
• Know the trade-off. Compared with Phoenix, you gain privacy and control, and take on uptime, backups, updates and channel management.

Opening and Managing Lightning Channels

The peers you connect to, the size of your channels and how their balances sit decide how well your node can send, receive and route.

Choosing Channel Peers

For good routes, connect to nodes that are well connected, online all the time and well funded. Look for:

• High uptime: a peer that is often offline makes your channel useless while it’s down
• Good connectivity: peers with many channels of their own give you short routes to much of the network
• Reasonable fee policies: very high fees make your payments expensive; nodes charging nothing are not always well run
• Reputation: explorers such as Amboss and LightningNetwork+ show a node’s channels, history and, on some, ratings

Channel Sizing

Size follows purpose. For your own spending, a channel of an amount you’re comfortable having locked up for months is enough. For routing, small channels (under about 500,000 sats) can only forward small payments, and the on-chain fees to open and close them weigh more against what they earn. Routing nodes commonly use channels of 1 to 10 million sats: in mempool.space’s snapshot of 30 August 2026, the median public channel held about 2 million sats and the average about 11.6 million (mempool.space). Larger channels carry bigger payments but tie up more of your bitcoin.

Whatever the size, each channel costs a mining fee to open and another to close. Our lesson on Lightning backups and watchtowers works them out from real transactions of August 2026: at about 1 sat/vB, opening a channel cost about 150 sats and closing it cooperatively about 190 (as of November 2026, 1 to 3 sat/vB is usually enough). At the 300 sat/vB seen in December 2023, each step costs tens of thousands of sats, and a force close costs about twice a cooperative close. So open channels you mean to keep, when fees are low, and close them cooperatively whenever the other node is online.

Channel Balance Matters

A channel you open starts with everything on your side. To route payments in both directions, each channel needs money on both sides; the “Rebalancing Channels” section below covers how to get there.

For a deeper look, see our Lightning Channel Management Masterclass.

Earning Routing Fees with Your Lightning Node

Each time your node forwards a payment from one of its channels to another, it keeps a small fee. You set two numbers per channel: a base fee, a flat amount per payment set in thousandths of a sat, and a fee rate, a proportion of the amount in parts per million (ppm). LND’s defaults are 1 sat and 1 ppm (LND sample configuration); the network’s median in August 2026 was 0.5 sat and 100 ppm.

How Routing Fees Work

When someone’s payment route goes through your node, you forward it and keep the fee:

fee = base fee + amount × rate ÷ 1,000,000

At 100 ppm, forwarding a 100,000-sat payment earns 10 sats, plus your base fee.

Typical Earnings

There is no reliable public data on what small nodes earn, and figures you see online are one operator’s experience, not a forecast. Do the arithmetic instead. At 100 ppm, your node earns 100 sats for every million sats it forwards. A small node that forwards a million sats a day would earn about 3,000 sats a month; many small nodes forward much less, some days nothing. Against that, count the on-chain fees to open and close channels and the cost of rebalancing. Plenty of hobby nodes spend more than they earn.

Fee Policy Strategy

Charge too much and payments route around you; charge too little and you won’t cover your costs. A reasonable start is near the network median, a base fee of 0 to 1 sat and 50 to 250 ppm, then adjust each channel to how payments flow through it. Tools such as charge-lnd and LNDg automate this.

Is Running a Lightning Node Profitable?

The honest answer depends on what you count as profit.

The Financial Reality

For most hobbyists, no. After hardware, electricity, on-chain fees for opening and closing channels, rebalancing and your time, a small node usually earns little or nothing compared with simply holding the same bitcoin. Run one for the other benefits, and treat any fee income as a bonus.

The Real Value of Running a Lightning Node

• Privacy: no wallet company sees your payments. Your channel partners and routing nodes still see what passes through their own channels, and channel openings and closings are public on the blockchain.
• Sovereignty: you choose your channels, your fees and your peers, without asking anyone.
• Network support: every well-run node adds routes and liquidity for everyone.
• Education: nothing teaches you how Lightning works like running a node.

When It Can Be Profitable

Routing at scale is a business: many bitcoin in channels, automated fee management and constant monitoring, and even then returns vary widely between operators. Don’t open your first channel expecting to earn a living.

Watchtowers and Security

A channel partner could try to cheat by publishing an old balance that gave them more than they now have. This is a breach. Your node can punish it and take the whole channel, but only if it notices within the waiting period your node set for that partner when the channel opened. With LND’s defaults, that window is 144 blocks, about a day, for channels under about 1.2 million sats, rising to 2,016 blocks, about two weeks, for the largest (LND sample configuration).

A watchtower is a service that watches the blockchain for you. If your node is offline and a partner publishes an old balance, the tower publishes the penalty transaction and the channel’s funds go to you.

Turning on the Watchtower Client

LND’s watchtower client is off by default (wtclient.active=false). Switch it on when you open your first channel: a tower only learns the balances revoked while the client runs, so one added the night before a trip leaves every older balance unguarded. To use a tower:

• On Umbrel: open the Lightning Node app’s Advanced Settings, switch on Watchtower Client, save and restart, then add a tower’s address, written pubkey@host:port.
• On plain LND: set wtclient.active=true in lnd.conf, restart, then run lncli wtclient add pubkey@host:port.

Which tower to use, how to run your own and what it can see are covered in Lesson 4.9: Lightning Backups and Watchtowers; our Lightning Watchtower Setup Guide has the commands.

Backups and Updates

• Back up channels the safe way: after every channel you open or close, copy a fresh channel.backup somewhere other than the node, and never rely on the channel database (channel.db) as your backup or restore an old copy of it. Lesson 4.7 shows where to find the file on Umbrel, and our lesson on Lightning backups and watchtowers explains what each file does and what a restore gets back.
• Keep LND and your platform updated: your node holds money on an internet-connected machine, and updates fix security problems. In November 2026, for example, Lightning nodes on Linux needed LND 0.21.6 or 0.20.7 and a patched system (see our advisory). Check our security advisories regularly.

Rebalancing Channels

As payments flow, channels drift out of balance. A channel with everything on one side can only route in one direction, which limits both your payments and your fee income.

Why Rebalancing Matters

If a 1,000,000-sat channel has everything on your side, you can send or route outward through it but can’t receive through it. The reverse is also true. Keeping channels roughly balanced, around 50/50 or at least 25/75, lets them work in both directions.

Rebalancing Methods

• Circular rebalancing: pay yourself, out through one channel and back in through another, to shift balance between them. Tools such as bos (Balance of Satoshis) automate this.
• Loop (Lightning Labs, for LND): Loop Out sends sats from a channel to an on-chain address, which frees up inbound capacity; Loop In moves on-chain sats into a channel, adding outbound capacity. See our Lightning Loop Tutorial on Submarine Swaps.
• Other swap services: swap between on-chain and Lightning funds without an account, often through a swap built into your wallet or node software. Boltz, the best known, switched off all its swaps on 3 August 2026 and was still offline when we checked on 8 November 2026. Several tools that used it have dropped it, so check that the service yours uses is running and try a small swap first.
• Spending and receiving: the most natural method; using your channels moves balances on its own.

Rebalancing costs money: routing fees for circular rebalances, and service and mining fees for swaps. Count these against what you earn, so you don’t spend more on rebalancing than routing brings in.

For advanced strategies, see our guide on Lightning Network Routing Optimization.

Frequently Asked Questions

How much does it cost to run a lightning node?

The hardware is the same small computer as your Bitcoin node, plus electricity (see Lesson 4.5 for how to work it out). On top come on-chain fees for opening and closing channels and, optionally, rebalancing costs. The bitcoin in your channels isn’t a cost (it is still yours), but it is locked up while the channels are open.

Do I need a static IP address to run a lightning node?

No. A node can reach the network over Tor, which works behind a changing IP address and without opening ports on your router. LND itself ships with Tor switched off (tor.active=false), but node platforms often set it up for you; check your node’s settings. Tor connections are slower but private; our lesson on network privacy compares Tor and VPNs. For faster clearnet connections, a static IP address or a dynamic DNS service helps. A dynamic DNS service keeps a fixed name pointing to your node when your home IP address changes.

Can I run a Lightning node without a 2 TB full node?

Yes, with trade-offs. LND can work with a pruned Bitcoin Core, one that deletes old blocks after checking them, and fetches from other nodes any old block it needs. It can also run on Neutrino, the light client that follows the chain with compact block filters instead of a full node (LND sample configuration); Zeus’s embedded LND option works that way, while its default built-in node, LDK Node, asks an Esplora server instead (Lesson 4.3). Neutrino trusts other nodes to check that transactions follow the rules, which your own full node would do itself. On Umbrel, the Bitcoin Node app has a Prune Old Blocks setting, but Umbrel warns that “some connected apps and services may not work with a pruned blockchain” (its settings), and pruning stops the Electrum servers this course uses (Lesson 4.5). For a node that will hold real money, a full node with a 2 TB drive remains the simplest and strongest setup.

Can I run a lightning node on a Raspberry Pi?

Yes: a Raspberry Pi 5 with 8 GB of memory and an external SSD can run a Bitcoin full node and a Lightning node together. Umbrel recommends the Pi 5 because USB drives “can make a Pi 4 crash” and calls the Pi 4 “fine for tinkering”, so for a node that holds channel funds, choose a Pi 5 or a mini-PC. A mini-PC gives more headroom for larger routing nodes.

What happens if my lightning node goes offline?

Your channels stay open, but two things can happen. Peers may force-close channels if your node stays unreachable for long. More importantly, if a peer publishes an old balance while you’re offline, someone has to respond within the waiting period, often 144 blocks, about a day, on LND channels under about 1.2 million sats. So either keep offline periods shorter than that, or run the watchtower client from your first channel. Routing nodes should aim for near-constant uptime.

How many channels should I open?

Quality beats quantity. For your own payments, one or two good channels can be enough. For routing, start with 3 to 5 well-chosen channels to well-connected nodes and add more as you learn; many experienced operators run 10 to 30. Each channel costs on-chain fees to open and close, so don’t open channels you won’t keep.

Check Your Understanding

1. Your node’s SSD and SD card both die. You have your 24 words but never copied channel.backup. What can you recover?

Answer

Your on-chain funds, from the 24 words. The words alone don’t recover the money in your channels: that needs the static channel backup, which tells a new node which peers to ask to close the channels. Check first whether your platform kept an automatic copy: Umbrel’s Lightning Node app uploads an encrypted one by default, and a node restored with the same 24 words can find it (Umbrel’s explanation). Without any copy, getting that money back is hard and not guaranteed: you depend on each peer force-closing the channel on its own, and you may need specialist recovery tools to find your share. That’s why you copy channel.backup off the node after every channel you open or close.

2. You’ll be away for a week and your node will be off. Your channels are 500,000 sats each on LND defaults. What is the risk, and what can you do?

Answer

On channels that small, a peer who publishes an old balance only has to wait 144 blocks, about a day. If your node is off for a week and no watchtower is watching, the cheat can go unpunished. The sure fix is to keep the node running. A tower switched on the night before helps only partly: it learns only the balances revoked from then on, so older ones stay unguarded. Next time, run the watchtower client from your first channel.

3. Your node forwarded 2 million sats this month at 100 ppm and a 1-sat base fee across 20 payments. Roughly how much did it earn?

Answer

100 ppm of 2,000,000 sats is 200 sats, plus 20 sats in base fees: about 220 sats. Compare that with what you spent opening, closing and rebalancing channels to see whether routing paid for itself.

Practical guides

• Running a Lightning Node: Complete 2026 Guide
• Lightning Loop Tutorial: Submarine Swaps