diff options
| author | Luke Dashjr <luke_github1@dashjr.org> | 2017-09-24 19:28:00 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-09-24 19:28:00 +0000 |
| commit | ed96b6bea537048c97358e813bf4daea445d43d0 (patch) | |
| tree | e47215fe7d9af82d66c65ad53a80e6ba8e1e99d8 | |
| parent | 6e01662f97a1fde92ffb1274761d59794b8183fe (diff) | |
| parent | 10798af90d3da3b4b3e4ff05ef79dec3ffd121c6 (diff) | |
| download | bips-ed96b6bea537048c97358e813bf4daea445d43d0.tar.xz | |
Merge pull request #595 from lsaether/patch-1
typo 'ECSDA' changed to correct 'ECDSA'
| -rw-r--r-- | bip-0032.mediawiki | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0032.mediawiki b/bip-0032.mediawiki index 6eba5f9..ab6ff9e 100644 --- a/bip-0032.mediawiki +++ b/bip-0032.mediawiki @@ -122,7 +122,7 @@ Each leaf node in the tree corresponds to an actual key, while the internal node ===Key identifiers=== -Extended keys can be identified by the Hash160 (RIPEMD160 after SHA256) of the serialized ECSDA public key K, ignoring the chain code. This corresponds exactly to the data used in traditional Bitcoin addresses. It is not advised to represent this data in base58 format though, as it may be interpreted as an address that way (and wallet software is not required to accept payment to the chain key itself). +Extended keys can be identified by the Hash160 (RIPEMD160 after SHA256) of the serialized ECDSA public key K, ignoring the chain code. This corresponds exactly to the data used in traditional Bitcoin addresses. It is not advised to represent this data in base58 format though, as it may be interpreted as an address that way (and wallet software is not required to accept payment to the chain key itself). The first 32 bits of the identifier are called the key fingerprint. |