-
Notifications
You must be signed in to change notification settings - Fork 902
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
Add network to init message #3300
Conversation
We are going to signal the genesis block hash in the init message.
ebbcb0e
to
1079696
Compare
Rebased to correct the use of |
Changelog-Added: protocol: We now signal the network we are running on at init.
1079696
to
a445b9e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack a445b9e
Technically, this isn't in the spec yet, so it should be wrapped in EXPERIMENTAL_FEATURES until it is. However, all the spec needs is interop testing, so if we can do that with LND or Eclair (once they've implemented it!) we can apply this.
If specified, this will add the corresponding chain_hash to the init message.
a445b9e
to
bcc7e70
Compare
Re-applying @rustyrussell's ACK, and merging: ACK bcc7e70 |
if (!tlvs->networks->chains) { | ||
status_peer_debug(&peer->id, | ||
"bad networks TLV in init '%s', closing", | ||
tal_hex(tmpctx, msg)); | ||
return io_close(conn); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note this is technically redundant, since it's covered elegently by the next part anyway.
This implements lightning/bolts#682