Bitcoin puzzle transaction ~32 BTC prize to who solves it

[nc50lc]

Or maybe they can share us the hint how lucky they were (if it was luck) with the addresses with exposed PubKey or the maths formula/pattern they used. We are eagar to learn   Also, maybe, there's a way to get the Pubkey of an address, maybe --> HAS160 (+ some codes) --> RPMID (+ maybe some codes) --> PubKey. I mean what could a harmless Pubkey do  

When they say "HASH160 of the Public Key" it means: RIPEMD160[SHA256(PubKey)]
Now to get from Address to Public key, you need to reverse RIPEMD160 first then SHA256.

If they found a way to do it, they wouldn't just claimed the puzzle reward, but exploit Bitcoin Mining to get constant block rewards.
Depending on the attack, they could also claim a couple of related bounties.

[1714889849]

1714889849

[1714889849]

1714889849

[1714889849]

1714889849

[digaran]

Is there any way to figure out the first character for #160 private key?, I figured since working more than 3 months on #125 resulted in a failure, it's better to work on something which nobody would go near for years. Lol

[batareyka]

Is there any way to figure out the first character for #160 private key?, I figured since working more than 3 months on #125 resulted in a failure, it's better to work on something which nobody would go near for years. Lol

If there is a way to find out the first one, it will be possible to find out all the other symbols.
Which will lead to a complete Bitcoin hack.

[bill32767]

Or maybe they can share us the hint how lucky they were (if it was luck) with the addresses with exposed PubKey or the maths formula/pattern they used. We are eagar to learn   Also, maybe, there's a way to get the Pubkey of an address, maybe --> HAS160 (+ some codes) --> RPMID (+ maybe some codes) --> PubKey. I mean what could a harmless Pubkey do  

When they say "HASH160 of the Public Key" it means: RIPEMD160[SHA256(PubKey)]
Now to get from Address to Public key, you need to reverse RIPEMD160 first then SHA256.

If they found a way to do it, they wouldn't just claimed the puzzle reward, but exploit Bitcoin Mining to get constant block rewards.
Depending on the attack, they could also claim a couple of related bounties.

So its basically impossible cuz in cryptography (crypto world) reversal is impossible.

[rosengold]

Congratulations to the solver of #125

12.5 BTC this was the greatest prize found by far on this puzzle. US $377.000 as today rates  

Please share the keys to update info about puzzle

[rosengold]

Is there any way to figure out the first character for #160 private key?, I figured since working more than 3 months on #125 resulted in a failure, it's better to work on something which nobody would go near for years. Lol

#160 is between:

7FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

and

FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

so the first character of #160 pvkey is from 8 to F in hex (8, 9, A, B, C, D, E, F)

most of priv keys starting with this same characters where found starting with E or F but this is completely impossible to know if it's the same for this.

[JamiePoc]

Hi all, I have not been here for a very long time and was hoping I could get some information on this thread.

First
There is a list in this thread showing all the addresses from 1 - 160
Do I understand this correctly?
Address 66 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so still needs resolving
I ask as I see in the post people congratulating others on finds in much higher ranges, is this one not worth the effort since it’s the easiest remaining.

And secondly
I wrote some custom software tonight to have a go at the above address, the software is currently checking slightly above 45,700 addresses per second, am I wasting my time? and how does this equate to the hash rates I see mentioned here.

Sorry if these seem dumb questions, answers would be very much appreciated.

So I did a little digging, is this correct
A hash will always be the same number of characters used so 1 Bitcoin address checked per second would equal a hash rate of 64?
If my above statement is correct then the software I wrote is running at 2,924,800 Hash's per second or 2.924 Mh/s, again am I wasting my time?

[casperas20]

u need to live   like   1 milion years to solve it with that slow speed

[digaran]

Hi all, I have not been here for a very long time and was hoping I could get some information on this thread.

First
There is a list in this thread showing all the addresses from 1 - 160
Do I understand this correctly?
Address 66 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so still needs resolving
I ask as I see in the post people congratulating others on finds in much higher ranges, is this one not worth the effort since it’s the easiest remaining.

And secondly
I wrote some custom software tonight to have a go at the above address, the software is currently checking slightly above 45,700 addresses per second, am I wasting my time? and how does this equate to the hash rates I see mentioned here.

Sorry if these seem dumb questions, answers would be very much appreciated.

So I did a little digging, is this correct
A hash will always be the same number of characters used so 1 Bitcoin address checked per second would equal a hash rate of 64?
If my above statement is correct then the software I wrote is running at 2,924,800 Hash's per second or 2.924 Mh/s, again am I wasting my time?

