Topic: CudaBrainSecp - Secp256k1 Seed Recovery Tool (Read 501 times)

How to run function of multiply point to scalar from this soft ?



link to fork if soft - https://github.com/XopMC/CudaBrainSecp

What exactly is your struggle?
1. If you don't know how to edit Makefile on terminal, learn how to use Nano. Check this guide, https://linuxize.com/post/how-to-use-nano-text-editor/.
2. If you don't know SM version of your GPU (called CCAP on Makefile), you could check it at https://developer.nvidia.com/cuda-gpus.
3. If you don't know location of CUDA , just run whereis cuda.

Has anyone been using this program?

Im currently using the option modebooks which combines affix(1word)+suffix(1word)

Is there a way to use it by say affix or suffix using 6+words

Does anyone know what this command does in the script?

//Maximum length of each Prime word (+1 because first byte contains word length)
#define MAX_LEN_WORD_PRIME 20

//Maximum length of each Affix word (+1 because first byte contains word length)
#define MAX_LEN_WORD_AFFIX 4

Thanks for any support and advice

Hello just noticed you paused development on this project how come?

can someone who's nice enough to compile Secp256k1 to windows.exe file?

GR,

Please bare with me as I’m not the most tech savvy.

My setup is windows 11, using windows subsystem Linux and Ubuntu 22

I’ve installed latest nvidia drivers and latest toolkit in Ubuntu

I think when I go to make it it’s not finding the path which is right in the makefile

I’ve read you have to change 2 path environment variables but I’m struggling with it

Can someone help us open, edit and save the editor please

Thanks

Has anyone got this up and running I’m having a hard time setting the right cuda paths?

You use CudaBrainSecp by simply running ./CudaBrainSecp

There are no other commands, so it's very simple - only the configuration file GPUSecp.h

If the test cases are running succesfully then you can replace the test books / hashes with your books / hashes and try recovering your desired keys.

Please look in Real Launch section about how to do it.

Thanks fxsniper, in the makefile compute was 86 which is right, I’ve tried changing the cuda path but is there anything else I should change aswell? Cheers

up to your system
mostly

/usr/lib/cuda
/usr/bin/nvcc

you need to config Makefile to correct

know by the search command
whereis cuda
whereis nvcc

the result will tell you the right location of your program


however how to use CudaBrainSecp

anyone know which is the correct path to use?

/.
/etc
/etc/nvcc.profile
/usr
/usr/bin
/usr/bin/bin2c
/usr/bin/cuda-memcheck
/usr/bin/cudafe++
/usr/bin/cuobjdump
/usr/bin/fatbinary
/usr/bin/gpu-library-advisor
/usr/bin/nvcc
/usr/bin/nvdisasm
/usr/bin/nvlink
/usr/bin/nvprune
/usr/bin/ptxas
/usr/include
/usr/include/nvvm.h
/usr/lib
/usr/lib/cuda
/usr/lib/cuda/bin
/usr/lib/cuda/include
/usr/lib/cuda/lib64
/usr/lib/cuda/nvvm
/usr/lib/cuda/version.txt
/usr/lib/nvidia-cuda-toolkit
/usr/lib/nvidia-cuda-toolkit/Sanitizer
/usr/lib/nvidia-cuda-toolkit/Sanitizer/include
/usr/lib/nvidia-cuda-toolkit/Sanitizer/include/sanitizer.h
/usr/lib/nvidia-cuda-toolkit/Sanitizer/include/sanitizer_callbacks.h
/usr/lib/nvidia-cuda-toolkit/Sanitizer/include/sanitizer_driver_cbid.h
/usr/lib/nvidia-cuda-toolkit/Sanitizer/include/sanitizer_memory.h
/usr/lib/nvidia-cuda-toolkit/Sanitizer/include/sanitizer_patching.h
/usr/lib/nvidia-cuda-toolkit/Sanitizer/include/sanitizer_result.h
/usr/lib/nvidia-cuda-toolkit/Sanitizer/include/sanitizer_runtime_cbid.h
/usr/lib/nvidia-cuda-toolkit/Sanitizer/libsanitizer-public.so
/usr/lib/nvidia-cuda-toolkit/bin
/usr/lib/nvidia-cuda-toolkit/bin/cicc
/usr/lib/nvidia-cuda-toolkit/bin/crt
/usr/lib/nvidia-cuda-toolkit/bin/crt/link.stub
/usr/lib/nvidia-cuda-toolkit/bin/crt/prelink.stub
/usr/lib/nvidia-cuda-toolkit/bin/g++
/usr/lib/nvidia-cuda-toolkit/bin/gcc
/usr/lib/nvidia-cuda-toolkit/bin/nvcc
/usr/lib/nvidia-cuda-toolkit/libdevice
/usr/lib/nvidia-cuda-toolkit/libdevice/libdevice.10.bc
/usr/share
/usr/share/doc
/usr/share/doc/nvidia-cuda-toolkit
/usr/share/doc/nvidia-cuda-toolkit/README.Debian.gz
/usr/share/doc/nvidia-cuda-toolkit/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/nvidia-cuda-toolkit
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/cuda-binaries.1.gz
/usr/lib/cuda/nvvm/libdevice
/usr/lib/nvidia-cuda-toolkit/bin/nvcc.profile
/usr/share/doc/nvidia-cuda-toolkit/changelog.Debian.gz
/usr/share/man/man1/cuda-memcheck.1.gz
/usr/share/man/man1/cuobjdump.1.gz
/usr/share/man/man1/nvcc.1.gz
/usr/share/man/man1/nvdisasm.1.gz
/usr/share/man/man1/nvprune.1.gz

@ETFbitcoin what did you change in the makefile i'm getting lots of commands not found?

As for compilation issues - i agree the compilation is not very simple and can result in various unexpected errors, mostly due to the complexity of Cuda / gcc / nvcc.

I have very limited knowledge of Cuda compilation / makefiles, however i did the best i could to describe the compilation process in Quick Setup section, and fully tested the project on two different Nvidia GPUs (Ubuntu 22.04)

I can suggest compiling the Nvidia Cuda sample project (https://github.com/NVIDIA/cuda-samples)

It is an excellent source of information about building cuda projects - and explains many different edge cases.

Yes, better instructions to setup a working build environment are highly appreciated and welcome.

Year 2022:
Satoshi's early mined coins are (nearly) impossible to guess  

Year 2122:
?  

If the private key is hashed then the GPU kernel can't simply re-use an existing public key.
Re-using a public key would be ideal, since that would allow doing one point-addition + modular inverse to obtain the next public key.
However since the private key is hashed then there is no way of knowing which is the correct point-addition (which point-addition would result in the next private key that you wish to check).
It is nearly impossible because it would be the same as guessing a 256-bit number (which is technically not impossible).

I should probably make that paragraph more clear and understandable.

On Github https://github.com/kpurens/CudaBrainSecp, you say:

In the example diagram an extra calculation Sha256 Transform is done before Secp256k1.
This calculation makes it (nearly) impossible to guess the previous or the next private key.

Why (nearly)? 

Thanks!

Fantastic work.

Development on this tool has been paused.