The Lightning Network: Bitcoin payments without waiting for blocks

Bitcoin settles a block roughly every ten minutes, and each block has limited space. That's a deliberate trade-off for security and decentralisation — but it makes Bitcoin awkward for buying a coffee. The Lightning Network is the best-known answer: a way to make many fast, cheap Bitcoin payments while touching the blockchain only occasionally.

Here's how it works, where it shines, and what it asks of you in return.

The core idea: a channel

Lightning is built from payment channels. Two people lock some bitcoin into a shared on-chain address that needs both of their signatures to spend — a 2-of-2 multisig, the same basic construction SSP uses for your vault.

Once the channel is open, the two parties pay each other by exchanging signed updates that say how the locked balance is currently split. Alice sends Bob 1,000 satoshis: they both sign a new version of the split. Bob sends 300 back: another new version. None of these updates goes on the blockchain. They're instant, and they cost almost nothing.

When they're done, either party can close the channel by publishing the latest split on-chain. Two on-chain transactions — open and close — can carry thousands of payments in between.

Keeping everyone honest

What stops Alice from publishing an old split, from before she paid Bob?

Each time the balance changes, both parties hand each other a way to punish anyone who publishes an outdated state. Old states are spendable by the cheated party during a waiting period enforced by time locks. If Alice broadcasts a stale state, Bob has a window to claim the whole channel balance as a penalty.

That's elegant, and it has a consequence: someone has to be watching. If you're offline for the whole dispute window, a cheating partner could get away with it. Lightning wallets handle this by staying online periodically or using "watchtower" services that monitor on your behalf.

From channels to a network

You don't need a channel with everyone you pay. Payments can hop across a chain of channels: you pay a node you're connected to, which pays the next one, and so on to the recipient.

The hops are linked with a cryptographic lock so that either the whole payment succeeds or none of it does — an intermediate node can't keep the money in the middle. Routing nodes charge tiny fees for forwarding.

Where Lightning shines

• Speed. Payments typically complete in seconds.
• Small amounts. Fees can be fractions of a cent, so tiny payments become practical.
• Privacy, in some respects. Individual channel payments don't appear on the blockchain.
• Bitcoin's security for settlement. Ultimately, channel balances settle on Bitcoin itself.

The trade-offs

Lightning is a layer 2 in the strict sense — it inherits Bitcoin's security for final settlement — but it isn't simply "Bitcoin, but faster":

• Liquidity is a real constraint. You can only send what's on your side of your channels, and only receive up to what's on the other side. Large payments can fail to find a route.
• You need to be online, or delegate watching. Self-custodial Lightning means your wallet, or a watchtower, must be able to respond to a cheating attempt.
• Channel state is a backup problem. Restoring a Lightning wallet isn't as simple as restoring from a recovery phrase; channel data matters, and losing it can mean force-closing channels.
• Opening and closing cost on-chain fees, which matter when the Bitcoin mempool is busy.
• Many popular Lightning apps are custodial. They're convenient precisely because the provider runs the channels — and holds the coins.

That last point is the one most people miss. A Lightning app that "just works" without any channel management is very often custodial: you hold a balance in someone else's system, with all the trade-offs that implies.

Lightning and SSP

SSP doesn't support Lightning. SSP holds your bitcoin in an on-chain 2-of-2 multisig vault and sends ordinary Bitcoin transactions, approved on both SSP Wallet and SSP Key.

That's a fit for savings and larger payments, where on-chain settlement and two-device approval matter most. Lightning suits a different job: frequent, small, fast payments, with the operational overhead that comes with channels. Many people use both — a secure on-chain vault for holdings, and a small Lightning wallet for spending, topped up as needed.

The honest summary

Lightning makes Bitcoin payments fast and cheap by moving them into two-party channels that settle on-chain only when opened and closed. It's genuinely clever engineering, built on multisig and time locks.

It also brings liquidity limits, an always-watching requirement and backup complexity — and many of the easiest Lightning apps quietly trade self-custody for convenience. Use it for what it's good at, and keep anything you can't afford to lose somewhere simpler.