Skip to content
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

Make process_onion_failure always blame an SCID for non-payment-failed #1598

Open
TheBlueMatt opened this issue Jul 6, 2022 · 1 comment
Assignees
Milestone

Comments

@TheBlueMatt
Copy link
Collaborator

We should try hard to make process_onion_failure always return a blamed SCID if we aren't considering the payment as retryable. If my reading is correct, the only case that needs to be covered to accomplish that is the case where we do not manage to read a valid failure packet at any hop. Its not clear to me what the right answer is in that case, though - can we determine who screwed up the crypto in some way?

Once we do that, as a followup, we should make Event::ProbeFailed::short_channel_id an non-Optional field, which will need to happen in the same release as its original inclusion, making this a blocker for 0.0.110. See #1567 (comment)

@TheBlueMatt TheBlueMatt added this to the 0.0.110 milestone Jul 6, 2022
@tnull tnull changed the title Make process_onion_failure always blane an SCID for non-payment-failed Make process_onion_failure always blame an SCID for non-payment-failed Jul 6, 2022
@TheBlueMatt TheBlueMatt self-assigned this Jul 14, 2022
@TheBlueMatt
Copy link
Collaborator Author

Don't think there's anything we can do here, immediately, even though we very much should do something. Probably blocked on #1625 or some other mechanism where we can assign a penalty to all the nodes in a path without setting their available capacity lower, which isn't really the right thing to do for an entire path.

@TheBlueMatt TheBlueMatt modified the milestones: 0.0.110, 0.1 Jul 25, 2022
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

1 participant