Commit Graph
4 Commits
Author SHA1 Message Date
David A. Harding 5be4021fa1 Disambiguate Which Key Is Compromised When Ext. PubKey + PrivKey Are Leaked
I mistakenly inferred from the following clause that a parent extended
public key plus a child private key would be equivalent to knowing the
extended *child* private key---meaning that the *parent* private key was
still secure:

> knowledge of the extended public key + any non-hardened private key
> descending from it is equivalent to knowing the extended private key

This patch's addition of the word "parent" (twice) removes the ambiguity
and may help other readers draw the correct inference that the parent
private key is no longer secure in this case.

I also changed "+" to "plus" to avoid confusion with the actual
mathematical operations used in this BIP.
2014-05-20 11:34:21 -04:00
David A. Harding 917838608c Update bip-0070.mediawiki
Revised final sentence of signature field description.
2014-04-28 14:56:30 -04:00
David A. Harding 3cbf3d7c03 Update bip-0070.mediawiki
Change "zero-byte placeholder" to "empty string"
2014-04-26 20:26:22 -04:00
David A. Harding 4081d3c57f Update bip-0070.mediawiki
Slightly re-worded description of the signature field in PaymentRequest

The previous phrasing confused me and I had to check the Bitcoin Core source code to see what it was expecting for a signature.
2014-03-31 21:34:07 -04:00