Channels, liquidity & routing
If Lightning is “instant Bitcoin,” then channels are the rails, liquidity is the fuel, and routing is the GPS. Understanding these three ideas explains why some payments fly… and why others fail.
📌 Sections
1) The simple explanation
Lightning moves value by using “pre-funded lanes” between people and services. These lanes are called channels.
- Channels hold balances between two peers.
- Liquidity is the available balance that can move in the direction you need.
- Routing stitches channels together so you can pay someone you’re not directly connected to.
2) What a Lightning channel really is
A channel is a shared balance between two participants, anchored by a Bitcoin on-chain transaction. Inside the channel, you can update balances instantly without touching the blockchain every time.
Think of it like a running tab: you only “settle up” on-chain when you open or close.
3) Liquidity: inbound vs outbound
Liquidity is often the missing piece. It’s not “do I have bitcoin?” — it’s “do I have bitcoin in the right place, on the right side of the channel?”
A simple mental model: sending consumes outbound; receiving consumes inbound. Over time, payments “shift” balances from side to side.
4) Routing: how payments find a path
You don’t need a direct channel to everyone. Lightning payments can hop across multiple nodes, using channels like stepping stones.
- A payment can traverse multiple nodes (hops).
- Each hop must have enough liquidity in the correct direction.
- Routes are chosen automatically by your wallet/node based on available paths and cost.
5) Why payments succeed or fail
Most Lightning “failures” are not bugs — they’re economics and topology. Here are the most common reasons:
- Insufficient liquidity somewhere along the route
- Route temporarily unavailable (node offline or channel disabled)
- Fees too high compared to other available routes
- Payment size too large for the available paths
6) Fees: why routes cost money
Routing nodes can charge small fees for forwarding payments. This is what incentivizes well-connected nodes to provide liquidity and stay online.
Good routing isn’t “free” — it’s a market for reliable payment paths.
7) Practical tips for beginners
If you mostly want to pay:
- Use a wallet/provider that manages liquidity automatically.
- Keep enough outbound liquidity (funds available to send).
- Start with smaller payments while you learn.
If you want to receive payments reliably:
- Ensure you have inbound liquidity (others can pay you).
- Consider well-connected peers (good network position).
- Keep your node/wallet online if you’re self-hosting.
8) Quick FAQ
Do I need to run a node to use Lightning?
No. Many wallets handle channels and routing for you. Running a node is optional for advanced control.
Why can I send but not receive?
You likely have outbound liquidity but little inbound liquidity.
Why can I receive but not send?
You may have inbound liquidity but not enough outbound liquidity (your side of channels is too low).
Is Lightning always instant?
When a route with sufficient liquidity is available, it’s typically near-instant. If not, your wallet may retry other routes.
What’s the best “4th concept” to learn after basics?
Channels + liquidity + routing — because it explains almost every real-world Lightning experience.