diff options
author | Alexander Cyon <alex.cyon@gmail.com> | 2024-05-28 19:25:46 +0200 |
---|---|---|
committer | Alexander Cyon <alex.cyon@gmail.com> | 2024-05-28 19:25:46 +0200 |
commit | 1eefea0456d661b4c51f3a40b7262d6a99161edd (patch) | |
tree | 4f84740d22e4220a8c0488e1932d6ee8b3841547 /bip-0085.mediawiki | |
parent | e2f7481a132e1c5863f5ffcbff009964d7c2af20 (diff) |
Fix typos on 17 files.
Diffstat (limited to 'bip-0085.mediawiki')
-rw-r--r-- | bip-0085.mediawiki | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0085.mediawiki b/bip-0085.mediawiki index 7311d8a..633210c 100644 --- a/bip-0085.mediawiki +++ b/bip-0085.mediawiki @@ -364,7 +364,7 @@ This specification relies on BIP32 but is agnostic to how the BIP32 root key is ==Discussion== -The reason for running the derived key through HMAC-SHA512 and truncating the result as necessary is to prevent leakage of the parent tree should the derived key (''k'') be compromized. While the specification requires the use of hardended key derivation which would prevent this, we cannot enforce hardened derivation, so this method ensures the derived entropy is hardened. Also, from a semantic point of view, since the purpose is to derive entropy and not a private key, we are required to transform the child key. This is done out of an abundance of caution, in order to ward off unwanted side effects should ''k'' be used for a dual purpose, including as a nonce ''hash(k)'', where undesirable and unforeseen interactions could occur. +The reason for running the derived key through HMAC-SHA512 and truncating the result as necessary is to prevent leakage of the parent tree should the derived key (''k'') be compromised. While the specification requires the use of hardended key derivation which would prevent this, we cannot enforce hardened derivation, so this method ensures the derived entropy is hardened. Also, from a semantic point of view, since the purpose is to derive entropy and not a private key, we are required to transform the child key. This is done out of an abundance of caution, in order to ward off unwanted side effects should ''k'' be used for a dual purpose, including as a nonce ''hash(k)'', where undesirable and unforeseen interactions could occur. ==Acknowledgements== |