Glossary

Inbound Capacity Market

An inbound capacity market lets Lightning nodes buy or lease inbound liquidity from other nodes to receive payments.

Key Takeaways

  • New Lightning nodes cannot receive payments until someone opens a channel to them with funds on the remote side: inbound capacity markets solve this inbound liquidity bootstrapping problem by letting nodes buy or lease receivable capacity from capital providers.
  • Several marketplace designs exist: protocol-level liquidity ads in Core Lightning, auction-based systems like Lightning Pool, peer-to-peer platforms like Magma, and automated LSP-based solutions that open channels on demand.
  • Layer 2 protocols like Spark eliminate the inbound capacity problem entirely by using a statechain-based architecture with no payment channels, so users can receive funds without acquiring inbound liquidity first.

What Is an Inbound Capacity Market?

An inbound capacity market is a marketplace where Lightning Network node operators can purchase or lease inbound liquidity from other nodes. When a Lightning node first comes online, it has zero inbound capacity: no one has opened a channel to it with funds on the remote side, so the node cannot receive any payments. This is known as the inbound liquidity bootstrapping problem.

Inbound capacity markets address this by creating a price discovery mechanism where nodes with available capital (sellers) can offer to open channels toward nodes that need receivable capacity (buyers). The buyer pays a fee, and the seller commits capital for a specified duration, giving the buyer the ability to receive Lightning payments up to the leased amount.

These markets range from fully decentralized protocol-level mechanisms to centralized matching platforms, each with different tradeoffs in pricing transparency, enforcement guarantees, and ease of use.

How It Works

The fundamental mechanics of an inbound capacity market involve three steps: a buyer signals demand for receivable capacity, a seller agrees to provide it by opening a channel, and payment is exchanged for the service. The specifics vary by platform.

The Inbound Liquidity Problem

Lightning channels are funded at creation. When a node opens a channel, the opener commits Bitcoin to the channel, giving them outbound liquidity (the ability to send). The remote side of the channel starts at zero, meaning the opener's counterparty has no inbound capacity from that channel.

For a merchant or service provider that primarily receives payments, this creates a chicken-and-egg problem: they need inbound liquidity to receive payments, but inbound liquidity only appears when someone else opens a channel toward them. Without a market mechanism, new nodes must rely on altruistic peers, manual channel requests, or spending their own funds outward and hoping for reciprocal channels.

Lease-Based Model

Most inbound capacity markets use a lease model where the buyer pays for a channel that remains open for a guaranteed period. A typical lease involves:

  1. The buyer specifies a desired channel size (for example, 5,000,000 sats) and a lease duration (commonly 28 days or 2,016 blocks)
  2. The seller agrees to open a channel of that size with funds on the buyer's inbound side
  3. The buyer pays a lease fee: either a flat amount, a percentage of the channel size, or an annualized interest rate
  4. The channel remains open for the lease period, during which the buyer can receive payments up to the channel capacity

Enforcement varies by platform. Protocol-level solutions like liquidity ads enforce the lease duration on-chain using timelocks (CLTV locks on the seller's commitment outputs), while marketplace platforms may rely on reputation scoring and escrow mechanisms.

Pricing Mechanisms

Inbound capacity is priced in several ways depending on the marketplace:

ModelHow It WorksExample
Flat feeFixed sats per channel regardless of size or duration5,000 sats for a 1M sat channel
Percentage of capacityFee scales with channel size1% of channel amount
Annualized rate (APR)Fee expressed as annual interest on locked capital2.5% APR for a 28-day lease
Auction clearing priceSealed-bid batch auction sets uniform priceLightning Pool batch settlement

Longer leases and larger channels generally cost more because the seller locks up capital for an extended period. Smaller channels (under 1,000,000 sats) tend to carry higher effective rates because the seller's fixed costs (on-chain transaction fees for channel opening and closing) represent a larger share of the total capital committed.

Major Inbound Capacity Platforms

Liquidity Ads (Protocol-Level)

Liquidity ads are a protocol-native mechanism for advertising and purchasing inbound liquidity, defined in a Lightning specification proposal and implemented in Core Lightning. A node broadcasts its willingness to provide liquidity along with its pricing terms via the gossip network. When a buyer wants to purchase capacity, they initiate a dual-funded channel opening where the seller contributes capital to the buyer's inbound side.

The lease duration is enforced on-chain: the seller's outputs on commitment transactions are encumbered with CLTV locks matching the agreed lease period, preventing the seller from closing the channel early and reclaiming their capital. Sellers set a funding weight fee and a lease fee rate expressed in basis points.

# Core Lightning: advertise liquidity for sale
lightning-cli funderupdate \
  --policy match \
  --lease_fee_base_msat 100000 \
  --lease_fee_basis 50 \
  --channel_fee_max_base_msat 1000 \
  --channel_fee_max_proportional_thousandths 10

# Buyer: open a channel requesting liquidity
lightning-cli fundchannel \
  <seller_node_id> \
  1000000sat \
  --request_amt 5000000sat \
  --compact_lease <lease_terms>

Liquidity ads are currently supported in Core Lightning. LND and Eclair do not natively support dual-funded channels or liquidity ads, which limits the buyer pool to CLN nodes.

Lightning Pool (Auction-Based)

Lightning Pool, developed by Lightning Labs, uses a sealed-bid frequent batch auction to match buyers and sellers of inbound capacity. Rather than bilateral negotiation, Pool aggregates orders into periodic batches and clears them at a uniform price, similar to how treasury auctions work.

Pool introduced the concept of a Lightning Channel Lease (LCL): an inbound channel with a maturity date expressed in blocks. The lease duration is enforced by Bitcoin script conditions, ensuring the seller cannot reclaim capital before the agreed term expires. The auction mechanism provides price discovery for the cost of Lightning liquidity.

As of 2026, Lightning Labs has shifted development focus toward Taproot Assets and other products, and Pool's auction activity has declined.

Magma (Peer-to-Peer Marketplace)

Magma, operated by Amboss, is a peer-to-peer marketplace where sellers list channel offers with specified sizes, durations, and fee rates. Unlike Pool's auction model, Magma uses direct seller-set pricing: sellers advertise their terms, and buyers choose from available offers.

Magma uses hodl invoices for payment escrow. When a buyer selects an offer, their payment is held in a hodl invoice until the seller confirms the channel opening on-chain. If the seller fails to open the channel, the hodl invoice times out and the buyer recovers their funds. Magma also tracks node reputation, penalizing sellers who fail to fulfill orders.

Magma works across LND, Core Lightning, and Eclair, making it the most implementation-agnostic marketplace. As of 2026, it is considered the most active dedicated Lightning liquidity marketplace.

LSP-Based Solutions

Lightning Service Providers (LSPs) offer an automated alternative to manual marketplace purchases. Instead of buying a channel in advance, the LSP opens a just-in-time (JIT) channel when an incoming payment arrives for a user who lacks sufficient inbound capacity.

The LSP intercepts the incoming HTLC, opens a channel to the recipient, and forwards the payment over the new channel. The fee (typically 1% of the inbound amount plus mining costs) is deducted from the payment itself, so the recipient does not need to pre-fund anything. This model is standardized as LSPS2 (JIT Channel Negotiation) and is used by wallets like Phoenix (ACINQ).

Use Cases

  • Merchant onboarding: a new merchant accepting Lightning payments needs inbound capacity before customers can pay. Purchasing a lease from a marketplace or connecting to an LSP provides immediate receivability.
  • Routing node bootstrapping: routing nodes need balanced channels to earn routing fees. Buying inbound capacity from well-connected nodes helps new routing nodes attract payment flow.
  • Exchange and service integration: businesses processing Lightning deposits need predictable inbound capacity. Leasing channels in bulk through marketplaces provides capacity guarantees that ad-hoc channel requests cannot.
  • Wallet providers: mobile wallet companies acting as LSPs lease capacity on behalf of their users, abstracting the complexity so end users never interact with liquidity markets directly.

Why It Matters

The inbound liquidity bootstrapping problem is one of the most significant usability barriers on the Lightning Network. Without a functioning market for inbound capacity, new participants face an unpredictable and often expensive onboarding process. Inbound capacity markets create price transparency, letting node operators make rational decisions about how much receivable capacity they need and what it should cost.

For a deeper analysis of acquisition costs across different channels, see the research article on what inbound liquidity actually costs on Lightning. For a comparison of marketplace platforms and LSP options, see the Lightning liquidity marketplace analysis.

Newer Bitcoin Layer 2 protocols like Spark take a different approach entirely. Spark uses a statechain-based architecture with no payment channels, so there is no concept of inbound or outbound capacity. Users can receive payments immediately without acquiring liquidity first. This eliminates the need for capacity markets altogether, though it introduces a different trust model where at least one operator in the signing group must remain honest. For a detailed comparison, see the Lightning vs. Spark glossary entry.

Risks and Considerations

Capital Inefficiency

Leased inbound capacity may go unused. If a merchant buys a 5 BTC inbound channel but only receives 0.5 BTC in payments during the lease period, 90% of the leased capital sat idle. The seller earned their fee regardless, but the buyer overpaid relative to their actual needs. Accurate demand forecasting is difficult, especially for new businesses.

Enforcement Gaps

Not all platforms enforce lease durations equally. Liquidity ads use on-chain timelocks, making early closure impossible. But marketplace platforms that rely on reputation systems have weaker enforcement: a seller could close a channel early, and the buyer's only recourse is a negative review. Buyers should verify how lease terms are enforced before committing funds.

Liquidity Drain

Inbound capacity is consumed as payments arrive. If a merchant receives a large payment early in the lease, their inbound capacity drops by that amount (it shifts to outbound). To maintain receivability, the merchant may need to rebalance with circular rebalances, Loop swaps, or splicing: each adding cost on top of the original lease fee.

Implementation Fragmentation

The Lightning ecosystem lacks a single standard for liquidity marketplaces. Liquidity ads work only on Core Lightning. Pool requires LND. Magma is implementation-agnostic but operates as a centralized platform. This fragmentation means buyers and sellers are siloed into smaller pools, reducing competition and potentially keeping prices higher than a unified market would produce.

Counterparty Risk

Depending on the marketplace design, buyers may face counterparty risk. A seller who opens a channel but provides poor uptime, sets unfavorable forwarding policies, or becomes unresponsive degrades the value of the leased capacity. Some platforms mitigate this with reputation scoring, but reputation systems can be gamed.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.