-
Notifications
You must be signed in to change notification settings - Fork 376
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
create_invoice_from_channelmanager
variant with description hash support
#1280
Comments
no need for dh in lnurl one can use preimage_hash as id for what is described as dh in lnurl spec. it is just a handle for id in roundtrips dh is stupid . why have a description if it gets hashed and unreadable at recipient ? |
a lnurl service could use a hash of the description not necessarily the bolt11 description_hash |
No, the lnurl spec requires you use the description_hash in bolt 11, so to support lnurl you need this. |
i used hash of preimige in a lnurl service . as it is only used as id in the roundtrip, where the service can id url and hash when incoming |
You as service can put a teddybear in that field as long as You as service can id the teddybear when it comes back, it is not used by the client, only by service ... |
maybe i am confusing it . lnurl-withdrawal can have teddybears in description_hash field, maybe lnurl-pay can not |
Ah, yes, I was referring to lnurl-pay. |
I'm not sure there's much use in description hashes in the wild today, except for lnurl/the lnpay stuff, which we'd of course like to support. We really need a variant of
create_invoice_from_channelmanager
which supports a description hash instead of explicit description for that, though, and will probably want something similar forcreate_phantom_invoice
after #1199 is merged.Tagging good first issue, but if someone does take this up, probably base it on #1199 or wait until that is merged.
The text was updated successfully, but these errors were encountered: