<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://en.bitcoin.it/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Nikos+1993</id>
	<title>Bitcoin Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://en.bitcoin.it/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Nikos+1993"/>
	<link rel="alternate" type="text/html" href="https://en.bitcoin.it/wiki/Special:Contributions/Nikos_1993"/>
	<updated>2026-05-06T08:37:32Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.8</generator>
	<entry>
		<id>https://en.bitcoin.it/w/index.php?title=Mini_private_key_format&amp;diff=29918</id>
		<title>Mini private key format</title>
		<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=Mini_private_key_format&amp;diff=29918"/>
		<updated>2012-08-20T12:08:03Z</updated>

		<summary type="html">&lt;p&gt;Nikos 1993: /* Python Code */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[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&#039;s size.]]&lt;br /&gt;
The &#039;&#039;&#039;mini private key format&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
An example key using this encoding is &#039;&#039;&#039;S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Usage on a physical bitcoin==&lt;br /&gt;
The way it might appear within a physical bitcoin is on a round card printed as follows:&lt;br /&gt;
&lt;br /&gt;
Side of discs showing mini private key: (from [[Casascius physical bitcoins]])&amp;lt;br/&amp;gt;&lt;br /&gt;
[[Image:Miniprivkeys.jpg|300px]]&lt;br /&gt;
&lt;br /&gt;
Side of discs showing prefix of bitcoin address (printed on the opposite side):&amp;lt;br/&amp;gt;&lt;br /&gt;
[[Image:Minipubkeys.jpg|300px]]&lt;br /&gt;
&lt;br /&gt;
The examples in this article use the private key and Bitcoin address of the leftmost circle in the above two photos.&lt;br /&gt;
&lt;br /&gt;
==Import==&lt;br /&gt;
Mini private keys can be imported through the following clients/services:&lt;br /&gt;
&lt;br /&gt;
===Applications===&lt;br /&gt;
* [[Armory]]&lt;br /&gt;
&lt;br /&gt;
The current mainline (&amp;quot;Satoshi&amp;quot;) client cannot currently be used to import minikeys.&lt;br /&gt;
&lt;br /&gt;
===Mobile===&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
===Web===&lt;br /&gt;
&lt;br /&gt;
* [[Blockchain.info]]&lt;br /&gt;
** 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.&lt;br /&gt;
* [[Strongcoin]]&lt;br /&gt;
* [[Mt. Gox]]&lt;br /&gt;
** Importing minikeys is done through the deposit screen using the &amp;quot;Import Private Key&amp;quot; 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.&lt;br /&gt;
** Mt. Gox also permanently remembers any imported private key and automatically sweeps any future funds sent to it into the user&#039;s Mt. Gox account.&lt;br /&gt;
** Mt. Gox&#039;s import screen doesn&#039;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&#039;t recognize was &amp;quot;successfully&amp;quot; imported.&lt;br /&gt;
&lt;br /&gt;
==Decoding==&lt;br /&gt;
The private key encoding consists of 30 alphanumeric characters from the [[base58]] alphabet used in Bitcoin.  The first of the characters is always the uppercase letter S.&lt;br /&gt;
&lt;br /&gt;
A simple test must be performed to determine which method shall be used:&lt;br /&gt;
&lt;br /&gt;
# Add a question mark to the end of the mini private key string.&lt;br /&gt;
# Take the SHA256 hash of the entire string.  However, we will only looking at the first two bytes of the result.&lt;br /&gt;
# If the first byte is 00, the string is a well-formed minikey.  If the first byte is not 00, the string should be rejected as a minikey.&lt;br /&gt;
&lt;br /&gt;
===Example with SHA256===&lt;br /&gt;
Here is an example with the sample private key S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy.&lt;br /&gt;
&lt;br /&gt;
The string &amp;quot;S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy?&amp;quot; has a SHA256 value that begins with 00, so it is well-formed.&lt;br /&gt;
&lt;br /&gt;
To obtain the full 256-bit private key, simply take the SHA256 hash of the entire string.  There is no encoding for breaks in the string even if printed that way - the SHA256 should be taken of exactly thirty bytes.&lt;br /&gt;
&lt;br /&gt;
 SHA256(&amp;quot;S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy&amp;quot;) = 4C7A9640C72DC2099F23715D0C8A0D8A35F8906E3CAB61DD3F78B67BF887C9AB  &lt;br /&gt;
&lt;br /&gt;
This sample key in [[wallet export format]] is 5JPy8Zg7z4P7RSLsiqcqyeAF1935zjNUdMxcDeVrtU1oarrgnB7, and the corresponding [[Bitcoin address]] is 1CciesT23BNionJeXrbxmjc7ywfiyM4oLW.&lt;br /&gt;
&lt;br /&gt;
==Check code==&lt;br /&gt;
The mini private key format offers a simple typo check code.  Mini private keys must be generated in a &amp;quot;brute force&amp;quot; fashion, keeping only keys that conform to the format&#039;s rules.  If a key is well-formed (30 Base58 characters starting with S), but fails the hash check, then it probably contains a typo.&lt;br /&gt;
&lt;br /&gt;
If the SHA256 hash of the string followed by &#039;?&#039; doesn&#039;t result in something that begins with 0x00, the mini private key is not valid.&lt;br /&gt;
&lt;br /&gt;
==Creating mini private keys==&lt;br /&gt;
Creating mini private keys is relatively simple.  One program which can create such keys is [[Casascius Bitcoin Utility]].&lt;br /&gt;
&lt;br /&gt;
Mini private keys must be created &amp;quot;from scratch&amp;quot;, 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.&lt;br /&gt;
&lt;br /&gt;
To create mini private keys, simply create random strings that satisfy the well-formedness requirement, and then eliminate the ones that do not pass the typo check.  (This means eliminating more than 99% of the candidates.)  Then use the appropriate algorithm to compute the corresponding private key, and in turn, the matching Bitcoin address.  The Bitcoin address can always be computed from just the private key.&lt;br /&gt;
&lt;br /&gt;
It is strongly advisable to avoid using the digit &amp;quot;1&amp;quot; in minikeys unless it is being printed in such a way where a user is unlikely to mistake it for the lowercase letter &amp;quot;l&amp;quot;.  Few clients and redemption tools are prepared to tell the user that their entry containing the letter &amp;quot;l&amp;quot; should actually be the number &amp;quot;1&amp;quot; - rather, they will simply reject the code and may leave the user confused.&lt;br /&gt;
&lt;br /&gt;
In all cases, you &#039;&#039;&#039;must&#039;&#039;&#039; use a secure cryptographic random number generator to eliminate risks of predictability of the random strings.&lt;br /&gt;
&lt;br /&gt;
==Casascius Series 1 coins==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Python Code==&lt;br /&gt;
The following code produces sample 22-character (weaker than 30-character) SHA256-based mini private keys in Python.  For real-world use, &#039;&#039;random&#039;&#039; must be replaced with a better source of entropy, as the Python documentation for &#039;&#039;random&#039;&#039; states the function &#039;&#039;&amp;quot;is completely unsuitable for cryptographic purposes&amp;quot;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;python&amp;quot;&amp;gt;&lt;br /&gt;
import random&lt;br /&gt;
import hashlib&lt;br /&gt;
&lt;br /&gt;
BASE58 = &#039;123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz&#039;&lt;br /&gt;
&lt;br /&gt;
def Candidate():&lt;br /&gt;
    &amp;quot;&amp;quot;&amp;quot;&lt;br /&gt;
    Generate a random, well-formed mini private key.&lt;br /&gt;
    &amp;quot;&amp;quot;&amp;quot;&lt;br /&gt;
    return(&#039;%s%s&#039; % (&#039;S&#039;, &#039;&#039;.join(&lt;br /&gt;
        [BASE58[ random.randrange(0,len(BASE58)) ] for i in range(21)])))&lt;br /&gt;
