|
|
|
@ -386,7 +386,7 @@ With that said, a +channel_announcement+ message has the following fields:
|
|
|
|
|
|
|
|
|
|
* +bitcoin_signature_1+: The signature of the multisig key (in the funding output) of the first node over the message digest.
|
|
|
|
|
|
|
|
|
|
* +bitcoin_signature_2+: The signature of the multi-sig key (in the funding output) of the second node over the message digest.
|
|
|
|
|
* +bitcoin_signature_2+: The signature of the multisig key (in the funding output) of the second node over the message digest.
|
|
|
|
|
|
|
|
|
|
* +features+: A feature bit vector that describes the set of protocol level features supported by this channel.
|
|
|
|
|
|
|
|
|
@ -400,7 +400,7 @@ With that said, a +channel_announcement+ message has the following fields:
|
|
|
|
|
|
|
|
|
|
* +bitcoin_key_1+: The raw multisig key for the channel funding output for the first node in the network.
|
|
|
|
|
|
|
|
|
|
* +bitcoin_key_2+: The raw multi-sig key for the channel funding output for the second node in the network.
|
|
|
|
|
* +bitcoin_key_2+: The raw multisig key for the channel funding output for the second node in the network.
|
|
|
|
|
|
|
|
|
|
===== Channel announcement validation
|
|
|
|
|
|
|
|
|
|