-
Notifications
You must be signed in to change notification settings - Fork 52
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
Return preimage in PostMintQuoteBolt11Response for paid invoices #168
Comments
+1 |
@callebtc @thesimplekid is it always guaranteed that the pre-image is always available? |
I'm not sure if this post relates to a melt or a mint request. Assuming the title is correct, it would mean that we return a preimage when creating an incoming invoice. This is in most cases not possible. Most Lightning backends do not return the preimage when you create an invoice. For melts, we do return the preimage (whenever possible, some backends do not support this either) in the |
@callebtc for minting, when checking if the invoice is paid (by checking the |
Most backends do not provide you with this information, no. |
what are most backends? and why do they not provide that information? how do you know the invoice is paid? |
I can't answer these questions because I'm not responsible for designing these backends. I'm just stating it as a fact and that's why this feature request can't be met. |
ok,understandable. as a follow up:
|
I don't understand. The payer can prove it by showing the preimage. We provide the preimage to a paying Cashu wallet. Are you referring to the receiver (like the top post)? There is no way to prove you've received a Lightning payment that I know of. |
Currently in Alby Hub we expect every paid transaction to have a preimage and we think this is important for data consistency so are hesitant about removing this check. I think other wallets would also want to show the preimage in the transaction list for settled payments, even received ones.
See getAlby/hub#651
The text was updated successfully, but these errors were encountered: