← Bitcoin Encyclopedia

Inbound Liquidity

🌿 Intermediate

💡 The Plain-English Definition

Inbound liquidity is your ability to receive payments on the Lightning Network. It’s the remote balance in your payment channels — the Bitcoin on the other side that can flow toward you. Without it, you can send Lightning payments but you can’t receive them.

🤔 But Why Though?

When you open a Lightning channel (a direct payment connection between two nodes), all the funds start on your side — you have maximum outbound liquidity (ability to send) and zero inbound liquidity (ability to receive). This is counterintuitive: you funded the channel, so why can’t you receive? Because receiving means funds flowing toward you, which requires space on your side of the channel — space that’s only created when your counterparty has funds to send you.

This is the inbound liquidity problem, and it’s one of the trickier aspects of Lightning for newcomers. A node with zero inbound liquidity is like a bucket with no opening — you can pour things in from the top (outbound — money leaving), but nothing can pour in from outside. Getting inbound liquidity requires one of several approaches: asking someone to open a channel to you (which puts funds on their side, creating your inbound capacity), using an LSP (Lightning Service Provider — a company that manages channels and provides liquidity on your behalf), performing a submarine swap (a service that exchanges on-chain Bitcoin for Lightning Bitcoin, injecting funds onto the remote side of your channel), or using dual-funded channels (where both parties contribute funds at channel open, so both have immediate inbound and outbound capacity from the start). For most casual Lightning users, this problem is invisible — custodial wallets and LSPs handle it automatically. For anyone running their own Lightning node, inbound liquidity is a recurring operational challenge that shapes which channels to open and with whom.

🌍 The Real-World Analogy

Think of a Lightning channel like a two-way street between two buildings. When you build the road, all the cars start parked outside your building — you can send cars to the other building (outbound) but no cars can come back yet, because your end of the street is full and the other end is empty. Inbound liquidity is creating parking space at your end of the street — which only happens when cars travel from the other building to yours, or when someone else builds a road that arrives at your building from a different direction.

⚡ So What?

If you’re running your own Lightning node and can’t receive payments, inbound liquidity is almost certainly the cause. The fix is one of the methods above — opening a new channel with a well-connected peer, using a swap service, or working with an LSP. For users of wallet apps that handle this automatically, understanding inbound liquidity explains why the app occasionally asks you to perform an on-chain transaction or pay a small fee “to receive payments” — it’s acquiring inbound capacity on your behalf.

Part of The Bitcoin Encyclopedia 167 terms, plain English, no jargon.