don't enforce description_hash checking #3288
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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