Inbound Liquidity

Inbound liquidity is the capacity to receive funds on the Lightning Network. Every Lightning channel holds a fixed total balance split between its two ends, and a participant can only receive as much as sits on the counterparty's side of their shared channels. A merchant with 5 million satoshis of inbound liquidity can accept at most that amount before channels must be rebalanced or expanded.

Why it matters

Inbound liquidity is Lightning's most counterintuitive concept and its most common operational headache. A new node that opens a channel funds its own side entirely, so it can send but cannot receive at all until it spends, earns incoming payments through a loop, or persuades someone to commit capital toward it. Merchants and exchanges must actively manage this, buying channel capacity from liquidity marketplaces, using swap services that convert on-chain funds into receiving room, or paying routing nodes to open channels toward them.

The constraint reflects Lightning's honest accounting: nothing is received unless real bitcoin is already positioned to move, which is what lets the network settle instantly without trust.

In the gold vs bitcoin debate

Lightning's liquidity mechanics answer the scaling criticism that bitcoin cannot serve everyday commerce, but they show the answer has costs, capital must be locked and managed to make payments flow. Gold's payment layers faced the same physics in their own way, with cleared balances prepositioned between banks. Both systems demonstrate that instant settlement at scale always requires someone's capital standing ready.