Bitcoin puzzle transaction ~32 BTC prize to who solves it

[D3XTR]

Hey guys! I'm getting this error. I got a video card Gefore GTX 760, any clue why this is happening? I tried to change from default 30 ,to 60, to 50, to 90 and nothing is working out. What am I doing wrong??




https://imgur.com/x4Wj4j4

[AndreuSmetanin]

Hey guys! I'm getting this error. I got a video card Gefore GTX 760, any clue why this is happening? I tried to change from default 30 ,to 60, to 50, to 90 and nothing is working out. What am I doing wrong??




https://imgur.com/x4Wj4j4

we are not psychics ,what problems to do a full-screen system window ,or at least to lay out the initial command to run this format cuBitCrack.exet -b 32-t 64-p 192 --keyspace 0908adc3872838975ccaebbad7834294786ddae8297

[iparktur]

Who can write the supposed keyspace for addresses

# 66 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so
# 67 1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9
# 68 1MVDYgVaSN6iKKEsbzRUAYFrYJadLYZvvZ
# 69 19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG
# 71 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
# 72 1JTK7s9YVYywfm5XUH7RNhHJH1LshCaRFR
# 73 12VVRNPi4SJqUTsp6FmqDqY5sGosDtysn4
# 74 1FWGcVDK3JGzCC3WtkYetULPszMaK2Jksv
# 76 1DJh2eHFYQfACPmrvpyWc8MSTYKh7w9eRF
# 77 1Bxk4CQdqL9p22JEtDfdXMsng1XacifUtE
# 78 15qF6X51huDjqTmF9BJgxXdt1xcj46Jmhb
# 79 1ARk8HWJMn8js8tQmGUJeQHjSE7KRkn2t8
# 81 15qsCm78whspNQFydGJQk5rexzxTQopnHZ
# 82 13zYrYhhJxp6Ui1VV7pqa5WDhNWM45ARAC
# 83 14MdEb4eFcT3MVG5sPFG4jGLuHJSnt1Dk2
# 84 1CMq3SvFcVEcpLMuuH8PUcNiqsK1oicG2D
# 86
# 87
# 88
# 89
# 91
# 92
# 93
# 94
# 96
# 97
# 98
# 99
# 105 1CMjscKB3QW7SDyQ4c3C3DEUHiHRhiZVib
# 110 12JzYkkN76xkwvcPT6AWKZtGX6w2LAgsJg
# 115 1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv
# 120 17s2b9ksz5y7abUm92cHwG8jEPCzK3dLnT
# 125 1PXAyUB8ZoH3WD8n5zoAthYjN15yN5CVq5
# 130 1Fo65aKq8s8iquMt6weF1rku1moWVEd5Ua
# 135 16RGFo6hjq9ym6Pj7N5H7L1NR1rVPJyw2v
# 140 1QKBaU6WAeycb3DbKbLBkX7vJiaS8r42Xo
# 145 19GpszRNUej5yYqxXoLnbZWKew3KdVLkXg
# 150 1MUJSJYtGPVGkBCTqGspnxyHahpt5Te8jy
# 155 1AoeP37TmHdFh8uN72fu9AqgtLrUwcv2wJ
# 160 1NBC8uXJy1GiJ6drkiZa1WuKn51ps7EPTv

in this format

# 62 2000000000000000 - 3FFFFFFFFFFFFFFFF
# 63 4000000000000000 - 7FFFFFFFFFFFFFFFFF
# 64 8000000000000000- FFFFFFFFFFFFFFFFF

[racminer]

# 66   20000000000000000 3FFFFFFFFFFFFFFFF
# 67   40000000000000000 7FFFFFFFFFFFFFFFF
# 68   80000000000000000 FFFFFFFFFFFFFFFFF
# 69 100000000000000000 1FFFFFFFFFFFFFFFFF

# 71   400000000000000000 7FFFFFFFFFFFFFFFFF
# 72   800000000000000000  FFFFFFFFFFFFFFFFFF
# 73 1000000000000000000 1FFFFFFFFFFFFFFFFFF
# 74 2000000000000000000 3FFFFFFFFFFFFFFFFFF

# 76   8000000000000000000 FFFFFFFFFFFFFFFFFFF
# 77 10000000000000000000 1FFFFFFFFFFFFFFFFFFF
# 78 20000000000000000000 3FFFFFFFFFFFFFFFFFFF
# 79 40000000000000000000 7FFFFFFFFFFFFFFFFFFF

# 81
# 82
# 83
# 84

# 86
# 87
# 88
# 89

# 91
# 92
# 93
# 94

# 96
# 97
# 98
# 99

# 101  10000000000000000000000000 1FFFFFFFFFFFFFFFFFFFFFFFFF
# 102  20000000000000000000000000 3FFFFFFFFFFFFFFFFFFFFFFFFF
# .....
# 159
# 160

You can do the rest now

Why did you skip 101, 102 etc .. and left only 105 110 115 ...  

[57fe]

#105 is solved. I'll post the private key later, after learn most significant BTC forks. A checkpoint right now is uncompressed address that corresponds to the same private key: 1JATjHbShdvgkvGHyoRv1vTnEeiibqMVnj.
Thanks very much for the creator of the puzzle! I have learned so many beautiful math at puzzle solving.   

[dextronomous]

So hi there 57fe.

when you gonna give you'r not only code away, but somewhat explain with what and how you did it,
you have a compiled version of the app like Telariust has given,

thanks again for the info.

[BurtW]

So now the race is on between #64 by brute force and #110 by kangaroos!

[supika]

#105 is solved. I'll post the private key later, after learn most significant BTC forks. A checkpoint right now is uncompressed address that corresponds to the same private key: 1JATjHbShdvgkvGHyoRv1vTnEeiibqMVnj.
Thanks very much for the creator of the puzzle! I have learned so many beautiful math at puzzle solving.   

@57e
What hardware did you used, CPU/GPU?
How long the discovery of private key took?
In your opinion the other keys up to a point can be found without huge resources?
I`m thinking that if huge resources are necessary only few people have access to huge amount of processing power.
Thanks!

[MeBender]

@57fe congrats brother

[iparktur]

racminer  -  THANK !
I missed those numbers - I just didn’t notice (my mistake)



Congratulations to 57fe on getting # 105.
57fe has proven several times that his method works!

[MeBender]

Here are the keyspaces for the remaining unsolved addresses up to #110

#64 = 8000000000000000:FFFFFFFFFFFFFFFF
#66 = 20000000000000000:3FFFFFFFFFFFFFFFF
#67 = 40000000000000000:7FFFFFFFFFFFFFFFF
#68 = 80000000000000000:FFFFFFFFFFFFFFFFF
#69 = 100000000000000000:1FFFFFFFFFFFFFFFFF
#71 = 400000000000000000:7FFFFFFFFFFFFFFFFF
#72 = 800000000000000000:FFFFFFFFFFFFFFFFFF
#73 = 1000000000000000000:1FFFFFFFFFFFFFFFFFF
#74 = 2000000000000000000:3FFFFFFFFFFFFFFFFFF
#76 = 8000000000000000000:FFFFFFFFFFFFFFFFFFF
#77 = 10000000000000000000:1FFFFFFFFFFFFFFFFFFF
#78 = 20000000000000000000:3FFFFFFFFFFFFFFFFFFF
#79 = 40000000000000000000:7FFFFFFFFFFFFFFFFFFF
#80 = 80000000000000000000:FFFFFFFFFFFFFFFFFFFF
#81 = 0100000000000000000000:01FFFFFFFFFFFFFFFFFFFF
#82 = 0200000000000000000000:03FFFFFFFFFFFFFFFFFFFF
#83 = 0400000000000000000000:07FFFFFFFFFFFFFFFFFFFF
#84 = 0800000000000000000000:0FFFFFFFFFFFFFFFFFFFFF
#86 = 2000000000000000000000:3FFFFFFFFFFFFFFFFFFFFF
#87 = 4000000000000000000000:7FFFFFFFFFFFFFFFFFFFFF
#88 = 8000000000000000000000:FFFFFFFFFFFFFFFFFFFFFF
#89 = 010000000000000000000000:01FFFFFFFFFFFFFFFFFFFFFF
#91 = 040000000000000000000000:07FFFFFFFFFFFFFFFFFFFFFF
#92 = 080000000000000000000000:0FFFFFFFFFFFFFFFFFFFFFFF
#93 = 100000000000000000000000:1FFFFFFFFFFFFFFFFFFFFFFF
#94 = 200000000000000000000000:3FFFFFFFFFFFFFFFFFFFFFFF
#96 = 800000000000000000000000:FFFFFFFFFFFFFFFFFFFFFFFF
#97 = 01000000000000000000000000:01FFFFFFFFFFFFFFFFFFFFFFFF
#98 = 02000000000000000000000000:03FFFFFFFFFFFFFFFFFFFFFFFF
#99 = 04000000000000000000000000:07FFFFFFFFFFFFFFFFFFFFFFFF
#101 = 10000000000000000000000000:1FFFFFFFFFFFFFFFFFFFFFFFFF
#102 = 20000000000000000000000000:3FFFFFFFFFFFFFFFFFFFFFFFFF
#103 = 40000000000000000000000000:7FFFFFFFFFFFFFFFFFFFFFFFFF
#104 = 80000000000000000000000000:FFFFFFFFFFFFFFFFFFFFFFFFFF
#106 = 0200000000000000000000000000:03FFFFFFFFFFFFFFFFFFFFFFFFFF
#107 = 0400000000000000000000000000:07FFFFFFFFFFFFFFFFFFFFFFFFFF
#108 = 0800000000000000000000000000:0FFFFFFFFFFFFFFFFFFFFFFFFFFF
#109 = 1000000000000000000000000000:1FFFFFFFFFFFFFFFFFFFFFFFFFFF
#110 = 2000000000000000000000000000:3FFFFFFFFFFFFFFFFFFFFFFFFFFF

[iparktur]

MeBender  -  I THANK  YOU!

[57fe]

#105 is solved. I'll post the private key later, after learn most significant BTC forks. A checkpoint right now is uncompressed address that corresponds to the same private key: 1JATjHbShdvgkvGHyoRv1vTnEeiibqMVnj.
Thanks very much for the creator of the puzzle! I have learned so many beautiful math at puzzle solving.   

@57e
What hardware did you used, CPU/GPU?
How long the discovery of private key took?
In your opinion the other keys up to a point can be found without huge resources?
I`m thinking that if huge resources are necessary only few people have access to huge amount of processing power.
Thanks!

I have used my own version of CUDA GPU code which almost exactly reproduces Pollard's Kangaroo algorithm published earlier as Python code. Solving #105 takes 1 month of working of GTX 1080ti at 270-275 Mh/s, and last 2 week of work of all my available GPUs (total h/s was approximately 1800Mh/s). So, it was not so simple as the Python code presented. I haven't reached published by j2002ba2 1600Mh/s. I has obtained only 470Mh/s with a cloud GPU server and one Tesla V100. I'm not a good programmer in CUDA, that why.
I guess, huge power is necessary for problems behind #120, as mentioned before by j2002ba2. At least with today state of art of ECDLP. Not only GPU power, but CPU and storage too, because we need to generate a huge amount of distinguished points (it was 24GB of data in my case) and to analyze this data in appropriate time. I guess, it is the reason why #105 was unsolved so long time.
The luck was 25% in my case. Very good luck. I apologize for my English.

[AndreuSmetanin]

#105 is solved. I'll post the private key later, after learn most significant BTC forks. A checkpoint right now is uncompressed address that corresponds to the same private key: 1JATjHbShdvgkvGHyoRv1vTnEeiibqMVnj.
Thanks very much for the creator of the puzzle! I have learned so many beautiful math at puzzle solving.   

@57e
What hardware did you used, CPU/GPU?
How long the discovery of private key took?
In your opinion the other keys up to a point can be found without huge resources?
I`m thinking that if huge resources are necessary only few people have access to huge amount of processing power.
Thanks!

I have used my own version of CUDA GPU code which almost exactly reproduces Pollard's Kangaroo algorithm published earlier as Python code. Solving #105 takes 1 month of working of GTX 1080ti at 270-275 Mh/s, and last 2 week of work of all my available GPUs (total h/s was approximately 1800Mh/s). So, it was not so simple as the Python code presented. I haven't reached published by j2002ba2 1600Mh/s. I has obtained only 470Mh/s with a cloud GPU server and one Tesla V100. I'm not a good programmer in CUDA, that why.
I guess, huge power is necessary for problems behind #120, as mentioned before by j2002ba2. At least with today state of art of ECDLP. Not only GPU power, but CPU and storage too, because we need to generate a huge amount of distinguished points (it was 24GB of data in my case) and to analyze this data in appropriate time. I guess, it is the reason why #105 was unsolved so long time.
The luck was 25% in my case. Very good luck. I apologize for my English.

Congratulations to the winner of the 105th puzzle, may you also be lucky in everything.!!!

[Darmont33]

Congratulations to the winner. What happened to your forum? Is he available? 57fe

[supika]

#105 is solved. I'll post the private key later, after learn most significant BTC forks. A checkpoint right now is uncompressed address that corresponds to the same private key: 1JATjHbShdvgkvGHyoRv1vTnEeiibqMVnj.
Thanks very much for the creator of the puzzle! I have learned so many beautiful math at puzzle solving.   

@57e
What hardware did you used, CPU/GPU?
How long the discovery of private key took?
In your opinion the other keys up to a point can be found without huge resources?
I`m thinking that if huge resources are necessary only few people have access to huge amount of processing power.
Thanks!

I have used my own version of CUDA GPU code which almost exactly reproduces Pollard's Kangaroo algorithm published earlier as Python code. Solving #105 takes 1 month of working of GTX 1080ti at 270-275 Mh/s, and last 2 week of work of all my available GPUs (total h/s was approximately 1800Mh/s). So, it was not so simple as the Python code presented. I haven't reached published by j2002ba2 1600Mh/s. I has obtained only 470Mh/s with a cloud GPU server and one Tesla V100. I'm not a good programmer in CUDA, that why.
I guess, huge power is necessary for problems behind #120, as mentioned before by j2002ba2. At least with today state of art of ECDLP. Not only GPU power, but CPU and storage too, because we need to generate a huge amount of distinguished points (it was 24GB of data in my case) and to analyze this data in appropriate time. I guess, it is the reason why #105 was unsolved so long time.
The luck was 25% in my case. Very good luck. I apologize for my English.

Thank you for you answer. Most of us we are not native english speakers so your english is ok.
So this puzzle is a fight between coders. I`m not a coder but I wish good luck to all brilliant coders

[dextronomous]

#105 is solved. I'll post the private key later, after learn most significant BTC forks. A checkpoint right now is uncompressed address that corresponds to the same private key: 1JATjHbShdvgkvGHyoRv1vTnEeiibqMVnj.
Thanks very much for the creator of the puzzle! I have learned so many beautiful math at puzzle solving.   

@57e
What hardware did you used, CPU/GPU?
How long the discovery of private key took?
In your opinion the other keys up to a point can be found without huge resources?
I`m thinking that if huge resources are necessary only few people have access to huge amount of processing power.
Thanks!

I have used my own version of CUDA GPU code which almost exactly reproduces Pollard's Kangaroo algorithm published earlier as Python code. Solving #105 takes 1 month of working of GTX 1080ti at 270-275 Mh/s, and last 2 week of work of all my available GPUs (total h/s was approximately 1800Mh/s). So, it was not so simple as the Python code presented. I haven't reached published by j2002ba2 1600Mh/s. I has obtained only 470Mh/s with a cloud GPU server and one Tesla V100. I'm not a good programmer in CUDA, that why.
I guess, huge power is necessary for problems behind #120, as mentioned before by j2002ba2. At least with today state of art of ECDLP. Not only GPU power, but CPU and storage too, because we need to generate a huge amount of distinguished points (it was 24GB of data in my case) and to analyze this data in appropriate time. I guess, it is the reason why #105 was unsolved so long time.
The luck was 25% in my case. Very good luck. I apologize for my English.

so hi man, would really love to try it out,
would it become available to use for us, wish it was made available for use with gpu, then again,
do you have a readme cause 6609y  8m 12d 19:32:04s this is not working> for me.
thanks man reading a lot and learning a lot here. greetz.

[racminer]

#105 is solved. I'll post the private key later, after learn most significant BTC forks. A checkpoint right now is uncompressed address that corresponds to the same private key: 1JATjHbShdvgkvGHyoRv1vTnEeiibqMVnj.
Thanks very much for the creator of the puzzle! I have learned so many beautiful math at puzzle solving.   

@57e
What hardware did you used, CPU/GPU?
How long the discovery of private key took?
In your opinion the other keys up to a point can be found without huge resources?
I`m thinking that if huge resources are necessary only few people have access to huge amount of processing power.
Thanks!

I have used my own version of CUDA GPU code which almost exactly reproduces Pollard's Kangaroo algorithm published earlier as Python code. Solving #105 takes 1 month of working of GTX 1080ti at 270-275 Mh/s, and last 2 week of work of all my available GPUs (total h/s was approximately 1800Mh/s). So, it was not so simple as the Python code presented. I haven't reached published by j2002ba2 1600Mh/s. I has obtained only 470Mh/s with a cloud GPU server and one Tesla V100. I'm not a good programmer in CUDA, that why.
I guess, huge power is necessary for problems behind #120, as mentioned before by j2002ba2. At least with today state of art of ECDLP. Not only GPU power, but CPU and storage too, because we need to generate a huge amount of distinguished points (it was 24GB of data in my case) and to analyze this data in appropriate time. I guess, it is the reason why #105 was unsolved so long time.
The luck was 25% in my case. Very good luck. I apologize for my English.

Very Nice !

I have a question : how many tame and wild kangaroo's were  there in the final tame.txt and wild.txt files?

[Blackside0011]

Drotika scammer!
he sells this script
https://github.com/beranm14/pollard_rho

https://github.com/Antonkee/Pollard-Rho-kangaroo scammer too, after purchase on satoshidisk you will receive an archive with a password that you do not know!

[BurtW]

Drotika scammer!
he sells this script
https://github.com/beranm14/pollard_rho

https://github.com/Antonkee/Pollard-Rho-kangaroo scammer too, after purchase on satoshidisk you will receive an archive with a password that you do not know!

There appears to be several scams like this.  That is why we decided to just write our own.  The project has been very educational!  We have a few more improvements to do then we will be moving our code on to a GPU some time later this year (when we can find the time to work on the project).

https://bitcointalk.org/index.php?topic=5173445.0