-
Notifications
You must be signed in to change notification settings - Fork 418
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: lightningdevkit/rust-lightning
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: e4e9fd7
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: lightningdevkit/rust-lightning
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 7bf0469
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 11 commits
- 8 files changed
- 1 contributor
Commits on Oct 18, 2023
-
Configuration menu - View commit details
-
Copy full SHA for ef3ec51 - Browse repository at this point
Copy the full SHA ef3ec51View commit details -
Configuration menu - View commit details
-
Copy full SHA for ccf6d7e - Browse repository at this point
Copy the full SHA ccf6d7eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 1c5a7b3 - Browse repository at this point
Copy the full SHA 1c5a7b3View commit details -
Await invoice for variable number of timer ticks
PendingOutboundPayment::AwaitingInvoice counts the number of timer ticks that have passed awaiting a Bolt12Invoice for an InvoiceRequest. When a constant INVOICE_REQUEST_TIMEOUT_TICKS has passed, the payment is forgotten. However, this mechanism is insufficient for the Refund scenario, where the Refund's expiration should be used instead. Change AwaitingInvoice to store the number of timer ticks remaining instead of the number that has passed. This allows for a variable number of ticks that are instead counted down.
Configuration menu - View commit details
-
Copy full SHA for 7e98017 - Browse repository at this point
Copy the full SHA 7e98017View commit details -
Configuration menu - View commit details
-
Copy full SHA for e7df074 - Browse repository at this point
Copy the full SHA e7df074View commit details -
Configuration menu - View commit details
-
Copy full SHA for 48f24b2 - Browse repository at this point
Copy the full SHA 48f24b2View commit details -
Stateless offer and refund builder utilities
Add utility functions to ChannelManager for creating OfferBuilder, and RefundBuilder such that derived keys are used for the signing pubkey and payer id, respectively. This allows for stateless verification of any InvoiceRequest and Invoice messages. Later, blinded paths can be included in the returned builders. Also tracks future payments using the given PaymentId such that the corresponding Invoice is paid only once.
Configuration menu - View commit details
-
Copy full SHA for 86252ea - Browse repository at this point
Copy the full SHA 86252eaView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2ea457e - Browse repository at this point
Copy the full SHA 2ea457eView commit details -
Configuration menu - View commit details
-
Copy full SHA for d2848f3 - Browse repository at this point
Copy the full SHA d2848f3View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1059231 - Browse repository at this point
Copy the full SHA 1059231View commit details -
Include a one-hop blinded path in Offer and Refund
While this doesn't add much privacy over not including any blinded paths, it allows us to exercise code for receiving on blinded paths.
Configuration menu - View commit details
-
Copy full SHA for 7bf0469 - Browse repository at this point
Copy the full SHA 7bf0469View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff e4e9fd7...7bf0469