-
Notifications
You must be signed in to change notification settings - Fork 491
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
BOLT 11: make UPPERCASE explicit. #677
Conversation
One for uppercase, and one with should-be-ignored fields. The first of these addresses lightning#659 (lightning#677 directly changes the text to make it clear this is allowed, and should also be applied). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
One for uppercase, and one with should-be-ignored fields. The first of these addresses lightning#659 (lightning#677 directly changes the text to make it clear this is allowed, and should also be applied). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
ACK 9a84c66 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK, just need to validate the new test vectors on eclair.
Test vectors were indeed already in our test suite, all good from our side!
Aren't they just uppercased versions of the previous vectors? |
Explicitly mirror the BIP-173 advice for QR codes, and note the reader requirements. Fixes: lightning#659 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
abe91b7
to
fa188db
Compare
Rebased without test vector change, since spec has since included an upper-case vector. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK fa188db
Explicitly mirror the BIP-173 advice for QR codes, and note the reader
requirements. In addition, we change the case of one of the examples
to ensure testing.
Fixes: #659
Alternative-to: #661