Skip to content

staticaddr/loopin: persist confirmed HTLC outputs - #1217

Draft
hieblmi wants to merge 2 commits into
lightninglabs:multi-address-withdrawal-hardeningfrom
hieblmi:multi-address-loopin-htlc-recovery
Draft

staticaddr/loopin: persist confirmed HTLC outputs#1217
hieblmi wants to merge 2 commits into
lightninglabs:multi-address-withdrawal-hardeningfrom
hieblmi:multi-address-loopin-htlc-recovery

Conversation

@hieblmi

@hieblmi hieblmi commented Aug 28, 2026

Copy link
Copy Markdown
Collaborator

Description

The server can publish any of the standard, high-fee, or extreme-fee HTLC transaction variants signed by the client. Timeout recovery previously reconstructed only the standard variant, which could target a nonexistent outpoint after a backup variant confirmed.

Persist the exact confirmed HTLC transaction hash, output index, and value before timeout recovery. Clear the recorded outpoint on reorg, validate that the confirmed transaction spends the selected deposits in signed order, and retain the legacy reconstruction fallback for older swaps.

This PR is stacked on #1215.

Testing

  • go test ./...
  • go vet ./...

Pull Request Checklist

  • Add an entry to docs/release-notes/release-notes-next.md, or apply the no-changelog label (required by CI)

Record the exact confirmed HTLC transaction, output index, and value so
recovery sweeps the server-published output instead of reconstructing it
from legacy assumptions.
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