invoice error for blind with no outpoint#123
Merged
dr-orlovsky merged 1 commit intoRGB-WG:masterfrom Feb 8, 2024
Merged
Conversation
Member
|
Good improvement, thank you |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR returns an error instead of silently switching to address-based mode when a blinded invoice is requested (no
-aoption specified) but no suitable outpoint is found.The rationale for this is that a user can request a blinded invoice and fail to notice what the command returned is instead an address-based one. This might be the case if, as an example, the wallet had available UTXOs on keychain
0but not on9.