-
Notifications
You must be signed in to change notification settings - Fork 357
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
Handle Payment Metadata in the Invoice/Send/Receive Pipelines #1221
Handle Payment Metadata in the Invoice/Send/Receive Pipelines #1221
Commits on Jan 26, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 1c1fc45 - Browse repository at this point
Copy the full SHA 1c1fc45View commit details -
Unset the optional bit for a feature when setting the required bit
There is no reason to set both, and this currently makes testing the new BOLT invoice tests slightly harder, so we just unset it.
Configuration menu - View commit details
-
Copy full SHA for cb82305 - Browse repository at this point
Copy the full SHA cb82305View commit details -
Configuration menu - View commit details
-
Copy full SHA for c8e2635 - Browse repository at this point
Copy the full SHA c8e2635View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2cfa80b - Browse repository at this point
Copy the full SHA 2cfa80bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 24c6792 - Browse repository at this point
Copy the full SHA 24c6792View commit details -
Store total payment amount in ClaimableHTLC explicitly
...instead of accessing it via the `OnionPayload::Invoice` form. This may be useful if we add MPP keysend support, but is directly useful to allow us to drop `FinalOnionHopData` from `OnionPayload`.
Configuration menu - View commit details
-
Copy full SHA for 7c16299 - Browse repository at this point
Copy the full SHA 7c16299View commit details -
Avoid storing a full FinalOnionHopData in OnionPayload::Invoice
We only use it to check the amount when processing MPP parts, but store the full object (including new payment metadata) in it. Because we now store the amount in the parent structure, there is no need for it at all in the `OnionPayload`. Sadly, for serialization compatibility, we need it to continue to exist, at least temporarily, but we can avoid populating the new fields in that case.
Configuration menu - View commit details
-
Copy full SHA for b0c7616 - Browse repository at this point
Copy the full SHA b0c7616View commit details -
Configuration menu - View commit details
-
Copy full SHA for 607cd2e - Browse repository at this point
Copy the full SHA 607cd2eView commit details -
Configuration menu - View commit details
-
Copy full SHA for c98733b - Browse repository at this point
Copy the full SHA c98733bView commit details -
Pipe payment metadata through the HTLC send pipeline
...without exposing it to the public `send_payment` API yet.
Configuration menu - View commit details
-
Copy full SHA for 588337f - Browse repository at this point
Copy the full SHA 588337fView commit details -
Configuration menu - View commit details
-
Copy full SHA for cd7e5ac - Browse repository at this point
Copy the full SHA cd7e5acView commit details