{
  "$schema": "https://degreesofsatoshi.com/encyclopedia/schemas/article-v1.json",
  "schemaVersion": "1.0.0",
  "id": "lightning-payment-channels",
  "canonical": "https://degreesofsatoshi.com/encyclopedia/lightning-payment-channels/",
  "collection": "bitcoin",
  "title": "Lightning channels: balances, commitments and closing",
  "description": "Understand how a Lightning payment channel updates a shared balance off-chain and how funding, commitment transactions and closing connect it to Bitcoin.",
  "aliases": [],
  "dates": {
    "published": "2026-10-02",
    "modified": "2026-10-02",
    "verified": "2026-10-02T18:15:23.891Z",
    "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 Lightning payment channel lets participants update their claims on bitcoin committed to a funding output without publishing every payment as a separate Bitcoin transaction. Commitment transactions and channel rules provide on-chain enforcement paths. Opening, closing, liquidity and monitoring requirements still matter.",
    "claimId": "lightning-payment-channels-quick-answer",
    "sourceIds": [
      "bolt2"
    ]
  },
  "keyFacts": [
    {
      "label": "Funding",
      "value": "Channel establishment commits funds through a Bitcoin funding transaction.",
      "sourceIds": [
        "bolt2"
      ],
      "id": "funding",
      "claimId": "lightning-payment-channels-fact-funding"
    },
    {
      "label": "Updates",
      "value": "Participants exchange messages and signatures that advance the channel state.",
      "sourceIds": [
        "bolt2"
      ],
      "id": "updates",
      "claimId": "lightning-payment-channels-fact-updates"
    },
    {
      "label": "Exit",
      "value": "Cooperative closing and unilateral commitment-based closing have different requirements.",
      "sourceIds": [
        "bolt2"
      ],
      "id": "exit",
      "claimId": "lightning-payment-channels-fact-exit"
    }
  ],
  "prerequisites": [
    "lightning-network-explained"
  ],
  "sections": [
    {
      "id": "balance",
      "heading": "Move claims within an existing allocation",
      "sourceIds": [
        "bolt2"
      ],
      "paragraphs": [
        "For a simplified example, a channel has 100,000 satoshis of capacity, with 70,000 on Alice’s side and 30,000 on Bob’s. A 10,000-satoshi payment from Alice to Bob shifts the allocation toward 60,000 and 40,000, before accounting for actual reserves, pending HTLCs and fees.",
        "No new bitcoin is created by this update. The parties change which claims can be enforced against the channel’s funding."
      ]
    },
    {
      "id": "routing",
      "heading": "A network payment can cross multiple channels",
      "sourceIds": [
        "bolt2",
        "bolt7"
      ],
      "paragraphs": [
        "Conditional payments allow a route to link transfers through intermediate nodes. Each hop needs usable capacity in the right direction and acceptable fee and timing conditions.",
        "A large total channel capacity does not guarantee that a particular payment route is available. Capacity placement, pending transfers and individual channel limits affect routing."
      ]
    },
    {
      "id": "closing",
      "heading": "On-chain enforcement has costs and timing",
      "sourceIds": [
        "bolt2"
      ],
      "paragraphs": [
        "Participants may agree on a cooperative close, or a party may publish a commitment transaction under the channel’s rules. Unilateral paths can involve delay and additional transactions.",
        "Keeping correct channel state and responding within relevant timing conditions are part of the security model. A channel is not simply a bank balance that remains safe under every backup or offline behavior."
      ]
    }
  ],
  "faq": [
    {
      "question": "Does each Lightning payment create a Bitcoin block transaction?",
      "answer": "No. Ordinary channel updates occur off-chain. Funding and closing or dispute-enforcement transactions connect the channel’s state to the Bitcoin chain.",
      "sourceIds": [
        "bolt2"
      ]
    }
  ],
  "claims": [
    {
      "id": "lightning-payment-channels-quick-answer",
      "articleSlug": "lightning-payment-channels",
      "statement": "A Lightning payment channel lets participants update their claims on bitcoin committed to a funding output without publishing every payment as a separate Bitcoin transaction. Commitment transactions and channel rules provide on-chain enforcement paths. Opening, closing, liquidity and monitoring requirements still matter.",
      "sourceIds": [
        "source-b9dd1646f089b1a7"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-b9dd1646f089b1a7",
          "locator": "Channel Establishment; Forwarding HTLCs; Channel Close"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T18:15:23.891Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read BOLT 2 Channel Establishment, commitment transitions, Forwarding HTLCs and Channel Close, plus BOLT 7 routing constraints. Funding, signed updates and cooperative/unilateral exits remain separate.",
          "Recomputed 70,000/30,000 allocation shifted by 10,000 to 60,000/40,000; the example excludes reserves, in-flight HTLCs and fees explicitly."
        ]
      }
    },
    {
      "id": "lightning-payment-channels-fact-funding",
      "articleSlug": "lightning-payment-channels",
      "statement": "Funding: Channel establishment commits funds through a Bitcoin funding transaction.",
      "sourceIds": [
        "source-b9dd1646f089b1a7"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-b9dd1646f089b1a7",
          "locator": "Channel Establishment; Forwarding HTLCs; Channel Close"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T18:15:23.891Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read BOLT 2 Channel Establishment, commitment transitions, Forwarding HTLCs and Channel Close, plus BOLT 7 routing constraints. Funding, signed updates and cooperative/unilateral exits remain separate.",
          "Recomputed 70,000/30,000 allocation shifted by 10,000 to 60,000/40,000; the example excludes reserves, in-flight HTLCs and fees explicitly."
        ]
      }
    },
    {
      "id": "lightning-payment-channels-fact-updates",
      "articleSlug": "lightning-payment-channels",
      "statement": "Updates: Participants exchange messages and signatures that advance the channel state.",
      "sourceIds": [
        "source-b9dd1646f089b1a7"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-b9dd1646f089b1a7",
          "locator": "Channel Establishment; Forwarding HTLCs; Channel Close"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T18:15:23.891Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read BOLT 2 Channel Establishment, commitment transitions, Forwarding HTLCs and Channel Close, plus BOLT 7 routing constraints. Funding, signed updates and cooperative/unilateral exits remain separate.",
          "Recomputed 70,000/30,000 allocation shifted by 10,000 to 60,000/40,000; the example excludes reserves, in-flight HTLCs and fees explicitly."
        ]
      }
    },
    {
      "id": "lightning-payment-channels-fact-exit",
      "articleSlug": "lightning-payment-channels",
      "statement": "Exit: Cooperative closing and unilateral commitment-based closing have different requirements.",
      "sourceIds": [
        "source-b9dd1646f089b1a7"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-b9dd1646f089b1a7",
          "locator": "Channel Establishment; Forwarding HTLCs; Channel Close"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T18:15:23.891Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read BOLT 2 Channel Establishment, commitment transitions, Forwarding HTLCs and Channel Close, plus BOLT 7 routing constraints. Funding, signed updates and cooperative/unilateral exits remain separate.",
          "Recomputed 70,000/30,000 allocation shifted by 10,000 to 60,000/40,000; the example excludes reserves, in-flight HTLCs and fees explicitly."
        ]
      }
    }
  ],
  "sources": [
    {
      "id": "bolt2",
      "label": "BOLT 2: Peer Protocol for Channel Management",
      "publisher": "Lightning specification contributors",
      "url": "https://raw.githubusercontent.com/lightning/bolts/1aadb719b4007c4cea0ba6e36b08c4fb53788dee/02-peer-protocol.md",
      "locator": "Channel Establishment; Forwarding HTLCs; Channel Close",
      "note": "Channel funding, commitment updates, forwarding and channel closing.",
      "version": null,
      "checkedAt": "2026-10-02T17:22:20.750Z",
      "contentSha256": "1b491b10b6ff92aa558df6aa9b70f4bd432cdded0c0c8087b9342bc57846f0c9",
      "recordId": "source-b9dd1646f089b1a7"
    },
    {
      "id": "bolt7",
      "label": "BOLT 7: P2P Node and Channel Discovery",
      "publisher": "Lightning specification contributors",
      "url": "https://raw.githubusercontent.com/lightning/bolts/1aadb719b4007c4cea0ba6e36b08c4fb53788dee/07-routing-gossip.md",
      "locator": "The channel_update Message; HTLC Fees; Example; fee_base_msat; fee_proportional_millionths",
      "note": "Direction-specific advertised routing fees and channel update parameters.",
      "version": null,
      "checkedAt": "2026-10-02T17:22:20.753Z",
      "contentSha256": "b7fb6e94e4efe29ab0011432874c2be1da8104b80f219d23ca5d375baeebe35a",
      "recordId": "source-d55abd3fe3dfc8b1"
    }
  ],
  "related": {
    "articles": [
      "lightning-inbound-liquidity",
      "lightning-routing-fees",
      "bitcoin-timelocks"
    ],
    "dossiers": [],
    "wallets": []
  },
  "revisionHistory": [
    {
      "date": "2026-10-02",
      "kind": "published",
      "summary": "Initial Bitcoin encyclopedia entry at this permanent URL."
    },
    {
      "date": "2026-10-02",
      "kind": "publishing-format",
      "summary": "Added reusable claims, explicit source locators, and matching Markdown and JSON. This publishing change does not itself establish factual verification."
    }
  ],
  "citation": "Degrees of Satoshi editorial project. “Lightning channels: balances, commitments and closing.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/lightning-payment-channels/"
}