Hello Guys
Anybody knows each bitcoin puzzles solved in what percent of ranges?
Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 36. (Read 192961 times)
happy birthday,
Thanks
Mostly, I work on puzzle 66, but today, being a special day, I was trying some of my old scripts, among which was a batch (.bat) file that I occasionally run. Today, When I executed it, I saw something like Start:2C15823997A13A9000000000000000000
Stop :2C15823997A13A9FFFFFFFFFFFFFFFFFF
Keys :1
Number of CPU thread: 0
Range width: 2^72
Jump Avg distance: 2^36.04
Number of kangaroos: 2^20.25
Suggested DP: 13
Expected operations: 2^37.12
Expected RAM: 707.9MB
DP size: 13 [0xFFF8000000000000]
GPU: GPU #0 NVIDIA GeForce RTX 3060 Ti (38x0 cores) Grid(76x128) (102.0 MB used)
SolveKeyGPU Thread GPU#0: creating kangaroos...
SolveKeyGPU Thread GPU#0: 2^20.25 kangaroos [4.2s]
[999.21 MK/s][GPU 999.21 MK/s][Count 2^36.91][Dead 1][02:27 (Avg 02:29)][483.1/610.4MB]
Key# 0 [1S]Pub: 0x03633CBE38F52C67DED3104637FAF4B05ABC85C6D9815DB628DF18719051FB8B3B
Priv: 0x2C15823997A13A99FE40A3DC9797A1F2E
Done: Total time 02:37
Which made me quite happy. However, this joy was short-lived because the batch file was originally created to check some sample public keys during an experiment, Following this realization I felt quite disheartened
in that sorrow, I typed the above message. 
I am the creator.
You are quite right, 161-256 are silly. I honestly just did not think of this. What is especially embarrassing, is this did not occur to me once, in two years. By way of excuse, I was not really thinking much about the puzzle at all.
I will make up for two years of stupidity. I will spend from 161-256 to the unsolved parts, as you suggest. In addition, I intend to add further funds. My aim is to boost the density by a factor of 10, from 0.001*length(key) to 0.01*length(key). Probably in the next few weeks. At any rate, when I next have an extended period of quiet and calm, to construct the new transaction carefully.
A few words about the puzzle. There is no pattern. It is just consecutive keys from a deterministic wallet (masked with leading 000...0001 to set difficulty). It is simply a crude measuring instrument, of the cracking strength of the community.
Finally, I wish to express appreciation of the efforts of all developers of new cracking tools and technology. The "large bitcoin collider" is especially innovative and interesting!
You are quite right, 161-256 are silly. I honestly just did not think of this. What is especially embarrassing, is this did not occur to me once, in two years. By way of excuse, I was not really thinking much about the puzzle at all.
I will make up for two years of stupidity. I will spend from 161-256 to the unsolved parts, as you suggest. In addition, I intend to add further funds. My aim is to boost the density by a factor of 10, from 0.001*length(key) to 0.01*length(key). Probably in the next few weeks. At any rate, when I next have an extended period of quiet and calm, to construct the new transaction carefully.
A few words about the puzzle. There is no pattern. It is just consecutive keys from a deterministic wallet (masked with leading 000...0001 to set difficulty). It is simply a crude measuring instrument, of the cracking strength of the community.
Finally, I wish to express appreciation of the efforts of all developers of new cracking tools and technology. The "large bitcoin collider" is especially innovative and interesting!
I need some fund to continue for my discoveries and projects, or else I'll have to abandon these endeavors entirely. It's quite distressing for me, but I've been left with no choice. The creator's support would mean the world to me as I strive to keep my work alive. As you mentioned, "it is simply a crude measuring instrument, of the cracking strength of the community." However, if all members of the community continue to leave their tasks incomplete due to constraints, your measuring instrument will repeatedly break. Please understand that in this community, 99% of members may have limited strength, but they put in a tremendous amount of effort. Anyways... Today is my birthday
happy birthday, I hope you get it, for my part I abandoned my idea of sharing knowledge regarding puzzles, I was thinking of releasing the method once I unlocked 130, but this is a community that does not work as a community, I prefer to wait 2 months if possible necessary, to unlock puzzle #130 on my own without anyone's help.
If I can do it with a broken i5 laptop without a keyboard in such a short time, it means I have an advantage over anyone else in the world. But although money is not important to me, I settle for what is necessary (because I need it). If I later unlock 135-140, I will donate it to charity and projects that I admire.
I am the creator.
You are quite right, 161-256 are silly. I honestly just did not think of this. What is especially embarrassing, is this did not occur to me once, in two years. By way of excuse, I was not really thinking much about the puzzle at all.
I will make up for two years of stupidity. I will spend from 161-256 to the unsolved parts, as you suggest. In addition, I intend to add further funds. My aim is to boost the density by a factor of 10, from 0.001*length(key) to 0.01*length(key). Probably in the next few weeks. At any rate, when I next have an extended period of quiet and calm, to construct the new transaction carefully.
A few words about the puzzle. There is no pattern. It is just consecutive keys from a deterministic wallet (masked with leading 000...0001 to set difficulty). It is simply a crude measuring instrument, of the cracking strength of the community.
Finally, I wish to express appreciation of the efforts of all developers of new cracking tools and technology. The "large bitcoin collider" is especially innovative and interesting!
You are quite right, 161-256 are silly. I honestly just did not think of this. What is especially embarrassing, is this did not occur to me once, in two years. By way of excuse, I was not really thinking much about the puzzle at all.
I will make up for two years of stupidity. I will spend from 161-256 to the unsolved parts, as you suggest. In addition, I intend to add further funds. My aim is to boost the density by a factor of 10, from 0.001*length(key) to 0.01*length(key). Probably in the next few weeks. At any rate, when I next have an extended period of quiet and calm, to construct the new transaction carefully.
A few words about the puzzle. There is no pattern. It is just consecutive keys from a deterministic wallet (masked with leading 000...0001 to set difficulty). It is simply a crude measuring instrument, of the cracking strength of the community.
Finally, I wish to express appreciation of the efforts of all developers of new cracking tools and technology. The "large bitcoin collider" is especially innovative and interesting!
I need some fund to continue for my discoveries and projects, or else I'll have to abandon these endeavors entirely. It's quite distressing for me, but I've been left with no choice. The creator's support would mean the world to me as I strive to keep my work alive. As you mentioned, "it is simply a crude measuring instrument, of the cracking strength of the community." However, if all members of the community continue to leave their tasks incomplete due to constraints, your measuring instrument will repeatedly break. Please understand that in this community, 99% of members may have limited strength, but they put in a tremendous amount of effort. Anyways... Today is my birthday
Has anyone managed to find #64 and #125 (again) to get their private keys?
#64 private key is 0xF7051F27B09112D4
To my knowledge, know one knows the private keys for #120 or #125, except for the solvers.
Has anyone managed to find #64 and #125 (again) to get their private keys?
I have a question, which is faster, generating the public key and then calculating the hash160 by adding and subtracting the private key, compared to calculating the hash160 by adding and subtracting the public key?
For example, I already know the public key of private key 1, to calculate the hash160 address of private key 2, is it faster to generate the public key and then generate the hash160 address by private key 2, or is it faster to calculate the hash160 by adding 1 to the public key of private key 1?
For example, I already know the public key of private key 1, to calculate the hash160 address of private key 2, is it faster to generate the public key and then generate the hash160 address by private key 2, or is it faster to calculate the hash160 by adding 1 to the public key of private key 1?
this might be a dumb question, but i want to ask that is the range of private keys which have P2PKH addresses, i searched for a answer and i found that it is between 2^96 - 2^97
the range is:
from : 1
to : 115792089237316195423570985008687907852837564279074904382605163141518161494337
or in hexadecimal:
from : 0x1
to : 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364141
log2(0)=2^0
log2(115792089237316195423570985008687907852837564279074904382605163141518161494337)=2^256
this might be a dumb question, but i want to ask that is the range of private keys which have P2PKH addresses, i searched for a answer and i found that it is between 2^96 - 2^97
What is your source to indicate that?
this might be a dumb question, but i want to ask that is the range of private keys which have P2PKH addresses, i searched for a answer and i found that it is between 2^96 - 2^97
the range is:
from : 1
to : 115792089237316195423570985008687907852837564279074904382605163141518161494337
or in hexadecimal:
from : 0x1
to : 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364141
That is the full range, but theorically any range of 2^160 keys can have altmost all the P2PKH addresses
this might be a dumb question, but i want to ask that is the range of private keys which have P2PKH addresses, i searched for a answer and i found that it is between 2^96 - 2^97
I would say that if someone has been working on #130 since #125 was found then yes, it will be found, or should be found before #66, but I don't agree that #135 and higher will be found before #66.
For #135, 135 / 2 + 1.05 = 68.55 ops needed to find key using Kangaroo algo, so 2^68.55 ops. #66 = max 2^65 ops.
It will be an interesting race between #66 and those #135 and higher.
That is assuming pollard kang remains best time reduction algo in the next, say, 100 years. Look, we all have beliefs. I believe cracking both SHA and RIPE of an insanely big number is far less likely than screwing around with EC properties until O(sqrt(n)) goes down in some way or another. We shall see.For #135, 135 / 2 + 1.05 = 68.55 ops needed to find key using Kangaroo algo, so 2^68.55 ops. #66 = max 2^65 ops.
It will be an interesting race between #66 and those #135 and higher.
Ok, but 100 years? #66 will be solved before then 😉
It’ll be an interesting arms race…and that’s only if a group of people are interested in finding the remaining addresses. I have a hunch, they will.
I would say that if someone has been working on #130 since #125 was found then yes, it will be found, or should be found before #66, but I don't agree that #135 and higher will be found before #66.
For #135, 135 / 2 + 1.05 = 68.55 ops needed to find key using Kangaroo algo, so 2^68.55 ops. #66 = max 2^65 ops.
It will be an interesting race between #66 and those #135 and higher.
That is assuming pollard kang remains best time reduction algo in the next, say, 100 years. Look, we all have beliefs. I believe cracking both SHA and RIPE of an insanely big number is far less likely than screwing around with EC properties until O(sqrt(n)) goes down in some way or another. We shall see. For #135, 135 / 2 + 1.05 = 68.55 ops needed to find key using Kangaroo algo, so 2^68.55 ops. #66 = max 2^65 ops.
It will be an interesting race between #66 and those #135 and higher.
To find a 66-bit number within 10 days with regular brute force, you would need to check approximately 200 giga/hashes - addresses per second.
Wrong. First of all, #66 is a 65-bit problem. Bit 66 is always 1. Computationally it can be discarded, just like all the known 0 bits.Code:
>>> n=2**65
>>> time_in_s = 10 * 86400
>>> n/time_in_s/1024/1024/1024
39768.2157037037
>>> hashes_per_s = 200 * 2**30
>>> n / hashes_per_s / 86400
1988.4107851851852
10 days to find requires 38 TH/s (7% of total current Bitcoin network hash rate)
200GH/s requires 1988 days.
Now, a "hash" means "obtain some EC point for which k is known + SHA + RIPE + check match". No one said those are zero-overhead operations.
I'd dare to assert that #130 will be found before #66. I have some theoretical and practical thoughts that make me conjunct that puzzles 135 to 160 will also be found before #66, in absence of any surplus proved bit of information we don't yet know (not non-sense).
I would say that if someone has been working on #130 since #125 was found then yes, it will be found, or should be found before #66, but I don't agree that #135 and higher will be found before #66. There are 2 main pools out there and one is already at 11%, for #66. But I know of others who have 'solo' pools/work, working on #66 as well. The one pool just offered a bonus for the key finder, so I imagine as the % of completion gets higher, more single card users will join in, hoping to grab that bonus. But we shall see.
For #135, 135 / 2 + 1.05 = 68.55 ops needed to find key using Kangaroo algo, so 2^68.55 ops. #66 = max 2^65 ops.
It will be an interesting race between #66 and those #135 and higher.
I don't know why but I'm smelling a big scam. Because a newbie that offer more than 12 000€ to solve a following of numbers this is strange...
I feel the same way because no one will give you such a big big prize or big money for this small thing. Because if it is not iskam, if it is not iskam, someone is so big or so. No one will show big offers. Maybe this is his new plan to increase Setar's ID or to take merit in his ID with their fake news. In that case, I will say whether anyone got this offer by participating. Please reply me.If not, this post is to the moderator. I will be forced to report because I don't think of anything other than harassing people like this Iskam post. You and I brother are right. It is Islam. I have seen it for a long time but I have seen it for so long.
To find a 66-bit number within 10 days with regular brute force, you would need to check approximately 200 giga/hashes - addresses per second.
Wrong. First of all, #66 is a 65-bit problem. Bit 66 is always 1. Computationally it can be discarded, just like all the known 0 bits.Code:
>>> n=2**65
>>> time_in_s = 10 * 86400
>>> n/time_in_s/1024/1024/1024
39768.2157037037
>>> hashes_per_s = 200 * 2**30
>>> n / hashes_per_s / 86400
1988.4107851851852
10 days to find requires 38 TH/s (7% of total current Bitcoin network hash rate)
200GH/s requires 1988 days.
Now, a "hash" means "obtain some EC point for which k is known + SHA + RIPE + check match". No one said those are zero-overhead operations.
I'd dare to assert that #130 will be found before #66. I have some theoretical and practical thoughts that make me conjunct that puzzles 135 to 160 will also be found before #66, in absence of any surplus proved bit of information we don't yet know (not non-sense).
Try this to figure it out, multiply puzzle #130 by 4 then subtract the result from this key
Then divide the result by 4 and subtract the result from puzzle key, you should see
The reason why that is happening is because it starts with 3.
Code:
0x0000000000000000000000000000001000000000000000000000000000000000
Public_key=
02e4f3fb0176af85d65ff99ff9198c36091f48e86503681e3e6686fd5053231e11
Code:
0x0000000000000000000000000000000300000000000000000000000000000000
Public_key=
0238381dbe2e509f228ba93363f2451f08fd845cb351d954be18e2b8edd23809fa
There is a flag in your logic if you don't see it, then it is a disappointment
can anyone tell me if the puzzle 130 starts from 2 or 3 ? since the range is 0x200000000000000000000000000000000 and 0x3ffffffffffffffffffffffffffffffff can anyone tell me if its private key starts from 2 or 3 ?
Try this to figure it out, multiply puzzle #130 by 4 then subtract the result from this keyCode:
0x0000000000000000000000000000001000000000000000000000000000000000
Public_key=
02e4f3fb0176af85d65ff99ff9198c36091f48e86503681e3e6686fd5053231e11
Code:
0x0000000000000000000000000000000400000000000000000000000000000000
Public_key=
037564539e85d56f8537d6619e1f5c5aa78d2a3de0889d1d4ee8dbcb5729b62026
Hello everyone, why do you think Puzzle 66 has not been found yet?
What are your thoughts?
What are your thoughts?
To find a 66-bit number within 10 days with regular brute force, you would need to check approximately 200 giga/hashes - addresses per second. It doesn't matter if it's an even or odd number.
Look here average PRNGs speed
https://developer.nvidia.com/gpugems/gpugems3/part-vi-gpu-computing/chapter-37-efficient-random-number-generation-and-application
And we need PRNGs Average Time: 0.000000000002 seconds to solve Puzzle 66
And then all other parts of the script no slower than this.
It's not a programming language problem.
There is no hardware on Earth that could reach this speed.
For 256-bit number a Type III civilization is a needed to solve this. A million years ahead of us.
can anyone tell me if the puzzle 130 starts from 2 or 3 ? since the range is 0x200000000000000000000000000000000 and 0x3ffffffffffffffffffffffffffffffff can anyone tell me if its private key starts from 2 or 3 ?
it starts with 3. Good luck
how do you say this ? is there a certain way to know if it starts from 3 ?
of course there is. But I am not allowed to tell you the details.
A Mathematical way ?
can anyone tell me if the puzzle 130 starts from 2 or 3 ? since the range is 0x200000000000000000000000000000000 and 0x3ffffffffffffffffffffffffffffffff can anyone tell me if its private key starts from 2 or 3 ?
it starts with 3. Good luck
how do you say this ? is there a certain way to know if it starts from 3 ?
of course there is. But I am not allowed to tell you the details.
Jump to: