Quote from: AlmostEpic on April 01, 2014, 07:50:51 AM

I've noticed it will pull/show that it is "finding" ~ 0.404% of the addresses generated when searching for the prefix of "1" or 0.389% when searching with 1[2-9A-P]. I did some more testing as well and found 1[1-9A-Za-z] found at ~0.399%, but 12 found at ~0.402% so I'm pretty sure that vanitygen is finding more than what is being reported (especially when using the prefix of just 1) and that the maximum addresses it can output when hashing is around 0.4% of the hashes generated, I might take a look at the vanitygen source tomorrow and see if I can find a way to have it output all found addresses to a text file instead of only the hashes it finds and possibly update oclvanitygen to include regex searching, if I can I would be able to have oclvanity generate about 2 million addresses per second (maybe less considering the regex) and my PHP script is able to check about 2 million/second as is. That would equate out to be about

120 million addresses per minute
7.2 billion addresses per hour
172.8 billion addresses per day
1.2 trillion addresses per week
62.9 trillion addresses per year (or 62,899,200,000,000 per year using a AMD Athlon II x4 760k, 4GB of 1600mhz RAM, and a nvidia GT 440).

as earlier discussed in this thread because of log(58^34) / log(2) ~= 200 a single bitcoin private key is actually only about 200 bits not 256 bits, following this 2^200 is ~= 1.606938e+60 or 1,606,938,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000

1.606938e+60 / 62.9 trillion = 2.554783e+46 years to generate the entire bitcoin keyspace so its still unreasonable to believe that I will ever find an address that contains bitcoins.

Still, I am going to continue to run and continue to develop the script mainly because its fun and challenging and a great learning experience learning how the keys are actually created, the checksum and learning about ECDSA encryption which I have not personally dealt with before now.

Only difficult part tomorrow is if I do get oclvanitygen modified and rebuilt and it does produce 2Mkey/s output to a text file... I'm going to run out of harddrive space on my 2nd partition which is running the program in approx 98.304 seconds (@ 100MB/800K keys) so I may have to break out one of the 1TB drives for this project lol (although even 1TB will fill up in ~ 69 minutes).

EDIT - I did just realize I have only been using vanitygen not vanitygen64. With vanitygen64 I am still only "finding" ~ 0.4% of the generated addresses but I am generating at a faster rate and "finding" ~ 750 addresses per second.

33.5 million BTC address have ever had any amount of Bitcoin in them.

2.55e+46/33.5 million = 7.5e+38

That makes it a huge total of 7.5e+38 years to find an address on average that has had any part of a bitcoin in it , ever.

To put this in perspective , if you took 21 million Bitcoins and started sending 1 satoshi per address to random addresses , you would be able to cover only 2.1e+15 addresses , not even being near to the chance of reaching an address.