Mini private key format - Revision history

Object In Space: /* Creating mini private keys */ convert Casascius Bitcoin Utility red link to link to GH repo, and add link to my utility too.

2025-11-11T07:02:07Z

Creating mini private keys: convert Casascius Bitcoin Utility red link to link to GH repo, and add link to my utility too.

← Older revision		Revision as of 07:02, 11 November 2025
Line 88:		Line 88:

	==Creating mini private keys==		==Creating mini private keys==
	Creating mini private keys is relatively simple. One program which can create such keys is [[Casascius Bitcoin Utility]].		Creating mini private keys is relatively simple. One program which can create such keys is [https://github.com/casascius/Bitcoin-Address-Utility Casascius Bitcoin Utility]. [https://codeberg.org/objectinspace/minikey Minikey] is also capable of generating minikeys.

	Mini private keys must be created "from scratch", as the conversion from mini private key to full-size private key is one-way. In other words, there is no way to convert an existing full-size private key into a mini private key.		Mini private keys must be created "from scratch", as the conversion from mini private key to full-size private key is one-way. In other words, there is no way to convert an existing full-size private key into a mini private key.

Object In Space: /* Import */ Add Electrum, Bitaddress.org, and my Minikey tool to the Import section

2025-11-11T06:57:25Z

Import: Add Electrum, Bitaddress.org, and my Minikey tool to the Import section

← Older revision		Revision as of 06:57, 11 November 2025
Line 38:		Line 38:
	===Applications===		===Applications===
	* [[Armory]]		* [[Armory]]
			* [[Electrum]]

	~~The current mainline ("Satoshi") client~~ cannot currently be used to import minikeys.		[[Bitcoin Core]] cannot currently be used to import minikeys directly, although it can be used in conjunction with the conversion tools listed below.

	===Web===		===Web===
Line 46:		Line 47:
	** Private keys can be imported into a Blockchain.info wallet and bitcoins can be sent to another address immediately upon import without needing to wait for any confirmations. Even after import, funds remain associated with the private key until they are actually spent to a different address.		** Private keys can be imported into a Blockchain.info wallet and bitcoins can be sent to another address immediately upon import without needing to wait for any confirmations. Even after import, funds remain associated with the private key until they are actually spent to a different address.
	* [[StrongCoin]]		* [[StrongCoin]]

			===Conversion tools===

			These tools can convert a minikey into its corresponding address, and private key in [[wallet import format]], where it can be used with any compatible software.

			* [https://codeberg.org/objectinspace/minikey Minikey] is a simple 100-line open-source tool with no external dependencies other than the programming language.
			* https://www.bitaddress.org/ can also convert minikeys - although be sure to run the software offline rather than entering the minikey directly into the website, where it could be intercepted.

	==Decoding==		==Decoding==

Taras at 03:03, 10 August 2017

2017-08-10T03:03:10Z

← Older revision		Revision as of 03:03, 10 August 2017
Line 4:		Line 4:
	The '''mini private key format''' is a method of encoding a Bitcoin private key in as few as 30 characters for the purpose of being embedded in a small space. A private key encoded in this format is called a '''minikey'''. This private key format was designed for and first used in [[Casascius physical bitcoins]], and is also favorable for use in QR codes. The fewer characters encoded in a QR code, the lower dot density can be used, as well as more dots allocated to error correction in the same space, significantly improving readability and resistance to damage. The mini private key format offers its own built-in check code as a small margin of protection against typos.		The '''mini private key format''' is a method of encoding a Bitcoin private key in as few as 30 characters for the purpose of being embedded in a small space. A private key encoded in this format is called a '''minikey'''. This private key format was designed for and first used in [[Casascius physical bitcoins]], and is also favorable for use in QR codes. The fewer characters encoded in a QR code, the lower dot density can be used, as well as more dots allocated to error correction in the same space, significantly improving readability and resistance to damage. The mini private key format offers its own built-in check code as a small margin of protection against typos.

	Casascius Series 1 holograms use a 22-character variant of the minikey format, instead of 30 characters. Everything is the same other than the length. To properly implement minikey redemption, services and clients must support the 30-character format, but may optionally support the 22-character format as well to ~~support~~ redemption of S1 Casascius coins. Use of the 22-character format for future applications is discouraged due to security considerations; the standard 30-character format should be used instead.		Casascius Series 1 holograms use a 22-character variant of the minikey format, instead of 30 characters. Everything is the same other than the length. To properly implement minikey redemption, services and clients must support the 30-character format, but may optionally support the 22-character format as well to allow redemption of old Casascius coins. Use of the 22-character format for future applications is discouraged due to security considerations; the standard 30-character format should be used instead.

	An example key using this encoding is '''S6c56bnXQiBjk9m{{taggant private key}}qSYE7ykVQ7NzrRy'''.		An example key using this encoding is '''S6c56bnXQiBjk9m{{taggant private key}}qSYE7ykVQ7NzrRy'''.
Line 29:		Line 29:
	The mini private key is suitable for use in QR codes. The recommended settings for maximizing readability are: QR version 3, error correction level Q (near highest, 25% possible lost codeword recovery). This results in a 29x29 grid. A minikey QR code can also fit in a 25x25 grid with QR version 2, error correction level L (lowest, 7% possible lost codeword recovery).		The mini private key is suitable for use in QR codes. The recommended settings for maximizing readability are: QR version 3, error correction level Q (near highest, 25% possible lost codeword recovery). This results in a 29x29 grid. A minikey QR code can also fit in a 25x25 grid with QR version 2, error correction level L (lowest, 7% possible lost codeword recovery).

	~~<table><tr><td>~~The sample private minikey encoded as a QR code on a 29x29 grid looks like this:~~</td><td>~~[[Image:Private_minikey_in_2D_barcode.gif]]~~</td></tr></table>~~		The sample private minikey encoded as a QR code on a 29x29 grid looks like this:

			[[Image:Private_minikey_in_2D_barcode.gif]]

	==Import==		==Import==
Line 57:		Line 59:
	Here is an example with the sample private key <tt>S6c56bnXQiBjk9mq{{taggant private key}}SYE7ykVQ7NzrRy</tt>.		Here is an example with the sample private key <tt>S6c56bnXQiBjk9mq{{taggant private key}}SYE7ykVQ7NzrRy</tt>.

	The string "<tt>~~S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy~~?</tt>" has a SHA256 value that begins with 00, so it is well-formed.		The string "<tt>S6c56bnXQiBjk9{{taggant private key}}mqSYE7ykVQ7NzrRy?</tt>" has a SHA256 value that begins with 00, so it is well-formed.

	To obtain the full 256-bit private key, simply take the SHA256 hash of the entire string. There is no encoding for line breaks in the string, even if the key is broken into multiple lines for printing. The SHA256 should be taken of exactly thirty bytes.		To obtain the full 256-bit private key, simply take the SHA256 hash of the entire string. There is no encoding for line breaks in the string, even if the key is broken into multiple lines for printing. The SHA256 should be taken of exactly thirty bytes.
Line 63:		Line 65:
	SHA256("S6c56bnXQiBjk9{{taggant private key}}mqSYE7ykVQ7NzrRy") = 4C7A9640C72DC2099F23715D0C8A0D8A35F8906E3CAB61DD3F78B67BF887C9AB		SHA256("S6c56bnXQiBjk9{{taggant private key}}mqSYE7ykVQ7NzrRy") = 4C7A9640C72DC2099F23715D0C8A0D8A35F8906E3CAB61DD3F78B67BF887C9AB

	This sample key in [[wallet ~~export~~ format]] is <tt>~~5JPy8Zg7z4P7RSLsiqcqyeAF1935zjNUdMxcDeVrtU1oarrgnB7~~</tt>, and the corresponding [[Bitcoin address]] is <tt>~~1CciesT23BNionJeXrbxmjc7ywfiyM4oLW~~</tt>.		This sample key in [[wallet import format]] is <tt>5JPy8Zg7z4P7RSLsiqcqyeAF1{{taggant private key}}935zjNUdMxcDeVrtU1oarrgnB7</tt>, and the corresponding [[Bitcoin address]] is <tt>1CciesT23BNionJe{{taggant address}}Xrbxmjc7ywfiyM4oLW</tt>.

	==== Command line verification ====		==== Command line verification ====
	To calculate SHA256 from the command line on OSX or Linux devices:		To calculate SHA256 from the command line on OSX or Linux devices:

	echo -n "~~S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy~~?" \| shasum -a 256		echo -n "S6c56bnXQiBjk9{{taggant private key}}mqSYE7ykVQ7NzrRy?" \| shasum -a 256

	That should output a line of text like "<tt>000f2453798ad4f951eecced2242eaef3e1cbc8a7c813c203ac7ffe57060355d -</tt>". Since the first two characters are <tt>00</tt> the verification passes for the mini key <tt>~~S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy~~</tt>		That should output a line of text like "<tt>000f2453798ad4f951eecced2242eaef3e1cbc8a7c813c203ac7ffe57060355d -</tt>". Since the first two characters are <tt>00</tt> the verification passes for the mini key <tt>S6c56bnXQiBjk9{{taggant private key}}mqSYE7ykVQ7NzrRy</tt>

	==Check code==		==Check code==

Taras at 02:45, 10 August 2017

2017-08-10T02:45:26Z

← Older revision		Revision as of 02:45, 10 August 2017
Line 1:		Line 1:
	[[Image:QR-privkeys-sidebyside.png\|thumb\|right\|QR codes of the same private key, in mini ~~versus regular~~ private key format. Both codes have the same dot density and error correction level, but the mini key is 57% of the full code's size.]]		[[Image:QR-privkeys-sidebyside.png\|thumb\|right\|Comparison of QR codes of the same private key, encoded in mini private key format (left) and [[wallet import format]] (right). Both codes have the same dot density and error correction level, but the mini key is 57% of the full code's size.]]
	The '''mini private key format''' is a method of encoding a Bitcoin private key in as few as 30 characters ~~so that it can be~~ embedded in a small space. This private key format was first used in [[Casascius physical bitcoins]], and is also favorable for use in QR codes. The fewer characters encoded in a QR code, the lower dot density can be used, as well as more dots allocated to error correction in the same space, significantly improving readability and resistance to damage. The mini private key format offers its own built-in check code as a small margin of protection against typos.		[[Image:Redeemed Denarium physical bitcoin.jpg\|thumb\|right\|A minikey in a small space on a physical bitcoin]]
			{{sample}}
			The '''mini private key format''' is a method of encoding a Bitcoin private key in as few as 30 characters for the purpose of being embedded in a small space. A private key encoded in this format is called a '''minikey'''. This private key format was designed for and first used in [[Casascius physical bitcoins]], and is also favorable for use in QR codes. The fewer characters encoded in a QR code, the lower dot density can be used, as well as more dots allocated to error correction in the same space, significantly improving readability and resistance to damage. The mini private key format offers its own built-in check code as a small margin of protection against typos.

	~~An example key using this encoding~~ is ~~'''S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy'''~~.		Casascius Series 1 holograms use a 22-character variant of the minikey format, instead of 30 characters. Everything is the same other than the length. To properly implement minikey redemption, services and clients must support the 30-character format, but may optionally support the 22-character format as well to support redemption of S1 Casascius coins. Use of the 22-character format for future applications is discouraged due to security considerations; the standard 30-character format should be used instead.

	~~==Usage on a physical bitcoin==~~		An example key using this encoding is '''S6c56bnXQiBjk9m{{taggant private key}}qSYE7ykVQ7NzrRy'''.
	~~The way it might appear within a physical bitcoin~~ is ~~on a round card printed as follows:~~

	~~Side of discs showing mini private key: (from~~ [[Casascius physical bitcoins]])~~<br/>~~		==Usage==
	~~[[Image:Miniprivkeys~~.~~jpg\|300px]]~~		===Physical bitcoins===
			{{multiple image\|align=vertical\|width=300
			\|image1=Miniprivkeys.jpg
			\|image2=Minipubkeys.jpg
			\|footer=Paper disc inserts for [[Casascius physical bitcoins\|Casascius coins]] with minikeys on the obverse (top) and corresponding address prefixes on the reverse (bottom)
			}}
			Minikeys are used extensively on physical bitcoins, because their small size allows them to be printed and read easily even on tiny surfaces inside the coins. Typically, a small paper or plastic disc is placed behind a tamper-evident security hologram on the back of a metal coin or bar, with the minikey printed on the inside such that it can only be read if the security hologram is removed.

	~~Side~~ of ~~discs showing~~ prefix of ~~bitcoin address (printed on~~ the ~~opposite side):<br/>~~		Some physical bitcoins include a window in the security hologram to view the back of this disc, which includes the prefix of the address corresponding to the hidden minikey.
	~~[[Image:Minipubkeys.jpg\|300px]]~~

	~~The examples in this article use the private key and Bitcoin~~ address ~~of the leftmost circle in~~ the ~~above two photos.~~

	~~==Usage in bar codes==~~
	The mini private key is suitable for use in QR codes. The recommended settings for maximizing readability are: QR version 3, error correction level Q (near highest, 25% possible lost codeword recovery). This results in a 29x29 grid. A minikey ~~QR code can also fit in a 25x25 grid with QR version 2, error correction level L (lowest, 7% possible lost codeword recovery).~~

	~~The sample private minikey encoded as a QR code on a 29x29 grid looks like this:~~

	~~[[Image:Private_minikey_in_2D_barcode~~.~~gif]]~~

			===1D barcodes===
	The mini private key is small enough to fit in a one-dimensional barcode while still remaining practical. Among the most popular one-dimensional barcode symbologies, the one known as "Code 128" is best suited for encoding a minikey due to its favorable data density and support for mixed case strings. The variant known as "Code 128-B" produces the shortest code for strings containing lowercase characters.		The mini private key is small enough to fit in a one-dimensional barcode while still remaining practical. Among the most popular one-dimensional barcode symbologies, the one known as "Code 128" is best suited for encoding a minikey due to its favorable data density and support for mixed case strings. The variant known as "Code 128-B" produces the shortest code for strings containing lowercase characters.

Line 27:		Line 25:

	[[Image:Private_minikey_in_1D_barcode.gif]]		[[Image:Private_minikey_in_1D_barcode.gif]]

			===2D barcodes===
			The mini private key is suitable for use in QR codes. The recommended settings for maximizing readability are: QR version 3, error correction level Q (near highest, 25% possible lost codeword recovery). This results in a 29x29 grid. A minikey QR code can also fit in a 25x25 grid with QR version 2, error correction level L (lowest, 7% possible lost codeword recovery).

			<table><tr><td>The sample private minikey encoded as a QR code on a 29x29 grid looks like this:</td><td>[[Image:Private_minikey_in_2D_barcode.gif]]</td></tr></table>

	==Import==		==Import==
Line 52:		Line 55:

	===Example with SHA256===		===Example with SHA256===
	Here is an example with the sample private key <tt>~~S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy~~</tt>.		Here is an example with the sample private key <tt>S6c56bnXQiBjk9mq{{taggant private key}}SYE7ykVQ7NzrRy</tt>.

	The string "<tt>S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy?</tt>" has a SHA256 value that begins with 00, so it is well-formed.		The string "<tt>S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy?</tt>" has a SHA256 value that begins with 00, so it is well-formed.
Line 58:		Line 61:
	To obtain the full 256-bit private key, simply take the SHA256 hash of the entire string. There is no encoding for line breaks in the string, even if the key is broken into multiple lines for printing. The SHA256 should be taken of exactly thirty bytes.		To obtain the full 256-bit private key, simply take the SHA256 hash of the entire string. There is no encoding for line breaks in the string, even if the key is broken into multiple lines for printing. The SHA256 should be taken of exactly thirty bytes.

	SHA256("~~S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy~~") = 4C7A9640C72DC2099F23715D0C8A0D8A35F8906E3CAB61DD3F78B67BF887C9AB		SHA256("S6c56bnXQiBjk9{{taggant private key}}mqSYE7ykVQ7NzrRy") = 4C7A9640C72DC2099F23715D0C8A0D8A35F8906E3CAB61DD3F78B67BF887C9AB

	This sample key in [[wallet export format]] is <tt>5JPy8Zg7z4P7RSLsiqcqyeAF1935zjNUdMxcDeVrtU1oarrgnB7</tt>, and the corresponding [[Bitcoin address]] is <tt>1CciesT23BNionJeXrbxmjc7ywfiyM4oLW</tt>.		This sample key in [[wallet export format]] is <tt>5JPy8Zg7z4P7RSLsiqcqyeAF1935zjNUdMxcDeVrtU1oarrgnB7</tt>, and the corresponding [[Bitcoin address]] is <tt>1CciesT23BNionJeXrbxmjc7ywfiyM4oLW</tt>.
Line 84:		Line 87:

	In all cases, you '''must''' use a secure cryptographic random number generator to eliminate risks of predictability of the random strings.		In all cases, you '''must''' use a secure cryptographic random number generator to eliminate risks of predictability of the random strings.

	~~==Casascius Series 1 coins==~~

	Casascius Series 1 Physical Bitcoins use a 22-character variant of the minikey format, instead of 30 characters. Everything is the same other than the length. To properly implement minikey redemption, services and clients MUST support the 30-character format, but MAY support the 22-character format as well. Use of the 22-character format for future applications is discouraged due to security considerations.

	==Python Code==		==Python Code==

W52WmqXDm4DZFN: Link "Casascius physical bitcoins" on first occurence

2016-09-12T16:19:14Z

Link "Casascius physical bitcoins" on first occurence

← Older revision		Revision as of 16:19, 12 September 2016
Line 1:		Line 1:
	[[Image:QR-privkeys-sidebyside.png\|thumb\|right\|QR codes of the same private key, in mini versus regular private key format. Both codes have the same dot density and error correction level, but the mini key is 57% of the full code's size.]]		[[Image:QR-privkeys-sidebyside.png\|thumb\|right\|QR codes of the same private key, in mini versus regular private key format. Both codes have the same dot density and error correction level, but the mini key is 57% of the full code's size.]]
	The '''mini private key format''' is a method of encoding a Bitcoin private key in as few as 30 characters so that it can be embedded in a small space. This private key format was first used in Casascius physical bitcoins, and is also favorable for use in QR codes. The fewer characters encoded in a QR code, the lower dot density can be used, as well as more dots allocated to error correction in the same space, significantly improving readability and resistance to damage. The mini private key format offers its own built-in check code as a small margin of protection against typos.		The '''mini private key format''' is a method of encoding a Bitcoin private key in as few as 30 characters so that it can be embedded in a small space. This private key format was first used in [[Casascius physical bitcoins]], and is also favorable for use in QR codes. The fewer characters encoded in a QR code, the lower dot density can be used, as well as more dots allocated to error correction in the same space, significantly improving readability and resistance to damage. The mini private key format offers its own built-in check code as a small margin of protection against typos.

	An example key using this encoding is '''S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy'''.		An example key using this encoding is '''S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy'''.

Friend: No more Mt. Gox.

2015-04-02T04:49:30Z

No more Mt. Gox.

← Older revision		Revision as of 04:49, 2 April 2015
Line 35:		Line 35:

	The current mainline ("Satoshi") client cannot currently be used to import minikeys.		The current mainline ("Satoshi") client cannot currently be used to import minikeys.

	~~===Mobile===~~

	* Mt. Gox Mobile can redeem a private key scanned from a QR Code or is entered using the keyboard. Upon importing, Mt. Gox sweeps the funds to a secondary address, and then a user must wait for six confirmations before the funds will appear in the Mt. Gox account.

	===Web===		===Web===
Line 45:		Line 41:
	** Private keys can be imported into a Blockchain.info wallet and bitcoins can be sent to another address immediately upon import without needing to wait for any confirmations. Even after import, funds remain associated with the private key until they are actually spent to a different address.		** Private keys can be imported into a Blockchain.info wallet and bitcoins can be sent to another address immediately upon import without needing to wait for any confirmations. Even after import, funds remain associated with the private key until they are actually spent to a different address.
	* [[StrongCoin]]		* [[StrongCoin]]
	* [[Mt. Gox]]
	** Importing minikeys is done through the deposit screen using the "Import Private Key" deposit method. Upon importing, Mt. Gox sweeps the funds to a secondary address, and then a user must wait for six confirmations before the funds will appear in the Mt. Gox account. Removing the imported bitcoins from the Mt. Gox account is treated as a bitcoin withdrawal and counts against daily/monthly limits.
	** Mt. Gox also permanently remembers any imported private key and automatically sweeps any future funds sent to it into the user's Mt. Gox account.
	** Mt. Gox's import screen doesn't properly detect or reject typos. If you make a mistake, Mt. Gox will treat it as a valid entry and report that a private key with a balance of 0.00 BTC from a bitcoin address you won't recognize was "successfully" imported.

	==Decoding==		==Decoding==

MidnightLightning: /* Example with SHA256 */ Add command-line verification command, and formatting

2013-12-04T18:41:13Z

Example with SHA256: Add command-line verification command, and formatting

← Older revision		Revision as of 18:41, 4 December 2013
Line 60:		Line 60:

	===Example with SHA256===		===Example with SHA256===
	Here is an example with the sample private key S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy.		Here is an example with the sample private key <tt>S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy</tt>.

	The string "S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy?" has a SHA256 value that begins with 00, so it is well-formed.		The string "<tt>S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy?</tt>" has a SHA256 value that begins with 00, so it is well-formed.

	To obtain the full 256-bit private key, simply take the SHA256 hash of the entire string. There is no encoding for line breaks in the string, even if the key is broken into multiple lines for printing. The SHA256 should be taken of exactly thirty bytes.		To obtain the full 256-bit private key, simply take the SHA256 hash of the entire string. There is no encoding for line breaks in the string, even if the key is broken into multiple lines for printing. The SHA256 should be taken of exactly thirty bytes.
Line 68:		Line 68:
	SHA256("S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy") = 4C7A9640C72DC2099F23715D0C8A0D8A35F8906E3CAB61DD3F78B67BF887C9AB		SHA256("S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy") = 4C7A9640C72DC2099F23715D0C8A0D8A35F8906E3CAB61DD3F78B67BF887C9AB

	This sample key in [[wallet export format]] is 5JPy8Zg7z4P7RSLsiqcqyeAF1935zjNUdMxcDeVrtU1oarrgnB7, and the corresponding [[Bitcoin address]] is 1CciesT23BNionJeXrbxmjc7ywfiyM4oLW.		This sample key in [[wallet export format]] is <tt>5JPy8Zg7z4P7RSLsiqcqyeAF1935zjNUdMxcDeVrtU1oarrgnB7</tt>, and the corresponding [[Bitcoin address]] is <tt>1CciesT23BNionJeXrbxmjc7ywfiyM4oLW</tt>.

			==== Command line verification ====
			To calculate SHA256 from the command line on OSX or Linux devices:

			echo -n "S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy?" \| shasum -a 256

			That should output a line of text like "<tt>000f2453798ad4f951eecced2242eaef3e1cbc8a7c813c203ac7ffe57060355d -</tt>". Since the first two characters are <tt>00</tt> the verification passes for the mini key <tt>S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy</tt>

	==Check code==		==Check code==

Wolf0 at 12:01, 26 June 2013

2013-06-26T12:01:31Z

← Older revision		Revision as of 12:01, 26 June 2013
Line 133:		Line 133:
	except KeyboardInterrupt:		except KeyboardInterrupt:
	break		break
	print('\n%s: %i\n%s: %i~~\n%s: %r~~\n%s: %.1f' %		print('\n%s: %i\n%s: %i\n%s: %.1f' %
	('Keys Generated', keysGenerated,		('Keys Generated', keysGenerated,
	'Total Candidates', totalCandidates,		'Total Candidates', totalCandidates,
	~~'Additional Security', additionalSecurity,~~
	'Reject Percentage',		'Reject Percentage',
	100*(1.0-keysGenerated/float(totalCandidates))))		100*(1.0-keysGenerated/float(totalCandidates))))

Bezzeb: /* Web */ Fixing broken link

2013-06-13T17:55:04Z

Web: Fixing broken link

← Older revision		Revision as of 17:55, 13 June 2013
Line 42:		Line 42:
	===Web===		===Web===

	* [[~~Blockchain~~.info]]		* [[BlockChain.info]]
	** Private keys can be imported into a Blockchain.info wallet and bitcoins can be sent to another address immediately upon import without needing to wait for any confirmations. Even after import, funds remain associated with the private key until they are actually spent to a different address.		** Private keys can be imported into a Blockchain.info wallet and bitcoins can be sent to another address immediately upon import without needing to wait for any confirmations. Even after import, funds remain associated with the private key until they are actually spent to a different address.
	* [[~~Strongcoin~~]]		* [[StrongCoin]]
	* [[Mt. Gox]]		* [[Mt. Gox]]
	** Importing minikeys is done through the deposit screen using the "Import Private Key" deposit method. Upon importing, Mt. Gox sweeps the funds to a secondary address, and then a user must wait for six confirmations before the funds will appear in the Mt. Gox account. Removing the imported bitcoins from the Mt. Gox account is treated as a bitcoin withdrawal and counts against daily/monthly limits.		** Importing minikeys is done through the deposit screen using the "Import Private Key" deposit method. Upon importing, Mt. Gox sweeps the funds to a secondary address, and then a user must wait for six confirmations before the funds will appear in the Mt. Gox account. Removing the imported bitcoins from the Mt. Gox account is treated as a bitcoin withdrawal and counts against daily/monthly limits.

Casascius: /* Python Code */

2012-11-07T00:12:42Z

Python Code

← Older revision		Revision as of 00:12, 7 November 2012
Line 91:		Line 91:

	==Python Code==		==Python Code==
	The following code produces sample ~~22-character (weaker than~~ 30-character) SHA256-based mini private keys in Python. For real-world use, ''random'' must be replaced with a better source of entropy, as the Python documentation for ''random'' states the function ''"is completely unsuitable for cryptographic purposes"''.		The following code produces sample 30-character SHA256-based mini private keys in Python. For real-world use, ''random'' must be replaced with a better source of entropy, as the Python documentation for ''random'' states the function ''"is completely unsuitable for cryptographic purposes"''.

	<source lang="python">		<source lang="python">
Line 97:		Line 97:
	import hashlib		import hashlib

	BASE58 = '~~123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz~~'		BASE58 = '23456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz'

	def Candidate():		def Candidate():
Line 104:		Line 104:
	"""		"""
	return('%s%s' % ('S', ''.join(		return('%s%s' % ('S', ''.join(
	[BASE58[ random.randrange(0,len(BASE58)) ] for i in range(21)])))		[BASE58[ random.randrange(0,len(BASE58)) ] for i in range(29)])))

	def GenerateKeys(numKeys = 10):		def GenerateKeys(numKeys = 10):
Line 155:		Line 155:
	Checks for typos in the short key.		Checks for typos in the short key.
	"""		"""
	if len(shortKey) != 22:		if len(shortKey) != 30:
	return False		return False
	t = '%s?' % shortKey		t = '%s?' % shortKey