Lesson Ready to Start
Foundational
Inbound vs Outbound Liquidity
Understanding directional liquidity in Lightning channels, why it matters for sending and receiving, and practical methods for acquiring the inbound capacity you need.
Transcript
Welcome back! In the last lesson, we learned how to open and close channels. Now let's understand one of Lightning's most important concepts: the difference between inbound and outbound liquidity and why it matters for everything you do on Lightning.
Understanding Directional Liquidity
In Lightning, liquidity refers to the funds available for payment within channels. But unlike a bank account, this liquidity has direction. Outbound liquidity is the funds on your side of the channel, representing satoshis you can spend or route outward. You naturally have outbound liquidity when you fund a new channel, receive payments, or rebalance funds to your side. Conversely, inbound liquidity is the funds on the remote side of the channel, representing the capacity for others to pay you. You acquire inbound liquidity when someone opens a channel to you, when you spend funds (pushing them to the other side), or when you route payments that flow inward.
Think of channel capacity like a seesaw or a pipe with water. The total capacity is fixed at opening, but the balance shifts constantly. If you open a channel with 1 million sats, you start with 1 million outbound (your side) and zero inbound (their side). If you spend 200,000 sats, your outbound drops to 800,000 while inbound rises to 200,000. Every payment pushes the balance, but the total never changes until the channel closes.
The Inbound Challenge
New Lightning users often struggle to receive payments, facing what we call the "Receiver's Dilemma." Because you typically start by opening and funding channels yourself, all your capacity begins as outbound. You can spend immediately, but you cannot receive until you have inbound liquidity. To fix this, you need funds on the other side of the channel. You can achieve this by spending sats (converting outbound to inbound), waiting for others to open channels to you (rare for new nodes), or using specific services.
To acquire inbound liquidity, you can use several methods. The simplest is to spend first; buying goods or donating converts your outbound capacity to inbound. Receiving via other channels works if you have multiple connections, as routing out of one channel creates inbound on the incoming channel. Channel swaps through communities like LightningNetwork.plus allow you to open a channel to a peer who opens one back to you, ensuring mutual inbound. Liquidity marketplaces like Pool or Magma allow you to pay for inbound capacity, and Lightning Service Providers (LSPs) can automate this process for you.
Liquidity States and Usage
Effective node usage requires understanding the four states of a channel: balanced (versatile for sending and receiving), outbound-heavy (great for sending), inbound-heavy (great for receiving), or depleted. For merchants and creators, inbound liquidity is crucial because without it, customers cannot pay you. For daily spenders, outbound liquidity is the priority. Node operators routing payments need balanced liquidity in both directions to facilitate flow—a payment comes IN one side and goes OUT the other; if either side is blocked, routing fails.
Management and Mindset
Successful node operation requires a "liquidity mindset," viewing your channels as dynamic flows rather than static balances. Monitor your inbound/outbound ratios regularly using tools like ThunderHub or RTL, and set alerts for depleted channels. Plan ahead so you don't find yourself unable to transact. Remember: total water in the pipe is fixed, but you control which direction it flows.
In this lesson, we've learned the critical difference between inbound and outbound liquidity. This understanding is fundamental to everything from receiving payments to running a routing node.
In our next lesson, we'll explore Channel Balancing Strategies — the art of keeping your liquidity where you need it.
Understanding Directional Liquidity
In Lightning, liquidity refers to the funds available for payment within channels. But unlike a bank account, this liquidity has direction. Outbound liquidity is the funds on your side of the channel, representing satoshis you can spend or route outward. You naturally have outbound liquidity when you fund a new channel, receive payments, or rebalance funds to your side. Conversely, inbound liquidity is the funds on the remote side of the channel, representing the capacity for others to pay you. You acquire inbound liquidity when someone opens a channel to you, when you spend funds (pushing them to the other side), or when you route payments that flow inward.
Think of channel capacity like a seesaw or a pipe with water. The total capacity is fixed at opening, but the balance shifts constantly. If you open a channel with 1 million sats, you start with 1 million outbound (your side) and zero inbound (their side). If you spend 200,000 sats, your outbound drops to 800,000 while inbound rises to 200,000. Every payment pushes the balance, but the total never changes until the channel closes.
The Inbound Challenge
New Lightning users often struggle to receive payments, facing what we call the "Receiver's Dilemma." Because you typically start by opening and funding channels yourself, all your capacity begins as outbound. You can spend immediately, but you cannot receive until you have inbound liquidity. To fix this, you need funds on the other side of the channel. You can achieve this by spending sats (converting outbound to inbound), waiting for others to open channels to you (rare for new nodes), or using specific services.
To acquire inbound liquidity, you can use several methods. The simplest is to spend first; buying goods or donating converts your outbound capacity to inbound. Receiving via other channels works if you have multiple connections, as routing out of one channel creates inbound on the incoming channel. Channel swaps through communities like LightningNetwork.plus allow you to open a channel to a peer who opens one back to you, ensuring mutual inbound. Liquidity marketplaces like Pool or Magma allow you to pay for inbound capacity, and Lightning Service Providers (LSPs) can automate this process for you.
Liquidity States and Usage
Effective node usage requires understanding the four states of a channel: balanced (versatile for sending and receiving), outbound-heavy (great for sending), inbound-heavy (great for receiving), or depleted. For merchants and creators, inbound liquidity is crucial because without it, customers cannot pay you. For daily spenders, outbound liquidity is the priority. Node operators routing payments need balanced liquidity in both directions to facilitate flow—a payment comes IN one side and goes OUT the other; if either side is blocked, routing fails.
Management and Mindset
Successful node operation requires a "liquidity mindset," viewing your channels as dynamic flows rather than static balances. Monitor your inbound/outbound ratios regularly using tools like ThunderHub or RTL, and set alerts for depleted channels. Plan ahead so you don't find yourself unable to transact. Remember: total water in the pipe is fixed, but you control which direction it flows.
In this lesson, we've learned the critical difference between inbound and outbound liquidity. This understanding is fundamental to everything from receiving payments to running a routing node.
In our next lesson, we'll explore Channel Balancing Strategies — the art of keeping your liquidity where you need it.
Views:
15
Course Navigation
Inbound vs Outbound Liquidity
Comment below with questions, suggestions and corrections.
Go to Comments