Skip to content

bolt07: Simplify signature scheme for channel_announcement #96

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.

Sign up for GitHub

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

Merged
rustyrussell merged 1 commit into from
Feb 1, 2017
Merged

bolt07: Simplify signature scheme for channel_announcement #96

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 5 additions & 9 deletions 07-routing-gossip.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,9 +47,9 @@ announcement message; that is done by having a signature from each
2. data:
* [64:node-signature-1]
* [64:node-signature-2]
* [8:channel-id]
* [64:bitcoin-signature-1]
* [64:bitcoin-signature-2]
* [8:channel-id]
* [33:node-id-1]
* [33:node-id-2]
* [33:bitcoin-key-1]
Expand All @@ -70,14 +70,10 @@ ascending numerical order, and MUST set `bitcoin-key-1` and
`bitcoin-key-2` to `funding-pubkey`s of `node-id-1` and `node-id-2`
respectively.

The creating node MUST set `bitcoin-signature-1` to the signature of
the double-SHA256 of `node-id-1` using `bitcoin-key-1`, and set
`bitcoin-signature-2` to the signature of the double-SHA256 of
`node-id-2` using `bitcoin-key-2`

The creating node MUST set `node-signature-1` and `node-signature-2`
to the signature of the double-SHA256 of the message after the end of
`node-signature-2`, using `node-id-1` and `node-id-2` as keys respectively.
The creating node MUST compute the double-SHA256 hash `h` of the message, starting at offset 256, up to the end of the message.
Thus the hash skips the 4 signatures, but hashes the rest of the message, including any future fields appended to the end.
`node-signature-1` and `node-signature-2` MUST be valid signatures of the hash `h` using the secret associated with `node-id-1` and `node-id-2` respectively.
`bitcoin-signature-1` and `bitcoin-signature-2` MUST be valid signatures of the hash `h` using the secret associated with `bitcoin-key-1` and `bitcoin-key-2` respectively.

The creating node SHOULD set `len` to the minimum length required to
hold the `features` bits it sets.
Expand Down