Core Lightning v26.04 Release Candidate 2, tagged April 2, 2026, has done something unremarkable on its surface: it added two new commands to the codebase. What those commands actually represent is the maturation of a feature that has sat in experimental purgatory for years — splicing, the ability to add funds to or remove funds from a Lightning channel while keeping it active and fully functional throughout the entire process. For the first time, `splicein` and `spliceout` are not hidden behind experimental flags. They are documented, stable, ready for wallet developers to expose to end users. This is the threshold moment: splicing stops being something developers talk about and starts being something users experience.
The Lightning Network landscape is dominated by three implementations: Lightning Labs' LND, Blockstream's Core Lightning (CLN), and ACINQ's Eclair. LND remains the most widely deployed, but CLN has consistently moved first on user-experience infrastructure — it was first with dual-funded channels, first with large-channel support, and now it is first to graduate splicing from experimental to stable. This matters because wallet developers watch CLN's releases for signals about what has matured enough to ship. When CLN marks something stable, the ecosystem begins to move. LND and Eclair will follow, but the gap between their own splice implementations and CLN's production code will narrow the moment v26.04 stable lands. That release is expected within 1–2 weeks of RC2.
Here is what `splicein` and `spliceout` actually do, stripped of the protocol language. Today, if you want to add Bitcoin to a Lightning channel, you close the channel (on-chain transaction), wait for one confirmation, and open a new one (another on-chain transaction). Your channel is dead during this window — you cannot send or receive payments. The whole process takes minutes at best, and costs you two full on-chain fees. With splicing, you initiate a splice command while the channel is open. The channel keeps working. Payments flow in and out. Then a single on-chain transaction settles the resize. When that transaction confirms, your channel is the new size, with no downtime, one fee instead of two. For users who manage nodes or who use advanced wallet features like Greenlight or Blockstream Green, this is a qualitative improvement in operational ease. For everyday users in a mainstream wallet, it is the difference between a smooth experience and a jarring interruption.
The timing here is not coincidental. Bitcoin on-chain fees sit at 1–4 sat/vB for various confirmation targets, according to Mempool.space at block height 943,493. This is a rare, extended low-fee environment. Node operators and wallet providers have a window right now — measured in weeks or months, not years — to perform channel maintenance and liquidity reshuffling at minimal cost. Splice makes that reshuffling transactional rather than disruptive. The RC2 release also introduces `cross-splice`: the ability to move funds between two channels in a single on-chain transaction by specifying a second channel ID as the splice destination. This is the first time the protocol has formalized multi-channel atomic operations at the user command level. It turns channel liquidity management from a sequence of sequential, expensive close-and-reopen operations into a single coordinated move. For node operators running multiple channels with unbalanced liquidity, this is the operation they have been implicitly asking for since 2018.
The broader feature set in RC2 signals a deliberate shift toward Lightning as a primary payment layer, not a secondary one. The new `payer-note` field in xpay, the BOLT12 fronting nodes feature (which lets users specify preferred peers for help routing payers across both BOLT11 and BOLT12), and the decoded offer descriptions in RPC responses — these are all UX scaffolding. They make it easier for wallet developers to build Lightning-first applications without forcing users to understand the underlying protocol complexity. Parallel pathfinding improvements in askrene and stricter BOLT spec compliance for splice commitments are the reliability undergirding. Across 480 commits in 82 days by 23 authors since v25.09, the velocity and breadth of the codebase signal a team that is not maintaining an experimental protocol feature — it is shipping infrastructure.
Our read: Splicing's graduation to stable is a material inflection point for Lightning UX, not because splicing is new — it has been in the works for years — but because it crosses the threshold from "ecosystem infrastructure that developers discuss" to "user-facing feature that wallet providers ship." The convergence of CLN's stable release (imminent), historically low on-chain fees (present now), and cross-splice atomicity (newly documented) creates a rare moment where first-movers in wallet UX have a clear advantage. Wallets that expose splicing in their UI within 60 days of v26.04 stable will own the narrative around "seamless on-chain to Lightning balance management" in an otherwise crowded market. Greenlight and Blockstream Green are obvious candidates; watch for smaller, mobile-first wallets to follow within weeks. The risk to this timeline is regulatory friction around channel management tools or wallet provider reluctance to expose splicing UI before competitive parity across LND and Eclair — that could push adoption to late Q2 or Q3. Two things would change this read: (1) If v26.04 stable is delayed beyond mid-April, the fee window narrows and first-wave adoption momentum stalls. (2) If Mempool fees spike above 15 sat/vB sustained, the economic advantage of splicing as a low-cost resizing tool disappears, and adoption shifts to next cycle's low-fee environment.
Watch for: (1) The stable v26.04 release tag on GitHub within 1–2 weeks — confirmation that `splicein` and `spliceout` are production-ready and the official starting gun for wallet integration. (2) The first wallet UI to expose splicing natively — screenshot it, track the adoption curve, and measure whether it meaningfully reduces support burden around channel management. (3) LND's response: whether Lightning Labs' next release includes splice parity with CLN or signals a delay to the next major version cycle — parity adoption curves tell you whether CLN's leadership here is permanent or temporary. (4) The April 2026 BPI/Fedi/Cornell study on policy and financial privacy UX: its findings on whether splice-style workflow improvements move the needle on non-technical user adoption will validate (or challenge) whether CLN's bet on UX infrastructure actually moves users, or if the friction remains elsewhere in the stack.