Skip to content

Allow uppercase bech32 HRP (main) #3506

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

Merged
merged 2 commits into from
Jan 8, 2025

Conversation

tnull
Copy link
Contributor

@tnull tnull commented Jan 6, 2025

This is #3505, but against main so we don't only have the change in the 0.1 branch.

Previously, we would fail parsing Offers if the HRP didn't match our expected (lowercase) HRP. Here, we relax this check in accordance with the spec to also allow all-uppercase HRPs.

@tnull tnull force-pushed the 2025-01-allow-upperase-hrp-main branch 5 times, most recently from af8c035 to 92f5d16 Compare January 6, 2025 18:34
tnull added 2 commits January 7, 2025 09:21
Previously, we would fail parsing `Offer`s if the HRP didn't match our
expected (lowercase) HRP. Here, we relax this check in accordance with
the spec to also allow all-uppercase HRPs.
.. to ensure we're able to decode all-uppercase HRPs and reject
mixed-case encodings.
@tnull tnull force-pushed the 2025-01-allow-upperase-hrp-main branch from 92f5d16 to 7d653c2 Compare January 7, 2025 08:22
@tnull
Copy link
Contributor Author

tnull commented Jan 8, 2025

Going ahead and landing this with one ACK as the 0.1 counterpart landed.

@tnull tnull merged commit 262d789 into lightningdevkit:main Jan 8, 2025
17 of 19 checks passed
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.

2 participants