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
I'm trying to ensure nodes see the full invoice they're paying, but as of now that's not possible with the current LndHub protocol, since you only hand the bolt11 string which may not contain the description (LNURL particularly likes to use the h description_hash field).
This is a real problem for node validation, since they don't know what they're paying, and for users who can't query their node to see what they actually paid (especially if they use multiple front-ends).
Hi!
I'm trying to ensure nodes see the full invoice they're paying, but as of now that's not possible with the current LndHub protocol, since you only hand the bolt11 string which may not contain the description (LNURL particularly likes to use the
h
description_hash field).This is a real problem for node validation, since they don't know what they're paying, and for users who can't query their node to see what they actually paid (especially if they use multiple front-ends).
(Note: I discovered this issue because lnbits actually has an LndHub extension which means you can actually use BlueWallet to drive CLN, which is 🔥 😮 and @callebtc reported it in ElementsProject/lightning#6092 (comment)).
The text was updated successfully, but these errors were encountered: