Skip to content
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

Closed
TheBlueMatt opened this issue Jan 25, 2022 · 7 comments · Fixed by #1361
Closed

create_invoice_from_channelmanager variant with description hash support #1280

TheBlueMatt opened this issue Jan 25, 2022 · 7 comments · Fixed by #1361
Labels
good first issue Good for newcomers

Comments

@TheBlueMatt
Copy link
Collaborator

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 for create_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.

@TheBlueMatt TheBlueMatt added the good first issue Good for newcomers label Jan 25, 2022
@xraid
Copy link

xraid commented Jan 31, 2022

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 ?

@xraid
Copy link

xraid commented Jan 31, 2022

a lnurl service could use a hash of the description not necessarily the bolt11 description_hash

@TheBlueMatt
Copy link
Collaborator Author

No, the lnurl spec requires you use the description_hash in bolt 11, so to support lnurl you need this.

@xraid
Copy link

xraid commented Feb 1, 2022

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

@xraid
Copy link

xraid commented Feb 1, 2022

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 ...

@xraid
Copy link

xraid commented Feb 1, 2022

maybe i am confusing it . lnurl-withdrawal can have teddybears in description_hash field, maybe lnurl-pay can not

@TheBlueMatt
Copy link
Collaborator Author

Ah, yes, I was referring to lnurl-pay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants