supika
what the hell are you saying

This is possibly the silliest thing I have read today. - if the owner decided to take the btc it would all already be gone. if he (guessing but the odds are 'he') wanted his friends to have it... same.. poof.. gone...  - the something that you believe (still not sure what that is btw- but a guess is to follow) that you will believe differently when you find a private key etc... I'm guessing is some sort of strange conspiracy where a guy takes a hundred billfolds with money in them, hides them all over the place and goes "find them" but secretly tells his friends where they are.. umm a) - why not just hand over some bills to your pal bob? b) why... like why the whole thing at all?  c) if that was the case, owner/friends would go get the 1.6 immediately.   -as a sidenote, but only slightly to the side... somewhere the owner spoke up and was talking about it being a way to encourage people to see what they can do towards figuring out ways around the cryptography, thus proving/disproving the "safety" of your coins. As we have seen, so long as you didn't use reaaaaally low entropy keys, and so long as you don't reuse an address you are fairly okay (so far) but keep using the same address and you are asking for trouble... maybe not fast trouble.. but trouble none-the-less. (It is my personal belief that the move revealing the pubkeys was prompted by all the talk about programs to get the private key from public and he was like "well hey let's see what they can really do here..." (otherwise why skip by five...) Now if you want a plausible conspiracy - which doesn't really take away from the "puzzle" so much as show a human side to things.. let's say bob creates puzzle when btc is cheap as dirt.. time goes on.. btc gets really up there.. bob has a hospital bill/car trouble/baby on the way etc.. whatever... people are popping off with prv key from pub, he needs a little something... but more than .62 so move.. and grab the first one.. still giving others a shot  (This imho is still VERY unlikely.. 'cause as we know he already has all the keys.. could take whenever he likes. so really he could have just snagged it all and walked away if he needed cash, so he really wants people to strive for better/shorter ways or similar to the lbc show exactly how hard this would be to do... the harder it is btw the more acceptable it is to joe public even though they will never REALLY understand that it is ALREADY harder even with low entropy to get a priv key than it is to get into their bank account - or their atm pin which is likely to be a family member's b-day anniversary or some foolish stuff like that.)
There is my 5 satoshi. inflation yo.

supika
Looks like you are one of those guys who truly believes in conspiracy theory. 

Ah this simply funny ,to think when you ,hacked methods which 30 years 90 bits private keys and hope, that the that you hacked(bitcoin) will rise in price,Ah the right this even as the unwise, that whether?

In CPU one core and PHP!!!
Av2!!!! Priv keys in one second!!!    

But tomorrow collectors can pick up the comp.

There is nothing "hacked" so far. The Distributed Pollard Kangaroo algorithm is known since 2000.

Let's get some numbers for the 90 bit challenge:

BitCrack runs at about 715 MKeys/s on Tesla V100 - look here.
If we remove hash160, the rate would be 1430 Mj/s. Mj here stands for million kangaroo jumps.
The algorithm has expected run time 2*sqrt(b-a) jumps, here b-a = 2⁸⁹.
This gives expected running time of 09:39:55.
Looks quite fast.
Of course this is just a probability, if lucky, the time goes down to 3-4 hours, or not lucky, then time doubles to 18-20 hours.
Or really unlucky, with triple the expected run time - 1 day 04:59:47.
Since the algorithm scales linearly, one could use multiple V100, let's say 8, resulting in expected time 01:12:29.
The price for 8x V100 in google cloud is $15/hour.

Someone having 20x RX 480, each running BitCrack at 107 MKeys/s.
Using the same assumptions that would give 214 Mj/s each, for a total of 4280 Mj/s.
Please note, that for complex code AMD OpenCL compiler is very, very bad, and the system might crash, or even worse, bug the computations.
Assuming 150W per RX 480, the system would consume 3kW.

|------+-------------+---------+---+-----------------+-------------|
|      |     8x Tesla V100     |   |         20x RX 480            |
| bits +-------------+---------+---+-----------------+-------------|
|      |    time     |  price  |   |       time      |    power    |
|------+-------------+---------+---+-----------------+-------------|
|   90 |    01:12:29 |     $18 |   |        03:13:45 |     9.7 kWh |
|   95 |    06:50:04 |    $103 |   |        18:16:05 |    54.8 kWh |
|  100 | 1d 14:39:43 |    $580 |   |     4d 07:20:24 |   310.0 kWh |
|  105 | 9d 02:42:22 |   $3281 |   |    24d 08:34:45 |  1753.7 kWh |
|  110 |   51 days   |  $18558 |   |   137 days      |  9920.6 kWh |
|  115 |  291 days   | $104979 |   | 2 years 49 days | 56119.6 kWh |
|------+-------------+---------+---+-----------------+-------------|

Of course these numbers could easily double when unlucky.
And someone else could solve it before, then it's all a loss.

If you expect somebody to write the the code for you and give it away freely, you're demonstrating millenial entitlement syndrome. Everybody is free to learn the necessary computer science and programming skills necessary to translate the algorithm into useful code.

I do not need any codes and programs,the Indians will write anything for $ 50? I'm talking about the forum and where it has slipped ,so again I say that lights out and dry the paddles .You can branch to close prichandaly to be measured is useless.

Key #95 in 10 1/2 hours on a single machine? That's impressive.

Why so many - 256 - kangaroos? Everyone says it is not optimal, do you have some new insights on this?

Man, can you share your ./kangaroo script?
My PM is open.
Thanks!