Difference between revisions of "Public key to bitmessage address"

From Bitmessage Wiki
Jump to navigation Jump to search
(Created page with "First the public part of the signing key and the encryption key are merged together. Then you take the SHA512 hash of that. Then you take the RIPEMD160 of that. This is rep...")
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
First the public part of the signing key and the encryption key are merged together.
+
{{stub}}
  
−
Then you take the SHA512 hash of that.
+
This page briefly describes, how to generate a Bitmessage Address from a public key.
 +
The variable after the list is used to refer to the step later
  
−
Then you take the RIPEMD160 of that.
+
# Create a private and a public key for encryption and signing (resulting in 4 keys)
 +
# Merge the public part of the signing key and the encryption key together. (encoded in uncompressed X9.62 format) (A)
 +
# Take the SHA512 hash of A. (B)
 +
# Take the RIPEMD160 of B. (C)
 +
# Repeat step 1-4 until you have a result that starts with a zero (Or two zeros, if you want a short address). (D)
 +
# Remove the zeros at the beginning of D. (E)
 +
# Put the stream number (as a [[Protocol specification#Variable length integer|var_int]]) in front of E. (F)
 +
# Put the address version (as a [[Protocol specification#Variable length integer|var_int]]) in front of F. (G)
 +
# Take a double SHA512 (hash of a hash) of G and use the first four bytes as a checksum, that you append to the end. (H)
 +
# base58 encode H. (J)
 +
# Put "BM-" in front J. (K)
  
−
This is repeated until you have a result that starts with a zero (Or two zeros, if eighteen byte ripe is required)
+
K is your full address
  
−
Then you remove the zeros at the beginning.
+
Note: Bitmessage's base58 encoding uses the following sequence (the same as Bitcoin's): "123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz". Many existing libraries for base58 do not use this ordering.
−
 
 
−
Then you slap the stream number (in big endian) in front of that.
 
−
 
 
−
Then you slap the address version (in big endian) in front of that.
 
−
 
 
−
Then you take a double SHA512 of that and use the first four bytes as a checksum, that you slap on at the end.
 
−
 
 
−
Then you slap "BM-" in front of it all.
 

Revision as of 17:01, 19 October 2013

This page is a stub, you can help by expanding it.

This page briefly describes, how to generate a Bitmessage Address from a public key. The variable after the list is used to refer to the step later

  1. Create a private and a public key for encryption and signing (resulting in 4 keys)
  2. Merge the public part of the signing key and the encryption key together. (encoded in uncompressed X9.62 format) (A)
  3. Take the SHA512 hash of A. (B)
  4. Take the RIPEMD160 of B. (C)
  5. Repeat step 1-4 until you have a result that starts with a zero (Or two zeros, if you want a short address). (D)
  6. Remove the zeros at the beginning of D. (E)
  7. Put the stream number (as a var_int) in front of E. (F)
  8. Put the address version (as a var_int) in front of F. (G)
  9. Take a double SHA512 (hash of a hash) of G and use the first four bytes as a checksum, that you append to the end. (H)
  10. base58 encode H. (J)
  11. Put "BM-" in front J. (K)

K is your full address

Note: Bitmessage's base58 encoding uses the following sequence (the same as Bitcoin's): "123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz". Many existing libraries for base58 do not use this ordering.

Retrieved from "https://wiki.bitmessage.org/index.php?title=Public_key_to_bitmessage_address&oldid=20767"