Skip to content

Conversation

@Anyitechs
Copy link
Owner

@Anyitechs Anyitechs commented Aug 13, 2025

This PR addresses the duplicate HTLC fail-back on stale force-close that fail-back one of them and waits till timeout to fail-back everything. This change adds proper tracking of HTLCs by payment hash to ensure all identical HTLCs are failed back immediately when detected, rather than waiting for timeout.

Also introduces a functional test that demonstrates the scenario by creating two identical HTLCs, performing a stale force-close, and verifying both HTLCs are failed back correctly.

Fixes

@Anyitechs Anyitechs marked this pull request as draft August 14, 2025 00:18
@Anyitechs Anyitechs force-pushed the duplicate-htlc-fail-back branch 4 times, most recently from efbbe8b to 146daef Compare September 9, 2025 01:00
@Anyitechs Anyitechs force-pushed the duplicate-htlc-fail-back branch from 146daef to c6b3f8a Compare September 22, 2025 22:30
@Anyitechs Anyitechs force-pushed the duplicate-htlc-fail-back branch from c6b3f8a to 42e9ba7 Compare October 6, 2025 00:12
@Anyitechs Anyitechs force-pushed the duplicate-htlc-fail-back branch from 42e9ba7 to 2a5ac7d Compare October 6, 2025 00:52
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.

2 participants