You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For someone implementing eg an lnurl server or some other server that generates invoices on demand, storing each invoice generated for receiving payments is potentially a large dos issue. Thus, storage should be optional, though storing them is generally useful to see payment status.
Btw, we're currently not storing the invoices, just tracking payment metadata by payment hash. However, maybe we should consider storing the invoice data for the user, which would allow them to retry failed payments without keeping the invoices around themselves.
Right, I suppose should have phrased as inbound payment metadata. Really should have specified that this is all about inbound payments - for outbound payments I don't think it really needs to be optional, and there indeed its probably useful to store the invoices themselves, at least in part because its the other half of the proof of payment.
Activity
tnull commentedon Jun 10, 2023
Btw, we're currently not storing the invoices, just tracking payment metadata by payment hash. However, maybe we should consider storing the invoice data for the user, which would allow them to retry failed payments without keeping the invoices around themselves.
TheBlueMatt commentedon Jun 10, 2023
Right, I suppose should have phrased as inbound payment metadata. Really should have specified that this is all about inbound payments - for outbound payments I don't think it really needs to be optional, and there indeed its probably useful to store the invoices themselves, at least in part because its the other half of the proof of payment.
Merge pull request lightningdevkit#51 from G8XSU/2025-03-12-events
tnull commentedon Aug 10, 2026
This will slip to v0.9 due to #425 slipping.