Skip to content

Follow-up to #792 (multi-LSP support)#956

Open
Camillarhi wants to merge 2 commits into
lightningdevkit:mainfrom
Camillarhi:multi-lsp-support-follow-up
Open

Follow-up to #792 (multi-LSP support)#956
Camillarhi wants to merge 2 commits into
lightningdevkit:mainfrom
Camillarhi:multi-lsp-support-follow-up

Conversation

@Camillarhi

@Camillarhi Camillarhi commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Some minor follow-ups after #792 landed.

  • Retry LSP protocol discovery when it fails at startup, so a transient connection failure doesn't leave a configured LSP permanently unusable. Adds a background retry with backoff and a Liquidity::retry_discovery(node_id) method for on-demand re-discovery (also useful when an LSP rolls out a new protocol).

  • Honor trust_peer_0conf independent of the LSP's supported protocols, It was previously only applied to LSPS2 peers, so LSPS1-only or undiscovered LSPs silently lost their configured 0-conf trust.

Leaving the LSP feature-gating for #900

Fixes - #936

- Add a background task that retries discovery for any LSP whose protocols
  are still undiscovered, using exponential backoff (5s up to 1h).
- Expose `Liquidity::retry_discovery(node_id)` so users can trigger
  re-discovery on demand, both to recover a stuck LSP and to pick up newly
  supported protocols after an LSP upgrade.
Look up trust_peer_0conf by node id via a protocol-independent helper
that does not depend on discovery
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant