Skip to content
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

Make BlindedHopFeatures optional per spec #2945

Conversation

valentinewallace
Copy link
Contributor

The spec states that if these features are missing, we MUST process the message as if it were present and contained an empty array. See [1].

H/t to @carlaKC for catching this!

The spec states that if these features are missing, we MUST process the message
as if it were present and contained an empty array.
@valentinewallace valentinewallace added this to the 0.0.122 milestone Mar 18, 2024
Copy link
Collaborator

@TheBlueMatt TheBlueMatt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, easy enough. Strictly more accepting and not changing the existing behavior. Should we also change our serialization-side to take advantage of the size reduction by not writing out features if they're empty?

@TheBlueMatt TheBlueMatt merged commit b747b39 into lightningdevkit:main Mar 19, 2024
16 checks passed
@valentinewallace
Copy link
Contributor Author

Sure, easy enough. Strictly more accepting and not changing the existing behavior. Should we also change our serialization-side to take advantage of the size reduction by not writing out features if they're empty?

Sure, opened #2949!

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.

None yet

2 participants