summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLogan Saether <lsaether@protonmail.com>2017-09-24 14:01:14 -0400
committerGitHub <noreply@github.com>2017-09-24 14:01:14 -0400
commit10798af90d3da3b4b3e4ff05ef79dec3ffd121c6 (patch)
tree91a4e33a0c1893315ba2f1ba370991054650e72e
parent7fccc601a0c81133720205598b61a13061b4a218 (diff)
downloadbips-10798af90d3da3b4b3e4ff05ef79dec3ffd121c6.tar.xz
typo 'ECSDA' changed to correct 'ECDSA'
Elliptic curve digital signature algorithm
-rw-r--r--bip-0032.mediawiki2
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.