It's not a hash per second, but key per second, generating public key from a private key, hashing the public key 2ice to generate the address, an old laptop with low end GPU  can search for 25 million + keys per second, good GPUs can do billions of keys/s.

From 5 to 160, every 5 puzzle there is an exposed public key, so since we already have the public key we can skip 2 hashes and only generate public keys, and that also is not 1 key at a time, we could practically subtract or add 10,000 trillion keys per second, just a minimum, that's why they can be solved faster.

Have a look at bitcrack and other tools to see what speed you get and compare with your tool.

[ApePunk]

What do yo think about creator step 5 bit range pubkey?
Faster search and get private key maybe he hint to you for solve non pubkey puzzle.

[digaran]

What do yo think about creator step 5 bit range pubkey?
Faster search and get private key maybe he hint to you for solve non pubkey puzzle.

Why would there be any hints? This is not a game, it's a measurement for time taken to solve different keys in certain ranges.
If there was a shortcut to find a private key with only having an address, bitcoin wouldn't be here today.

[unclevito]

Hi all, I have not been here for a very long time and was hoping I could get some information on this thread.

First
There is a list in this thread showing all the addresses from 1 - 160
Do I understand this correctly?
Address 66 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so still needs resolving
I ask as I see in the post people congratulating others on finds in much higher ranges, is this one not worth the effort since it’s the easiest remaining.

And secondly
I wrote some custom software tonight to have a go at the above address, the software is currently checking slightly above 45,700 addresses per second, am I wasting my time? and how does this equate to the hash rates I see mentioned here.

Sorry if these seem dumb questions, answers would be very much appreciated.

So I did a little digging, is this correct
A hash will always be the same number of characters used so 1 Bitcoin address checked per second would equal a hash rate of 64?
If my above statement is correct then the software I wrote is running at 2,924,800 Hash's per second or 2.924 Mh/s, again am I wasting my time?

A little slow. I get 850 million/second with a Rtx 3060 ti at 50% power no cpu on 66.  But it is mainly luck not speed. Like mining bitcoin it only takes a single correct hash but the more hashes you generate the better the chance but this mining is finding the keyspace location or public address by prefix.

[mcdouglasx]

It all lies in computing power, currently I can reduce the range of puzzle #130 to the equivalent of looking for the public key of puzzle #103 without slowing down the search (my resources aren't useful for looking for a public key in range 103 anyway), I could reduce more but I do not have the necessary resources for it and the search becomes slow, therefore it is my "acceptable" range. It doesn't seem unreasonable to me that more puzzles will continue to be found this year by comparing what I can do with basic resources with others who have many .

in short, a puzzle for rich people

[digaran]

It all lies in computing power, currently I can reduce the range of puzzle #130 to the equivalent of looking for the public key of puzzle #103 without slowing down the search (my resources aren't useful for looking for a public key in range 103 anyway), I could reduce more but I do not have the necessary resources for it and the search becomes slow, therefore it is my "acceptable" range. It doesn't seem unreasonable to me that more puzzles will continue to be found this year by comparing what I can do with basic resources with others who have many .

in short, a puzzle for rich people

Well, if you can really reduce the range down to 103 bits, there are already a few hunters with decent rigs willing to help you out and then you could use an escrow to split the prize, you could also divide the 103 bit range into 100 small ranges and search each one per day, after 100 days or even less, you will find the key, but the question is, are you really sure you can lower the range to 103 or even lower? What if the key you are looking for is not there?

You need to provide a reasonable solution to prove that the target is in the said range.

Good luck though, I'm off this puzzle till I see the private keys for #120 and especially #125, I might work on other puzzles here and there, but won't engage in sharing my findings and talk about possible solutions, as it seems we could spend more than 120 days 24/7 just to have nothing at the end, and I don't mean money, who ever solved it they deserve it and I hope the best for them, but not being able to have the answer ( private key ) of the puzzle, even an empty key, is a deal breaker.

[mcdouglasx]

It all lies in computing power, currently I can reduce the range of puzzle #130 to the equivalent of looking for the public key of puzzle #103 without slowing down the search (my resources aren't useful for looking for a public key in range 103 anyway), I could reduce more but I do not have the necessary resources for it and the search becomes slow, therefore it is my "acceptable" range. It doesn't seem unreasonable to me that more puzzles will continue to be found this year by comparing what I can do with basic resources with others who have many .

in short, a puzzle for rich people

Well, if you can really reduce the range down to 103 bits, there are already a few hunters with decent rigs willing to help you out and then you could use an escrow to split the prize, you could also divide the 103 bit range into 100 small ranges and search each one per day, after 100 days or even less, you will find the key, but the question is, are you really sure you can lower the range to 103 or even lower? What if the key you are looking for is not there?

You need to provide a reasonable solution to prove that the target is in the said range.

Good luck though, I'm off this puzzle till I see the private keys for #120 and especially #125, I might work on other puzzles here and there, but won't engage in sharing my findings and talk about possible solutions, as it seems we could spend more than 120 days 24/7 just to have nothing at the end, and I don't mean money, who ever solved it they deserve it and I hope the best for them, but not being able to have the answer ( private key ) of the puzzle, even an empty key, is a deal breaker.

I am completely sure of it because I tested it with public keys that I know the pk and I was able to know that the script work

My problem is that I lack computing power and at this time I do not have how to invest in it. I have thought about sharing the script but we would return to the same starting point where someone with a lot of computer power takes advantage of the script, take the money and then do not even have the decency to thank the developers or reveal the key.

[digaran]

Ok, lets test your script without you revealing it to the public, just drop the first 2 characters on the left for this public key's private key :

03cefd304a9a8da40666e97b2d9650e31a71a9a9fcd29a24724d31a2fabbc8ea0e

Do you need the exact range or not? It has 32 characters and it starts with F, just drop the second character and give me the public key for it to verify, that could help a lot for others to believe you.

[mcdouglasx]

Ok, lets test your script without you revealing it to the public, just drop the first 2 characters on the left for this public key's private key :

03cefd304a9a8da40666e97b2d9650e31a71a9a9fcd29a24724d31a2fabbc8ea0e

Do you need the exact range or not? It has 32 characters and it starts with F, just drop the second character and give me the public key for it to verify, that could help a lot for others to believe you.

32 Characters hex?

[mcdouglasx]

Ok, lets test your script without you revealing it to the public, just drop the first 2 characters on the left for this public key's private key :

03cefd304a9a8da40666e97b2d9650e31a71a9a9fcd29a24724d31a2fabbc8ea0e

Do you need the exact range or not? It has 32 characters and it starts with F, just drop the second character and give me the public key for it to verify, that could help a lot for others to believe you.

I did not understand your proposal very well regarding the range of your pk

but for example if you eliminate the first 2 digits of your pk in decimal and generate another pubkey you will possibly get a pubkey that starts (although I recommend explaining the range better):

1= 03941029...
2=02caf96e4..

After I know what your pubkey is, I get the rest of the digits.

without the need to generate millions of keys.

[batareyka]

It all lies in computing power, currently I can reduce the range of puzzle #130 to the equivalent of looking for the public key of puzzle #103 without slowing down the search (my resources aren't useful for looking for a public key in range 103 anyway), I could reduce more but I do not have the necessary resources for it and the search becomes slow, therefore it is my "acceptable" range. It doesn't seem unreasonable to me that more puzzles will continue to be found this year by comparing what I can do with basic resources with others who have many .

in short, a puzzle for rich people

Well, if you can really reduce the range down to 103 bits, there are already a few hunters with decent rigs willing to help you out and then you could use an escrow to split the prize, you could also divide the 103 bit range into 100 small ranges and search each one per day, after 100 days or even less, you will find the key, but the question is, are you really sure you can lower the range to 103 or even lower? What if the key you are looking for is not there?

You need to provide a reasonable solution to prove that the target is in the said range.

Good luck though, I'm off this puzzle till I see the private keys for #120 and especially #125, I might work on other puzzles here and there, but won't engage in sharing my findings and talk about possible solutions, as it seems we could spend more than 120 days 24/7 just to have nothing at the end, and I don't mean money, who ever solved it they deserve it and I hope the best for them, but not being able to have the answer ( private key ) of the puzzle, even an empty key, is a deal breaker.

I am completely sure of it because I tested it with public keys that I know the pk and I was able to know that the script work

My problem is that I lack computing power and at this time I do not have how to invest in it. I have thought about sharing the script but we would return to the same starting point where someone with a lot of computer power takes advantage of the script, take the money and then do not even have the decency to thank the developers or reveal the key.

You can eliminate as many numbers as you like.
for example, I can reduce the key by 4 digits from 32 to 28, but for this there will be 65,000 open keys, which I count is a lot.
5 and 6 digits can also be eliminated.
 

[citb0in]

There is even a way to find out the range in which the key is located, ...

Really? So tell us what the range is where #66 is lying