-
Notifications
You must be signed in to change notification settings - Fork 403
Follow-ups to #2970 #3028
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
Follow-ups to #2970 #3028
Conversation
PaymentContext is already stored in ClaimablePayment via PaymentPurpose, so there is no need to repeat it in each ClaimableHTLC via OnionPayload. This avoids cloning the PaymentContext each time an HTLC is received, other than for the first HTLC for a payment.
Event::PaymentClaimable and Event::PaymentClaimed already contain the paid amount, so there's no need to included the requested amount in InvoiceRequestFields.
InvoiceRequestFeatures may contain a large, odd bit. Including this in InvoiceRequestFields, which is in each BlindedPath of a Bolt12Invoice, could cause the invoice's onion message to exceed the maximum size. The features are already checked before sending an invoice.
33b6162
11fda41
to
33b6162
Compare
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #3028 +/- ##
==========================================
+ Coverage 89.13% 89.48% +0.35%
==========================================
Files 118 118
Lines 97492 99913 +2421
Branches 97492 99913 +2421
==========================================
+ Hits 86903 89411 +2508
+ Misses 8349 8246 -103
- Partials 2240 2256 +16 ☔ View full report in Codecov by Sentry. |
CI is failing, though it seems unrelated. |
CI failures are some new warning on beta, not related. |
…followups Follow-ups to lightningdevkit#2970
Remove some unnecessary clones when handling HTLCs and unnecessary / problematic TLVs from
InvoiceRequestFields
.