Base58Check encoding - Revision history

Pseudo geek: Add "References" subtitle

2021-10-28T22:03:36Z

Add "References" subtitle

← Older revision		Revision as of 22:03, 28 October 2021
Line 264:		Line 264:
	* [https://github.com/luke-jr/libbase58 libbase58 C code (decode and encode, no external libraries needed)]		* [https://github.com/luke-jr/libbase58 libbase58 C code (decode and encode, no external libraries needed)]
	* [http://lenschulwitz.com/b58/base58perl.txt Base58 Decode, Encode, and Validate in Perl]		* [http://lenschulwitz.com/b58/base58perl.txt Base58 Decode, Encode, and Validate in Perl]

			== References ==
			<references />

	[[Category:Technical]]		[[Category:Technical]]

	[[es:Codificación Base58Check]]		[[es:Codificación Base58Check]]

Pseudo geek: Add electrum-defined and deprecated WIF version numbers; distinguish between compressed and uncompressed pubkey

2021-10-28T22:00:29Z

Add electrum-defined and deprecated WIF version numbers; distinguish between compressed and uncompressed pubkey

← Older revision		Revision as of 22:00, 28 October 2021
Line 237:		Line 237:
	\|128		\|128
	\|5		\|5
	\|Private key		\|Private key (uncompressed pubkey)
			\|-
			\|128
			\|K or L
			\|Private key (compressed pubkey)
			\|-
			\|129-135
			\|5, K, L, or M
			\|Private key (Electrum-defined<ref name="electrum-300-wif">[https://github.com/spesmilo/electrum/blob/3.0.0/RELEASE-NOTES#L42]</ref> and now deprecated<ref name="electrum-310-wif">[https://github.com/spesmilo/electrum/blob/3.1.0/RELEASE-NOTES#L58]</ref>)
	\|-		\|-
	\|111		\|111

Randolf: /* Base58 symbol chart */ Added a parenthesized note that 0, O, I, and l are excluded

2017-11-27T09:11:24Z

Base58 symbol chart: Added a parenthesized note that 0, O, I, and l are excluded

← Older revision		Revision as of 09:11, 27 November 2017
Line 46:		Line 46:

	==Base58 symbol chart==		==Base58 symbol chart==
	The Base58 symbol chart used in Bitcoin is specific to the Bitcoin project and is not intended to be the same as any other Base58 implementation used outside the context of Bitcoin.		The Base58 symbol chart used in Bitcoin is specific to the Bitcoin project and is not intended to be the same as any other Base58 implementation used outside the context of Bitcoin (the characters excluded are: 0, O, I, and l).
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-

JonathanCross: /* Encoding a Bitcoin address */ Simplifying the "payload" display and using fixed code font.

2016-10-24T14:05:35Z

Encoding a Bitcoin address: Simplifying the "payload" display and using fixed code font.

← Older revision		Revision as of 14:05, 24 October 2016
Line 34:		Line 34:
	==Encoding a Bitcoin address==		==Encoding a Bitcoin address==
	Bitcoin addresses are implemented using the Base58Check encoding of the hash of either:		Bitcoin addresses are implemented using the Base58Check encoding of the hash of either:
	* Pay-to-script-hash (p2sh): payload is [[RIPEMD160]]([[SHA256]](redeemScript the wallet knows how to spend)); version 0x05 (these addresses begin with the digit '3')		* Pay-to-script-hash (p2sh): payload is: <code>[[RIPEMD160]]([[SHA256]]('''redeemScript'''))</code> where '''redeemScript''' is a script the wallet knows how to spend; version <code>0x05</code> (these addresses begin with the digit '3')
	* Pay-to-pubkey-hash (p2pkh): payload is [[RIPEMD160]]([[SHA256]](~~ECDSA~~ public key the wallet knows the private key for)); version 0x00 (these addresses begin with the digit '1')		* Pay-to-pubkey-hash (p2pkh): payload is <code>[[RIPEMD160]]([[SHA256]]('''ECDSA_publicKey'''))</code> where '''ECDSA_publicKey''' is a public key the wallet knows the private key for; version <code>0x00</code> (these addresses begin with the digit '1')

	The resulting hash in both of these cases is always exactly 20 bytes.		The resulting hash in both of these cases is always exactly 20 bytes.

Jayemar: /* Creating a Base58Check string */ Added a link to the technical background of the bitcoin address

2015-07-03T13:59:18Z

Creating a Base58Check string: Added a link to the technical background of the bitcoin address

← Older revision		Revision as of 13:59, 3 July 2015
Line 30:		Line 30:
	# The leading character '1', which has a value of zero in base58, is reserved for representing an entire leading zero '''byte''', as when it is in a leading position, has no value as a base-58 symbol. There can be one or more leading '1's when necessary to represent one or more leading zero bytes. Count the number of leading zero bytes that were the result of step 3 (for old Bitcoin addresses, there will always be at least one for the version/application byte; for new addresses, there will never be any). Each leading zero byte shall be represented by its own character '1' in the final result.		# The leading character '1', which has a value of zero in base58, is reserved for representing an entire leading zero '''byte''', as when it is in a leading position, has no value as a base-58 symbol. There can be one or more leading '1's when necessary to represent one or more leading zero bytes. Count the number of leading zero bytes that were the result of step 3 (for old Bitcoin addresses, there will always be at least one for the version/application byte; for new addresses, there will never be any). Each leading zero byte shall be represented by its own character '1' in the final result.
	# Concatenate the 1's from step 5 with the results of step 4. '''This is the Base58Check result.'''		# Concatenate the 1's from step 5 with the results of step 4. '''This is the Base58Check result.'''
			A more detailed example is provided on the page describing the [[Technical_background_of_version_1_Bitcoin_addresses#How_to_create_Bitcoin_Address \| technical background]] of the bitcoin address.

	==Encoding a Bitcoin address==		==Encoding a Bitcoin address==

Luke-jr: /* Source code */

2014-09-16T00:09:32Z

Source code

← Older revision		Revision as of 00:09, 16 September 2014
Line 252:		Line 252:

	== Source code ==		== Source code ==
	* [https://github.com/bitcoin/bitcoin/blob/master/src/base58.h "Satoshi" C++ codebase (encode~~/decode using BigNum library~~)]		* [https://github.com/bitcoin/bitcoin/blob/master/src/base58.cpp "Satoshi" C++ codebase (decode and encode, no external libraries needed)]
	* [https://github.com/luke-jr/libbase58 libbase58 C code (decode and encode, no external libraries needed)]		* [https://github.com/luke-jr/libbase58 libbase58 C code (decode and encode, no external libraries needed)]
	* [http://lenschulwitz.com/b58/base58perl.txt Base58 Decode, Encode, and Validate in Perl]		* [http://lenschulwitz.com/b58/base58perl.txt Base58 Decode, Encode, and Validate in Perl]

Luke-jr: /* Source code */ libblkmaker is now using libbase58 for base58

2014-09-16T00:08:38Z

Source code: libblkmaker is now using libbase58 for base58

← Older revision		Revision as of 00:08, 16 September 2014
Line 254:		Line 254:
	* [https://github.com/bitcoin/bitcoin/blob/master/src/base58.h "Satoshi" C++ codebase (encode/decode using BigNum library)]		* [https://github.com/bitcoin/bitcoin/blob/master/src/base58.h "Satoshi" C++ codebase (encode/decode using BigNum library)]
	* [https://github.com/luke-jr/libbase58 libbase58 C code (decode and encode, no external libraries needed)]		* [https://github.com/luke-jr/libbase58 libbase58 C code (decode and encode, no external libraries needed)]
	* [https://gitorious.org/bitcoin/libblkmaker/blobs/master/base58.c libblkmaker C code (decode only, no external libraries needed)]
	* [http://lenschulwitz.com/b58/base58perl.txt Base58 Decode, Encode, and Validate in Perl]		* [http://lenschulwitz.com/b58/base58perl.txt Base58 Decode, Encode, and Validate in Perl]

Friend: Added link to Base58 Encode/Decode online tool and Perl code.

2014-09-15T19:09:21Z

Added link to Base58 Encode/Decode online tool and Perl code.

← Older revision		Revision as of 19:09, 15 September 2014
Line 247:		Line 247:
	\|}		\|}
	[[List of address prefixes]] is a more complete list.		[[List of address prefixes]] is a more complete list.

			== See Also ==
			* [http://lenschulwitz.com/base58 Online Base58 Decoder, Encoder, and Validator]

	== Source code ==		== Source code ==
Line 252:		Line 255:
	* [https://github.com/luke-jr/libbase58 libbase58 C code (decode and encode, no external libraries needed)]		* [https://github.com/luke-jr/libbase58 libbase58 C code (decode and encode, no external libraries needed)]
	* [https://gitorious.org/bitcoin/libblkmaker/blobs/master/base58.c libblkmaker C code (decode only, no external libraries needed)]		* [https://gitorious.org/bitcoin/libblkmaker/blobs/master/base58.c libblkmaker C code (decode only, no external libraries needed)]
			* [http://lenschulwitz.com/b58/base58perl.txt Base58 Decode, Encode, and Validate in Perl]

	[[Category:Technical]]		[[Category:Technical]]

	[[es:Codificación Base58Check]]		[[es:Codificación Base58Check]]

Mmortal03: /* Encoding a private key */

2014-08-24T07:26:20Z

Encoding a private key

← Older revision		Revision as of 07:26, 24 August 2014
Line 42:		Line 42:
	Base58Check encoding is also used for encoding [[private key\|ECDSA private keys]] in the [[wallet import format]].		Base58Check encoding is also used for encoding [[private key\|ECDSA private keys]] in the [[wallet import format]].
	This is formed exactly the same as a Bitcoin address, except that 0x80 is used for the version/application byte, and the payload is 32 bytes instead of 20 (a private key in Bitcoin is a single 32-byte unsigned big-endian integer).		This is formed exactly the same as a Bitcoin address, except that 0x80 is used for the version/application byte, and the payload is 32 bytes instead of 20 (a private key in Bitcoin is a single 32-byte unsigned big-endian integer).
	~~Such~~ encodings will always yield a 51-character string that starts with '5', or more specifically, either '5H', '5J', or '5K'.		For private keys associated with an uncompressed public key, such encodings will always yield a 51-character string that starts with '5', or more specifically, either '5H', '5J', or '5K'.

	==Base58 symbol chart==		==Base58 symbol chart==

Theymos: Fix RIPEMD160 link

2014-08-19T03:30:12Z

Fix RIPEMD160 link

← Older revision		Revision as of 03:30, 19 August 2014
Line 33:		Line 33:
	==Encoding a Bitcoin address==		==Encoding a Bitcoin address==
	Bitcoin addresses are implemented using the Base58Check encoding of the hash of either:		Bitcoin addresses are implemented using the Base58Check encoding of the hash of either:
	* Pay-to-script-hash (p2sh): payload is [[~~RIPEMD60~~]]([[SHA256]](redeemScript the wallet knows how to spend)); version 0x05 (these addresses begin with the digit '3')		* Pay-to-script-hash (p2sh): payload is [[RIPEMD160]]([[SHA256]](redeemScript the wallet knows how to spend)); version 0x05 (these addresses begin with the digit '3')
	* Pay-to-pubkey-hash (p2pkh): payload is [[~~RIPEMD60~~]]([[SHA256]](ECDSA public key the wallet knows the private key for)); version 0x00 (these addresses begin with the digit '1')		* Pay-to-pubkey-hash (p2pkh): payload is [[RIPEMD160]]([[SHA256]](ECDSA public key the wallet knows the private key for)); version 0x00 (these addresses begin with the digit '1')

	The resulting hash in both of these cases is always exactly 20 bytes.		The resulting hash in both of these cases is always exactly 20 bytes.