Skip to content

Add test vector for (invalid) mixed-case offer encoding#1217

Merged
t-bast merged 1 commit intolightning:masterfrom
tnull:2025-01-add-mixed-case-test-vector
Feb 4, 2025
Merged

Add test vector for (invalid) mixed-case offer encoding#1217
t-bast merged 1 commit intolightning:masterfrom
tnull:2025-01-add-mixed-case-test-vector

Conversation

@tnull
Copy link
Contributor

@tnull tnull commented Jan 7, 2025

The spec requires the bech32 offer encodings to be all upper- or lowercase, but disallows mixed-case encodings.

Here, we add a test vector checking for this.

The spec requires the bech32 offer encodings to be all upper- or
lowercase, but disallows mixed-case encodings.

Here, we add a test vector for this.
@t-bast
Copy link
Collaborator

t-bast commented Jan 7, 2025

@thomash-acinq I don't know what eclair currently does: can you check and add this test vector?

@thomash-acinq
Copy link

Eclair wasn't implementing this string format. It's added in ACINQ/eclair#2985

@t-bast
Copy link
Collaborator

t-bast commented Feb 4, 2025

Merging, as agreed during the last spec meeting.

@t-bast t-bast merged commit 5f31faa into lightning:master Feb 4, 2025
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.

3 participants