2^256 Deep Space Vagabond

[AlmostEpic]

So in my ever expanding curiosity (yes I know it's damn near impossible but I like the challange of scripting new things) I have re-written a few different scripts in PHP-CLI to make calls to vanitygen to generate addresses/privatekeys and check them against an array loaded with keys/balances.

The program currently uses about 450MB of memory per instance of it running and its checking it against a subset of ~1.3 million addresses or so. I did notice that when making the call out to generate a key I was getting about 0.15 secs/key generated using the options in the code box below and the amount of time to actually check the address against the database was so fast the php function microtime was not able to determine the time. I decided to go ahead and instead of calling vanity gen over and over to generate 1 address at a time I would start up vanity gen in one command prompt using options in code box 2 and run the checking script against the output file instead. Now the problem is that the cpu vanity gen only generates about 240 Kkeys/s on my CPU and the PHP script checks 50,000 addresses in less than 2 seconds.

So I decided I would try OCLvanitygen to generate addresses even faster since my GT440 generates around 2.70 Mkeys/s but I'm having an issue with oclvanitygen that maybe one of you might have some insight into. I have noticed when running OCLvanitygen under -q it will list its generating 2.7 Mkey/s but with the prefix set at "1" it states that its finding 1 or 2 keys per second (output in code box 3). Any idea how to get OCLVanitygen to output all 2.7Mkey/s to the output file?

(PS- the reason for the regex is because 93.94% of bitcoin addresses with a balance greater than 0 are between the prefix 121 and 1Pz which cuts down on the total amount of variables to try and check against my keys script.)

Code:

vanitygen.exe -q -t 4 -r -k 1[A-P2-9] 

Code:

vanitygen.exe -q -t 4 -r -k -o generated.txt 1[A-P2-9] 

Code:

D:\>vanitygenlib.exe -q -t 4 -r -k -o generated.txt 1
[131.34 Kkey/s][total 699554][Found 2827]

D:\>oclvanitygen.exe -q -k -d 0:0 -o generated.txt 1
[1.36 Mkey/s][total 20971520][Found 5]

[organofcorti]

I've noticed the same thing - I wanted to use regex with oclvanitygen and thought I could just run a regex script batchwise on the generated files, but as you noticed it's very slow. I can't help you with that, but:

(PS- the reason for the regex is because 93.94% of bitcoin addresses with a balance greater than 0 are between the prefix 121 and 1Pz which cuts down on the total amount of variables to try and check against my keys script.)

I'm pretty sure this has to do with the probability of those addresses existing rather than the probability of them having a balance != 0. This means that trying them does not increase the time taken to find a balance > 0 since the probabilityof generating these addresses is much lower as well.

[AlmostEpic]

What I mean by it cuts down on the total amount of variables to try and check against my keys script is that I only have vanitygen generating keys that are between 121-19z and 1A1-1Pz, It is generating more keys than that but those are the only keys being output to text file. By doing that I am reducing the number of keys I am checking against my balance list (which contains only addresses between those prefixes with a balance greater than 0).

I took all of the addresses that had a balance greater than 0 and sorted them by prefix and generated the graph below. As you can see vertical axis is the total amount of addresses that begin with each prefix (horizontal axis).

http://i60.tinypic.com/juu2qa.jpg

[organofcorti]

What I mean by it cuts down on the total amount of variables to try and check against my keys script is that I only have vanitygen generating keys that are between 121-19z and 1A1-1Pz, It is generating more keys than that but those are the only keys being output to text file. By doing that I am reducing the number of keys I am checking against my balance list (which contains only addresses between those prefixes with a balance greater than 0).

I took all of the addresses that had a balance greater than 0 and sorted them by prefix and generated the graph below. As you can see vertical axis is the total amount of addresses that begin with each prefix (horizontal axis).

<IMG snip>

I know what you mean, but if you compare that to a list of the frequency distribution of *all* addresses, I'm betting that the distributions will be very similar - which means you don't gain anything by leaving them out.

[nimda]

I know what you mean, but if you compare that to a list of the frequency distribution of *all* addresses, I'm betting that the distributions will be very similar - which means you don't gain anything by leaving them out.

And in fact, you're probably slightly slowing the generation process down.

[AlmostEpic]

I don't believe I am slowing down the generation process because as seen in my original post vanitygen can only "find" so many addresses per second, even using a prefix of 1 (all bitcoin addresses) it still only "finds" ~ 0.4% of the addresses generated. I believe I am going to have to implement address generation directly within PHP using something along the lines of Zamgo's PHPCoinAddress.php https://github.com/zamgo/PHPCoinAddress/blob/master/PHPCoinAddress.php and see if I can't speed up the process of address generation that way. Even if I can get it to iterate at about 500 address per second it would be generating faster than vanitygen can "find" addresses.

[organofcorti]

I don't believe I am slowing down the generation process because as seen in my original post vanitygen can only "find" so many addresses per second, even using a prefix of 1 (all bitcoin addresses) it still only "finds" ~ 0.4% of the addresses generated. I believe I am going to have to implement address generation directly within PHP using something along the lines of Zamgo's PHPCoinAddress.php https://github.com/zamgo/PHPCoinAddress/blob/master/PHPCoinAddress.php and see if I can't speed up the process of address generation that way. Even if I can get it to iterate at about 500 address per second it would be generating faster than vanitygen can "find" addresses.

500 addresses per second is pretty good, I found a python generator which could only do about 100 per second. It'd be nice to know why vanitygen is so slow at generating real addresses.

Is it still slow if you define the first two characters instead of just "1" ?

[AlmostEpic]

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.

[organofcorti]

If I was able to get 2 mega-addresses per second, I'd have an absolutely awesome personalised address. Even this address took weeks of CPU power:

1QC2KE4GZ4SZ8AnpwVT483D2E97SLHTGCG

[AlmostEpic]

My GPU can run through 2.78 Mkeys/second if you can generate a ECDSA public/private key pair and PM me the public key and the vanity address you would like (up to about 5 or 6 characters (including the 1 prefix)) I'd be willing to generate a public/private key pair that comes out to your preferred prefix. The way it works is

Your Private Key -> Your Public Key

Generated Private Key -> Generated Public Key

Your Public Key + Generated Public Key -> converted to Bitcoin Address with your preferred prefix.

I send you the Private/public keys -> you add Your Private Key to the Private Key I send you and then import that into your wallet.

the vanitygen programs are setup to accept this type of setup and by doing so your still protecting your address because only you have the private key that generated the public key you give me to generate your vanity address. I'd be willing to do it free of charge but tips are always welcome

EDIT : If you are interested you would need to get the vanitygen program (if you don't already have it) https://bitcointalk.org/index.php?topic=25804.0
Then run from a command prompt

Code:

keyconv.exe -g

This will give you a private and public key, of which you would only need to send me the Public Key (Hash) which would look something like

Code:

Pubkey (hex): 041d2e778ae6d9124736df131cd22d3a2483f336c55156d87a84c4bdc6d89f8518e33de85ae0f907a7128c476281bc8cc7742b43a54ccc2c7824dc4c4a438a7fbc

[organofcorti]

Thanks for the offer, but I'm interested in much more difficult regexs than '1abcde'. See if you can figure out the regex I used in the address I posted above.

[AlmostEpic]

Well considering all of the letters except npw are capitalized I would say that  the regex is something along the lines of

Code:

^1[A-Z0-9]*[n][p][w][A-Z0-9]*$

EDIT: Forgot the $ at the end lol.

EDIT2: It seems the regex done by vanitygen is actually different than regex done by Ruby or PHP. The above regex or even the below regex both only match patterns like your address when done in Ruby or PHP but VanityGen seems to return strings with lowercase letters other than npw even though its not allowed by the regex.

Code:

^1[A-Z0-9]+npw[A-Z0-9]+$

In ruby/php out of these addresses, address 1 and 3 are found and address 5, 6, and 7 are addresses that were found by vanitygen but are not matched when added to the ruby/php list to check.

Code:

1QC2KE4GZ4SZ8AnpwVT4832E97SLHTGCG
1a209hasdp98h09asd09npw09u1209hasd
109JASD09JH23npw09HG09HJAS908GHH23
1LRbG1xndkUw6YK5mESukd8Y4mFvfRYqFe
154NxoxQxnTSujw6wwRe6h5QVUw1WJnpwN
1L5z3q7S6FHL32WXWMSTqazTcBG1E2npwV

[AlmostEpic]

does this work like the vanity address finder? does it use my cpu?

The 2^256 Deep Space Vagabond program does use your CPU and yes it works like vanity address finder accept in continually creates more and more addresses and checks them against a known list of lost Bitcoin addresses that have bitcoins on them, but like everyone has said in this thread the possibility of finding a single one is so infinitely small it would not be worth even trying.

The likelihood is so small that if you put every single computer on the entire earth that has ever been produced, took all of the individual computer parts that are not in computers and built computers from them, added in all of the super computers and servers, cell phones, iPads, tablets, nooks, kindles, gaming consoles, and every other digital device that could ever possibly calculate a Bitcoin ECDSA key pair and perform SHA256/RIPEMD160 functions on the keys, it would take longer than the universe has been around to generate all of the possible keys.

[AlmostEpic]

Link to flatfly's google code page for deep space vagabond. https://code.google.com/p/win-electrum/downloads/detail?name=dsv-1457.scr

[jambola2]

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.

[lussifa]

anywhere to download?

[Hash Hyena]

Amazing to see the community pulling together to finally point out a serious weakness in Bitcoin. We. the Hash Hyena's have been hiding in the shadows for a long time for developers to put their talents to use in forcing hard fixes to some of these weaknesses.

Thank you to all of you developers for your efforts. We do not care how much a misinformed community may laugh at the probabilities, and big numbers like they mean impossibility. Its real, it has happened, and it will continue to happen.

For any developer that would like the proof, and like to join forces with the Hash Hyena's on the "Hash Hyena" project to further development on our new platform that we intend to open source and soon release to the world please message us directly through BitcoinTalk.

For the rest of you, If you want to get leaps and bounds ahead of everyone else in the game when we officially launch the Hash Hyena software do these two things.

1: start stocking up on hard drives. The more storage space the better. ( we currently have 1.18PB and growing )

2: run the line of code below in vanitygen, make tons and tons of output files and start storing them, we will soon release the program that converts them into .csv files that we use for importing. The more files you have when we launch the further you are ahead of everyone else when this all goes public in a few short weeks or months.

Code:

vanitygen64 -k -o output.txt 1

We will be releasing a batch file for those of you with high performance CPU's to run multiple outputs at a time in a nice little packaged .rar download. We will be starting our own thread soon

[Korbman]

Amazing to see the community pulling together to finally point out a serious weakness in Bitcoin. We. the Hash Hyena's have been hiding in the shadows for a long time for developers to put their talents to use in forcing hard fixes to some of these weaknesses.

[...]

For the rest of you, If you want to get leaps and bounds ahead of everyone else in the game when we officially launch the Hash Hyena software do these two things.

1: start stocking up on hard drives. The more storage space the better. ( we currently have 1.18PB and growing )

2: run the line of code below in vanitygen, make tons and tons of output files and start storing them, we will soon release the program that converts them into .csv files that we use for importing. The more files you have when we launch the further you are ahead of everyone else when this all goes public in a few short weeks or months.

Code:

vanitygen64 -k -o output.txt 1

Is your plan, by any chance, to generate enough addresses to own a majority, or to own enough that there might be a slight possibility someone might accidentally send coins to the wrong address and end up in one of the billions you've created?

At roughly 38 bytes of uncompressed space per generated address through vanitygen (in text format), you're looking at somewhere close to 11.5 septillion petabytes of storage needed for only 2¹²⁸ addresses that could be generated...or 1.6 quadrillion petabytes for every man, woman, and child on this planet.

[BurtW]

Amazing to see the community pulling together to finally point out a serious weakness in Bitcoin. We. the Hash Hyena's have been hiding in the shadows for a long time for developers to put their talents to use in forcing hard fixes to some of these weaknesses.

Thank you to all of you developers for your efforts. We do not care how much a misinformed community may laugh at the probabilities, and big numbers like they mean impossibility. Its real, it has happened, and it will continue to happen.

For any developer that would like the proof, and like to join forces with the Hash Hyena's on the "Hash Hyena" project to further development on our new platform that we intend to open source and soon release to the world please message us directly through BitcoinTalk.

For the rest of you, If you want to get leaps and bounds ahead of everyone else in the game when we officially launch the Hash Hyena software do these two things.

1: start stocking up on hard drives. The more storage space the better. ( we currently have 1.18PB and growing )

2: run the line of code below in vanitygen, make tons and tons of output files and start storing them, we will soon release the program that converts them into .csv files that we use for importing. The more files you have when we launch the further you are ahead of everyone else when this all goes public in a few short weeks or months.

Code:

vanitygen64 -k -o output.txt 1

We will be releasing a batch file for those of you with high performance CPU's to run multiple outputs at a time in a nice little packaged .rar download. We will be starting our own thread soon

Hyena?  Do you mean Laughing Hyena as in this is a total joke Hyena?  Or, worse yet you are serious and just not very good at basic math?

[Hash Hyena]

Amazing to see the community pulling together to finally point out a serious weakness in Bitcoin. We. the Hash Hyena's have been hiding in the shadows for a long time for developers to put their talents to use in forcing hard fixes to some of these weaknesses.

Thank you to all of you developers for your efforts. We do not care how much a misinformed community may laugh at the probabilities, and big numbers like they mean impossibility. Its real, it has happened, and it will continue to happen.

For any developer that would like the proof, and like to join forces with the Hash Hyena's on the "Hash Hyena" project to further development on our new platform that we intend to open source and soon release to the world please message us directly through BitcoinTalk.

For the rest of you, If you want to get leaps and bounds ahead of everyone else in the game when we officially launch the Hash Hyena software do these two things.

1: start stocking up on hard drives. The more storage space the better. ( we currently have 1.18PB and growing )

2: run the line of code below in vanitygen, make tons and tons of output files and start storing them, we will soon release the program that converts them into .csv files that we use for importing. The more files you have when we launch the further you are ahead of everyone else when this all goes public in a few short weeks or months.

Code:

vanitygen64 -k -o output.txt 1

We will be releasing a batch file for those of you with high performance CPU's to run multiple outputs at a time in a nice little packaged .rar download. We will be starting our own thread soon

Hyena?  Do you mean Laughing Hyena as in this is a total joke Hyena?  Or, worse yet you are serious and just not very good at basic math?

Or better, just over 1 PB worth of data storage and we managed to nab a few transactions from the blockchain already. Next, it has nothing to do with basic math, there is nothing basic about the math behind any cryptographic function. Lastly, who needs 50% of the addresses? if a few thousand people had a few quadrillion addresses each it makes up a large enough percentage that a person is no longer chasing a moving target. It also means that every time you move your bitcoins, you have to wonder...... Has someone got the key for this address?

Ask yourself, how many bitcoin supporters are going to feel comfortable with their investment knowing that 15%, 10%, 5%, hell eve 1% of all bitcoin addresses are indexed and monitored. (the fed has already done this, that is where this project stemmed from)

Imagine everyone involved in crypto currency to date had the ability to randomly generate addresses using the same faulted PSRNG system that 80% of wallets use and fill even 100 gigs of space on a hard drive. How comfortable do you feel with your investment then?

Imagine as hard drives and storage become cheaper, As is we are already buying 6TB drives for $190usd. You can already go make a $70 investment and buy a 1TB external. With our software's it would take maybe a week for you to fill it and monitor it in real time. take that multiplied by even a thousand, and growing daily. How comfortable are you with your investment then?

Imagine next year when Segate launches its first 10TB 5,200rpm HDD for only $350. (already in the works) Thats pocket change for most of us here....... You get the point. How comfortable are you with your investment then?

If you can honestly say that you still have no worries about your bitcoin after taking all that into consideration, then you sir are an idiot with no common sense.

Granted we are not giving you the WHOLE story yet, waiting on a few final developments that will make it all more platform neutral and basic user friendly so we are not just talking about it but letting everyone do it. But in summary, about a year ago, we were where you are now. In the very recent past, we have hijacked about 3.3BTC from a total of 5 addresses.

Developers who want to join the team and help spread awareness get the source now pending their contributions as well as a basic overview of how it works. The rest will have a beta platform within the next month or so to start cataloging their outputs, in a few months anyone who has some hard drive space that wants to catalog some bitcoin addresses has a chance to play along.

Final disclaimer,

Yes, if we find bitcoins we are taking them but this is not about being thieves. its about making people aware that 75% of the hype about bitcoin security is FALSE, even by the admission of some of the current bitcoin core developers. A direct quote from one of them in a recent interview "It is scary how many people have invested so much money in such a young technology that is filled with security flaws". We ourselves could not possibly steal enough bitcoin to make a difference, but as a community (full of thieves anyways) we could chip away at it and tally up enough hijacked coins over time to force the hand of the developers to assess the important and most prominent security flaws NOW before it drives bitcoin into the ground.

If you want to troll, go for it, we all love a good laugh and 80% of us on this forum are only here to see the dumb stuff anyways. Otherwise, just hang on and we will get you software soon so you can participate and put some of those old no longer used hard drives to good use.

BTW: Yes Hyena's laugh, ever wonder why? THEY ARE THE BIGGEST THIEVES IN THE ANIMAL KINGDOM