Bitcoin puzzle transaction ~32 BTC prize to who solves it

[nomachine]

We don't even know if there is yet some unpublished weakness in ECDSA that was exploited.  Also why would one gather 1.7 million $ in a single script address and not touch it at all after more than a year and a half, assuming there was a high cost of solving, that needs to be paid...?

The public program on GitHub could serve as a honeypot, used to monitor those trying to solve cryptographic puzzles or who are interested in cracking ECDSA. It could act as a form of surveillance, watching who interacts with it, akin to government efforts to track those with knowledge of or interest in sensitive cryptographic topics.

The non-public solution could indicate that powerful entities (e.g., intelligence agencies, corporations) are exploiting vulnerabilities privately while letting the public chase dead ends or false leads.

The decision to not touch the funds could simply be a matter of operational security.

[mcdouglasx]

The source code is free, you can be thankful, but don't you think it's a little unfair to complain about someone for imperfect code or code that doesn't meet your own needs? Developers are not slaves nor are you paying them a subscription to demand "this isn't Netflix". Apart from complaining, the internet is also ideal for learning to program, and I see a lot of opinions and little code here, that sometimes it's lazy to read.

I don't think it's about complaining, it's about waking up people to the fact they're putting blind faith into an imperfect program, not an imperfect code, if you can understand the difference. And it's not just about some 125-bit self-developer-imposed limitation. You may very well have some great written code which doesn't work (i.e it seems to work since no one bothered to QA it and no tests exist), and spaghetti code that correctly controls a rocket landing on Mars. It's obvious by now the 130 solver (which might very well be an organization or some huge zombie botnet) did not use JLP's program, and likely not even for 120 or 125. Just because something is not revealed does not make it non-existent. In the same way, just because something happened, it does not mean it happened because of a specific reason. We don't even know if there is yet some unpublished weakness in ECDSA that was exploited.  Also why would one gather 1.7 million $ in a single script address and not touch it at all after more than a year and a half, assuming there was a high cost of solving, that needs to be paid...?

I think Kangaroo has already fulfilled its purpose, it is a purely probabilistic algorithm and for future puzzles it is not profitable to use it, it is better to mine blocks, I think it is time for new things that do not depend only on computing power, I am sure there are some things cooking out there: logic + strength.
but I do not think there will be a back door, new techniques yes, after all the keys to the puzzles are insecure it is not surprising that they are deciphered and if the prizes are large, even faster.

[Akito S. M. Hosana]

We don't even know if there is yet some unpublished weakness in ECDSA that was exploited.  Also why would one gather 1.7 million $ in a single script address and not touch it at all after more than a year and a half, assuming there was a high cost of solving, that needs to be paid...?

The public program on GitHub could serve as a honeypot, used to monitor those trying to solve cryptographic puzzles or who are interested in cracking ECDSA. It could act as a form of surveillance, watching who interacts with it, akin to government efforts to track those with knowledge of or interest in sensitive cryptographic topics.

The non-public solution could indicate that powerful entities (e.g., intelligence agencies, corporations) are exploiting vulnerabilities privately while letting the public chase dead ends or false leads.

The decision to not touch the funds could simply be a matter of operational security.

That's why I never downloaded the prebuilt binaries of these tools. It's VERY dangerous. And who knows what lies behind that Iceland Secp256k1. After all, look at the Wireshark logs to see what's happening. 

[COBRAS]

pubkey new down....

...


cf4863281bb44f52677de8876600000000 10000

c1d204c36910280a6e0952c00000000000 111c80
bad8afea76b82aa806c0d19a8000000000 11c000
aeb619ed70bba24a4d8dd0000000000000 12fb9e <-
ae8dccc375a55045649fec3c2000000000 130000

...

a3379838c4438008c873a4000000000000 1451d8


...

up down ,up down... new down...up down ,up down...


to be continue

ps  needs stock of zero's for this manipulations 

[nomachine]

Yes, there are some bugs. But the biggest stupidity is that such a program does not support all GPU cards. I mean AMD graphics. I have a pile of Radeon cards that are useless.  

You can run Nvidia CUDA applications natively on Radeon GPUs

https://github.com/vosen/ZLUDA/tree/9e56862ebb5a3273b9849eabbd3e0eac9548922c

The code that was previously here has been taken down at AMD's request but there are 597 forks of the repo  

[brainless]

Information!!!!
As per above discussion and blam on developers unfair
They provide you best freeware
Only mindset at public they want ready to eat
They don't have ability to create such app not able to apply math, nor able to apply brain
How they can use such app
Let me give u 1 more tip
Don't use start to end full bit range
Example
134bit to 135bit don't use
What to use
Split 135bit in parts of 70bit to 100 bits for run kangaroo in between, depand your gpu power
Or
Generate random number in 135 bit range and to set +100 bit for adjust range for checking key
A = 135 random generator
B = a+ 100bit range
Adjust a and b in your kangaroo command
Hope above small tips help you for use kangaroo and such app,
It's also help your mindset of kangaroo 125bit max etc
Enjoy!!!