From 1f51de2b518f2ef8e403ff32c27bb0b2d6f8c19c Mon Sep 17 00:00:00 2001 From: Frnk Date: Mon, 5 Apr 2021 15:45:18 +0200 Subject: [PATCH] SHA256 of "Dinas secret" is 0575965b3b44be51e8057d551c4016d83cb1fba9ea8d6e986447ba33fe69f6b3 replace former SHA256 of "Glorias secret" --- routing.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/routing.asciidoc b/routing.asciidoc index 179a73e..b5110dc 100644 --- a/routing.asciidoc +++ b/routing.asciidoc @@ -129,7 +129,7 @@ We call this hash of the payment's secret the payment hash. The secret which "unlocks" the payment is called the payment secret. For now, we keep things simple and assume that Dina's secret is simply the text line: `+Dinas secret+`. -In order to "commit" to this secret, she computes the SHA256 hash which when encoded in hex, can be displayed as: `+f23c83babfb0e5f001c5030cf2a06626f8a940af939c1c35bd4526e90f9759f5+`. +In order to "commit" to this secret, she computes the SHA256 hash which when encoded in hex, can be displayed as: `+0575965b3b44be51e8057d551c4016d83cb1fba9ea8d6e986447ba33fe69f6b3+`. footnote:[You can verify this by typing `echo -n "Dinas secret" | sha256sum` to your Linux command line shell.] To facilitate Alice's payment, Dina will create the secret and the payment hash and send the payment hash to Alice. Alice doesn't know the secret but she can rewrite her contract to use the hash of the secret as a proof of payment: