Pages:
Author

Topic: Questions on Private Key Generation - page 2. (Read 2008 times)

legendary
Activity: 1092
Merit: 1001
January 25, 2015, 03:29:15 PM
#4
From https://en.bitcoin.it/wiki/Private_key#Base58_Wallet_Import_format:

"Wallet import format is the most common way to represent private keys in Bitcoin. For private keys associated with uncompressed public keys, they are 51 characters and always start with the number 5 on mainnet (9 on testnet). Private keys associated with compressed public keys are 52 characters and start with a capital L or K on mainnet (c on testnet)."

The beginning encodes some metadata, like a version id; so you shouldn't expect the first two characters to be very random. But if the software you're using generates keys beginning with 5 instead of L or K it is outdated and producing keys which will result in significantly more data-size in your transactions.

I would recommend avoiding any browser based key generators. Many of them have dangerous implementations which provide little to no cryptographic security at all, most of them have never been reviewed by a third party.

Thank you both for your answers. I understand now, I'm just a noob. lol.

Two other question though.

(1) If you do not recommend browser based key generation (most people if not all here and on other sites tell people to go to bitaddress.org and use them in an offline manner for cold storage addresses generations), what do you consider to be reviewed or vetted and approved as being most safe for privatekey generation?

(2) Also, if there are privatekeys that are compressed and uncompressed, compression being used to cause less strain on the "Bitcoin Network", how come there isn't a dev mandated update or movement toward all future addresses being generated as compressed? (with old non-compressed addresses generated in the past still being accepted and usable by the network, of course)

Thanks again.
staff
Activity: 4284
Merit: 8808
January 25, 2015, 02:46:33 PM
#3
The beginning encodes some metadata, like a version id; so you shouldn't expect the first two characters to be very random. But if the software you're using generates keys beginning with 5 instead of L or K it is outdated and producing keys which will result in significantly more data-size in your transactions.

I would recommend avoiding any browser based key generators. Many of them have dangerous implementations which provide little to no cryptographic security at all, most of them have never been reviewed by a third party.
hero member
Activity: 910
Merit: 1000
January 25, 2015, 02:38:18 PM
#2
From https://en.bitcoin.it/wiki/Private_key#Base58_Wallet_Import_format:

"Wallet import format is the most common way to represent private keys in Bitcoin. For private keys associated with uncompressed public keys, they are 51 characters and always start with the number 5 on mainnet (9 on testnet). Private keys associated with compressed public keys are 52 characters and start with a capital L or K on mainnet (c on testnet)."
legendary
Activity: 1092
Merit: 1001
January 25, 2015, 02:26:24 PM
#1
Hey everyone,

I have been generating many paper wallets lately through different sources and have noticed that all the private keys I generate start either with "5K" or "5J". I'm talking about many dozen individual generations.

I have generated paper wallets on blockchain.info, bitaddress.org, and bitcoinpaperwallet.com and all have started for me with either "5K" or "5J"

If i compare all private addresses I control (all hot/cold addresses I have ever used), these are the common starting digits, 5K, 5J, L5, L1,  and these are the least common L2, L4, Ky, Kw. I have a total of 40 used addresses and the most common starting digits are 90% of the private keys, with 5K and 5J being 75% of the 90%. This seems unusual, but I am still an noob and don't pretend to understand everything.

Questions:

(1) Why isn't my private key generation more random (as to the first two digits)?

(2) Are those digits generated from the browser I'm using (currently used firefox for all the above generations)?

(3) Is this something to be concerned about or just a normal outcome from private key generations?


Thanks.
Pages:
Jump to: