From 6f76f9620f5d79cab1cd7f8f6e62448bdd6244ea Mon Sep 17 00:00:00 2001 From: Enrico Rubboli Date: Tue, 23 Jun 2020 19:43:34 +0200 Subject: [PATCH] Fix `Glorias secret` hashing example --- routing.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/routing.asciidoc b/routing.asciidoc index c64b002..8939205 100644 --- a/routing.asciidoc +++ b/routing.asciidoc @@ -65,7 +65,7 @@ In reality Gloria would come up with a large random number as a secret. This is to be really secure and prevent others from guessing it. But let us assume that in our case Glorias secret take reads `*Glorias secret*`. She would commit to the secret by computing the sha256 hash which reads `*70c87220dd901a004804b49e9ec2fd73283fad127cf112fefa67e6b79b8739b7*`. -You can verify this by typing `echo "Glorias secret | sha256sum"` to your linux command line. +You can verify this by typing `echo "Glorias secret" | sha256sum` to your linux command line. As Alice wants to send 10 golden coins to Gloria she is told by Gloria to use this payment hash to receive a proof of payment. Alice now sets up a contract that reads: