-
Notifications
You must be signed in to change notification settings - Fork 6
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
stateless invoices #9
Conversation
9c56e42
to
d17b9bb
Compare
For stateless invoices, there is no option anymore to store this value per invoice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great and simplifies the code a lot! I did leave a couple of comments about potentially handling a set of HTLCs that overpays an invoice, which could be especially useful in the case of donations or overpayments for the sake of reliable routing. If you want to make a TODO, I would like to implement a test for this condition and the handling of it as a first issue for me?
6e42206
to
8150785
Compare
Converts lnmux to always use stateless invoices. This means that nothing needs to be stored on disk when an invoice is generated.
As a result of this, the number of invoice (sub)states in the database is reduced as well. Only incoming payments for which settlement is requested are stored on disk.