SHA256 of "Dinas secret" is 0575965b3b44be51e8057d551c4016d83cb1fba9ea8d6e986447ba33fe69f6b3

replace former SHA256 of "Glorias secret"
3 years ago · 1f51de2b51
parent b837eb9569
commit 1f51de2b51
1 changed files with 1 additions and 1 deletions
--- 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: