{
  "$schema": "https://degreesofsatoshi.com/encyclopedia/schemas/article-v1.json",
  "schemaVersion": "1.0.0",
  "id": "lightning-force-close",
  "canonical": "https://degreesofsatoshi.com/encyclopedia/lightning-force-close/",
  "collection": "bitcoin",
  "title": "Lightning force closes: why funds can take time to return",
  "description": "Understand a Lightning force close, its delayed outputs, sweep transactions and the difference from a cooperative close.",
  "aliases": [
    "lightning force close waiting",
    "lightning force close waiting explained"
  ],
  "dates": {
    "published": "2026-10-02",
    "modified": "2026-10-02",
    "verified": "2026-10-02T19:29:20.637Z",
    "dataAsOf": "2026-10-02"
  },
  "authorship": {
    "publisher": "Degrees of Satoshi editorial project",
    "process": "AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied."
  },
  "quickAnswer": {
    "text": "A force close publishes a channel commitment transaction so a party can exit without obtaining a new closing agreement from its peer. It can involve delayed outputs and additional transactions before all funds are spendable. A cooperative close is jointly arranged and usually simpler. The exact delay, fees and recovery stages depend on channel type and outstanding payments, so a closed-channel label does not mean every satoshi is already available.",
    "claimId": "lightning-force-close-quick-answer",
    "sourceIds": [
      "x425-btc-ln-lifecycle",
      "x425-btc-ln-sweeping",
      "x425-btc-bolt3"
    ]
  },
  "keyFacts": [
    {
      "label": "Unilateral exit",
      "value": "Can use an existing commitment",
      "sourceIds": [
        "x425-btc-ln-lifecycle"
      ],
      "id": "unilateral-exit",
      "claimId": "lightning-force-close-fact-unilateral-exit"
    },
    {
      "label": "Delayed funds",
      "value": "Some outputs wait before they can be spent",
      "sourceIds": [
        "x425-btc-ln-sweeping"
      ],
      "id": "delayed-funds",
      "claimId": "lightning-force-close-fact-delayed-funds"
    },
    {
      "label": "Sweep",
      "value": "A later transaction can collect eligible outputs",
      "sourceIds": [
        "x425-btc-ln-sweeping"
      ],
      "id": "sweep",
      "claimId": "lightning-force-close-fact-sweep"
    }
  ],
  "prerequisites": [
    "lightning-payment-channels",
    "bitcoin-timelocks"
  ],
  "sections": [
    {
      "id": "agreement",
      "heading": "A force close uses an already signed commitment",
      "sourceIds": [
        "x425-btc-ln-lifecycle",
        "x425-btc-bolt3"
      ],
      "paragraphs": [
        "A cooperative close requires the parties to agree on a closing transaction. If a peer is unreachable or agreement fails, a party can instead publish the appropriate commitment it already holds. This is an exit mechanism, not an automatic refund of every original deposit.",
        "The balance and pending conditional payments in that state determine the outputs. Fees and the transactions needed to claim those outputs also affect the final result."
      ]
    },
    {
      "id": "example",
      "heading": "Count confirmations and spending eligibility separately",
      "sourceIds": [
        "x425-btc-ln-sweeping",
        "x425-btc-bolt3",
        "x425-btc-whitepaper"
      ],
      "paragraphs": [
        "Suppose a force-close transaction confirms and one output has a relative delay of 144 blocks. That output must satisfy its block delay before the applicable spend can be included. Reaching eligibility is still not the same as the sweep transaction confirming.",
        "At a ten-minute average, 144 blocks is roughly one day, but actual timing varies. Pending conditional payments can add separate timeout and claim stages."
      ]
    },
    {
      "id": "fees",
      "heading": "Check the pending-output view before concluding funds are lost",
      "sourceIds": [
        "x425-btc-ln-sweeping",
        "x425-btc-ln-disaster"
      ],
      "paragraphs": [
        "The sweeping system may group outputs or wait until spending them is economically worthwhile. A small output can remain uneconomical to collect when the required on-chain fee is large.",
        "Use the wallet’s documented pending-channel and sweep information to see whether funds are waiting for a delay, a fee decision or confirmation. Do not restore an old channel database in an attempt to undo a close."
      ]
    }
  ],
  "faq": [
    {
      "question": "Does force closing erase the channel balance?",
      "answer": "No. The commitment and its claim paths determine where funds can go. Recovery can involve delays and fees, so the final spendable amount and time need to be examined rather than inferred from the word closed.",
      "sourceIds": [
        "x425-btc-ln-sweeping",
        "x425-btc-bolt3"
      ]
    },
    {
      "question": "Are funds spendable immediately when the close transaction confirms?",
      "answer": "Not always. Some outputs are delayed, and pending payments may require further transactions. Even an eligible sweep still needs inclusion in a block.",
      "sourceIds": [
        "x425-btc-ln-sweeping"
      ]
    }
  ],
  "claims": [
    {
      "id": "lightning-force-close-quick-answer",
      "articleSlug": "lightning-force-close",
      "statement": "A force close publishes a channel commitment transaction so a party can exit without obtaining a new closing agreement from its peer. It can involve delayed outputs and additional transactions before all funds are spendable. A cooperative close is jointly arranged and usually simpler. The exact delay, fees and recovery stages depend on channel type and outstanding payments, so a closed-channel label does not mean every satoshi is already available.",
      "sourceIds": [
        "source-d0625e6983c0ac55",
        "source-9ed194ab4aaa2ccc",
        "source-b886d1d57cf59732"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-d0625e6983c0ac55",
          "locator": "Opening a channel; Sending funds through a payment channel; Closing a channel; Cooperatively; Non-cooperatively"
        },
        {
          "sourceId": "source-9ed194ab4aaa2ccc",
          "locator": "Types of funds that need to be swept; Local force closure; Remote force closure; Incoming HTLCs; Outgoing HTLCs; Batch sweeping; LNCLI and uneconomical sweeps"
        },
        {
          "sourceId": "source-b886d1d57cf59732",
          "locator": "Commitment Transaction; HTLC Outputs; Closing Transaction"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "Educational explanation. Product-specific behavior is scoped to the cited documentation, checked 2026-10-02.",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:29:20.637Z",
        "reviewer": "Independent automated verification — Codex /root/verify_ethereum_100, separate from the Bitcoin drafting agent",
        "notes": [
          "Checked local/remote and HTLC paths in BOLT3 plus LND sweeping. Output delay, eligibility and sweep confirmation are separate. Added disaster source for old database caution and timing source for144block arithmetic; no uniform output delay is asserted."
        ]
      }
    },
    {
      "id": "lightning-force-close-fact-unilateral-exit",
      "articleSlug": "lightning-force-close",
      "statement": "Unilateral exit: Can use an existing commitment",
      "sourceIds": [
        "source-d0625e6983c0ac55"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-d0625e6983c0ac55",
          "locator": "Opening a channel; Sending funds through a payment channel; Closing a channel; Cooperatively; Non-cooperatively"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:29:20.637Z",
        "reviewer": "Independent automated verification — Codex /root/verify_ethereum_100, separate from the Bitcoin drafting agent",
        "notes": [
          "Checked local/remote and HTLC paths in BOLT3 plus LND sweeping. Output delay, eligibility and sweep confirmation are separate. Added disaster source for old database caution and timing source for144block arithmetic; no uniform output delay is asserted."
        ]
      }
    },
    {
      "id": "lightning-force-close-fact-delayed-funds",
      "articleSlug": "lightning-force-close",
      "statement": "Delayed funds: Some outputs wait before they can be spent",
      "sourceIds": [
        "source-9ed194ab4aaa2ccc"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-9ed194ab4aaa2ccc",
          "locator": "Types of funds that need to be swept; Local force closure; Remote force closure; Incoming HTLCs; Outgoing HTLCs; Batch sweeping; LNCLI and uneconomical sweeps"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:29:20.637Z",
        "reviewer": "Independent automated verification — Codex /root/verify_ethereum_100, separate from the Bitcoin drafting agent",
        "notes": [
          "Checked local/remote and HTLC paths in BOLT3 plus LND sweeping. Output delay, eligibility and sweep confirmation are separate. Added disaster source for old database caution and timing source for144block arithmetic; no uniform output delay is asserted."
        ]
      }
    },
    {
      "id": "lightning-force-close-fact-sweep",
      "articleSlug": "lightning-force-close",
      "statement": "Sweep: A later transaction can collect eligible outputs",
      "sourceIds": [
        "source-9ed194ab4aaa2ccc"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-9ed194ab4aaa2ccc",
          "locator": "Types of funds that need to be swept; Local force closure; Remote force closure; Incoming HTLCs; Outgoing HTLCs; Batch sweeping; LNCLI and uneconomical sweeps"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:29:20.637Z",
        "reviewer": "Independent automated verification — Codex /root/verify_ethereum_100, separate from the Bitcoin drafting agent",
        "notes": [
          "Checked local/remote and HTLC paths in BOLT3 plus LND sweeping. Output delay, eligibility and sweep confirmation are separate. Added disaster source for old database caution and timing source for144block arithmetic; no uniform output delay is asserted."
        ]
      }
    }
  ],
  "sources": [
    {
      "id": "x425-btc-ln-lifecycle",
      "label": "The lifecycle of a payment channel",
      "publisher": "Lightning Labs",
      "url": "https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/payment-channels/lifecycle-of-a-payment-channel.md",
      "locator": "Opening a channel; Sending funds through a payment channel; Closing a channel; Cooperatively; Non-cooperatively",
      "note": "Cooperative versus unilateral closes and confirmation/delay requirements.",
      "version": "Pinned Lightning Labs documentation revision; LND/Loop implementation scope",
      "checkedAt": "2026-10-02T18:53:57.295Z",
      "contentSha256": "4e1188e6df305f081372400c0b4ad8af00406002b9cdcbfcb994f700994bb67b",
      "recordId": "source-d0625e6983c0ac55"
    },
    {
      "id": "x425-btc-ln-sweeping",
      "label": "Understanding Sweeping",
      "publisher": "Lightning Labs",
      "url": "https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/payment-channels/understanding-sweeping.md",
      "locator": "Types of funds that need to be swept; Local force closure; Remote force closure; Incoming HTLCs; Outgoing HTLCs; Batch sweeping; LNCLI and uneconomical sweeps",
      "note": "Claiming outputs after channel closures depends on confirmation and applicable delays.",
      "version": "Pinned Lightning Labs documentation revision; LND/Loop implementation scope",
      "checkedAt": "2026-10-02T18:53:57.424Z",
      "contentSha256": "000318eeb9e0a552240c6044875f498c42bab7a75bf1aab5ecf6de708024cc86",
      "recordId": "source-9ed194ab4aaa2ccc"
    },
    {
      "id": "x425-btc-bolt3",
      "label": "BOLT 3: Bitcoin Transaction and Script Formats",
      "publisher": "Lightning specification contributors",
      "url": "https://raw.githubusercontent.com/lightning/bolts/1aadb719b4007c4cea0ba6e36b08c4fb53788dee/03-transactions.md",
      "locator": "Commitment Transaction; HTLC Outputs; Closing Transaction",
      "note": "Commitment output delays and conditional HTLC settlement on chain.",
      "version": "Pinned BOLTs revision",
      "checkedAt": "2026-10-02T18:53:57.097Z",
      "contentSha256": "27ffbf1ae436f257bff3f255b4d1e4d4bbf8597fb1e2533d7ff9b66f4fe38d43",
      "recordId": "source-b886d1d57cf59732"
    },
    {
      "id": "x425-btc-whitepaper",
      "label": "Bitcoin: A Peer-to-Peer Electronic Cash System",
      "publisher": "Satoshi Nakamoto",
      "url": "https://bitcoin.org/bitcoin.pdf",
      "locator": "Sections 4, 6, 7, 10 and 11",
      "note": "Independent hash attempts, incentives, transaction collaboration limits and Poisson block-arrival approximation.",
      "version": "2008 paper",
      "checkedAt": "2026-10-02T18:53:58.187Z",
      "contentSha256": "b1674191a88ec5cdd733e4240a81803105dc412d6c6708d53ab94fc248f4f553",
      "recordId": "source-0e46aca4dbc5a030"
    },
    {
      "id": "x425-btc-ln-disaster",
      "label": "Disaster recovery",
      "publisher": "Lightning Labs",
      "url": "https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/lightning-network-tools/lnd/disaster-recovery.md",
      "locator": "1. Recover as much data as you can; 2. Set up a new node; 3. Begin the recovery process; B) Static channel backup; C) Force-closing all other channels",
      "note": "Recovery procedures and need to avoid outdated channel-state reuse.",
      "version": "Pinned Lightning Labs documentation revision; LND/Loop implementation scope",
      "checkedAt": "2026-10-02T18:53:57.281Z",
      "contentSha256": "82993b7b39b5a48f38b7196c6e68c61ea24deb5e199249a0daca3894a7ae20e5",
      "recordId": "source-df81d0f88f3e71df"
    }
  ],
  "related": {
    "articles": [
      "lightning-payment-channels",
      "bitcoin-timelocks",
      "lightning-watchtowers",
      "lightning-payment-status"
    ],
    "dossiers": [],
    "wallets": []
  },
  "revisionHistory": [
    {
      "date": "2026-10-02",
      "kind": "published",
      "summary": "First publication after primary-source research and separate automated verification."
    }
  ],
  "citation": "Degrees of Satoshi editorial project. “Lightning force closes: why funds can take time to return.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/lightning-force-close/"
}