fix: resolve manual holds at their block-height deadline #24
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/hold-deadlines"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A hold can remain Pending in LDK after its HTLCs fail back at the claim deadline, leaving a selected application reservation unresolved. Compare the node block height with the stored deadline in authorization, claim, rejection, and recovery paths. Preserve successful payments and persist a conservative 2,016-block bound when a deadline was missed.
Document the required node:read permission and test deadline tightening, offline observations, restart, and already-successful claims.
Closes #21. Depends on #23.
Validation: focused protocol tests, workspace formatting/Clippy/tests/docs, and real Bitcoin/LDK regtest passed. The final dependent stack passed all 78 tests and native Nix checks.