Skip to content

Conversation

@cdecker
Copy link
Collaborator

@cdecker cdecker commented Feb 10, 2026

Before creating an LSPS2 invoice that requires JIT channel negotiation, check if the node already has sufficient incoming capacity to receive the payment directly.

When the receivable capacity (with a 5% buffer for fees) exceeds the invoice amount, create a regular invoice instead of negotiating with the LSP. This avoids unnecessary LSP fees and channel opening costs when the node can already receive the payment.

The capacity check:

  • Sums receivable_msat across all CHANNELD_NORMAL channels with connected peers
  • Applies a 5% buffer to account for routing fees
  • Falls back to JIT negotiation if capacity is insufficient or for 'any amount' invoices

Copy link
Member

@nepet nepet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the buffer math needs a check, otherwise 👍

Before creating an LSPS2 invoice that requires JIT channel negotiation,
check if the node already has sufficient incoming capacity to receive
the payment directly.

When the receivable capacity (with a 5% buffer for fees) exceeds the
invoice amount, create a regular invoice instead of negotiating with
the LSP. This avoids unnecessary LSP fees and channel opening costs
when the node can already receive the payment.

The capacity check:
- Sums receivable_msat across all CHANNELD_NORMAL channels with
  connected peers
- Applies a 5% buffer to account for routing fees
- Falls back to JIT negotiation if capacity is insufficient or
  for 'any amount' invoices
@cdecker cdecker force-pushed the 2026w06-lsp-invoice-capacity-check branch from deac94d to 1d3a93a Compare February 11, 2026 12:00
@cdecker cdecker merged commit a923d67 into main Feb 11, 2026
12 checks passed
@cdecker cdecker deleted the 2026w06-lsp-invoice-capacity-check branch February 11, 2026 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

sdk: receive will always pick an LSP or fail

2 participants