diff options
| author | Justus Ranvier <justusranvier@riseup.net> | 2015-06-25 11:15:57 -0500 |
|---|---|---|
| committer | Justus Ranvier <justusranvier@riseup.net> | 2015-07-10 12:36:02 -0500 |
| commit | e700392b1563d044509d7b58fe6237edff6d0254 (patch) | |
| tree | dc0ad102320b8eac205ee525a1247c01aa8e3ee4 | |
| parent | 2616c9abc3f80ec28ce8dee5579e0649de8da57f (diff) | |
| download | bips-e700392b1563d044509d7b58fe6237edff6d0254.tar.xz | |
improve Bitmessage key derivation
| -rw-r--r-- | bip-0047.mediawiki | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/bip-0047.mediawiki b/bip-0047.mediawiki index 3fb6a2a..d49b0ea 100644 --- a/bip-0047.mediawiki +++ b/bip-0047.mediawiki @@ -214,9 +214,9 @@ A recipient prefers to receive notifications via Bitmessage indiates this prefer The sender uses this information to construct a valid notification Bitmessage address: -# Use the recipient's 0<sup>th</sup> public key as the Bitmessage signing key: <pre>B</pre> +# Derive a Bitmessage signing key as: <pre>B = payment code / 0 / 0</pre> # Initialize a counter at 1: <pre>n</pre> -# Derive a candidate encryption key: <pre>B' = B + nG</pre> +# Derive a candidate encryption key as: <pre>B' = payment code / 0 / n</pre> # If the combination of B and B` do not form a valid Bitmessage address, increment n by one and try again # Use the address version, signing key, encryption key, and stream number to construct a Bitmessage address per the Bitmessage protocol |