From dca5f7131099540c5a78c0503baa458b3b3c45a5 Mon Sep 17 00:00:00 2001 From: Patrick Lemke Date: Thu, 20 Feb 2020 17:48:27 +0100 Subject: [PATCH] wording --- ch03.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch03.asciidoc b/ch03.asciidoc index a3fd386..9760361 100644 --- a/ch03.asciidoc +++ b/ch03.asciidoc @@ -303,8 +303,8 @@ Besides some other meta data the most important but not quite obvious data in th The payee will choose a truly random number `r` and produces the `sha256` of that number which we call the Payment Hash `H(r)`. Note that an adversary should have no means of guessing or predicting `r`. Using a customer id or the hash of entries of the shopping cart together with a timestamp is not truly random and yields a security risk. -The payment process of the lightning network is only secure if `r` is chosen completely randomly and is not predictable and as long as the Hash function cannot be inverted. -We note that this is not an additional security assumption to Bitcoin as the security of the Hash function is currently what Bitcoin mining is building upon. +The payment process of the Lightning Network is only secure if `r` is chosen completely randomly and is not predictable and as long as the Hash function cannot be inverted. +We note that this is not an additional security assumption for Bitcoin as the security of the Hash function is currently what Bitcoin mining is built upon. ==== Additional Meta Data Invoices can encode some other useful meta data.