[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lsd0001] branch master updated: use POW with 'POW value' consistently
From: |
gnunet |
Subject: |
[lsd0001] branch master updated: use POW with 'POW value' consistently |
Date: |
Tue, 01 Feb 2022 15:55:22 +0100 |
This is an automated email from the git hooks/post-receive script.
grothoff pushed a commit to branch master
in repository lsd0001.
The following commit(s) were added to refs/heads/master by this push:
new d03f92e use POW with 'POW value' consistently
d03f92e is described below
commit d03f92e3ec97cf59edee3d50e8050d1fa89342bc
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Tue Feb 1 15:55:20 2022 +0100
use POW with 'POW value' consistently
---
draft-schanzen-gns.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/draft-schanzen-gns.xml b/draft-schanzen-gns.xml
index 6737a89..3b41221 100644
--- a/draft-schanzen-gns.xml
+++ b/draft-schanzen-gns.xml
@@ -565,7 +565,7 @@ zTLD := zkl[126..129].zkl[63..125].zkl[0..62]
<dl>
<dt>POW</dt>
<dd>
- A 64-bit solution to the PoW. In network byte order.
+ A 64-bit value that is a solution to the PoW. In network byte order.
</dd>
<dt>TIMESTAMP</dt>
<dd>
@@ -584,7 +584,7 @@ zTLD := zkl[126..129].zkl[63..125].zkl[0..62]
</dd>
</dl>
<t>
- Traditionally, PoW schemes require to find a POW such that
+ Traditionally, PoW schemes require to find a POW value such that
at least D leading zeroes are found in the hash result.
D is then referred to as the difficulty of the PoW.
In order to reduce the variance in time it takes to calculate the
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [lsd0001] branch master updated: use POW with 'POW value' consistently,
gnunet <=