-
Notifications
You must be signed in to change notification settings - Fork 448
Introduce Realistic constraints for Dummy Hops #4501
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
shaavan
wants to merge
6
commits into
lightningdevkit:main
Choose a base branch
from
shaavan:dummy-follow
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
d14446b
Return dummy-hop-specific error on blinded-forward underflow
shaavan 125c69e
Track dummy-hop skimmed fees through receive handling
shaavan 0c0f741
Account for dummy-hop fees in payment test helpers
shaavan 9c0de90
Use realistic dummy-hop defaults in blinded path admission
shaavan 3372b44
Test payinfo handling for dummy-hop blinded paths
shaavan 942e455
Make `BlindedPaymentPath::new_with_dummy_hops` public
shaavan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm, yea, I don't think this is quite sufficient sadly. I think what we should do is actually round up fees for normal hops within some threshold buckets (like we do for CLTVs already) and then pick constants from there. Right now nodes are likely to have relatively precise fee amounts and we'll set those explicitly on the path and then pick these constants for the dummy hops, revealing that they're dummy. I feel like we should use the previous hop's feerate if its "low" and otherwise pick the most common on the network today, which are: