Thank you for posting your idea!

but this idea is really rare to success and to happen, and it takes a lot of time to do searching in a such huge range space. We need a better algorithm to target public keys.

Dear albertobsd,
can you develop an or is there algorithm to try to get public keys of the unsolved puzzles? example; puzzle 64, 66, 67, 68?
if we get the publickeys, the puzzles would be solved in less than minute.
Thanks in advance.

Hello guys, i've been trying to randomly bruteforce puzzle #64 for WEEKS in a row. I was using Bitcoincrack to randomly Bruteforce addresses that share the same 7 letters of 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN.
after bitcoincrack generated today 1000 addresses that share the same first 7 address characters, i have always looked for the last 3 characters of the generated addresses to go through the addresses quickly and see if #64 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN is on the list.
and indeed, i saw an addresses that ends with the last 3 characters "XQN" that the original puzzle 64 address have. And the moment i saw XQN, i freaking screamed I WON 30K EUROS and smashed couple of glass bottles and went quickly to say and to celebrate with my friends.
after my friends came, we checked the address again and it was NOT the address i was looking for. it was so embarrassment, and i'm now broken and sad as hell.
What are the odds that i find the last 3 characters address, that i'm looking for in the range 64? ITS pretty much low, that's why i thought i found the 0.64 BTC. but unfortunately not. I should be the unluckiest guy ever...
Here is the Address, i thought i got the 0.64 bitcoin from it.
isn't that sad situation?
Pub Addr: 16jY7qLHKTofWA2DYS9ZaWyvZ5qnjfSXQN
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ3tw8CPZjZciVwEz8EV
Priv (HEX): 0x000000000000000000000000000000000000000000000000DAA7B7BDF277A7B7

That's insane! Thank you for clarifying!
may i ask but, how is it possible to an same address to relate to another completely different public keys and private keys? how do they match to same address, if they're completely different?
Thanks again.

arulbero, i'm wondering, how does these 2^96 collisions happen? does the 2^96 addresses each address share all the same public key or how does 2^96 addresses can generate the same address?

Yes you are right, but one point i don't get it.
why would i scan 2^256 range? isn't it  scanning only 2^160 using for example BSGS to find any specific publickey with its private key? (since all publickeys and all private keys are in the range of 2^160.)

Ok, thank you so much, so let's say i want to bruteforce a specific publickey that has for example 1,000 bitcoins in it. so my questions are:
so does the publickey that i want to attack for example using Kangaroo exists only 1 TIME with its privatekey in the whole range of 2^160 is that right ?
so if i want to get that unique private key from its unique publickey, i need to bruteforce from 0 to 2^160 in order to get it, is that also correct?

guys dumb question, there are 2^256 private and public keys and total of 2^160 addresses, so 2^256/2^160 = 2^96 keys per address. but how can be 2^96 keys that connect to same address? so what changes then? does public key stay the same and only private key changes, or does both changes with 2^96 address each one..?

Hello albertobsd i have a Questions outside and inside this awesome program that you have made.
i've been looking for correct answers for weeks, but everyone says differently so your the one who to ask, because you're a bitcoin expert here.
Questions:


So total  possible public keys are 2^256 and are mapped to a set of 2^160 (160 bits) addresses. Since there are more public keys and private keys than addresses, but every public key can be mapped to an 160 bits address, there must be then in average 2^256 / 2^160 = 2^96 keys to each address. so if there are 2^96 addresses for each bitcoin address, so does all that 2^96 addresses that one Address have, share ALL the same public key? because that's what you need  in order to have the same RIPEMD-160 hash. so only private key which changes, not public key with the 2^96 key possible keys per Address right?

==========

Another Question related:

So if all my thoughts are right, then from what i understood, All addresses of bitcoin exists only 1 TIME from the range ( 160 bits ) 0 - ( FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF ), and the rest 2^96 addresses per address start to exists after the range of 2^160, so starting from 2^161. Is that also correct?


==========


Last Question.

Then if bitcoin addresses have 160 bits, can't we just try to Bruteforce that 160 bits from ( 0 - FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF )  Hex-Range with  high number of  Random peta/keys checks - - using BSGS, won't we have a 1 of 2^160 chance of unlocking any addresses that have the public key? can that work using BSGS right, or with BSGS that method doesn't work? (even with low chance, i still believe in luck)

==========

if you could answer all this three Question, then i really appreciate it!
Best regards.

Hello albert0bsd,
So, may i ask if this is a real legit puzzle that is solvable then?
or is this a fake puzzle?
and if this puzzle is solvable, what is the chances that actually someone unlock that 3350 BTC Address?
Regards!

Yes, ok but could you share us the program? which program is this..

Yes i think too it's a prank.
there's no way that a program can search THIS much addreseses/s

Please guys share us the program that does 2714579271.01Tera/s
What kind of program is this? how does it search with such a very huge fast speed?
many thanks

Hello guys, please help
I'm having compile errors and bugs using linux.....
Please help me someone post me a link to download keyhunt.exe file i would really be thankful!
Thank you guys!

Thank you for this great explanation!
How does this "Kangaroo program actually finds the private key from only the public key? isn't that impossible?

Hey guys can anyone help me? i'm noob to all this.


Start:10000000000000000
Stop :1FFFFFFFFFFFFFFFF
Range width: 2^64
DP size: 15 [0xFFFE000000000000]
[20.33 MK/s][GPU 0.00 MK/s][Count 2^33.38][Dead 1][10:02 (Avg 07:25)][12.4/37.8MB]
Key# 0 [1S]Pub:  0x0230210C23B1A047BC9BDBB13448E67DEDDC108946DE6DE639BCC75D47C0216B1B
       Priv: 0x1A838B13505B26867
Done: Total time 10:02
 / / / /
i got this small private key part (1A838B13505B26867) what is this exaclty? does this belongs to the public key i put in my work file?
another question also, does the private key starts with that 1A838B13505B26867. . . . or they mean it end at . . ..1A838B13505B26867 ?
Thank you guys for help.

Hello, can i contact you? the developer of eloncoin. i have few question please.
Thank you.