I try this version https://github.com/JeanLucPons/Kangarooon my linux subsystem (windows 10) I compile with command make success make and use ./kangaroo -gpu in.txt I got message GPU code not compiled, use -DWITHGPU when compiling. gpu meter not show [GPU 0.00 MK/s] How I can compile with gpu code? |
|
|
|
For some reason nobody updated the CUDA path so you need to edit the Makefile yourself and find the line that says CUDA = /usr/local/cuda-8.0 And replace it with The CUDA installer creates a symlink at /usr/local/cuda to whatever the actual installed CUDA version is. Can kangaroo compile with CUDA 10.1 or 11 ? I don't have cuda 8.0 |
|
|
|
Can someone tell what exact happens in bsgs and kangaroo. In layman terms and by giving some examples. If possible please explain by example of any 10 bit 20 bit key so it can be understood easily. Like if i take a 64 bit known pub key and starts my bsgs or kangaroo , then what happens inside it. I understood that it uses pubkey + n*G to calculate anoher pubkey and if value of prv key related to this new pubkey is known then prv key for the input key can be calculated. but how that helps. We still have to go through billions of keys and keypairs. How it generated those keypairs first. Secondly how it can be so fast to search for 64 bit in some seconds. Its still a large space. Confused ...
Did you read description explain on JeanLucPons Kangaroo at github already? try read for understand https://github.com/JeanLucPons/Kangaroo |
|
|
|
some error on all bitcrack all version include original may be only me error only happen on my laptop when run script batch file and bitcrack struck with scan not finish bitcrack should be open scan and close by fast but when feel while minute bitcrack will be scan and not finish and continue run non stop start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace 8b9052780c6a8800:8b9072780c6a9000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace 98b9b228d0d42800:98b9d228d0d42800 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace 9e4b41ba17b24800:9e4b61ba17b24800 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace a4f4e25630790000:a4f5025630790000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace af55ec59c335c800:af560c59c335c800 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace b19d5e1486268800:b19d7e1486268800 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace b3801ec84da91000:b3803ec84da91000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace b78a6e102a66c000:b78a8e102a66c800 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace c1e9922ae9ebc000:c1e9b22ae9ebc000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace d26e02d90c69b000:d26e22d90c69b000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace d41c489a82d93000:d41c689a82d93000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace d7034c8d37df7800:d7036c8d37df8000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace d8f5407ad846b000:d8f5607ad846b000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace e92d8770f9568800:e92da770f9569000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace ea1a4c66dcc11800:ea1a6c66dcc12000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace f99cadfb599ed000:f99ccdfb599ed000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qL.txt --keyspace fc0791825367b800:fc07b1825367c000 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace 8b9062780c5b45c0:8b9062780c79d240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace 98b9c228d0c4e5c0:98b9c228d0e36a40 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace 9e4b51ba17a305c0:9e4b51ba17c18a40 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace a4f4f2563069bdc0:a4f4f25630884240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace af55fc59c32685c0:af55fc59c3450a40 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace b19d6e14861745c0:b19d6e148635ca40 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace b3802ec84d99cdc0:b3802ec84db85240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace b78a7e102a577dc0:b78a7e102a760a40 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace c1e9a22ae9dc7dc0:c1e9a22ae9fb0240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace d26e12d90c5a6dc0:d26e12d90c78f240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace d41c589a82c9edc0:d41c589a82e87240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace d7035c8d37d035c0:d7035c8d37eec240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace d7035c8d37d035c0:d8f5507ad855f240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace d8f5507ad8376dc0:e92d9770f965d240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace ea1a5c66dcb1d5c0:ea1a5c66dcd06240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace f99cbdfb598f8dc0:f99cbdfb59ae1240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
start /wait cuBitCrack.exe --device 0 -c -u -o 16jY7qLJnxb7CHZ.txt --keyspace fc07a182535875c0:fc07a18253770240 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
|
|
|
|
Add BUILD_CUDA=1 at the end of the make call. To adjust the compute cap add COMPUTE_CAP=xy as well, where "x" is the major version and "y" is the minor version of the compute cap without any dot in the middle, eg "61", "35" and "52".
Thank you I will try again on linux |
|
|
|
|
How can setup Tesla V100 on google cloud?
and when using on google cloud is use on linux right?
how I compile bitcrack on linux ?
I try on ubuntu on windows subsystem already not success compile
I use command make already but have error on linux subsystem not have CUDA
no bitcrack program
have only program addrgen
|
|
|
|
|
some detail
both version optimize GPU
both use memory a lot for calculate it made continue search will struck when search over memory used
if run only one time not a problem
may be possible about free memory after used
I solve that problem by open new windows or new process
example batch file modify code to open new windows
or program lunch by open new windows (when finish and windows close with close memory)
|
|
|
|
I test both version https://github.com/sp-hash/Bitcrack/releases/tag/sp-mod1up speed from 11 to 50 and https://github.com/BoGnY/BitCrackup speed from 11 to 30 very good work for very fast than normal I testing fine to works generate address each 1000 million address to in.txt and testing search it is work correct found key when scan over 1000 million found key each 1000 million as generate key high bits with fast speed not answer for high bits brute force because still use a lot of time I think strategy or algorithm calculate key space target and scan that keyspace for fast found key |
|
|
|
I played around with the code and managed a 50% increase in speed on pascal cards. I forked this repository: https://github.com/BoGnY/BitCrackspeed without sp-mod: 267MHASH. after, 400MHASH sp_ link I found some problem I use batch file run group of command cubitcrack first time run fast but after that 3-5 set look like slow or struck it Reached end of keyspace very fast feel 2-3 set but faster 2-3 it not pass to next order (each set 2,000,000) |
|
|
|
# make gpu=1
cd obj &&mkdir -p SECPK1
cd obj && mkdir -p GPU
/usr/local/cuda-8.0/bin/nvcc -maxrregcount=0 --ptxas-options=-v --compile --compiler-options -fPIC -ccbin /usr/bin/g++-4.8 -m64 -O2 -I/usr/local/cuda-8.0/include -gencode=arch=compute_,code=sm_ -o obj/GPU/GPUEngine.o -c GPU/GPUEngine.cu
make: /usr/local/cuda-8.0/bin/nvcc: Command not found
make: *** [Makefile:75: obj/GPU/GPUEngine.o] Error 127 How I can compile kangaroo on windows? upper command is compile on linux right? |
|
|
|
I am not sure why debug is use time very long but release version result is better BoGnY/BitCrack debug = 1 M/s BoGnY/BitCrack release = 58 M/s brichard19/BitCrack = 11 M/s   |
|
|
|
ok, now I can compile some bitcrack  test compile with version https://github.com/brichard19/BitCrackstill can not compile have some problem same machine with version compile https://github.com/BoGnY/BitCrackresult compile success with many warning yellow line when using bitcrack this fork version program waiting to generate point long time more than brichard19 (waiting before show 10% to 100%) my result is reverse BoGnY run only 1M/s and brichard19 11M/s  |
|
|
|
 Windows can install multiple CUDA Toolkit right? CUDA Toolkit 11.2 CUDA Toolkit 10.2 |
