bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-05-26 12:10:14 +00:00
Code Issues Releases Wiki Activity

Correct mistake and add italics to previous post.

Eric Voskuil 2017-02-11 07:31:12 -08:00
parent e382379fc7
commit 4a05fe97f5
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Comments:BIP-0038.md

@ -8,6 +8,6 @@ Thank you Eric. It seems the security issues only relate to the [Confirmation C
That is correct. In implementing all aspects of BIP38 (and BIP39) in the libbitcoin library, and providing a command line interface via bx, we had a chance to thoroughly review the scenarios. The confirmation code scenario is inherently flawed and the entire section should be struck. The other scenarios appear to be secure to the extent one trusts the platform and the cryptographic assumptions. The former is up to the user and I'm not qualified to asses the latter.
In response to your initial query, backing up an HD wallet consists of securing the master private key, which this BIP accomplishes. It is useful in the case where one must secure any *existing* private key. If one intends to create a new HD wallet BIP39 may be a better option. It accomplishes the objective of securing the master public key (which it generates) but cannot secure an existing key.
In response to your initial query, backing up an HD wallet consists of securing the master private key, which this BIP accomplishes. It is useful in the case where one must secure any *existing* private key. If one intends to create a *new* HD wallet BIP39 may be a better option. It accomplishes the objective of securing a private key (which it generates) but cannot secure an existing key.
--Eric Voskuil, 2017-02-11