Splice-Out

Splice-out is the act of moving bitcoin out of an open Lightning channel to an on-chain address in a single cooperative transaction, while keeping the channel operational. It is the mirror image of splice-in: instead of adding capacity, it withdraws some of the channel's balance on-chain and leaves the channel running at a reduced size. This replaces the old, costly pattern of closing a channel just to free up a portion of its funds — a pattern that burned two on-chain transactions, destroyed accumulated routing history, and took the channel offline for the duration.

Spending the Funding Output

Mechanically, the two peers build a transaction that spends the channel's existing funding output, sends part of the value to an external on-chain destination, and routes the remainder into a new, smaller funding output that the channel continues from. Both peers negotiate and sign this interactively, and critically, the channel does not pause while the splice confirms: implementations maintain commitment state for both the old and new funding outputs during the pending window, so payments keep flowing and either version can be enforced if things go wrong. Once the splice transaction confirms to an agreed depth, the old funding output is history and the channel proceeds from the new one, with its identity, peer relationship, and off-chain state intact. The splicing protocol handles the bookkeeping; from the outside it looks like nothing happened except that an on-chain payment appeared.

Practical Uses

Splice-out turns a Lightning channel from a locked box into a working account. A routing node operator can sweep accumulated fee revenue to cold storage without sacrificing the channel that earned it. A merchant accepting Lightning payments can periodically drain the local balance to an on-chain treasury address while keeping receive capacity live. An individual can pay a large on-chain invoice — an exchange deposit, a hardware purchase — directly from channel funds, in one transaction, without a close-and-reopen cycle that would cost two transactions and weeks of re-established routing reputation. For miners running Lightning-enabled payout flows, the same logic applies: liquidity parked in a payment channel stays productive right up until the moment part of it is needed on-chain.

Trade-offs and Requirements

Splicing is cooperative by construction: both peers must support the protocol and be online to negotiate, so you cannot splice out of a channel whose counterparty is unresponsive — a force close remains the unilateral exit. Support has been spreading across major Lightning implementations since the protocol's specification effort matured, but it is not yet universal, so channel partners' software matters when you plan around this capability. There is also a mempool-dependent confirmation wait before the new channel state is fully anchored, though payments continue during it. None of these caveats change the headline: the marginal cost of accessing on-chain liquidity from a healthy channel has dropped to a single cooperative transaction.

Why It Matters for Sovereignty

The deeper significance is what splice-out does to the custody calculus. One reason users historically parked funds with custodial Lightning providers was flexibility — moving between on-chain and Lightning was clumsy with self-managed channels. Splicing removes much of that clumsiness: your Lightning node becomes a single pool of bitcoin that is simultaneously spendable off-chain and reachable on-chain, all under your own keys. Splice-out is the capacity-reducing counterpart to splice-in, and like all splices it rewrites the funding output while preserving everything that makes an established channel valuable: uptime, reputation, and the routing relationships you have already paid to build.

Operationally, treat splice-outs like any other on-chain spend: batch them when fees are low, verify the destination address through your own node, and remember that the on-chain payment is visible to chain surveillance even though the channel activity around it is not. A routing node that sweeps revenue on a calm Sunday instead of a congested Monday keeps more of what its channels earned — the protocol removed the ceremony, but fee discipline is still yours to apply.