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

don't enforce description_hash checking #3288

Merged
merged 1 commit into from Nov 25, 2019

Conversation

fiatjaf
Copy link
Contributor

@fiatjaf fiatjaf commented Nov 24, 2019

Although BOLT11 says "a reader MUST check" I'm not sure "reader" refers specifically to the Lightning server.

Sometimes the reader may be an application and the application may want to decode the invoice first before looking for the full description somewhere else and then proceeding to check either on its own or by calling decodepay again.

Sometimes the reader is a final payer, but there are some circumstances, like a custodial wallet provider or some other odd situations in which the Lightning server is not the final payer and thus not the "reader" that should care about this.

Sometimes the "full description" is not a UTF-8 string. In these cases they may still be checked against the description_hash but it will be impossible to pass it to lightningd.

I don't know, just think that failing when a description to be checked is not given is too brutal.

Changelog-None

@cdecker
Copy link
Member

cdecker commented Nov 25, 2019

ACK 0ed0c13

@cdecker cdecker merged commit 17bb862 into ElementsProject:master Nov 25, 2019
@fiatjaf fiatjaf deleted the patch-1 branch November 26, 2019 00:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants