Add threshold for disabling from_future_htlc#3293
Merged
Conversation
When funding a transaction using `from_future_htlc`, we are taking the risk that the remote node doesn't fulfill the corresponding HTLCs. If we detect that too many peers fail such HTLCs, this may indicate a bug on the wallet side, so we automatically disable `from_future_htlc` to limit our exposure. We also ensure that nodes that already had one suspicious payment are blacklisted for other payments. This issue can happen when wallet users use multiple devices in unsupported scenarios.
pm47
reviewed
Apr 17, 2026
Member
There was a problem hiding this comment.
LGTM.
My only comment is that it is not possible to independently (e.g. from a monitoring/alert point of view) tell whether we are currently rejecting all otf fundings, as it becomes dependent from the configuration. I think it's acceptable and not worth adding more complexity.
pm47
approved these changes
Apr 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When funding a transaction using
from_future_htlc, we are taking the risk that the remote node doesn't fulfill the corresponding HTLCs. If we detect that too many peers fail such HTLCs, this may indicate a bug on the wallet side, so we automatically disablefrom_future_htlcto limit our exposure.We also ensure that nodes that already had one suspicious payment are blacklisted for other payments. This issue can happen when wallet users use multiple devices in unsupported scenarios.