-
Notifications
You must be signed in to change notification settings - Fork 386
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
Include expiry in invoices #1411
Comments
I can try pick this up. Would be some alright exposure to |
Great! Also, note that his only is a problem for |
Seems only the second option would make sense in this case as requiring a |
I don't think at need to worry about the expiry not being encoded properly - you can't use phantom nodes without it so if the expiry isn't encoded correctly we should be erroring anyway. Does seem like this needs to be based on #1384. |
We may want to consider having the phantom invoice utility functions directly call the exposed creation functions from #1384 instead of exposing functions for decoding. Then the interface would more closely match the non-phantom invoice utility functions. |
Adding to 107 cause it's an oversight we should fix, but if it slips no big deal. |
I see #1384 is merged so will get back to work on this. Spread myself a bit thin with the Qala.dev stuff 🥲 Edit: Should have a PR out on Friday. Have been working on it today. |
Re-opening since while #1422 added an |
Will fix today. |
When creating an
Invoice
using functions in thelightning-invoice
crate'sutils
module, the invoice expiration is not set. It should be set with the value encoded in the provided payment secret. Otherwise, BOLT 11 defines the default expiry to be 1 hour whereasChannelManager
will use whatever value is encoded in the payment secret.This may be tricky because either the methods will need to take in a
ChannelManager
to verify the payment secret and extract the expiry or the expiry needs to be passed in but could potentially not match what's encoded in the payment secret.The text was updated successfully, but these errors were encountered: