Search content
Sort by

Showing 5 of 5 results by kpurens
Post
Topic
Board Development & Technical Discussion
Re: CudaBrainSecp - Secp256k1 Seed Recovery Tool
by
kpurens
on 20/08/2022, 10:04:50 UTC

however how to use CudaBrainSecp
[/quote]

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 your books / hashes and try recovering your desired keys.

Please look in Real Launch section about how to do it.
Post
Topic
Board Development & Technical Discussion
Re: CudaBrainSecp - Secp256k1 Seed Recovery Tool
by
kpurens
on 19/08/2022, 17:50:45 UTC
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.
Post
Topic
Board Development & Technical Discussion
Re: CudaBrainSecp - Secp256k1 Seed Recovery Tool
by
kpurens
on 19/08/2022, 04:23:17 UTC
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)?  Smiley
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.
Post
Topic
Board Development & Technical Discussion
Re: CudaBrainSecp - Secp256k1 Seed Recovery Tool
by
kpurens
on 18/08/2022, 19:28:57 UTC
Post
Topic
Board Development & Technical Discussion
Merits 41 from 8 users
Topic OP
CudaBrainSecp - Secp256k1 Seed Recovery Tool
by
kpurens
on 18/08/2022, 18:27:57 UTC
⭐ Merited by ETFbitcoin (11) ,NotATether (10) ,BlackHatCoiner (6) ,Cricktor (4) ,o_e_l_e_o (4) ,n0nce (3) ,Pmalek (2) ,DdmrDdmr (1)
Hello,

I would like to present a new project that i have been working on for the past four months.
It is a fully functional Cuda / GPU seed recovery tool - performing full Secp256k1 point multiplication directly on GPU.

Possible recovery use-cases are:
  • Brain Wallets
  • Seed Phrases
  • Mnemonic Phrases / BIP39

The main difference between existing projects (BitCrack / KeyHunt / RotorCuda / etc) is the ability to fully calculate public keys on GPU, even if the private keys are hashed.

Existing projects are still faster in scenarios where it's possible to derive public keys from each-other (Bitcoin-Puzzle / Wallet-Import-Format / etc).
However CudaBrainSecp opens up completely new possibilities that were previously unreachable (or you had to do calculations on a CPU).

The current implementation focuses mostly on brain wallet recovery and includes two operation modes.
Several optimizations are used on GPU side to allow extremely fast / efficient public key Secp256k1 generation / search.

Please see the documentation on Github repository for full information about the project:
https://github.com/kpurens/CudaBrainSecp

Please read FAQ section if you have any questions - or you can ask them in this thread.