Pages:
Author

Topic: BitCrack - A tool for brute-forcing private keys - page 66. (Read 74373 times)

legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
Noname, COMPUTE_CAP=35 this in the makefile instead of COMPUTE_CAP=30 makes it work for me same with
your files as with yoyodapro's files, thanks for the help there mate

Oh my goodness, you just reminded me something. I keep forgetting that CUDA toolkit 11 dropped compute cap 30 so that you need to make it at least 35.

I've done a bit of CUDA development, I might be able to help out.  I have a 3070 card arriving by courier in a few days.

Can you tell me any specific error messages you are getting?   Smiley

See this message. Some function is feeding bad pointers to batchBeginAdd() and batchBeginAddWithDouble(), and these are passed to MulModP() --> copyBigInt() to the point where array access of either of copyBigInt() parameters generates athe Misaligned Access exception everyone here is getting.

It might be something in host code that's giving batchBeginAdd some pointer that's incremented by 1 and not aligned or something. I didn't get a chance to check.
jr. member
Activity: 32
Merit: 4
Ive compiled cuBitCrack.exe and clBitCrack.exe using 11.2 targets. clBitCrack confirmed working using -t 128 -b 256 -p 1024, if anyone could provide the recommended settings for these cards it would be greatly appreciated! cuBitCrack still not working for 20** and 30** series cards, hoping someone can help me figure it out  Cool

I've done a bit of CUDA development, I might be able to help out.  I have a 3070 card arriving by courier in a few days.

Can you tell me any specific error messages you are getting?   Smiley
full member
Activity: 427
Merit: 105
yes that is an edited vanitsearch used there, used with wildcards. * stronger cards and more means more chances,
or to say lesser wildcards. good luck there,

Noname, COMPUTE_CAP=35 this in the makefile instead of COMPUTE_CAP=30 makes it work for me same with
your files as with yoyodapro's files, thanks for the help there mate
,
sr. member
Activity: 661
Merit: 250
16jY7qLJnN4eqD1eArr9vRVABixvcbLyXY   KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYxZTMH89fVdXM613vVD   0x0000000000000000000000000000000000000000000000009A97E3E4A6A15391
...
16jY7qLJDnq54cdpm6RSrj1QPocvQkTeii   KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ55RfbNgUCsLt7ZBzXj   0x000000000000000000000000000000000000000000000000E8D53BD260ED66E5

may be this will help someone to solve P 64
With what tool have you generated keys ? VanitySearch ? Thanks
newbie
Activity: 26
Merit: 0
good evening to all enthusiasts.
I found many versions and modifications of this project. In addition to the original branch from the respected brichard19, I found a branch with a random search. Should I use it? the better or worse it is.
in the original branch, everything is simple (start + step + step + N step)
random points are generated in the branch. but I don’t understand after the generation, the search proceeds further by random choice or also (random point + step + step + N step)

Are you talking about the points being chosen by an RNG? I am not totally sure how long does the process of generating random numbers takes because I haven't measured it, but I'd say it could take a noticeable percentage of the time it takes to check a private key.

I still feel like pregenerating a bunch of keyspace ranges beforehand and passing those to bitcrack serially is a better approach at randomization than generating a random number 2^X times per second (X is an arbitrary number proportional to the speed of your GPU).

Anyway it would be nice if you linked that version of Bitcrack you're talking about so we can take a look at it's commit history to see what it changed.

https://github.com/brichard19/BitCrack/pull/148/commits

I will be grateful for any thoughts.
newbie
Activity: 26
Merit: 0
Thanks for the help a ton, and only changed the c_c to 35 in my case. made the solution file work as a charm,
otherwise no issues yet.
is there a verbose mode on this bitcrack as of no others have that, like show where it is now instead of continue file.
changed to 1024 now.
thanks guys

I compiled for you.
try it. if it starts, I will give the value MAKE ()

https://drive.google.com/drive/folders/1LJNcU_CGvWJONH0fJf6KEWi0qmxxW5Ro?usp=sharing

NVCCFLAGS=-std=c++11 -gencode=arch=compute_50,code=sm_50 -gencode=arch=compute_52,code=sm_52 -gencode=arch=compute_60,code=sm_60 -gencode=arch=compute_61,code=sm_61 -gencode=arch=compute_61,code=compute_61 -gencode=arch=compute_70,code=sm_70 -gencode=arch=compute_75,code=sm_75 -Xptxas="-v" -Xcompiler "${CXXFLAGS}"

I compiled for you.
try it. if it starts, I will give the value MAKE
or try changing MAKE and compile it yourself.
The CUDA version is very good.
https://github.com/djarumlights/BitCrack
full member
Activity: 427
Merit: 105
Thanks for the help a ton, and only changed the c_c to 35 in my case. made the solution file work as a charm,
otherwise no issues yet.
is there a verbose mode on this bitcrack as of no others have that, like show where it is now instead of continue file.
changed to 1024 now.
thanks guys
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
cubitcrack does - the provided PTX was compiled with an unsupported toolchain

I sometimes got that error when changing the compute cap and arch to different values from whatever the GPU's using e.g to compute_70 and sm_70 when working with a compute cap 86 GPU.

Try building the program again but with COMPUTE_CAP variable changed to 61 , that is the corresponding value for Pascal GPUs.

try -t 128 -b 256 -t 1024

I doubt that aligning the thread size to 1024 will fix an unsupported PTX binary problem since according to the error, the CUDA program cannot even be read by the GPU.

The worst a misaligned thread size (not aligned to 32 threads i.e the size of a warp) can do is degrade performance.
jr. member
Activity: 49
Merit: 7
try -t 128 -b 256 -t 1024
full member
Activity: 427
Merit: 105
i am using a 1070, 128 1000 256
jr. member
Activity: 49
Merit: 7
Error: misaligned address
Huh?

What is your hardware and -t -b -p settings?
newbie
Activity: 3
Merit: 0
 Error: misaligned address
Huh?
full member
Activity: 427
Merit: 105
cubitcrack does - the provided PTX was compiled with an unsupported toolchain

clbitcrack works fine,
newbie
Activity: 26
Merit: 0
good evening to all enthusiasts.
I found many versions and modifications of this project. In addition to the original branch from the respected brichard19, I found a branch with a random search. Should I use it? the better or worse it is.
in the original branch, everything is simple (start + step + step + N step)
random points are generated in the branch. but I don’t understand after the generation, the search proceeds further by random choice or also (random point + step + step + N step)

Are you talking about the points being chosen by an RNG? I am not totally sure how long does the process of generating random numbers takes because I haven't measured it, but I'd say it could take a noticeable percentage of the time it takes to check a private key.

I still feel like pregenerating a bunch of keyspace ranges beforehand and passing those to bitcrack serially is a better approach at randomization than generating a random number 2^X times per second (X is an arbitrary number proportional to the speed of your GPU).

Anyway it would be nice if you linked that version of Bitcrack you're talking about so we can take a look at it's commit history to see what it changed.
He is probably talking about Pica's version with random feature. Many say it had some bugs in it. I neve used it.

My version generates millions of random starting points, in the bit range you desire, and then counts sequentially, from each of those random starting points. So if you only want to look in the 8F00000000000000 range, it will generate millions of starting points all starting with 8F, and then compute sequentially. It doesn't take long to generate the points, no longer than generating Kangaroos. It's fast at finding keys in any 2^48 range, but above that, It's better to just search sequentially starting with one key. IMO. So if we took #64 puzzle, and assigned people the front 2^16 range, example 8F00, and another person 8F01, and another person 8F02, etc. all the way to 8FFF, then we only need 256 people to check the 8F range quickly. Now, once that range is done, start with another one like 80, 81, 82, 83, C0, C1, etc.
Who's in?! lol  Grin

Yes that's right.
I am currently using version (Pica's) https://github.com/neutron220/BitCrack

but based on the above, when finding (example) 30m points, I would like to have a random search within the range between the points. I think this will speed up the search.
and it also gives a chance for people with slow and old cards to play this game. as fast cards go through consistently much faster and we have no chance.
member
Activity: 261
Merit: 19
the right steps towerds the goal
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
Ive successfully compiled a release for Windows that utilizes Cuda 11.2.

https://github.com/yoyodapro/BitCrack/releases/tag/v11.2-beta

Ive compiled cuBitCrack.exe and clBitCrack.exe using 11.2 targets. clBitCrack confirmed working using -t 128 -b 256 -p 1024, if anyone could provide the recommended settings for these cards it would be greatly appreciated! cuBitCrack still not working for 20** and 30** series cards, hoping someone can help me figure it out  Cool

Awesome man, I'll send you a PM and see if I can get this thing working. Hopefully there is some kind of debugger bundled with the CUDA toolkit for Windows  Undecided I think it will make the problem more obvious than cuda-gdb.

I will update this post or just make a new one if I can find the optimal settings. Maybe someone can make bitcrack keep a list of GPUs known in advance and load optimal settings for them (preferably by means of some benchmarking program).
newbie
Activity: 26
Merit: 0
Very interesting, was looking for a tool like this.
Definitely going to give it a try. Cheesy

https://github.com/djarumlights/BitCrack (rndom only CUDA)
https://github.com/neutron220/BitCrack (random all) low speed RX480 8gb 100m/s

jr. member
Activity: 49
Merit: 7
Ive successfully compiled a release for Windows that utilizes Cuda 11.2.

https://github.com/yoyodapro/BitCrack/releases/tag/v11.2-beta

Ive compiled cuBitCrack.exe and clBitCrack.exe using 11.2 targets. clBitCrack confirmed working using -t 128 -b 256 -p 1024, if anyone could provide the recommended settings for these cards it would be greatly appreciated! cuBitCrack still not working for 20** and 30** series cards, hoping someone can help me figure it out  Cool

[2021-01-13.23:39:32] [Info] Compression: compressed
[2021-01-13.23:39:32] [Info] Starting at: 0000000000000000000000000000000000000000000000008000000000000001
[2021-01-13.23:39:32] [Info] Ending at:   000000000000000000000000000000000000000000000000FFFFFFFFFFFFFFFF
[2021-01-13.23:39:32] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000002
[2021-01-13.23:39:32] [Info] Compiling OpenCL kernels...
[2021-01-13.23:39:45] [Info] Initializing GeForce RTX 3070
[2021-01-13.23:39:49] [Info] Generating 33,554,432 starting points (1280.0MB)
[2021-01-13.23:39:51] [Info] 10.0%
[2021-01-13.23:39:52] [Info] 20.0%
[2021-01-13.23:39:52] [Info] 30.0%
[2021-01-13.23:39:52] [Info] 40.0%
[2021-01-13.23:39:52] [Info] 50.0%
[2021-01-13.23:39:52] [Info] 60.0%
[2021-01-13.23:39:52] [Info] 70.0%
[2021-01-13.23:39:52] [Info] 80.0%
[2021-01-13.23:39:53] [Info] 90.0%
[2021-01-13.23:39:53] [Info] 100.0%
[2021-01-13.23:39:53] [Info] Done
GeForce RTX 3070 3072 / 8192MB | 1 target 936.15 MKey/s (40,802,189,312 total) [00:00:38][2021-01-13.23:40:33]

[2021-01-13.23:39:32] [Info] Compression: compressed
[2021-01-13.23:39:32] [Info] Starting at: 0000000000000000000000000000000000000000000000008000000000000000
[2021-01-13.23:39:32] [Info] Ending at:   000000000000000000000000000000000000000000000000FFFFFFFFFFFFFFFF
[2021-01-13.23:39:32] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000002
[2021-01-13.23:39:32] [Info] Compiling OpenCL kernels...
[2021-01-13.23:39:32] [Info] Initializing GeForce RTX 2080
[2021-01-13.23:39:35] [Info] Generating 33,554,432 starting points (1280.0MB)
[2021-01-13.23:39:38] [Info] 10.0%
[2021-01-13.23:39:38] [Info] 20.0%
[2021-01-13.23:39:39] [Info] 30.0%
[2021-01-13.23:39:39] [Info] 40.0%
[2021-01-13.23:39:39] [Info] 50.0%
[2021-01-13.23:39:39] [Info] 60.0%
[2021-01-13.23:39:39] [Info] 70.0%
[2021-01-13.23:39:39] [Info] 80.0%
[2021-01-13.23:39:39] [Info] 90.0%
[2021-01-13.23:39:40] [Info] 100.0%
[2021-01-13.23:39:40] [Info] Done
GeForce RTX 2080 3072 / 8192MB | 1 target 710.05 MKey/s (38,050,725,888 total) [00:00:51][2021-01-13.23:40:33]
newbie
Activity: 5
Merit: 0
Very interesting, was looking for a tool like this.
Definitely going to give it a try. Cheesy
Pages:
Jump to: