Bitcoin puzzle transaction ~32 BTC prize to who solves it

[GonzAlex]

What is the current status of the puzzles? Can anyone give a quick update? Which puzzles have already been solved, and which ones are still open?

https://privatekeys.pw/puzzles/bitcoin-puzzle-tx?table=1&status=all

[E36cat]

how much thousands year taken for solve 69 and 68 puzzle ?

I don't even believe that they were resolved in a normal way. That there is a conspiracy.

how I solved 68 was thoroughly discussed here already…

what would be your method for 135 if it would have been , using servers with ram or gpus? how many needed and for how long to find it and make profit? thank you

[Bram24732]

how much thousands year taken for solve 69 and 68 puzzle ?

I don't even believe that they were resolved in a normal way. That there is a conspiracy.

how I solved 68 was thoroughly discussed here already…

what would be your method for 135 if it would have been , using servers with ram or gpus? how many needed and for how long to find it and make profit? thank you

I actually wrote and tested all the code for 135. Works quite well.
It’s the same dispatcher as for 67 and 68, with run parameters varying by GPU model.
There’s a central server accumulating all the DP. It was actually the most complex bit to write, because handling the load from tens of thousands of GPUs sending points there was quite the challenge.

135 is roughly as complex as 68, so with 20k GPUs like I had back then it’s a matter of a couple months.
Probably 300k ish investment for the 13.5Btc reward.

[E36cat]

how much thousands year taken for solve 69 and 68 puzzle ?

I don't even believe that they were resolved in a normal way. That there is a conspiracy.

how I solved 68 was thoroughly discussed here already…

what would be your method for 135 if it would have been , using servers with ram or gpus? how many needed and for how long to find it and make profit? thank you

I actually wrote and tested all the code for 135. Works quite well.
It’s the same dispatcher as for 67 and 68, with run parameters varying by GPU model.
There’s a central server accumulating all the DP. It was actually the most complex bit to write, because handling the load from tens of thousands of GPUs sending points there was quite the challenge.

135 is roughly as complex as 68, so with 20k GPUs like I had back then it’s a matter of a couple months.
Probably 300k ish investment for the 13.5Btc reward.

what speed does one gpu have so you can do it with 20k gpus in a couple of months, cause even if each gpu has 20 Ekeys per second still takes many many years
i`m new to this thats why i am asking, i just want to understand thank you for taking the time to respond

[Bram24732]

what speed does one gpu have so you can do it with 20k gpus in a couple of months, cause even if each gpu has 20 Ekeys per second still takes many many years
i`m new to this thats why i am asking, i just want to understand thank you for taking the time to respond

It’s a mix of nVidia and AMD, some are 10 years old some are brand new.
Also I don’t mesure speed in EKeys, always seemed strange to me. What matters is how long it takes to reach 50% chance of collision.

[ee1234ee]

Do any friends know the details of solving problem 69?
Why was it solved so quickly? Is the person who solved it in this forum? I heard it was stolen in the end.

[Cricktor]

...

All your questions you probably could have answered yourself with some search skills, simply by going through a bunch of pages in this thread starting from the withdrawal tx time. Let me spare you the effort to use some brain cells.

The private key of puzzle #69 was at around 0.72% of start of this puzzle's range. So, those who scanned the range from the start got lucky.

User MrBitcoin1997 claimed to have solved #69 in a team effort, quoted from below linked deleted post "...12 software developers in Asia...", but they were too stupid to use slipstream.mara.com for withdrawal and said they were robbed. Fools, when Bram24732 demonstrated with successful non-public withdrawal of #67 and #68 that Slipstream service works just fine and reliable.

Deleted post in this thread: https://bitlist.co/post/65333518

As the solver's withdrawal tx 651d171e...8213c07a was foolishly broadcasted to public mempools, it got RBF replaced in a series of replacements. I think nochkin here was the first to post about the RBF chain:

Seems like another stolen reward.
The original TX: https://mempool.space/tx/65f5f2c358651ee12c983051423f9925e1339b8ef52b93e23943e26e80609827
Which was replaced by: https://mempool.space/tx/65f5f2c358651ee12c983051423f9925e1339b8ef52b93e23943e26e80609827 ($1000 in fees)
And that was replaced again by: https://mempool.space/tx/6102b9d3c9a8e40c16ef6eab8c5c8a6819ffac8fc0d22fc850c674863ae5e65c ($1120 in fees)
And again: https://mempool.space/tx/a52c5046f3097a8c2bd3b9889df2fb47b104d47a16cc679d3357feec003db753 ($1130 in fees using Binance pool)

Happy New Year! May the luck be with you, may you come to senses to not pyramid full-quote all the time and whatnot else, lol!

[GinnyBanzz]

...

