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

Reflect legacy payload type handling implementation in BOLT #703

Closed
wants to merge 1 commit into from

Conversation

arik-so
Copy link

@arik-so arik-so commented Nov 18, 2019

In sphinx.go, legacy payloads are not given a length prefix byte.

Copy link
Collaborator

@Roasbeef Roasbeef left a comment

Choose a reason for hiding this comment

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

I think this is already covered in the "Packet Structure" section:

The length field determines both the length and the format of the hop_payload field; the following formats are defined:
Legacy hop_data format, identified by a single 0x00 byte for length. In this case the hop_payload_length is defined to be 32 bytes.

Although it may be the case that we need to make this more explicit.

@niftynei niftynei added the clarification substantive change or addition around wording or meaning label Jan 6, 2020
@t-bast
Copy link
Collaborator

t-bast commented Dec 21, 2020

@arik-so do you think this clarification is still needed? If so can you rebase your PR and we'll include it?

In sphinx.go, legacy payloads are not given a length prefix byte.
@t-bast
Copy link
Collaborator

t-bast commented Dec 21, 2022

We got rid of the legacy format in #962 so we don't need this PR anymore.

@t-bast t-bast closed this Dec 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification substantive change or addition around wording or meaning
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants