Bitcoin puzzle transaction ~32 BTC prize to who solves it

[stalker00075]

it does not work.
By firing "from scratch" on a clean script for the scope --keyspace 01000000000000000: 01FFFFFFFFFFFFFFF --share 41/160, the estimated time is 1.75 months. Using the --continue file which contains the starting point at half of what I initially set (just: in a situation where 50% of the range has already been scanned) - the counter gives 1.75 months. This is not something here .... since I've scanned 50% ... it can not be that it will take as long as it will last as if I started scanning from now on again The -r option can not be used because it does not work with "- -continue "and not using this option at this level is probably a waste of time.

Thanks! Fixed respecting the --continue file. Working on the changes for --continue with -r option now.
All changes are in the master branch now and the remaining branch has been removed.

how use this https://github.com/pikachunakapika/BitCrack  need exe file

[1715109208]

1715109208

[1715109208]

1715109208

[1715109208]

1715109208

[1715109208]

1715109208

[zielar]

it does not work.
By firing "from scratch" on a clean script for the scope --keyspace 01000000000000000: 01FFFFFFFFFFFFFFF --share 41/160, the estimated time is 1.75 months. Using the --continue file which contains the starting point at half of what I initially set (just: in a situation where 50% of the range has already been scanned) - the counter gives 1.75 months. This is not something here .... since I've scanned 50% ... it can not be that it will take as long as it will last as if I started scanning from now on again The -r option can not be used because it does not work with "- -continue "and not using this option at this level is probably a waste of time.

Thanks! Fixed respecting the --continue file. Working on the changes for --continue with -r option now.
All changes are in the master branch now and the remaining branch has been removed.

Now everything works as it should! After changing the change of the exe file - it shows (probably) correctly the remaining time which in my case shortened from 1.75 to 1.2 month. Well, just a little suggestion that it would look like this: X months X days X hours X minutes instead of the current x.xx months, because in practice I do not know how to understand the period 1.75 months or the currently displayed 1.2 months in days ?
Thank you for a good job! For sure I will remember about you in the progress of the finds :-)

[zielar]

it does not work.
By firing "from scratch" on a clean script for the scope --keyspace 01000000000000000: 01FFFFFFFFFFFFFFF --share 41/160, the estimated time is 1.75 months. Using the --continue file which contains the starting point at half of what I initially set (just: in a situation where 50% of the range has already been scanned) - the counter gives 1.75 months. This is not something here .... since I've scanned 50% ... it can not be that it will take as long as it will last as if I started scanning from now on again The -r option can not be used because it does not work with "- -continue "and not using this option at this level is probably a waste of time.

Thanks! Fixed respecting the --continue file. Working on the changes for --continue with -r option now.
All changes are in the master branch now and the remaining branch has been removed.

how use this https://github.com/pikachunakapika/BitCrack  need exe file

Stalker i compile for You executable versions of last release by Pikachanapika. You can get them from my repo: https://github.com/ZielarSRC/BitCrack/releases/tag/v0.30

[brainless]

Rx480 has  a limit ... You can't have  -t  higher than 256.

Oh ... it changes the form of things :-) well ... I wanted better :-)
---
Is there someone here who would be able to convert the counting number of scanned keys in BitCrack into a counter showing the number of REMOTE keys to be scanned along with the estimated remaining time to complete? It would be more interesting information than the amount that was scanned. Unfortunately, I do not know the programming language completely, and my knowledge ends at the stage of compiling a ready solution with possible code change in the sources. I would be grateful for such a small addition.

Please checkout the branch "remaining" at https://github.com/pikachunakapika/BitCrack. It also includes my changes for random starting points. With -r you get no ETA and remaining count.

Hello all
i notice, this random called update just start with random starting points instead of series starting points
after 1st generates random starting points, each starting point  start searching series,
Random should be every second each every string random

if you understand, its ok, if you need to understand more in details with example, feel free to ask

your random version of bitcrack working like
[2019-03-04.21:09:12] [Info] Starting point sample: 5B60A7D6CAC10CEF8FF0CD0F7D3D4D7E72265EA3564F3A7C4CEC060DD434BD5E (255 bit range)
[2019-03-04.21:09:12] [Info] Starting point sample: 507B5ACCB577F908D97155CD7A8F2827D7FF6752051D42D70AF33F6A80D4573F (255 bit range)
[2019-03-04.21:09:12] [Info] Starting point sample: 5C45836A0BFB1EAE9FE807030A511FAF5AE30E1708E6E9AC4CEEEEEF0D85883E (255 bit range)

each starting point key once random, next it starting working in series
starting point key : 5B60A7D6CAC10CEF8FF0CD0F7D3D4D7E72265EA3564F3A7C4CEC060DD434BD5E
next working  : 5B60A7D6CAC10CEF8FF0CD0F7D3D4D7E72265EA3564F3A7C4CEC060DD434BD5f, ...60, ....61, .....62, ....63

starting point key : 507B5ACCB577F908D97155CD7A8F2827D7FF6752051D42D70AF33F6A80D4573F
next working : 507B5ACCB577F908D97155CD7A8F2827D7FF6752051D42D70AF33F6A80D4573F  ,... 40, ... 41, ...42

each starting point working in series

what should be random, every second new starting point as random key should be in search pool

have you all tested pinka... BitCrack ?
have you seen this random style

[zielar]

Rx480 has  a limit ... You can't have  -t  higher than 256.

Oh ... it changes the form of things :-) well ... I wanted better :-)
---
Is there someone here who would be able to convert the counting number of scanned keys in BitCrack into a counter showing the number of REMOTE keys to be scanned along with the estimated remaining time to complete? It would be more interesting information than the amount that was scanned. Unfortunately, I do not know the programming language completely, and my knowledge ends at the stage of compiling a ready solution with possible code change in the sources. I would be grateful for such a small addition.

Please checkout the branch "remaining" at https://github.com/pikachunakapika/BitCrack. It also includes my changes for random starting points. With -r you get no ETA and remaining count.

Hello all
i notice, this random called update just start with random starting points instead of series starting points
after 1st generates random starting points, each starting point  start searching series,
Random should be every second each every string random

if you understand, its ok, if you need to understand more in details with example, feel free to ask

your random version of bitcrack working like
[2019-03-04.21:09:12] [Info] Starting point sample: 5B60A7D6CAC10CEF8FF0CD0F7D3D4D7E72265EA3564F3A7C4CEC060DD434BD5E (255 bit range)
[2019-03-04.21:09:12] [Info] Starting point sample: 507B5ACCB577F908D97155CD7A8F2827D7FF6752051D42D70AF33F6A80D4573F (255 bit range)
[2019-03-04.21:09:12] [Info] Starting point sample: 5C45836A0BFB1EAE9FE807030A511FAF5AE30E1708E6E9AC4CEEEEEF0D85883E (255 bit range)

each starting point key once random, next it starting working in series
starting point key : 5B60A7D6CAC10CEF8FF0CD0F7D3D4D7E72265EA3564F3A7C4CEC060DD434BD5E
next working  : 5B60A7D6CAC10CEF8FF0CD0F7D3D4D7E72265EA3564F3A7C4CEC060DD434BD5f, ...60, ....61, .....62, ....63

starting point key : 507B5ACCB577F908D97155CD7A8F2827D7FF6752051D42D70AF33F6A80D4573F
next working : 507B5ACCB577F908D97155CD7A8F2827D7FF6752051D42D70AF33F6A80D4573F  ,... 40, ... 41, ...42

each starting point working in series

what should be random, every second new starting point as random key should be in search pool

have you all tested pinka... BitCrack ?
have you seen this random style

You must precise your individual range to scan by --keyspace command (eg. start:end ) and add -r before all.
Try this:
cuBitCrack.exe -r 1AVJKwzs9AskraJLGHAZPiaZcrpDr1U6AB -c -o FOUND.txt --keyspace 01000000000000000:01FFFFFFFFFFFFFFF
... and you have random range only for #61 address

[brainless]

Rx480 has  a limit ... You can't have  -t  higher than 256.

Oh ... it changes the form of things :-) well ... I wanted better :-)
---
Is there someone here who would be able to convert the counting number of scanned keys in BitCrack into a counter showing the number of REMOTE keys to be scanned along with the estimated remaining time to complete? It would be more interesting information than the amount that was scanned. Unfortunately, I do not know the programming language completely, and my knowledge ends at the stage of compiling a ready solution with possible code change in the sources. I would be grateful for such a small addition.

Please checkout the branch "remaining" at https://github.com/pikachunakapika/BitCrack. It also includes my changes for random starting points. With -r you get no ETA and remaining count.

Hello all
i notice, this random called update just start with random starting points instead of series starting points
after 1st generates random starting points, each starting point  start searching series,
Random should be every second each every string random

if you understand, its ok, if you need to understand more in details with example, feel free to ask

your random version of bitcrack working like
[2019-03-04.21:09:12] [Info] Starting point sample: 5B60A7D6CAC10CEF8FF0CD0F7D3D4D7E72265EA3564F3A7C4CEC060DD434BD5E (255 bit range)
[2019-03-04.21:09:12] [Info] Starting point sample: 507B5ACCB577F908D97155CD7A8F2827D7FF6752051D42D70AF33F6A80D4573F (255 bit range)
[2019-03-04.21:09:12] [Info] Starting point sample: 5C45836A0BFB1EAE9FE807030A511FAF5AE30E1708E6E9AC4CEEEEEF0D85883E (255 bit range)

each starting point key once random, next it starting working in series
starting point key : 5B60A7D6CAC10CEF8FF0CD0F7D3D4D7E72265EA3564F3A7C4CEC060DD434BD5E
next working  : 5B60A7D6CAC10CEF8FF0CD0F7D3D4D7E72265EA3564F3A7C4CEC060DD434BD5f, ...60, ....61, .....62, ....63

starting point key : 507B5ACCB577F908D97155CD7A8F2827D7FF6752051D42D70AF33F6A80D4573F
next working : 507B5ACCB577F908D97155CD7A8F2827D7FF6752051D42D70AF33F6A80D4573F  ,... 40, ... 41, ...42

each starting point working in series

what should be random, every second new starting point as random key should be in search pool

have you all tested pinka... BitCrack ?
have you seen this random style

You must precise your individual range to scan by --keyspace command (eg. start:end ) and add -r before all.
Try this:
cuBitCrack.exe -r 1AVJKwzs9AskraJLGHAZPiaZcrpDr1U6AB -c -o FOUND.txt --keyspace 01000000000000000:01FFFFFFFFFFFFFFF
... and you have random range only for #61 address

you did not follow
each starting point is random, onword from starting point series generating for process

example you searching from 100:1ff

7 starting point created, like 1 8 20 35 37 60 80
when process start
from 1 point to 8 close in sequence same 35 to 37 close , but all in sequence
first is starting point 
1  2 3 4 5 6 7 8 9 10
8 9 10 11 12 13 14
20 21 22 23 24 25 26 27

in this sanrio, main brichard master branch is better continue sequence

Random should be not only starting point, after each next step should be random key for process
 

[racminer]

it does not work.
By firing "from scratch" on a clean script for the scope --keyspace 01000000000000000: 01FFFFFFFFFFFFFFF --share 41/160, the estimated time is 1.75 months. Using the --continue file which contains the starting point at half of what I initially set (just: in a situation where 50% of the range has already been scanned) - the counter gives 1.75 months. This is not something here .... since I've scanned 50% ... it can not be that it will take as long as it will last as if I started scanning from now on again The -r option can not be used because it does not work with "- -continue "and not using this option at this level is probably a waste of time.

Thanks! Fixed respecting the --continue file. Working on the changes for --continue with -r option now.
All changes are in the master branch now and the remaining branch has been removed.

how use this https://github.com/pikachunakapika/BitCrack  need exe file

Stalker i compile for You executable versions of last release by Pikachanapika. You can get them from my repo: https://github.com/ZielarSRC/BitCrack/releases/tag/v0.30

./clBitCrack  -d 1 -b 72 -t 256 -p 1024 --keyspace 1ABBCE2000000000:1ABBCE3000000000 -o res61.txt 1AVJKwzs9AskraJLGHAZPiaZcrpDr1U6AB
[2019-03-04.19:49:36] [Info] Compression: compressed
[2019-03-04.19:49:36] [Info] Starting at: 0000000000000000000000000000000000000000000000001ABBCE2000000000
[2019-03-04.19:49:36] [Info] Ending at:   0000000000000000000000000000000000000000000000001ABBCE3000000000
[2019-03-04.19:49:36] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-03-04.19:49:36] [Info] Compiling OpenCL kernels...
[2019-03-04.19:49:43] [Info] Initializing Ellesmere
[2019-03-04.19:49:45] [Info] Generating 18,874,368 starting points (720.0MB)
[2019-03-04.19:49:49] [Info] 10.0%
[2019-03-04.19:49:51] [Info] 20.0%
[2019-03-04.19:49:52] [Info] 30.0%
[2019-03-04.19:49:52] [Info] 40.0%
[2019-03-04.19:49:53] [Info] 50.0%
[2019-03-04.19:49:53] [Info] 60.0%
[2019-03-04.19:49:53] [Info] 70.0%
[2019-03-04.19:49:54] [Info] 80.0%
[2019-03-04.19:49:54] [Info] 90.0%
[2019-03-04.19:49:55] [Info] 100.0%
[2019-03-04.19:49:55] [Info] Done
[00:02:06] 1152/7536MB | 1 target 109.79 MKey/s (0000000FB6800000 remaining) [ETA 10.23 minutes]

This does not work ETA stays 10min for too long. And the "remaining" never goes below 0000000F00000000 ...
I think  that you may  have a declaration problem, your "remaining" integer may have been declared as a 32bit integer.

[zielar]

Rx480 has  a limit ... You can't have  -t  higher than 256.

Oh ... it changes the form of things :-) well ... I wanted better :-)
---
Is there someone here who would be able to convert the counting number of scanned keys in BitCrack into a counter showing the number of REMOTE keys to be scanned along with the estimated remaining time to complete? It would be more interesting information than the amount that was scanned. Unfortunately, I do not know the programming language completely, and my knowledge ends at the stage of compiling a ready solution with possible code change in the sources. I would be grateful for such a small addition.

Please checkout the branch "remaining" at https://github.com/pikachunakapika/BitCrack. It also includes my changes for random starting points. With -r you get no ETA and remaining count.

Hello all
i notice, this random called update just start with random starting points instead of series starting points
after 1st generates random starting points, each starting point  start searching series,
Random should be every second each every string random

if you understand, its ok, if you need to understand more in details with example, feel free to ask

your random version of bitcrack working like
[2019-03-04.21:09:12] [Info] Starting point sample: 5B60A7D6CAC10CEF8FF0CD0F7D3D4D7E72265EA3564F3A7C4CEC060DD434BD5E (255 bit range)
[2019-03-04.21:09:12] [Info] Starting point sample: 507B5ACCB577F908D97155CD7A8F2827D7FF6752051D42D70AF33F6A80D4573F (255 bit range)
[2019-03-04.21:09:12] [Info] Starting point sample: 5C45836A0BFB1EAE9FE807030A511FAF5AE30E1708E6E9AC4CEEEEEF0D85883E (255 bit range)

each starting point key once random, next it starting working in series
starting point key : 5B60A7D6CAC10CEF8FF0CD0F7D3D4D7E72265EA3564F3A7C4CEC060DD434BD5E
next working  : 5B60A7D6CAC10CEF8FF0CD0F7D3D4D7E72265EA3564F3A7C4CEC060DD434BD5f, ...60, ....61, .....62, ....63

starting point key : 507B5ACCB577F908D97155CD7A8F2827D7FF6752051D42D70AF33F6A80D4573F
next working : 507B5ACCB577F908D97155CD7A8F2827D7FF6752051D42D70AF33F6A80D4573F  ,... 40, ... 41, ...42

each starting point working in series

what should be random, every second new starting point as random key should be in search pool

have you all tested pinka... BitCrack ?
have you seen this random style

You must precise your individual range to scan by --keyspace command (eg. start:end ) and add -r before all.
Try this:
cuBitCrack.exe -r 1AVJKwzs9AskraJLGHAZPiaZcrpDr1U6AB -c -o FOUND.txt --keyspace 01000000000000000:01FFFFFFFFFFFFFFF
... and you have random range only for #61 address

you did not follow
each starting point is random, onword from starting point series generating for process

example you searching from 100:1ff

7 starting point created, like 1 8 20 35 37 60 80
when process start
from 1 point to 8 close in sequence same 35 to 37 close , but all in sequence
first is starting point  
1  2 3 4 5 6 7 8 9 10
8 9 10 11 12 13 14
20 21 22 23 24 25 26 27

in this sanrio, main brichard master branch is better continue sequence

Random should be not only starting point, after each next step should be random key for process
 

it does not work.
By firing "from scratch" on a clean script for the scope --keyspace 01000000000000000: 01FFFFFFFFFFFFFFF --share 41/160, the estimated time is 1.75 months. Using the --continue file which contains the starting point at half of what I initially set (just: in a situation where 50% of the range has already been scanned) - the counter gives 1.75 months. This is not something here .... since I've scanned 50% ... it can not be that it will take as long as it will last as if I started scanning from now on again The -r option can not be used because it does not work with "- -continue "and not using this option at this level is probably a waste of time.

Thanks! Fixed respecting the --continue file. Working on the changes for --continue with -r option now.
All changes are in the master branch now and the remaining branch has been removed.

how use this https://github.com/pikachunakapika/BitCrack  need exe file

Stalker i compile for You executable versions of last release by Pikachanapika. You can get them from my repo: https://github.com/ZielarSRC/BitCrack/releases/tag/v0.30

./clBitCrack  -d 1 -b 72 -t 256 -p 1024 --keyspace 1ABBCE2000000000:1ABBCE3000000000 -o res61.txt 1AVJKwzs9AskraJLGHAZPiaZcrpDr1U6AB
[2019-03-04.19:49:36] [Info] Compression: compressed
[2019-03-04.19:49:36] [Info] Starting at: 0000000000000000000000000000000000000000000000001ABBCE2000000000
[2019-03-04.19:49:36] [Info] Ending at:   0000000000000000000000000000000000000000000000001ABBCE3000000000
[2019-03-04.19:49:36] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-03-04.19:49:36] [Info] Compiling OpenCL kernels...
[2019-03-04.19:49:43] [Info] Initializing Ellesmere
[2019-03-04.19:49:45] [Info] Generating 18,874,368 starting points (720.0MB)
[2019-03-04.19:49:49] [Info] 10.0%
[2019-03-04.19:49:51] [Info] 20.0%
[2019-03-04.19:49:52] [Info] 30.0%
[2019-03-04.19:49:52] [Info] 40.0%
[2019-03-04.19:49:53] [Info] 50.0%
[2019-03-04.19:49:53] [Info] 60.0%
[2019-03-04.19:49:53] [Info] 70.0%
[2019-03-04.19:49:54] [Info] 80.0%
[2019-03-04.19:49:54] [Info] 90.0%
[2019-03-04.19:49:55] [Info] 100.0%
[2019-03-04.19:49:55] [Info] Done
[00:02:06] 1152/7536MB | 1 target 109.79 MKey/s (0000000FB6800000 remaining) [ETA 10.23 minutes]

This does not work ETA stays 10min for too long. And the "remaining" never goes below 0000000F00000000 ...
I think  that you may  have a declaration problem, your "remaining" integer may have been declared as a 32bit integer.

Lol.
I would leave it without comment, but I MUST (...):
The original version works in the same way (builds starting points [different] within the given range)... The difference is that you CAN NOT see it in it. In the "pikachunakapika" version this information is shown and this is not a reason to deny its contribution to development. I also mention that the option "-r" which is responsible for the randomness of a given interval is not imposed on the user, so it is simply an option for people who want to try this way ... I would even say that it is reasonable for the majority, because the original version is probably not the chances of scanning the amount I have already scanned (to get the key sooner).
I confirm after almost an hour of testing the current version of Pika that it works properly and is stable. I also agree with my readouts in the checkpoint files, so I can confirm that the progress is correct and scans in the correct order.
@pikachunakapika - to the suggestion regarding the format of presenting the remaining time, I still have a suggestion regarding the PRESENCE of the remaining keys, namely that it should be shown in the form DEC and not HEX.
@racminer - I will check it out on cuBitCrack or if the problem is the same. Nevertheless, even if so I think that ten minutes of incompatibility at this stage can be regarded as a tolerance threshold with a slight breath

[bill32767]

[Error] Error detecting devices: CUDA driver version is insufficient for CUDA runtime version

Please where to place Cudart32&64 files?

The above error happens anytime I run the Bitcrack 3.0 and the latest CUDA Driver wouldn't install (always saying system restart is required). Please pikachunakapika Help with solutions...thanks

[pikachunakapika]

@pikachunakapika - to the suggestion regarding the format of presenting the remaining time, I still have a suggestion regarding the PRESENCE of the remaining keys, namely that it should be shown in the form DEC and not HEX.
@racminer - I will check it out on cuBitCrack or if the problem is the same. Nevertheless, even if so I think that ten minutes of incompatibility at this stage can be regarded as a tolerance threshold with a slight breath

New version shows decimal remaining time.

Please git pull as I accidentally push a commit without random seed while testing for the last version. So the last version has always the same random values.

[Error] Error detecting devices: CUDA driver version is insufficient for CUDA runtime version

Please where to place Cudart32&64 files?

The above error happens anytime I run the Bitcrack 3.0 and the latest CUDA Driver wouldn't install (always saying system restart is required). Please pikachunakapika Help with solutions...thanks

I guess you are on windows. I will setup a windows machine soon to help you (currently have none).
Zielar, can you help him please?

Regards

[lolobit2]

pikachunakapika
BitCrack with PRNG starting points and remaining time (WIP)

hi, very interested in this kind of work. There are a lot of ideas. How can I contact you?write to me in PM.
can give i7-8700k +2 *1080ti sli

[pikachunakapika]

./clBitCrack  -d 1 -b 72 -t 256 -p 1024 --keyspace 1ABBCE2000000000:1ABBCE3000000000 -o res61.txt 1AVJKwzs9AskraJLGHAZPiaZcrpDr1U6AB
[2019-03-04.19:49:36] [Info] Compression: compressed
[2019-03-04.19:49:36] [Info] Starting at: 0000000000000000000000000000000000000000000000001ABBCE2000000000
[2019-03-04.19:49:36] [Info] Ending at:   0000000000000000000000000000000000000000000000001ABBCE3000000000
[2019-03-04.19:49:36] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-03-04.19:49:36] [Info] Compiling OpenCL kernels...
[2019-03-04.19:49:43] [Info] Initializing Ellesmere
[2019-03-04.19:49:45] [Info] Generating 18,874,368 starting points (720.0MB)
[2019-03-04.19:49:49] [Info] 10.0%
[2019-03-04.19:49:51] [Info] 20.0%
[2019-03-04.19:49:52] [Info] 30.0%
[2019-03-04.19:49:52] [Info] 40.0%
[2019-03-04.19:49:53] [Info] 50.0%
[2019-03-04.19:49:53] [Info] 60.0%
[2019-03-04.19:49:53] [Info] 70.0%
[2019-03-04.19:49:54] [Info] 80.0%
[2019-03-04.19:49:54] [Info] 90.0%
[2019-03-04.19:49:55] [Info] 100.0%
[2019-03-04.19:49:55] [Info] Done
[00:02:06] 1152/7536MB | 1 target 109.79 MKey/s (0000000FB6800000 remaining) [ETA 10.23 minutes]

This does not work ETA stays 10min for too long. And the "remaining" never goes below 0000000F00000000 ...
I think  that you may  have a declaration problem, your "remaining" integer may have been declared as a 32bit integer.

Thanks! It is fixed now.

[conanmori]

While playing around with my bot, I found out this mysterious transaction:
[...]
The prize would be ~32 BTC

EDIT: If you find the solution feel free to leave a tip 1DPUhjHvd2K4ZkycVHEJiN6wba79j5V1u3

Started to anaylize this, but figured out its not actually a puzzle at all. Its attempt to steal of this funds right? There is no official puzzle by owner of this addresses? By what you saying i think there is no consent here.
From what i see you guys have fun, but it shouldn't be allowed at all

You are right mate, their is no statement about the address owner to have a contest in that address. Its looks like they hacking that account rather than a contest. Well they are having fun and we can see that Bitcoin address are really that strong to crack. The OP started this 4years ago and too many people try to crack the address but no one did it yet for so long.

[zielar]

@pikachunakapika - to the suggestion regarding the format of presenting the remaining time, I still have a suggestion regarding the PRESENCE of the remaining keys, namely that it should be shown in the form DEC and not HEX.
@racminer - I will check it out on cuBitCrack or if the problem is the same. Nevertheless, even if so I think that ten minutes of incompatibility at this stage can be regarded as a tolerance threshold with a slight breath

New version shows decimal remaining time.

Please git pull as I accidentally push a commit without random seed while testing for the last version. So the last version has always the same random values.

[Error] Error detecting devices: CUDA driver version is insufficient for CUDA runtime version

Please where to place Cudart32&64 files?

The above error happens anytime I run the Bitcrack 3.0 and the latest CUDA Driver wouldn't install (always saying system restart is required). Please pikachunakapika Help with solutions...thanks

I guess you are on windows. I will setup a windows machine soon to help you (currently have none).
Zielar, can you help him please?

Regards

Of course...
For run you must have already installed the Newest CUDA Toolkit (drivers, runtimes and libraries) [CUDA ver 10.1 you can download from this site - https://developer.nvidia.com/cuda-downloads?target_os=Windows&target_arch=x86_64 ]
When you finish installing that successfully -> you have newest NVIDIA drivers (418.96) and you can use that without adding files Cudaart anywhere.
You can install only the drivers without CUDA Toolkits, but minimal required version is 418.96 attached in CUDA 10.1. Official drivers is lower than drivers used in Cuda so now you can't use this method. However if NVIDIA release them - put the files cudaart to the folder when you have executable file of BitCrack.
In the next some minutes i update last version of Pika release on my repo.
@bill if your GPU is not compatible with newest CUDA drivers (which is real when you have older GPU models) - i can compile .exe for you on lower version CUDA Tools (compatible with your GPU). Please tell how model of GPU you have for that.

[zielar]

All work very good now. Awesome work. Executable is updated on my Git https://github.com/ZielarSRC/BitCrack/releases/tag/v0.30
You need have already installed latest update of CUDA Toolkit (10.1) [only runtimes & libraries + DRIVERS attached to the installer (v 418.96)]
If you have newer version of drivers - you don't need install the toolkit, but put the cudaart files from my repo into the same folder when you have BitCrack .exe files to launch this release.

[malikusama]

It's funny that how everyone is responding while knowing that it wasn't a puzzle and the thread is approximately 4 years old.
OP was trying to extract private keys from the given addresses to find a perfect combination but it's not that easy as it seems.

[Bajula]

For the lazy:

https://bitcointalk.org/index.php?topic=1306983.240
scroll down a bit where a guy says he did the transaction, and they were right no point it going all the way to 256 so he is going to shift it
to 2^160 and up the amounts in the remaining ones. - So A) if the guy is cool with it.. why do you have to think it is something nefarious?
B) if the guy moved it (and yes it was moved like he said.. you can look and see in the blockchain. C) umm the obvious one.. anyone able to move it like that could remove it.. which means he WANTS it this way... no not technically a "puzzle", but the addresses we are working on the guy could take it all out if he wanted to... the original poster is not the guy who made the transaction but the creator is cool with this .... can we move on now?

While playing around with my bot, I found out this mysterious transaction:
[...]
The prize would be ~32 BTC

EDIT: If you find the solution feel free to leave a tip 1DPUhjHvd2K4ZkycVHEJiN6wba79j5V1u3

Started to anaylize this, but figured out its not actually a puzzle at all. Its attempt to steal of this funds right? There is no official puzzle by owner of this addresses? By what you saying i think there is no consent here.
From what i see you guys have fun, but it shouldn't be allowed at all

You are right mate, their is no statement about the address owner to have a contest in that address. Its looks like they hacking that account rather than a contest. Well they are having fun and we can see that Bitcoin address are really that strong to crack. The OP started this 4years ago and too many people try to crack the address but no one did it yet for so long.

[AndreuSmetanin]

C:\Users\User>"C:\Users\User\Desktop\Hoвaя пaпкa\cuBitCrack.exe" -r 1AVJKwzs9AskraJLGHAZPiaZcrpDr1U6AB -o keys.txt --keyspace 01900000000000000:01FFFFFFFFFFFFFFF
[2019-03-06.17:58:11] [Info] Compression: compressed
[2019-03-06.17:58:11] [Info] Starting at: 0000000000000000000000000000000000000000000000001900000000000000
[2019-03-06.17:58:11] [Info] Ending at:   0000000000000000000000000000000000000000000000001FFFFFFFFFFFFFFF
[2019-03-06.17:58:11] [Info] Generating random starting points
[2019-03-06.17:58:11] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-03-06.17:58:11] [Info] Initializing GeForce GTX 650
[2019-03-06.17:58:11] [Info] Generating 262,144 starting points (10.0MB)
[2019-03-06.17:58:11] [Info] Starting point sample: 0000000000000000000000000000000000000000000000001FAE9EFAD091BB5C (61 bit range)
[2019-03-06.17:58:11] [Info] Starting point sample: 0000000000000000000000000000000000000000000000001CC31F97E7E1FAEE (61 bit range)
[2019-03-06.17:58:11] [Info] Starting point sample: 0000000000000000000000000000000000000000000000001C07B8022082352C (61 bit range)
[2019-03-06.17:58:11] [Info] Error: invalid device symbol



Passes 3 cycles and gets an error ,who knows what's the problem?

[bill32767]

@pikachunakapika - to the suggestion regarding the format of presenting the remaining time, I still have a suggestion regarding the PRESENCE of the remaining keys, namely that it should be shown in the form DEC and not HEX.
@racminer - I will check it out on cuBitCrack or if the problem is the same. Nevertheless, even if so I think that ten minutes of incompatibility at this stage can be regarded as a tolerance threshold with a slight breath

New version shows decimal remaining time.

Please git pull as I accidentally push a commit without random seed while testing for the last version. So the last version has always the same random values.

[Error] Error detecting devices: CUDA driver version is insufficient for CUDA runtime version

Please where to place Cudart32&64 files?

The above error happens anytime I run the Bitcrack 3.0 and the latest CUDA Driver wouldn't install (always saying system restart is required). Please pikachunakapika Help with solutions...thanks

I guess you are on windows. I will setup a windows machine soon to help you (currently have none).
Zielar, can you help him please?

Regards

Yes I use windows, thanks for the development, the new update has a speed improvement on CPU (which mine's usually was 7.4MK/S).
clBitcrack works on windows (showing decimal remaining time and its a little bit slower 20MK/s while cuBitcrack at 32MK/s) but it kinda redirects & runs on GPU and not CPU, did you notice that?

[bill32767]

All work very good now. Awesome work. Executable is updated on my Git https://github.com/ZielarSRC/BitCrack/releases/tag/v0.30
You need have already installed latest update of CUDA Toolkit (10.1) [only runtimes & libraries + DRIVERS attached to the installer (v 418.96)]
If you have newer version of drivers - you don't need install the toolkit, but put the cudaart files from my repo into the same folder when you have BitCrack .exe files to launch this release.

Thanks Zielar. When I try to install new updates for drivers it keeps telling me "a system restart is required". I did the restart like a hundred times yet it keeps saying same, I am just tired. I use a GeForce 940M GPU with 2GB Dedicated RAM. Maybe you can help with a .exe file compatible with my GPU running on 398 version of CUDA tool kit.