&lt;br /&gt;
def GenerateKeys(numKeys = 10):&lt;br /&gt;
    &amp;quot;&amp;quot;&amp;quot;&lt;br /&gt;
    Generate mini private keys and output the mini key as well as the full&lt;br /&gt;
    private key. numKeys is The number of keys to generate, and &lt;br /&gt;
    &amp;quot;&amp;quot;&amp;quot;&lt;br /&gt;
    keysGenerated = 0&lt;br /&gt;
    totalCandidates = 0&lt;br /&gt;
    while keysGenerated &amp;lt; numKeys:&lt;br /&gt;
        try:&lt;br /&gt;
            cand = Candidate()&lt;br /&gt;
            # Do typo check&lt;br /&gt;
            t = &#039;%s?&#039; % cand&lt;br /&gt;
            # Take one round of SHA256&lt;br /&gt;
            candHash = hashlib.sha256(t).digest()&lt;br /&gt;
            # Check if the first eight bits of the hash are 0&lt;br /&gt;
            if candHash[0] == &#039;\x00&#039;:&lt;br /&gt;
                privateKey = GetPrivateKey(cand)&lt;br /&gt;
                print(&#039;\n%s\nSHA256( ): %s\nsha256(?): %s&#039; %&lt;br /&gt;
                      (cand, privateKey, candHash.encode(&#039;hex_codec&#039;)))&lt;br /&gt;
                if CheckShortKey(cand):&lt;br /&gt;
                    print(&#039;Validated.&#039;)&lt;br /&gt;
                else:&lt;br /&gt;
                    print(&#039;Invalid!&#039;)&lt;br /&gt;
                keysGenerated += 1&lt;br /&gt;
            totalCandidates += 1&lt;br /&gt;
        except KeyboardInterrupt:&lt;br /&gt;
            break&lt;br /&gt;
    print(&#039;\n%s: %i\n%s: %i\n%s: %r\n%s: %.1f&#039; %&lt;br /&gt;
          (&#039;Keys Generated&#039;, keysGenerated,&lt;br /&gt;
           &#039;Total Candidates&#039;, totalCandidates,&lt;br /&gt;
           &#039;Additional Security&#039;, additionalSecurity,&lt;br /&gt;
           &#039;Reject Percentage&#039;,&lt;br /&gt;
           100*(1.0-keysGenerated/float(totalCandidates))))&lt;br /&gt;
&lt;br /&gt;
def GetPrivateKey(shortKey):&lt;br /&gt;
    &amp;quot;&amp;quot;&amp;quot;&lt;br /&gt;
    Returns the hexadecimal representation of the private key corresponding&lt;br /&gt;
    to the given short key.&lt;br /&gt;
    &amp;quot;&amp;quot;&amp;quot;&lt;br /&gt;
    if CheckShortKey(shortKey):&lt;br /&gt;
        return hashlib.sha256(shortKey).hexdigest()&lt;br /&gt;
    else:&lt;br /&gt;
        print(&#039;Typo detected in private key!&#039;)&lt;br /&gt;
        return None&lt;br /&gt;
&lt;br /&gt;
def CheckShortKey(shortKey):&lt;br /&gt;
    &amp;quot;&amp;quot;&amp;quot;&lt;br /&gt;
    Checks for typos in the short key.&lt;br /&gt;
    &amp;quot;&amp;quot;&amp;quot;&lt;br /&gt;
    if len(shortKey) != 22:&lt;br /&gt;
        return False&lt;br /&gt;
    t = &#039;%s?&#039; % shortKey&lt;br /&gt;
    tHash = hashlib.sha256(t).digest()&lt;br /&gt;
    # Check to see that first byte is \x00&lt;br /&gt;
    if tHash[0] == &#039;\x00&#039;:&lt;br /&gt;
        return True&lt;br /&gt;
    return False&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;/div&gt;</summary>
		<author><name>Nikos 1993</name></author>
	</entry>
	<entry>
		<id>https://en.bitcoin.it/w/index.php?title=Mini_private_key_format&amp;diff=29917</id>
		<title>Mini private key format</title>
		<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=Mini_private_key_format&amp;diff=29917"/>
		<updated>2012-08-20T12:07:20Z</updated>

		<summary type="html">&lt;p&gt;Nikos 1993: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[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&#039;s size.]]&lt;br /&gt;
The &#039;&#039;&#039;mini private key format&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
An example key using this encoding is &#039;&#039;&#039;S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Usage on a physical bitcoin==&lt;br /&gt;
The way it might appear within a physical bitcoin is on a round card printed as follows:&lt;br /&gt;
&lt;br /&gt;
Side of discs showing mini private key: (from [[Casascius physical bitcoins]])&amp;lt;br/&amp;gt;&lt;br /&gt;
[[Image:Miniprivkeys.jpg|300px]]&lt;br /&gt;
&lt;br /&gt;
Side of discs showing prefix of bitcoin address (printed on the opposite side):&amp;lt;br/&amp;gt;&lt;br /&gt;
[[Image:Minipubkeys.jpg|300px]]&lt;br /&gt;
&lt;br /&gt;
The examples in this article use the private key and Bitcoin address of the leftmost circle in the above two photos.&lt;br /&gt;
&lt;br /&gt;
==Import==&lt;br /&gt;
Mini private keys can be imported through the following clients/services:&lt;br /&gt;
&lt;br /&gt;
===Applications===&lt;br /&gt;
* [[Armory]]&lt;br /&gt;
&lt;br /&gt;
The current mainline (&amp;quot;Satoshi&amp;quot;) client cannot currently be used to import minikeys.&lt;br /&gt;
&lt;br /&gt;
===Mobile===&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
===Web===&lt;br /&gt;
&lt;br /&gt;
* [[Blockchain.info]]&lt;br /&gt;
** 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.&lt;br /&gt;
* [[Strongcoin]]&lt;br /&gt;
* [[Mt. Gox]]&lt;br /&gt;
** Importing minikeys is done through the deposit screen using the &amp;quot;Import Private Key&amp;quot; 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.&lt;br /&gt;
** Mt. Gox also permanently remembers any imported private key and automatically sweeps any future funds sent to it into the user&#039;s Mt. Gox account.&lt;br /&gt;
** Mt. Gox&#039;s import screen doesn&#039;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&#039;t recognize was &amp;quot;successfully&amp;quot; imported.&lt;br /&gt;
&lt;br /&gt;
==Decoding==&lt;br /&gt;
The private key encoding consists of 30 alphanumeric characters from the [[base58]] alphabet used in Bitcoin.  The first of the characters is always the uppercase letter S.&lt;br /&gt;
&lt;br /&gt;
A simple test must be performed to determine which method shall be used:&lt;br /&gt;
&lt;br /&gt;
# Add a question mark to the end of the mini private key string.&lt;br /&gt;
# Take the SHA256 hash of the entire string.  However, we will only looking at the first two bytes of the result.&lt;br /&gt;
# If the first byte is 00, the string is a well-formed minikey.  If the first byte is not 00, the string should be rejected as a minikey.&lt;br /&gt;
&lt;br /&gt;
===Example with SHA256===&lt;br /&gt;
Here is an example with the sample private key S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy.&lt;br /&gt;
&lt;br /&gt;
The string &amp;quot;S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy?&amp;quot; has a SHA256 value that begins with 00, so it is well-formed.&lt;br /&gt;
&lt;br /&gt;
To obtain the full 256-bit private key, simply take the SHA256 hash of the entire string.  There is no encoding for breaks in the string even if printed that way - the SHA256 should be taken of exactly thirty bytes.&lt;br /&gt;
&lt;br /&gt;
 SHA256(&amp;quot;S6c56bnXQiBjk9mqSYE7ykVQ7NzrRy&amp;quot;) = 4C7A9640C72DC2099F23715D0C8A0D8A35F8906E3CAB61DD3F78B67BF887C9AB  &lt;br /&gt;
&lt;br /&gt;
This sample key in [[wallet export format]] is 5JPy8Zg7z4P7RSLsiqcqyeAF1935zjNUdMxcDeVrtU1oarrgnB7, and the corresponding [[Bitcoin address]] is 1CciesT23BNionJeXrbxmjc7ywfiyM4oLW.&lt;br /&gt;
&lt;br /&gt;
==Check code==&lt;br /&gt;
The mini private key format offers a simple typo check code.  Mini private keys must be generated in a &amp;quot;brute force&amp;quot; fashion, keeping only keys that conform to the format&#039;s rules.  If a key is well-formed (30 Base58 characters starting with S), but fails the hash check, then it probably contains a typo.&lt;br /&gt;
&lt;br /&gt;
If the SHA256 hash of the string followed by &#039;?&#039; doesn&#039;t result in something that begins with 0x00, the mini private key is not valid.&lt;br /&gt;
&lt;br /&gt;
==Creating mini private keys==&lt;br /&gt;
Creating mini private keys is relatively simple.  One program which can create such keys is [[Casascius Bitcoin Utility]].&lt;br /&gt;
&lt;br /&gt;
Mini private keys must be created &amp;quot;from scratch&amp;quot;, 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.&lt;br /&gt;
&lt;br /&gt;
To create mini private keys, simply create random strings that satisfy the well-formedness requirement, and then eliminate the ones that do not pass the typo check.  (This means eliminating more than 99% of the candidates.)  Then use the appropriate algorithm to compute the corresponding private key, and in turn, the matching Bitcoin address.  The Bitcoin address can always be computed from just the private key.&lt;br /&gt;
&lt;br /&gt;
It is strongly advisable to avoid using the digit &amp;quot;1&amp;quot; in minikeys unless it is being printed in such a way where a user is unlikely to mistake it for the lowercase letter &amp;quot;l&amp;quot;.  Few clients and redemption tools are prepared to tell the user that their entry containing the letter &amp;quot;l&amp;quot; should actually be the number &amp;quot;1&amp;quot; - rather, they will simply reject the code and may leave the user confused.&lt;br /&gt;
&lt;br /&gt;
In all cases, you &#039;&#039;&#039;must&#039;&#039;&#039; use a secure cryptographic random number generator to eliminate risks of predictability of the random strings.&lt;br /&gt;
&lt;br /&gt;
==Casascius Series 1 coins==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Python Code==&lt;br /&gt;
The following code produces sample SHA256-based mini private keys in Python.  For real-world use, &#039;&#039;random&#039;&#039; must be replaced with a better source of entropy, as the Python documentation for &#039;&#039;random&#039;&#039; states the function &#039;&#039;&amp;quot;is completely unsuitable for cryptographic purposes&amp;quot;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;python&amp;quot;&amp;gt;&lt;br /&gt;
import random&lt;br /&gt;
import hashlib&lt;br /&gt;
&lt;br /&gt;
BASE58 = &#039;123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz&#039;&lt;br /&gt;
&lt;br /&gt;
def Candidate():&lt;br /&gt;
    &amp;quot;&amp;quot;&amp;quot;&lt;br /&gt;
    Generate a random, well-formed mini private key.&lt;br /&gt;
    &amp;quot;&amp;quot;&amp;quot;&lt;br /&gt;
    return(&#039;%s%s&#039; % (&#039;S&#039;, &#039;&#039;.join(&lt;br /&gt;
        [BASE58[ random.randrange(0,len(BASE58)) ] for i in range(21)])))&lt;br /&gt;
&lt;br /&gt;
def GenerateKeys(numKeys = 10):&lt;br /&gt;
    &amp;quot;&amp;quot;&amp;quot;&lt;br /&gt;
    Generate mini private keys and output the mini key as well as the full&lt;br /&gt;
    private key. numKeys is The number of keys to generate, and &lt;br /&gt;
    &amp;quot;&amp;quot;&amp;quot;&lt;br /&gt;
    keysGenerated = 0&lt;br /&gt;
    totalCandidates = 0&lt;br /&gt;
    while keysGenerated &amp;lt; numKeys:&lt;br /&gt;
        try:&lt;br /&gt;
            cand = Candidate()&lt;br /&gt;
            # Do typo check&lt;br /&gt;
            t = &#039;%s?&#039; % cand&lt;br /&gt;
            # Take one round of SHA256&lt;br /&gt;
            candHash = hashlib.sha256(t).digest()&lt;br /&gt;
            # Check if the first eight bits of the hash are 0&lt;br /&gt;
            if candHash[0] == &#039;\x00&#039;:&lt;br /&gt;
                privateKey = GetPrivateKey(cand)&lt;br /&gt;
                print(&#039;\n%s\nSHA256( ): %s\nsha256(?): %s&#039; %&lt;br /&gt;
                      (cand, privateKey, candHash.encode(&#039;hex_codec&#039;)))&lt;br /&gt;
                if CheckShortKey(cand):&lt;br /&gt;
                    print(&#039;Validated.&#039;)&lt;br /&gt;
                else:&lt;br /&gt;
                    print(&#039;Invalid!&#039;)&lt;br /&gt;
                keysGenerated += 1&lt;br /&gt;
            totalCandidates += 1&lt;br /&gt;
        except KeyboardInterrupt:&lt;br /&gt;
            break&lt;br /&gt;
    print(&#039;\n%s: %i\n%s: %i\n%s: %r\n%s: %.1f&#039; %&lt;br /&gt;
          (&#039;Keys Generated&#039;, keysGenerated,&lt;br /&gt;
           &#039;Total Candidates&#039;, totalCandidates,&lt;br /&gt;
           &#039;Additional Security&#039;, additionalSecurity,&lt;br /&gt;
           &#039;Reject Percentage&#039;,&lt;br /&gt;
           100*(1.0-keysGenerated/float(totalCandidates))))&lt;br /&gt;
&lt;br /&gt;
def GetPrivateKey(shortKey):&lt;br /&gt;
    &amp;quot;&amp;quot;&amp;quot;&lt;br /&gt;
    Returns the hexadecimal representation of the private key corresponding&lt;br /&gt;
    to the given short key.&lt;br /&gt;
    &amp;quot;&amp;quot;&amp;quot;&lt;br /&gt;
    if CheckShortKey(shortKey):&lt;br /&gt;
        return hashlib.sha256(shortKey).hexdigest()&lt;br /&gt;
    else:&lt;br /&gt;
        print(&#039;Typo detected in private key!&#039;)&lt;br /&gt;
        return None&lt;br /&gt;
&lt;br /&gt;
def CheckShortKey(shortKey):&lt;br /&gt;
    &amp;quot;&amp;quot;&amp;quot;&lt;br /&gt;
    Checks for typos in the short key.&lt;br /&gt;
    &amp;quot;&amp;quot;&amp;quot;&lt;br /&gt;
    if len(shortKey) != 22:&lt;br /&gt;
        return False&lt;br /&gt;
    t = &#039;%s?&#039; % shortKey&lt;br /&gt;
    tHash = hashlib.sha256(t).digest()&lt;br /&gt;
    # Check to see that first byte is \x00&lt;br /&gt;
    if tHash[0] == &#039;\x00&#039;:&lt;br /&gt;
        return True&lt;br /&gt;
    return False&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;/div&gt;</summary>
		<author><name>Nikos 1993</name></author>
	</entry>
	<entry>
		<id>https://en.bitcoin.it/w/index.php?title=Casascius_physical_bitcoins&amp;diff=29916</id>
		<title>Casascius physical bitcoins</title>
		<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=Casascius_physical_bitcoins&amp;diff=29916"/>
		<updated>2012-08-20T12:06:28Z</updated>

		<summary type="html">&lt;p&gt;Nikos 1993: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:Casascius 25btc size compare.jpg|thumb|right|300px|Various views of Casascius coins]]&lt;br /&gt;
[[File:Physbitcoinkey.jpg|thumb|right|Redeemed Casascius coin]]&lt;br /&gt;
&#039;&#039;&#039;Casascius physical bitcoins&#039;&#039;&#039;, also called &#039;&#039;&#039;Casascius coins&#039;&#039;&#039;, are physical metal coins created by Bitcoin user [[User:Casascius|Casascius]] (Mike Caldwell, Sandy, Utah, USA) that contain an embedded piece of paper with digital Bitcoin value, covered by a tamper-resistant hologram.  Casascius coins are available in 1, 10, 25, 100, and 1000 BTC increments.  They can be purchased at Casascius&#039;s website, https://www.casascius.com (only Bitcoin accepted), or at http://www.MemoryDealers.com (PayPal and credit cards accepted).&lt;br /&gt;
&lt;br /&gt;
The coins are designed such that they could be circulated in face-to-face transactions.  The first person to redeem a private key gets the value on the coin, and afterwards, the coin no longer has any Bitcoin value.  However, it is difficult or impossible to read the private key on the coin without damaging or destroying the hologram, which exposes a honeycomb-like tamper evidence pattern when peeled.&lt;br /&gt;
&lt;br /&gt;
The piece of paper inside each coin has a [[private key]] which forms the backing for the Bitcoin value represented by the coin.  Redeeming the private key back into digital Bitcoins is currently available at [[MtGox]] (via the &#039;&#039;Add Funds - Redeem Private Key&#039;&#039; screen), as well as with a patched Bitcoin client.&lt;br /&gt;
&lt;br /&gt;
Casascius coins are similar to [[Bitbills]] in that they are an object that contains a redemption code that serves as a bearer item for digital bitcoins.&lt;br /&gt;
&lt;br /&gt;
An independent website called [[Casascius Bitcoin Analyzer]] (http://www.uberbills.com) tracks the status of all Casascius coins in circulation, based on information from the block chain, as well as &lt;br /&gt;
&lt;br /&gt;
==Releases of Casascius coins==&lt;br /&gt;
&lt;br /&gt;
===Original series 1 BTC coin===&lt;br /&gt;
* 1.125 inches in diameter&lt;br /&gt;
* Solid brass&lt;br /&gt;
* Year printed on coins: 2011&lt;br /&gt;
* Approximately 0.24 ounces&lt;br /&gt;
* Eight-digit &amp;quot;[[firstbits]]&amp;quot; inkjetted onto surface of hologram sticker&lt;br /&gt;
* First appeared in September 2011&amp;lt;ref&amp;gt;[http://bitcointalk.org/index.php?topic=41892.0 CASASCIUS PHYSICAL BITCOIN - In Stock Now!]&amp;lt;/ref&amp;gt;.&lt;br /&gt;
* Private key: 22 character string inside the coin, the 256-bit private key is SHA256(string)&lt;br /&gt;
* Approximate number produced: 3,500 as of November 2011&lt;br /&gt;
* A spelling error can be found in the small lettering of the hologram: &amp;quot;CASACIUS&amp;quot; instead of &amp;quot;CASASCIUS&amp;quot;&lt;br /&gt;
* Casascius has stated that no more than 11,000 may be produced&lt;br /&gt;
* All 11,000 Bitcoin addresses pre-generated for the series have been published as a signed text file&lt;br /&gt;
&lt;br /&gt;
===Second series 1 BTC coin===&lt;br /&gt;
[[Image:Casascius-series-2.jpg|thumb|right|200px|Second series 1 BTC Casascius coin]]&lt;br /&gt;
The hologram and the private key is different, the metal part of the coin is the same as the first series.&lt;br /&gt;
* 1.125 inches in diameter&lt;br /&gt;
* Solid brass&lt;br /&gt;
* Year printed on coins: 2011&lt;br /&gt;
* Approximately 0.24 ounces&lt;br /&gt;
* Denomination (&amp;quot;ONE BTC&amp;quot;) appears on the hologram&lt;br /&gt;
* Eight-digit &amp;quot;firstbits&amp;quot; visible through a small transparent window that allows limited visibility of one side of the private key paper&lt;br /&gt;
* Private key: 30 character string inside the coin, the 256-private key is SHA256(string)&lt;br /&gt;
* First appeared in November 2011&lt;br /&gt;
* No spelling error in hologram&lt;br /&gt;
&lt;br /&gt;
===10 BTC silver round===&lt;br /&gt;
* First available on Dec 1, 2011&lt;br /&gt;
* 39mm diameter&lt;br /&gt;
* 1 troy ounce .999 Fine Silver&lt;br /&gt;
* Uses second series holograms marked TEN BTC&lt;br /&gt;
* Comes in a clear plastic capsule&lt;br /&gt;
* Zeroes and ones on the back encode the message &amp;quot;Bitcoin: an idea too big to fail&amp;quot;&lt;br /&gt;
&lt;br /&gt;
===25 BTC coin===&lt;br /&gt;
[[Image:Casascius 25btc.jpg|thumb|right|Casascius 25BTC coin]]&lt;br /&gt;
* 1.75 inches in diameter, about 3mm thick&lt;br /&gt;
* Gold-plated alloy&lt;br /&gt;
* Approximately 1.2 ounces&lt;br /&gt;
* Printed year: 2011&lt;br /&gt;
* Uses same holograms and private key scheme as original series 1 BTC coin&lt;br /&gt;
* First appeared in October 2011&lt;br /&gt;
* Zeroes and ones on the back encode the message &amp;quot;You asked for change, we gave you coins&amp;quot;&lt;br /&gt;
&lt;br /&gt;
===100 BTC gold plated bar===&lt;br /&gt;
* Weight: 4.2oz&lt;br /&gt;
* Dimensions: 8cm x 4cm x 0.6cm&lt;br /&gt;
* Printed year: none&lt;br /&gt;
* Indented features: &amp;quot;100 BTC&amp;quot;, Bitcoin logo, &amp;quot;gold plated bearer bar&amp;quot;&lt;br /&gt;
* Hologram: V1 or V2&lt;br /&gt;
&lt;br /&gt;
===1000 BTC gold plated bar===&lt;br /&gt;
* Weight: 4.2oz&lt;br /&gt;
* Dimensions: 8cm x 4cm x 0.6cm&lt;br /&gt;
* Hologram: V1&lt;br /&gt;
* Printed year: none&lt;br /&gt;
* Lasered overprinting on the hologram to indicate the denomination&lt;br /&gt;
* This is a non-denominated bar that has been engraved with a 1000 BTC denomination.  It is indented with the Bitcoin logo and the words &amp;quot;gold plated bearer bar&amp;quot; like the 100 BTC bar, but is not indented with a denomination.  The denomination is applied via laser engraving.&lt;br /&gt;
* This item is presently listed for sale only through MemoryDealers.com&lt;br /&gt;
&lt;br /&gt;
===1000 BTC 1 troy ounce gold coin===&lt;br /&gt;
* Available as of Dec 16, 2011&lt;br /&gt;
* Printed year: 2012&lt;br /&gt;
* Diameter: 30mm&lt;br /&gt;
* Special order item, 3 business day lead time&lt;br /&gt;
* Hologram: V1 with Bitcoin address lasered at top instead of inkjetted across middle&lt;br /&gt;
* Availability: Purchase from MemoryDealers.com, or directly from Casascius with BTC, or USD bank wire&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
* [[Mini private key format]]&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Physical bitcoins]]&lt;/div&gt;</summary>
		<author><name>Nikos 1993</name></author>
	</entry>
	<entry>
		<id>https://en.bitcoin.it/w/index.php?title=Casascius_physical_bitcoins&amp;diff=29915</id>
		<title>Casascius physical bitcoins</title>
		<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=Casascius_physical_bitcoins&amp;diff=29915"/>
		<updated>2012-08-20T12:05:25Z</updated>

		<summary type="html">&lt;p&gt;Nikos 1993: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:Casascius 25btc size compare.jpg|thumb|right|300px|Various views of Casascius coins]]&lt;br /&gt;
[[File:Physbitcoinkey.jpg|thumb|right|Redeemed Casascius coin]]&lt;br /&gt;
[[File:Miniprivkeys.jpg|right]]&lt;br /&gt;
[[File:Minipubkeys.jpg|right]]&lt;br /&gt;
&#039;&#039;&#039;Casascius physical bitcoins&#039;&#039;&#039;, also called &#039;&#039;&#039;Casascius coins&#039;&#039;&#039;, are physical metal coins created by Bitcoin user [[User:Casascius|Casascius]] (Mike Caldwell, Sandy, Utah, USA) that contain an embedded piece of paper with digital Bitcoin value, covered by a tamper-resistant hologram.  Casascius coins are available in 1, 10, 25, 100, and 1000 BTC increments.  They can be purchased at Casascius&#039;s website, https://www.casascius.com (only Bitcoin accepted), or at http://www.MemoryDealers.com (PayPal and credit cards accepted).&lt;br /&gt;
&lt;br /&gt;
The coins are designed such that they could be circulated in face-to-face transactions.  The first person to redeem a private key gets the value on the coin, and afterwards, the coin no longer has any Bitcoin value.  However, it is difficult or impossible to read the private key on the coin without damaging or destroying the hologram, which exposes a honeycomb-like tamper evidence pattern when peeled.&lt;br /&gt;
&lt;br /&gt;
The piece of paper inside each coin has a [[private key]] which forms the backing for the Bitcoin value represented by the coin.  Redeeming the private key back into digital Bitcoins is currently available at [[MtGox]] (via the &#039;&#039;Add Funds - Redeem Private Key&#039;&#039; screen), as well as with a patched Bitcoin client.&lt;br /&gt;
&lt;br /&gt;
Casascius coins are similar to [[Bitbills]] in that they are an object that contains a redemption code that serves as a bearer item for digital bitcoins.&lt;br /&gt;
&lt;br /&gt;
An independent website called [[Casascius Bitcoin Analyzer]] (http://www.uberbills.com) tracks the status of all Casascius coins in circulation, based on information from the block chain, as well as &lt;br /&gt;
&lt;br /&gt;
==Releases of Casascius coins==&lt;br /&gt;
&lt;br /&gt;
===Original series 1 BTC coin===&lt;br /&gt;
* 1.125 inches in diameter&lt;br /&gt;
* Solid brass&lt;br /&gt;
* Year printed on coins: 2011&lt;br /&gt;
* Approximately 0.24 ounces&lt;br /&gt;
* Eight-digit &amp;quot;[[firstbits]]&amp;quot; inkjetted onto surface of hologram sticker&lt;br /&gt;
* First appeared in September 2011&amp;lt;ref&amp;gt;[http://bitcointalk.org/index.php?topic=41892.0 CASASCIUS PHYSICAL BITCOIN - In Stock Now!]&amp;lt;/ref&amp;gt;.&lt;br /&gt;
* Private key: 22 character string inside the coin, the 256-bit private key is SHA256(string)&lt;br /&gt;
* Approximate number produced: 3,500 as of November 2011&lt;br /&gt;
* A spelling error can be found in the small lettering of the hologram: &amp;quot;CASACIUS&amp;quot; instead of &amp;quot;CASASCIUS&amp;quot;&lt;br /&gt;
* Casascius has stated that no more than 11,000 may be produced&lt;br /&gt;
* All 11,000 Bitcoin addresses pre-generated for the series have been published as a signed text file&lt;br /&gt;
&lt;br /&gt;
===Second series 1 BTC coin===&lt;br /&gt;
[[Image:Casascius-series-2.jpg|thumb|right|200px|Second series 1 BTC Casascius coin]]&lt;br /&gt;
The hologram and the private key is different, the metal part of the coin is the same as the first series.&lt;br /&gt;
* 1.125 inches in diameter&lt;br /&gt;
* Solid brass&lt;br /&gt;
* Year printed on coins: 2011&lt;br /&gt;
* Approximately 0.24 ounces&lt;br /&gt;
* Denomination (&amp;quot;ONE BTC&amp;quot;) appears on the hologram&lt;br /&gt;
* Eight-digit &amp;quot;firstbits&amp;quot; visible through a small transparent window that allows limited visibility of one side of the private key paper&lt;br /&gt;
* Private key: 30 character string inside the coin, the 256-private key is SHA256(string)&lt;br /&gt;
* First appeared in November 2011&lt;br /&gt;
* No spelling error in hologram&lt;br /&gt;
&lt;br /&gt;
===10 BTC silver round===&lt;br /&gt;
* First available on Dec 1, 2011&lt;br /&gt;
* 39mm diameter&lt;br /&gt;
* 1 troy ounce .999 Fine Silver&lt;br /&gt;
* Uses second series holograms marked TEN BTC&lt;br /&gt;
* Comes in a clear plastic capsule&lt;br /&gt;
* Zeroes and ones on the back encode the message &amp;quot;Bitcoin: an idea too big to fail&amp;quot;&lt;br /&gt;
&lt;br /&gt;
===25 BTC coin===&lt;br /&gt;
[[Image:Casascius 25btc.jpg|thumb|right|Casascius 25BTC coin]]&lt;br /&gt;
* 1.75 inches in diameter, about 3mm thick&lt;br /&gt;
* Gold-plated alloy&lt;br /&gt;
* Approximately 1.2 ounces&lt;br /&gt;
* Printed year: 2011&lt;br /&gt;
* Uses same holograms and private key scheme as original series 1 BTC coin&lt;br /&gt;
* First appeared in October 2011&lt;br /&gt;
* Zeroes and ones on the back encode the message &amp;quot;You asked for change, we gave you coins&amp;quot;&lt;br /&gt;
&lt;br /&gt;
===100 BTC gold plated bar===&lt;br /&gt;
* Weight: 4.2oz&lt;br /&gt;
* Dimensions: 8cm x 4cm x 0.6cm&lt;br /&gt;
* Printed year: none&lt;br /&gt;
* Indented features: &amp;quot;100 BTC&amp;quot;, Bitcoin logo, &amp;quot;gold plated bearer bar&amp;quot;&lt;br /&gt;
* Hologram: V1 or V2&lt;br /&gt;
&lt;br /&gt;
===1000 BTC gold plated bar===&lt;br /&gt;
* Weight: 4.2oz&lt;br /&gt;
* Dimensions: 8cm x 4cm x 0.6cm&lt;br /&gt;
* Hologram: V1&lt;br /&gt;
* Printed year: none&lt;br /&gt;
* Lasered overprinting on the hologram to indicate the denomination&lt;br /&gt;
* This is a non-denominated bar that has been engraved with a 1000 BTC denomination.  It is indented with the Bitcoin logo and the words &amp;quot;gold plated bearer bar&amp;quot; like the 100 BTC bar, but is not indented with a denomination.  The denomination is applied via laser engraving.&lt;br /&gt;
* This item is presently listed for sale only through MemoryDealers.com&lt;br /&gt;
&lt;br /&gt;
===1000 BTC 1 troy ounce gold coin===&lt;br /&gt;
* Available as of Dec 16, 2011&lt;br /&gt;
* Printed year: 2012&lt;br /&gt;
* Diameter: 30mm&lt;br /&gt;
* Special order item, 3 business day lead time&lt;br /&gt;
* Hologram: V1 with Bitcoin address lasered at top instead of inkjetted across middle&lt;br /&gt;
* Availability: Purchase from MemoryDealers.com, or directly from Casascius with BTC, or USD bank wire&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Physical bitcoins]]&lt;/div&gt;</summary>
		<author><name>Nikos 1993</name></author>
	</entry>
	<entry>
		<id>https://en.bitcoin.it/w/index.php?title=Casascius_physical_bitcoins&amp;diff=29913</id>
		<title>Casascius physical bitcoins</title>
		<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=Casascius_physical_bitcoins&amp;diff=29913"/>
		<updated>2012-08-20T11:52:45Z</updated>

		<summary type="html">&lt;p&gt;Nikos 1993: +redeemed picture&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:Casascius 25btc size compare.jpg|thumb|right|300px|Various views of Casascius coins]]&lt;br /&gt;
[[File:Physbitcoinkey.jpg|thumb|right|Redeemed Casascius coin]]&lt;br /&gt;
&#039;&#039;&#039;Casascius physical bitcoins&#039;&#039;&#039;, also called &#039;&#039;&#039;Casascius coins&#039;&#039;&#039;, are physical metal coins created by Bitcoin user [[User:Casascius|Casascius]] (Mike Caldwell, Sandy, Utah, USA) that contain an embedded piece of paper with digital Bitcoin value, covered by a tamper-resistant hologram.  Casascius coins are available in 1, 10, 25, 100, and 1000 BTC increments.  They can be purchased at Casascius&#039;s website, https://www.casascius.com (only Bitcoin accepted), or at http://www.MemoryDealers.com (PayPal and credit cards accepted).&lt;br /&gt;
&lt;br /&gt;
The coins are designed such that they could be circulated in face-to-face transactions.  The first person to redeem a private key gets the value on the coin, and afterwards, the coin no longer has any Bitcoin value.  However, it is difficult or impossible to read the private key on the coin without damaging or destroying the hologram, which exposes a honeycomb-like tamper evidence pattern when peeled.&lt;br /&gt;
&lt;br /&gt;
The piece of paper inside each coin has a [[private key]] which forms the backing for the Bitcoin value represented by the coin.  Redeeming the private key back into digital Bitcoins is currently available at [[MtGox]] (via the &#039;&#039;Add Funds - Redeem Private Key&#039;&#039; screen), as well as with a patched Bitcoin client.&lt;br /&gt;
&lt;br /&gt;
Casascius coins are similar to [[Bitbills]] in that they are an object that contains a redemption code that serves as a bearer item for digital bitcoins.&lt;br /&gt;
&lt;br /&gt;
An independent website called [[Casascius Bitcoin Analyzer]] (http://www.uberbills.com) tracks the status of all Casascius coins in circulation, based on information from the block chain, as well as &lt;br /&gt;
&lt;br /&gt;
==Releases of Casascius coins==&lt;br /&gt;
&lt;br /&gt;
===Original series 1 BTC coin===&lt;br /&gt;
* 1.125 inches in diameter&lt;br /&gt;
* Solid brass&lt;br /&gt;
* Year printed on coins: 2011&lt;br /&gt;
* Approximately 0.24 ounces&lt;br /&gt;
* Eight-digit &amp;quot;[[firstbits]]&amp;quot; inkjetted onto surface of hologram sticker&lt;br /&gt;
* First appeared in September 2011&amp;lt;ref&amp;gt;[http://bitcointalk.org/index.php?topic=41892.0 CASASCIUS PHYSICAL BITCOIN - In Stock Now!]&amp;lt;/ref&amp;gt;.&lt;br /&gt;
* Private key: 22 character string inside the coin, the 256-bit private key is SHA256(string)&lt;br /&gt;
* Approximate number produced: 3,500 as of November 2011&lt;br /&gt;
* A spelling error can be found in the small lettering of the hologram: &amp;quot;CASACIUS&amp;quot; instead of &amp;quot;CASASCIUS&amp;quot;&lt;br /&gt;
* Casascius has stated that no more than 11,000 may be produced&lt;br /&gt;
* All 11,000 Bitcoin addresses pre-generated for the series have been published as a signed text file&lt;br /&gt;
&lt;br /&gt;
===Second series 1 BTC coin===&lt;br /&gt;
[[Image:Casascius-series-2.jpg|thumb|right|200px|Second series 1 BTC Casascius coin]]&lt;br /&gt;
The hologram and the private key is different, the metal part of the coin is the same as the first series.&lt;br /&gt;
* 1.125 inches in diameter&lt;br /&gt;
* Solid brass&lt;br /&gt;
* Year printed on coins: 2011&lt;br /&gt;
* Approximately 0.24 ounces&lt;br /&gt;
* Denomination (&amp;quot;ONE BTC&amp;quot;) appears on the hologram&lt;br /&gt;
* Eight-digit &amp;quot;firstbits&amp;quot; visible through a small transparent window that allows limited visibility of one side of the private key paper&lt;br /&gt;
* Private key: 30 character string inside the coin, the 256-private key is SHA256(string)&lt;br /&gt;
* First appeared in November 2011&lt;br /&gt;
* No spelling error in hologram&lt;br /&gt;
&lt;br /&gt;
===10 BTC silver round===&lt;br /&gt;
* First available on Dec 1, 2011&lt;br /&gt;
* 39mm diameter&lt;br /&gt;
* 1 troy ounce .999 Fine Silver&lt;br /&gt;
* Uses second series holograms marked TEN BTC&lt;br /&gt;
* Comes in a clear plastic capsule&lt;br /&gt;
* Zeroes and ones on the back encode the message &amp;quot;Bitcoin: an idea too big to fail&amp;quot;&lt;br /&gt;
&lt;br /&gt;
===25 BTC coin===&lt;br /&gt;
[[Image:Casascius 25btc.jpg|thumb|right|Casascius 25BTC coin]]&lt;br /&gt;
* 1.75 inches in diameter, about 3mm thick&lt;br /&gt;
* Gold-plated alloy&lt;br /&gt;
* Approximately 1.2 ounces&lt;br /&gt;
* Printed year: 2011&lt;br /&gt;
* Uses same holograms and private key scheme as original series 1 BTC coin&lt;br /&gt;
* First appeared in October 2011&lt;br /&gt;
* Zeroes and ones on the back encode the message &amp;quot;You asked for change, we gave you coins&amp;quot;&lt;br /&gt;
&lt;br /&gt;
===100 BTC gold plated bar===&lt;br /&gt;
* Weight: 4.2oz&lt;br /&gt;
* Dimensions: 8cm x 4cm x 0.6cm&lt;br /&gt;
* Printed year: none&lt;br /&gt;
* Indented features: &amp;quot;100 BTC&amp;quot;, Bitcoin logo, &amp;quot;gold plated bearer bar&amp;quot;&lt;br /&gt;
* Hologram: V1 or V2&lt;br /&gt;
&lt;br /&gt;
===1000 BTC gold plated bar===&lt;br /&gt;
* Weight: 4.2oz&lt;br /&gt;
* Dimensions: 8cm x 4cm x 0.6cm&lt;br /&gt;
* Hologram: V1&lt;br /&gt;
* Printed year: none&lt;br /&gt;
* Lasered overprinting on the hologram to indicate the denomination&lt;br /&gt;
* This is a non-denominated bar that has been engraved with a 1000 BTC denomination.  It is indented with the Bitcoin logo and the words &amp;quot;gold plated bearer bar&amp;quot; like the 100 BTC bar, but is not indented with a denomination.  The denomination is applied via laser engraving.&lt;br /&gt;
* This item is presently listed for sale only through MemoryDealers.com&lt;br /&gt;
&lt;br /&gt;
===1000 BTC 1 troy ounce gold coin===&lt;br /&gt;
* Available as of Dec 16, 2011&lt;br /&gt;
* Printed year: 2012&lt;br /&gt;
* Diameter: 30mm&lt;br /&gt;
* Special order item, 3 business day lead time&lt;br /&gt;
* Hologram: V1 with Bitcoin address lasered at top instead of inkjetted across middle&lt;br /&gt;
* Availability: Purchase from MemoryDealers.com, or directly from Casascius with BTC, or USD bank wire&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Physical bitcoins]]&lt;/div&gt;</summary>
		<author><name>Nikos 1993</name></author>
	</entry>
	<entry>
		<id>https://en.bitcoin.it/w/index.php?title=File:Physbitcoinkey.jpg&amp;diff=29912</id>
		<title>File:Physbitcoinkey.jpg</title>
		<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=File:Physbitcoinkey.jpg&amp;diff=29912"/>
		<updated>2012-08-20T11:50:54Z</updated>

		<summary type="html">&lt;p&gt;Nikos 1993: Source: http://img199.imageshack.us/img199/6272/physbitcoinkey.jpg&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Source: http://img199.imageshack.us/img199/6272/physbitcoinkey.jpg&lt;/div&gt;</summary>
		<author><name>Nikos 1993</name></author>
	</entry>
</feed>