Public key to bitmessage address - Revision history

AyrA: Add key format details and hint about API binary data

2022-08-04T10:49:05Z

Add key format details and hint about API binary data

AyrA: /* Deterministic address */

2022-08-04T02:11:07Z

Deterministic address

AyrA: Add much more details

2022-08-03T22:46:53Z

Add much more details

Burntbrunch at 17:01, 19 October 2013

2013-10-19T17:01:59Z

Kgo at 16:52, 8 September 2013

2013-09-08T16:52:47Z

AyrA: made this thing a lot better

2013-08-21T12:23:16Z

made this thing a lot better

AyrA at 12:20, 21 August 2013

2013-08-21T12:20:03Z

Kgo at 23:27, 14 August 2013

2013-08-14T23:27:23Z

Kgo: 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..."

2013-08-14T23:26:23Z

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..."

New page

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 repeated until you have a result that starts with a zero (Or two zeros, if eighteen byte ripe is required)

Then you remove the zeros at the beginning.

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.

@@ Line 6: / Line 6: @@
 # Create two key pairs using secp256k1, one for encryption and one for signing (privEnc, pubEnc, privSign, pubSign)
-# Merge keys together using <code>pubSign + pubEnc</code>. Be sure to use the uncompressed keys (64 bytes per key, X9.62 format). (A)
+# Merge keys together using <code>pubSign + pubEnc</code>. Be sure to use the uncompressed keys (65 bytes per key, serialized X9.62 format). (A)
 # <code>SHA512(A)</code>. (B)
 # <code>RIPEMD160(B)</code>. (C)
@@ Line 46: / Line 46: @@
 The PyBitmessage client doesn't states how the passphrase is converted into bytes.
 This means using "äöü" as a passphrase will deliver different results across different operating systems because of how strings in python are handled internally.
 The entire hashing and leading zero restrictions only apply to the public signing key, not the encryption key.

@@ Line 22: / Line 22: @@
 == Deterministic address ==
-Deterministic addresses are created by using the '''last''' 32 bytes of <code>SHA512(passphrase + var_int)</code> as private key instead of randomly generating one.
+Deterministic addresses are created by using the first 32 bytes of <code>SHA512(passphrase + var_int)</code> as private key instead of randomly generating one.
 The var_int for the signing key starts at 0, and for the encryption key at 1.
 On every failed attempt to create an address, increment both integers by two and repeat the attempt. This means the integer for the signing key is always even,

@@ Line 1: / Line 1: @@
-{{stub}}
+This page briefly describes, how to generate a Bitmessage Address from a public key.
-This page briefly describes, how to generate a Bitmessage Address from a public key.
+Bitmessage's base58 encoding uses the following sequence (the same as Bitcoin's): "123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz".
-The variable after the list is used to refer to the step later
+Many existing libraries for base58 do not use this ordering.
-# Create a private and a public key for encryption and signing (resulting in 4 keys)
+As you may have noticed, the address version and stream number are not part of the keys, this means it's technically possible to move an address between streams and versions, although the Base58 encoding makes the address look completely different each time.
-K is your full address
+The PyBitmessage client doesn't states how the passphrase is converted into bytes.
-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.
+The entire hashing and leading zero restrictions only apply to the public signing key, not the encryption key.

@@ Line 5: / Line 5: @@
 # 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. (A)
+# 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 (in big endian) in front of E. (F)
+# Put the stream number (as a [[Protocol specification#Variable length integer|var_int]]) in front of E. (F)
-# Put the address version (in big endian) in front of F. (G)
+# 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)
@@ Line 18: / Line 18: @@
 K is your full address
-Note: Bitmessage's base58 encoding uses the following sequence: "123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz".  Many existing libraries for base58 do not use this ordering.
+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.

← Older revision		Revision as of 16:52, 8 September 2013
Line 17:		Line 17:

	K is your full address		K is your full address
		+
		+	Note: Bitmessage's base58 encoding uses the following sequence: "123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz". Many existing libraries for base58 do not use this ordering.

@@ 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.
-Then you take the RIPEMD160 of that.
+# The public part of the signing key and the encryption key are merged together. (A)
-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

← Older revision		Revision as of 23:27, 14 August 2013
Line 14:		Line 14:

	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 take a double SHA512 of that and use the first four bytes as a checksum, that you slap on at the end.
		+
		+	Then you base58 encode this.

	Then you slap "BM-" in front of it all.		Then you slap "BM-" in front of it all.