v2.6.2 support input of a private key in base6 format which shall be defined as:99 characters (1,2,3,4,5,0) where 1=1 and 6=0

This allows you to create a private key with physical randomness with 99 rolls of a die. Use 3 dice and do 33 rolls.Then enter the 99 character string into the wallet details tab of bitaddress.org and you've got yourself a truly randomly generated bitcoin wallet.

v2.6.2 support input of a private key in base6 format which shall be defined as:99 characters (1,2,3,4,5,0) where 1=1 and 6=0

This allows you to create a private key with physical randomness with 99 rolls of a die. Use 3 dice and do 33 rolls.Then enter the 99 character string into the wallet details tab of bitaddress.org and you've got yourself a truly randomly generated bitcoin wallet.

1) The QR codes are non-standard. This is a recent change, as they used to be good. The QR Code standard says that there's supposed to be a "Quiet Zone" (whitespace) around the QR code, of 4 blocks, I believe. But in Firefox (at least), bitaddress.org writes text adjacent to the QR code.

2) When generating addresses, it'd be nice to also generate a signed message confirming that the private key is ok. For example, a simple signed message saying "This message is signed by the private key calculated for the bitcoin address 1933phfhK3ZgFQNLGSDXvqCn32k2buXY8a" could be used online to verify that the private key actually works (without copying the private key).

v2.6.2 support input of a private key in base6 format which shall be defined as:99 characters (1,2,3,4,5,0) where 1=1 and 6=0

This allows you to create a private key with physical randomness with 99 rolls of a die. Use 3 dice and do 33 rolls.Then enter the 99 character string into the wallet details tab of bitaddress.org and you've got yourself a truly randomly generated bitcoin wallet.

Unless someone reads the changelog the average user will not know what B6 means at the details tab. Perhaps a little explanation would be useful to explain the procedure for creating a B6 key.

On second thought, I think having a "dice wallet" tab would be more clear and match the rest of the website functionality.

Seems pretty technical but many seem to like the site so I will do some reading and hopefully become a user myself once I have an understanding of the general process to acquire an address kudos on the work you done on the site.

v2.6.2 support input of a private key in base6 format which shall be defined as:99 characters (1,2,3,4,5,0) where 1=1 and 6=0

This allows you to create a private key with physical randomness with 99 rolls of a die. Use 3 dice and do 33 rolls.Then enter the 99 character string into the wallet details tab of bitaddress.org and you've got yourself a truly randomly generated bitcoin wallet.

If throwing 3 dice... would need to ensure you don't introduce any bias such as reading from lowest to highest. Would be best to read dice from left to right as they fell.

Guys I was reading up in bitcoin's freenode irc room about some people arguing against paper wallets like yours versus Armory's paper wallet.

One or two of the operators stated that depositing more than one time to the public address of a printed bitaddress "wallet"/keypair will create too many signatures which the hackers will use to decode the private address.

But doesn't bitaddress not create signatures to begin with??? Can you guys explain this a little bit to a beginner like myself?

I already know that the random mouse movement and printing everything offline, in a livecd linux, will create a very secure unique set of addresses, but then when bitcoin veterans would advise against using bitaddress puts me in a dilemma on what to use.