All your questions you probably could have answered yourself with some search skills, simply by going through a bunch of pages in this thread starting from the withdrawal tx time. Let me spare you the effort to use some brain cells.

The private key of puzzle #69 was at around 0.72% of start of this puzzle's range. So, those who scanned the range from the start got lucky.

User MrBitcoin1997 claimed to have solved #69 in a team effort, quoted from below linked deleted post "...12 software developers in Asia...", but they were too stupid to use slipstream.mara.com for withdrawal and said they were robbed. Fools, when Bram24732 demonstrated with successful non-public withdrawal of #67 and #68 that Slipstream service works just fine and reliable.

Deleted post in this thread: https://bitlist.co/post/65333518

As the solver's withdrawal tx 651d171e...8213c07a was foolishly broadcasted to public mempools, it got RBF replaced in a series of replacements. I think nochkin here was the first to post about the RBF chain:

Seems like another stolen reward.
The original TX: https://mempool.space/tx/65f5f2c358651ee12c983051423f9925e1339b8ef52b93e23943e26e80609827
Which was replaced by: https://mempool.space/tx/65f5f2c358651ee12c983051423f9925e1339b8ef52b93e23943e26e80609827 ($1000 in fees)
And that was replaced again by: https://mempool.space/tx/6102b9d3c9a8e40c16ef6eab8c5c8a6819ffac8fc0d22fc850c674863ae5e65c ($1120 in fees)
And again: https://mempool.space/tx/a52c5046f3097a8c2bd3b9889df2fb47b104d47a16cc679d3357feec003db753 ($1130 in fees using Binance pool)

Happy New Year! May the luck be with you, may you come to senses to not pyramid full-quote all the time and whatnot else, lol!

I'm confused on this part, so the first TX was done by the person who found the private key. Even with RBF, how was this TX replaced with another unless the other person who replaced it also had the private key?

[ee1234ee]

My friends, I have a new doubt.
When I was using RCKangaroo, I discovered an issue while scanning question 135. If I set it to the 134 bit range, the program shows that it will take 849950 days.

RCKangaroo.exe -dp 32 -range 134 -start 4000000000000000000000000000000000 -pubkey 02145d2611c823a396ef6712ce0f712f09b9b4f3135e3e0aa3230fb9b6d08d1e16
GPUs started...
MAIN: Speed: 2311 MKeys/s, Err: 0, DPs: 0K/39513699K, Time: 0d:00h:00m/849950d:22h:43m

And when I set the program to a range of 116 bits, it showed that it would take 1680 days to complete.

RCKangaroo.exe -dp 32 -range 116 -start 4000000000000000000000000000000000 -pubkey 02145d2611c823a396ef6712ce0f712f09b9b4f3135e3e0aa3230fb9b6d08d1e16
GPUs started...
MAIN: Speed: 2283 MKeys/s, Err: 0, DPs: 0K/77175K, Time: 0d:00h:00m/1680d:10h:05m

However, the range of 134 bits is 262143 times that of the range of 116 bits. If we calculate this way, the time does not correspond. Why is the difference so large? Did I miscalculate?

[Bram24732]

My friends, I have a new doubt.
When I was using RCKangaroo, I discovered an issue while scanning question 135. If I set it to the 134 bit range, the program shows that it will take 849950 days.

RCKangaroo.exe -dp 32 -range 134 -start 4000000000000000000000000000000000 -pubkey 02145d2611c823a396ef6712ce0f712f09b9b4f3135e3e0aa3230fb9b6d08d1e16
GPUs started...
MAIN: Speed: 2311 MKeys/s, Err: 0, DPs: 0K/39513699K, Time: 0d:00h:00m/849950d:22h:43m

And when I set the program to a range of 116 bits, it showed that it would take 1680 days to complete.

RCKangaroo.exe -dp 32 -range 116 -start 4000000000000000000000000000000000 -pubkey 02145d2611c823a396ef6712ce0f712f09b9b4f3135e3e0aa3230fb9b6d08d1e16
GPUs started...
MAIN: Speed: 2283 MKeys/s, Err: 0, DPs: 0K/77175K, Time: 0d:00h:00m/1680d:10h:05m

However, the range of 134 bits is 262143 times that of the range of 116 bits. If we calculate this way, the time does not correspond. Why is the difference so large? Did I miscalculate?

The difficulty is proportional to the square root of the number of bits.

[ee1234ee]

The difficulty is proportional to the square root of the number of bits.

Thank you for your response
If that's the case, I originally intended to divide the scope of question 135 into several small areas to scan separately, but this would be ineffective.
A better approach may be for all GPUs to simultaneously scan the 134 bit range, then save the program's DP data for unified comparison, which may be more efficient.

[sxiclub]

