{
  "$schema": "https://degreesofsatoshi.com/encyclopedia/schemas/article-v1.json",
  "schemaVersion": "1.0.0",
  "id": "lightning-inbound-liquidity",
  "canonical": "https://degreesofsatoshi.com/encyclopedia/lightning-inbound-liquidity/",
  "collection": "bitcoin",
  "title": "Lightning inbound liquidity: why receiving needs capacity",
  "description": "Learn why a Lightning wallet can have funds available to send but insufficient capacity to receive, with a simple channel-balance example.",
  "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": "Inbound Lightning liquidity is usable channel capacity that peers can move toward your side when you receive a payment. Outbound liquidity supports payments in the opposite direction. A channel’s total capacity does not describe how much you can receive or send now; balance placement and channel constraints matter.",
    "claimId": "lightning-inbound-liquidity-quick-answer",
    "sourceIds": [
      "lnd-liquidity",
      "bolt2"
    ]
  },
  "keyFacts": [
    {
      "label": "Direction",
      "value": "Inbound and outbound liquidity describe different directions through a channel.",
      "sourceIds": [
        "lnd-liquidity"
      ],
      "id": "direction",
      "claimId": "lightning-inbound-liquidity-fact-direction"
    },
    {
      "label": "Balance",
      "value": "A payment shifts allocation between channel participants.",
      "sourceIds": [
        "bolt2"
      ],
      "id": "balance",
      "claimId": "lightning-inbound-liquidity-fact-balance"
    },
    {
      "label": "Constraints",
      "value": "Reserves, pending HTLCs and routing limits reduce usable capacity.",
      "sourceIds": [
        "bolt2"
      ],
      "id": "constraints",
      "claimId": "lightning-inbound-liquidity-fact-constraints"
    }
  ],
  "prerequisites": [
    "lightning-payment-channels"
  ],
  "sections": [
    {
      "id": "example",
      "heading": "Separate capacity from available receiving room",
      "sourceIds": [
        "lnd-liquidity",
        "bolt2"
      ],
      "paragraphs": [
        "Ignoring reserves and fees, a 100,000-satoshi channel with 90,000 on your side and 10,000 on your peer’s has roughly 90,000 of sending room and 10,000 of receiving room on that channel. The full 100,000 is not available in both directions simultaneously.",
        "Actual limits can be lower because some funds are reserved or committed to pending transfers. The example explains direction; it is not a wallet quote."
      ]
    },
    {
      "id": "change",
      "heading": "Sending can create room to receive later",
      "sourceIds": [
        "lnd-liquidity"
      ],
      "paragraphs": [
        "When a successful payment moves your balance toward the peer’s side, that channel can gain receiving room. Receiving moves it back toward your side. This is a rearrangement of funds, not a yield payment.",
        "Rebalancing services and liquidity purchases can change placement, but introduce fees and service-specific conditions. Opening a channel funded entirely from your side does not automatically solve an inbound shortage."
      ]
    },
    {
      "id": "network",
      "heading": "A local balance is not the whole route",
      "sourceIds": [
        "bolt2",
        "bolt7"
      ],
      "paragraphs": [
        "A recipient can have suitable last-hop inbound capacity while earlier hops are constrained. A sender can have outbound balance while no usable path reaches the recipient for the requested amount.",
        "A failed route therefore does not prove that the recipient has no bitcoin or that the network has no capacity. It indicates that the attempted path and conditions did not complete."
      ]
    }
  ],
  "faq": [
    {
      "question": "Does opening a larger self-funded channel guarantee I can receive more?",
      "answer": "No. If most funds begin on your side, that primarily increases outbound capacity. Receiving depends on usable funds on the peer side and on the rest of the route.",
      "sourceIds": [
        "lnd-liquidity",
        "bolt2"
      ]
    }
  ],
  "claims": [
    {
      "id": "lightning-inbound-liquidity-quick-answer",
      "articleSlug": "lightning-inbound-liquidity",
      "statement": "Inbound Lightning liquidity is usable channel capacity that peers can move toward your side when you receive a payment. Outbound liquidity supports payments in the opposite direction. A channel’s total capacity does not describe how much you can receive or send now; balance placement and channel constraints matter.",
      "sourceIds": [
        "source-648d3322879b342a",
        "source-b9dd1646f089b1a7"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-648d3322879b342a",
          "locator": "Payments; Receiving funds; Routing liquidity"
        },
        {
          "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": [
          "Original lnd-liquidity citation was a landing page lacking inbound/outbound explanation. Independently retrieved and read its linked Understanding Liquidity page; catalog URL/title/locators were corrected.",
          "Receiving funds/Payments/Routing liquidity and BOLT 2 reserves support direction and routing limits. Checked 90,000 outbound/10,000 inbound illustrative split; no guarantee of route availability."
        ]
      }
    },
    {
      "id": "lightning-inbound-liquidity-fact-direction",
      "articleSlug": "lightning-inbound-liquidity",
      "statement": "Direction: Inbound and outbound liquidity describe different directions through a channel.",
      "sourceIds": [
        "source-648d3322879b342a"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-648d3322879b342a",
          "locator": "Payments; Receiving funds; Routing liquidity"
        }
      ],
      "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": [
          "Original lnd-liquidity citation was a landing page lacking inbound/outbound explanation. Independently retrieved and read its linked Understanding Liquidity page; catalog URL/title/locators were corrected.",
          "Receiving funds/Payments/Routing liquidity and BOLT 2 reserves support direction and routing limits. Checked 90,000 outbound/10,000 inbound illustrative split; no guarantee of route availability."
        ]
      }
    },
    {
      "id": "lightning-inbound-liquidity-fact-balance",
      "articleSlug": "lightning-inbound-liquidity",
      "statement": "Balance: A payment shifts allocation between channel participants.",
      "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": [
          "Original lnd-liquidity citation was a landing page lacking inbound/outbound explanation. Independently retrieved and read its linked Understanding Liquidity page; catalog URL/title/locators were corrected.",
          "Receiving funds/Payments/Routing liquidity and BOLT 2 reserves support direction and routing limits. Checked 90,000 outbound/10,000 inbound illustrative split; no guarantee of route availability."
        ]
      }
    },
    {
      "id": "lightning-inbound-liquidity-fact-constraints",
      "articleSlug": "lightning-inbound-liquidity",
      "statement": "Constraints: Reserves, pending HTLCs and routing limits reduce usable capacity.",
      "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": [
          "Original lnd-liquidity citation was a landing page lacking inbound/outbound explanation. Independently retrieved and read its linked Understanding Liquidity page; catalog URL/title/locators were corrected.",
          "Receiving funds/Payments/Routing liquidity and BOLT 2 reserves support direction and routing limits. Checked 90,000 outbound/10,000 inbound illustrative split; no guarantee of route availability."
        ]
      }
    }
  ],
  "sources": [
    {
      "id": "lnd-liquidity",
      "label": "Understanding Liquidity",
      "publisher": "Lightning Labs",
      "url": "https://docs.lightning.engineering/the-lightning-network/liquidity/understanding-liquidity",
      "locator": "Payments; Receiving funds; Routing liquidity",
      "note": "Channel balance placement determines the direction in which a payment can move.",
      "version": null,
      "checkedAt": "2026-10-02T17:55:17.054Z",
      "contentSha256": "55a8fb3d43edeb66958dce5676a435022f75853b8076d6d1df70ee923bc0cc9f",
      "recordId": "source-648d3322879b342a"
    },
    {
      "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-payment-channels",
      "lightning-routing-fees",
      "lightning-network-explained"
    ],
    "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 inbound liquidity: why receiving needs capacity.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/lightning-inbound-liquidity/"
}