Feedback
Sign in./start

Site navigation

Theme

Learn

  • Roadmaps

Build

  • Projects
  • Developer Tools

Contribute

  • Open Source Projects
  • Issues
  • Reviews
  • First Contribution
  • BountiesSoon
  • Feedback

Prove

  • Builders

Ecosystem

  • Partners
  • Get Funded↗
  • HackathonsSoon
Sign in./start-building

Become an Open Source Builder. Learn. Build. Contribute. Prove.

Feedback welcome — open a GitHub issue.

Learn

RoadmapsStart Building

Build

ProjectsDeveloper Tools

Contribute

Open Source ProjectsIssuesReviewsFirst ContributionSupportFeedback

Prove

Builders Directory

Account

Sign in

Legal

PrivacyTermsCredits

© 2026 Pull // code MIT · curriculum CC BY-SA 4.0

PrivacyTermsCredits

lesson // lightning

Dual Funding & Splicing

Add or remove capacity without closing the channel.

advanced5 days

Public lesson — sign in to track progress on this roadmap.

./sign-in

On this page

Learning objectives

  • Explain dual-funded channel opens
  • Describe splicing as on-chain capacity adjustment
  • Know that interactive funding flows are implementation-sensitive

study // plan

Lessons are primers. Start with Step 1 (required reading) when present, then follow the numbered steps in the article. Depth comes from primary sources, labs, reflection, and evidence.

Research on Bitcoin Search
splicingdual fundingchannel capacityinteractive-txBOLT2

Step 1 // Required reading

Complete these before the numbered steps in the lesson body. Links are listed here once — not repeated below.

  • boltBOLT2 Peer Protocol (interactive funding & splicing)

    Dual-funded opens and splicing are defined in the interactive-tx section.

Reflection prompts

  1. Explain Dual Funding & Splicing to a teammate without jargon - what problem does it solve?
  2. What would break in production if you misunderstood Dual Funding & Splicing?
  3. Which BOLT (or implementation doc) is the source of truth for this topic, and what did you verify there?

Lab // Dual-fund vs splice brief

Complete Steps 2–3. From BOLT2 / Optech / CLN docs, write when you would dual-fund at open vs splice later. Note support on the stack you ship. Optional: attempt a dual-fund or splice on a supporting Polar/CLN lab.

evidence required

  • ·One-paragraph dual-fund vs splice decision guide
  • ·Implementation support note (LND/CLN/LDK version you checked)
  • ·Link to BOLT2 interactive-tx or Optech splicing section
  • ·Optional: lab command/UI output
  1. 01

    Worked mental model

    Re-read the diagrams in this lesson once out loud in plain language. If you cannot explain the flow to a friend without jargon, pause and revisit the Mastering Bitcoin / Mastering Lightning chapters linked in Resources. Chapter references are intentional, not decorative.

  2. 02

    Hands-on habit

    Every protocol idea should be paired with one local experiment. That habit turns reading into builder instinct.

    1. Reproduce the happy path on regtest (or Polar for Lightning)
    2. Break it on purpose (wrong fee, expired invoice, offline peer)
    3. Write down what error you saw and which layer produced it (wallet, node, mempool, peer)
  3. 03

    Glossary check

    Pick three terms from this lesson and define them in one sentence each without opening notes. Weak definitions mean the lesson is not finished yet.

  4. 04

    Resource order

    Use Resources in order: narrative book chapter first, then BIP/BOLT for precision, then implementation docs for commands. Jumping straight to RPC flags without the mental model creates brittle knowledge.

Classic channels are often single-funded. Dual funding lets both sides contribute at open. Splicing adjusts channel capacity later with an on-chain transaction without losing the channel relationship.

Complete Step 1 // Required reading in the study plan above, then continue here. This closes Channels & HTLCs.

Step 2 — Core idea: reshape capacity without teardown

Liquidity needs change. Closing and reopening wastes fees and downtime. Splicing and dual funding make the network more capital-efficient.

Analogy: Dual funding is both roommates paying the security deposit. Splicing is adding money to the joint jar (or withdrawing some) without ending the lease.

Loading diagram…

Interactive on-chain transactions reshape channel capacity.

Feature availability

Support differs across LND/CLN/LDK versions. Prototype on regtest with the stack you ship.

Done when: You can say when dual-fund beats single-fund at open, and when splice beats close/reopen.

Step 3 — Decision brief (lab)

Write the dual-fund vs splice guide and check docs for your target implementation. Optional hands-on if your lab supports it.

Common mistakes

  • Assuming splice always beats open/close without fee math
  • Interrupting interactive funding flows mid-protocol
  • Neglecting backup updates after capacity changes

Done when: Lab evidence (decision paragraph + support note + source) is complete. Complete the chapter quiz when prompted.

Next lesson

Liquidity Operations — loops, swaps, rebalancing, and inbound capacity.

further reading

  • docsCore Lightning splicing
  • articleBitcoin Optech: Splicing

review // club

Chapter review picks

Practice on real Lightning OSS changes tied to this chapter. Read the diff, use the checklist, and optionally paste your review comment URL in your lab notes.

  • CLN splicing documentation

    Review a splicing-related PR or doc change and note how capacity changes without closing the channel.

    pr review
    capacity managementon-chain interaction
    50 min·advancedopen on GitHub
  • Polar local dev GFI

    Polar powers most labs - review a small issue that improves local Lightning learning.

    gfi
    developer UXregtest
    25 min·beginneropen on GitHub
  • CLN plugin docs good first issue

    Pick a documentation GFI related to channels or plugins and draft a review comment on clarity.

    gfi
    readabilityexamples
    30 min·beginneropen on GitHub
  • LND HTLC failure handling PRs

    Find an HTLC-related PR and trace how failures unwind along the path.

    pr review
    timelockserror propagation
    45 min·advancedopen on GitHub
review checklist
  1. Does the change solve the stated problem?
  2. Are edge cases and rollout behavior covered?
  3. Are tests or test vectors included?
  4. Is the diff minimal and clearly explained?

More repos and GFIs on /discover and /issues.

build // next

Apply this chapter in a project

You have the concepts — ship something small to prove it. These Pull projects connect directly to what you just studied.

  • project // ln-node-dashboard

    Node Ops Dashboard
    ./spec./submit

discussion

Discussion

prevChannel LifecyclenextLiquidity Operations

On this page

Press Shift + ? for keyboard shortcuts.

Press R to research on Bitcoin Search.

No questions yet — be the first to ask.