I'm confused on this part, so the first TX was done by the person who found the private key. Even with RBF, how was this TX replaced with another unless the other person who replaced it also had the private key?

The first outgoing transaction in a wallet exposes its public key on the blockchain. A bot scanning the movements of the address puzzles below 85 can calculate the private key from the public key using Pollard's Kangaroo and replace the transaction in a few seconds. You can be absolutely certain that there are currently active bots scanning unsolved puzzles below 85, waiting for some unsuspecting user to solve them and execute a public transaction. That's why the use of Mara Slipstream has been discussed so much in this thread.

[kTimesG]

If that's the case, I originally intended to divide the scope of question 135 into several small areas to scan separately, but this would be ineffective.
A better approach may be for all GPUs to simultaneously scan the 134 bit range, then save the program's DP data for unified comparison, which may be more efficient.

Seems like 2026 will again be the year humanity rediscovers fire and reinvents the round wheel.

In other words, you are correct, but these things were already known for at least 30 years, and repeated inhere hundreds of times already.

Bram: why are you so sure RC is on #135? If he wanted to crack it, it would have been solved already, and we don't have any status updates from him.

You can be absolutely certain that there are currently active bots scanning unsolved puzzles below 85, waiting for some unsuspecting user to solve them and execute a public transaction.

Just 85 bits tops? Maybe for the script kiddies who would only use a single machine to solve the ECDLP, from scratch. I'm gonna remind you the estimated cost of breaking a 100 bits ECDLP, which is less than 2 dollars. 110 bits? 60ish dollars. Now, just because there isn't some GitHub repo that can do this in less than 10 minutes, it doesn't make it impossible to be in existence.

[ee1234ee]

Seems like 2026 will again be the year humanity rediscovers fire and reinvents the round wheel.

In other words, you are correct, but these things were already known for at least 30 years, and repeated inhere hundreds of times already.

Bram: why are you so sure RC is on #135? If he wanted to crack it, it would have been solved already, and we don't have any status updates from him.

Friend, could you please provide specific and substantial content every time you speak, instead of always telling a few funny jokes. Thank you

For example, how to quickly compare the DP data of all GPUs when multiple GPUs are scanning a range of 134 bits simultaneously?

The people who come to this forum have different times, and some content may not be accessible to everyone.

[kTimesG]

Friend, could you please provide specific and substantial content every time you speak, instead of always telling a few funny jokes. Thank you

For example, how to quickly compare the DP data of all GPUs when multiple GPUs are scanning a range of 134 bits simultaneously?

What substantial content do you want? Each GPU finds DPs (from different walks), those get collected centrally, and the matching is performed.

If you want actual code, write it yourself. Bram explained already how it can be done, so why repeat something which was already posted less than 24 hours ago?

Hint: it's not 10 lines of Python, it's about building an entire distributed software architecture and solving hundreds of different issues which have very less to do with the basic algorithm.

[Bram24732]

Bram: why are you so sure RC is on #135? If he wanted to crack it, it would have been solved already, and we don't have any status updates from him.

I recall reading back then that he was working on it and hoping a match by the end of 2025 ?
Can’t find this message again but I’m hangover and on my phone so maybe I missed it.
If he’s not on it and you’re not on it I could probably break it quite quickly

[ArtificialLove]

Hi everybody,

I have a question: If I had two addresses which were relatively close [Note below] and their beginning and ending characters matched the puzzle, does that mean I am close?
I don't have decent hardware, just randomly doing random searches on my laptop, should I buy a 5090?

* It's several thousand trillions I guess, I can check the exact distance if that matters, and as for characters, the last four, and the first four and five are identical to 71.



Thanks!

[fixedpaul]

If I had two addresses which were relatively close [Note below] and their beginning and ending characters matched the puzzle, does that mean I am close?

No

[ArtificialLove]

If I had two addresses which were relatively close [Note below] and their beginning and ending characters matched the puzzle, does that mean I am close?

No

How come? I mean, how can one be sure?

[nomachine]

How come? I mean, how can one be sure?

People are wired to hunt for patterns.Spotting stuff like 2:3, 4:7, and whatever else feels like there's some kinda order there. Wrong gut feelings from stuff that's not random.Like databases, file systems, tricks, or compression, those all got built-in structure.But crypto key spaces? They're made on purpose to have zero patterns. Bitcoin's whole safety gig relies on smashing any shortcuts like that. If Bitcoin private keys had some bias, like certain hex starts or spots being more common...Then:You could crack all keys easy. Address clashes would show up everywhere. Cash would get stolen left and right on a huge scale.secp256k1 would be trashed as broken.The whole crypto nerd world would be flipping out.None of that's going down. This thing's been hammered since 2009 by governments, math whizzes, GPU setups, chip makers, and haters trying to break it.