Edited 11_gossip_channel_graph.asciidoc with Atlas code editor

3 years ago · a17d508162
parent 525ea5ba98
commit a17d508162
1 changed files with 1 additions and 1 deletions
--- a/11_gossip_channel_graph.asciidoc
+++ b/11_gossip_channel_graph.asciidoc
@ -337,7 +337,7 @@ Validating an incoming +node_announcement+ is straightforward. The following ass

  * If no +node_announcement+ exists for the given node, then an existing +channel_announcement+ that references the given node (more on that later) must already exist in one's local channel graph.

-  * The included +signature+ must be a valid ECDSA signature verified using the included +node_id+ public key and the double-sha256 digest of the raw message encoding (minus the signature and frame header) as the message.
+  * The included +signature+ must be a valid ECDSA signature verified using the included +node_id+ public key and the double-SHA-256 digest of the raw message encoding (minus the signature and frame header) as the message.

  * All included +addresses+ must be sorted in ascending order based on their address identifier.