|
|
|
You don't have OpenCL headers installed. They should be available from CUDA toolkit or AMD's OpenCL SDK.
I install CUDA Tools kits https://developer.nvidia.com/cuda-downloadsand Intel® SDK For OpenCL, still not work Where can I download correct OpenCL SDK |
|
|
|
I played around with the code and managed a 50% increase in speed on pascal cards. I forked this repository: https://github.com/BoGnY/BitCrackspeed without sp-mod: 267MHASH. after, 400MHASH  How can I compile bitcrack on windows? I use windows 10 and Visual Studio 2019 I install CUDA Toolkit 11.2 already https://developer.nvidia.com/cuda-downloadsCUDA SDK and CUDA Toolkit is same right? |
|
|
|
|
Thank you both BlackHatCoiner and NotATether
help me know more and some I miss understand
I never try use Verifying an encrypted message before
Do encrypted message and signature have cost?
need do transaction or not?
if free will be try to use it one for education.
|
|
|
|
|
I don't know about signature mush, can I ask some question for know more
my question
encrypted message not store on blockchain right
bitcoin message signature not store on bitcoin network right
I understand correct or not?
verify message is one way method?
just method proof by give message and code to check
because code generate from private key
viewer must have 3 thing
1. know IP
2. know message
3. know signature key
signature key mad from private key
What difference encrypt message and sign/verify message?
|
|
|
|
|
I try to compile BitCrack
using Visual Studio 2019
but found error
Severity Code Description Project File Line Suppression State
Error C1083 Cannot open include file: 'CL/cl.h': No such file or directory clUtil \BitCrack\clUtil\clutil.h 8
How I can fix it?
|
|
|
|
As for me, I observe the topic from time to time - you can be sure. However, I do not understand the question. I am not the creator of this challenge, but only run the main thread about it and take an active part in it. At this stage, I can only say that there is a problem with VanitySearch and BitCrack on the new NVIDIA GPU hardware (all RTX 30xx) with SM80 and SM86 architecture. If anyone has a desire and I can see the solution to the problem -> I refer to GitHub where I described as many details as possible: https://github.com/JeanLucPons/VanitySearch/issues/81#issuecomment-800473778developer program stop update multiple month, year it need some one programmer, coder who interesting on challenge help to fix and update by pull request to merge main code, or some one fork to update new one |
|
|
|
Like I said, the program will give you an estimated RAM usage. If you are using save option, that is how much storage space you will need.
Another way to look at it. If you are trying the full range of #120, you will need to perform 2^60 + 1 = 2^61. Now, take the -d you are or may want to use and subtract that from 2^61. So if you are using -d 30, you will need to save 2^31 points. If you are using -d 10, you will need to save 2^51 points. The lower your -d, the more storage space/RAM (if not using the save option) you will need.
Thank you I will try again tonight |
|
|
|
|
Show Posts
