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

wire: update to latest version of the spec. #3782

Merged

Conversation

rustyrussell
Copy link
Contributor

The main change here is that the previously-optional open/accept
fields and reestablish fields are now compulsory (everyone was
including them anyway). In fact, the open/accept is a TLV
because it was actually the same format.

For more details, see lightning-rfc/f068dd0d8dfa5ae75feedd99f269e23be4777381

Signed-off-by: Rusty Russell rusty@rustcorp.com.au

@rustyrussell rustyrussell force-pushed the reestablish-always-has-fields branch 2 times, most recently from e4040ed to a0dd1c7 Compare June 23, 2020 00:06
The main change here is that the previously-optional open/accept
fields and reestablish fields are now compulsory (everyone was
including them anyway).  In fact, the open/accept is a TLV
because it was actually the same format.

For more details, see lightning-rfc/f068dd0d8dfa5ae75feedd99f269e23be4777381

Changelog-Removed: protocol: support for optioned form of reestablish messages now compulsory.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
@rustyrussell rustyrussell force-pushed the reestablish-always-has-fields branch from a0dd1c7 to 6530f9f Compare June 23, 2020 07:04
@cdecker
Copy link
Member

cdecker commented Jun 23, 2020

ACK 6530f9f

@cdecker cdecker merged commit 93d04d0 into ElementsProject:master Jun 23, 2020
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