emphasis fixes
parent
df1395ff63
commit
7595242a36
2 changed files with 5 additions and 5 deletions
|
|
@ -1,6 +1,6 @@
|
|||
*NOTE: the instructions on this page are for a Bitcoin-only setup. For
|
||||
altcoin support, additional installation steps are required. See
|
||||
[**Altcoin and Forkcoin Support**][af] for more information.*
|
||||
altcoin support, additional installation steps are required. See*
|
||||
[**Altcoin and Forkcoin Support**][af] *for more information.*
|
||||
|
||||
### Perform the following steps on both your online and offline computers:
|
||||
|
||||
|
|
|
|||
|
|
@ -134,14 +134,14 @@ to just keep hashing:
|
|||
![]["share2 = SHA256(share1), share3 = SHA256(share2), ..."]
|
||||
|
||||
But you may have already spotted the mistake here: the owner of the first share
|
||||
can generate all the successive shares up to *n*-1. Without the final *n*’th
|
||||
can generate all the successive shares up to *n*-1. Without the final <em>n</em>’th
|
||||
share he can’t recover the seed, but the whole benefit of having the additional
|
||||
shares has been nullified.
|
||||
|
||||
***Important disclaimer:*** *there are other reasons, beyond the scope of this
|
||||
discussion, why using a bare hash of the seed as our random number source might
|
||||
not be a good idea. Bear in mind that this is a simplified **theoretical**
|
||||
introduction, and the examples presented herein are not suitable for
|
||||
not be a good idea. Bear in mind that this is a simplified* **theoretical**
|
||||
*introduction, and the examples presented herein are not suitable for
|
||||
implementation in real production code.*
|
||||
|
||||
The above example illustrates what happens when we violate the golden rule of
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue