• Why Submarine Swaps Are One of Lightning’s Most Underappreciated Features
  • The Problem They Solve
  • How a Submarine Swap Works
  • The Reverse Direction
  • The Privacy Dimension
  • Key Takeaways

§Why Submarine Swaps Are One of Lightning’s Most Underappreciated Features

Submarine swaps enable transferring BTC between Lightning and on-chain Bitcoin without trusting a custodian. They’ve been quietly powering a significant portion of Lightning’s practical utility, and understanding them clarifies why Lightning can work without needing every user to manage their own channel liquidity.

§The Problem They Solve

Lightning requires channel liquidity: to receive a payment, you need inbound capacity. To send a payment, you need outbound capacity. For most users, getting this right is practically difficult.

Example: Alice has a Lightning wallet with 100,000 sats. She receives 200,000 sats from Bob. Her wallet now has 300,000 sats — but all of it is in Lightning, she has no on-chain UTXO, and her channel has no outbound liquidity to send BTC on-chain.

When she wants to move BTC to her hardware wallet, she needs to either close a Lightning channel (expensive, slow) or use a submarine swap.

§How a Submarine Swap Works

A submarine swap (from Alice’s Lightning wallet to on-chain):

1. Alice’s Lightning wallet generates an invoice for the amount she wants to swap
2. The submarine swap service (say, Loop, Boltz, or a personal node) pays the Lightning invoice
3. Alice sends the same amount of BTC on-chain to the service’s address
4. The service’s Lightning payment is atomic: either the Lightning payment succeeds AND the on-chain payment happens, or neither happens

The net effect: Alice converted Lightning BTC to on-chain BTC. She used a service, but the service couldn’t steal because the swap is atomic. Alice’s Lightning wallet paid the invoice, so the service received the Lightning BTC. In exchange, Alice sent on-chain BTC to the service’s address. Both happen or neither happens.

§The Reverse Direction

Submarine swaps work in reverse too: sending from on-chain to Lightning. You send BTC on-chain to a service, they send equivalent BTC on Lightning to your invoice. This is how you “top up” Lightning with fresh inbound capacity.

This is what makes the service economically viable: they accumulate inbound liquidity on Lightning (they receive sats), which lets them pay out Lightning invoices for other users. The on-chain BTC they receive in swap goes toward opening new channels.

§The Privacy Dimension

Submarine swaps have a privacy property that’s often overlooked: they break the on-chain link between your Lightning payments and your on-chain addresses. Normally, if you receive 10 Lightning payments from 10 different people, all those payments are linked by your node’s public key on the Lightning network.

When you submarine-swap to on-chain, you’re receiving on-chain BTC at a fresh address that has no link to your Lightning node. The swap service knows the link, but chain analysis firms can’t see it.

§Key Takeaways

• Submarine swaps enable atomic BTC transfers between Lightning and on-chain without custodians
• They solve the liquidity management problem: convert Lightning balance to on-chain without closing channels
• The reverse swap (on-chain to Lightning) tops up inbound capacity
• Services like Loop and Boltz make submarine swaps accessible to non-technical users
• Submarine swaps provide privacy benefits by breaking on-chain/Lightning address links

⚡ If this was useful, a zap is always welcome. tomford@rizful.com