Skip to content

Revisit PendingHTLCsForwardable delay duration #3768

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tnull opened this issue May 6, 2025 · 1 comment
Open

Revisit PendingHTLCsForwardable delay duration #3768

tnull opened this issue May 6, 2025 · 1 comment

Comments

@tnull
Copy link
Contributor

tnull commented May 6, 2025

The currently proposed MIN_HTLC_RELAY_HOLDING_CELL_MILLIS = 100 is quite high for a lower-bound on the forwarding delay, as is delaying HTLC forwarding up to 500ms.

As the proposed values are pretty conservative and they seem to discourage users from applying any forwarding delay at all, we should revisit them. Proposing a forwarding delay to cover 1-2 RTTs around the node should likely be sufficient, especially if multiple nodes per path apply it. To this end, drawing from a (preferably log-normal) distribution from something in [50,250] would likely suffice.

@TheBlueMatt
Copy link
Collaborator

Makes sense. If we do this we should probably just do the random draw for the user. Tho if we want to get fancy we probably want to just do bulk forwards on a fixed timer unrelated to when we receive HTLCs, eg every 100ms.

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

No branches or pull requests

2 participants