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

Just change "-m address" to "-m addresses" 

If anyone has a fast cpu (like intel i9 or ryzen9 or near) he could help with a test on a bigger keyspace, like 1.000.000.000.000 keys, just to verify that it founds the privkey.
On my old laptop it takes around 72 hours to calculate this amount of keys, of course keyhunt can find the key sooner, on average in half the time.

The command is :

keyhunt -m rmd160 -f 64rmd160.txt -r f7051ed5cdb09800:f7051fbea255a800 -l compress -c btc -R -t 4 -q

In the 64rmd160.txt just write : 3ee4133d991f52fdf6a25c9834e0745ac74248a4

If your cpu has more than 4 threads (you can check the threads number on intel website) change the -t value.

keyhunt.exe download here: https://github.com/secp8x32/keyhunt/tree/master/x64/Release)

I added some keys at the end of the keyspace so the privkey is inside, but KeyHunt-Cuda still not finds the privkey!!! 

C:\Keyhunt>KeyHunt-Cuda.exe -t 4 --gpui 0 -m address --coin BTC --range f7051f27b08d1800:f7051f27b0913800 -i puzzle64.bin

KeyHunt-Cuda v1.08

COMP MODE    : COMPRESSED
COIN TYPE    : BITCOIN
SEARCH MODE  : Single Address
DEVICE       : CPU
CPU THREAD   : 4
SSE          : YES
RKEY         : 0 Mkeys
MAX FOUND    : 65536
BTC ADDRESS  :
OUTPUT FILE  : Found.txt


Bloom at 00000208CD62A5B0
  Version    : 2.1
  Entries    : 2
  Error      : 0.0000010000
  Bits       : 57
  Bits/Elem  : 28.755175
  Bytes      : 8 (0 MB)
  Hash funcs : 20

Start Time   : Sun Oct  2 09:45:28 2022
Global start : F7051F27B08D1800 (64 bit)
Global end   : F7051F27B0913800 (64 bit)
Global range : 42000 (19 bit)


[00:00:02] [CPU+GPU: 6.09 Mk/s] [GPU: 0.00 Mk/s] [C: 4609.090909 %] [R: 0] [T: 12,460,032 (24 bit)] [F: 0]

BYE

C:\Keyhunt>

I found the problem in your range "f7051f27b08d1800:f7051f27b09112d4" the end range which will not cover is the 64 address so you need to increase it at least by one.

In windows there are no commands. You must work with Microsoft Visual Studio (not visual code) to run it.

Mining is just one type of hashing until you get to certain condition, like start with 17 zero so any hash that start 17 zero will be accepted.
Which mean there will be too many right answer.

Hacking/cracking/searching bitcoin address require more work and power.
start with create Secp256k1 private key and public key. then hash it with sha256 and then hash it again with RIPEMD160.
then you need to get exactly like address bits(100% the same)
We are here talking about address start with 1, others type of address require one more sha256 at the begin.

So as you can see the lost mining power will be at last cut a half to do cracking wallet.

Keyhunt in pub2rmd mode doesn't work too!!! keyrange 260000 keys, test with puzzle 64.

C:\Keyhunt>keyhunt -m pub2rmd -f 64rmd160.txt -t 4 -q -r f7051f27b08d1800:f7051f27b09112d4

• Version 0.2.211012 Chocolate ┬íBeta!, developed by AlbertoBSD(Win64 build by KV)
• Mode pub2rmd
• Threads : 4
• Quiet thread output
• Opening file 64rmd160.txt
• Allocating memory for 1 elements: 0.00 MB
• Bloom filter for 1 elements.
• Loading data to the bloomfilter total: 0.00 MB
• Bloomfilter completed
• Sorting data ... done! 1 values were loaded and sorted

^C] Total 94371840 keys in 720 seconds: 131072 keys/s
C:\Keyhunt>

It should find the pubkey in 2-3 seconds.. but it doesn't find anything and it continues non stop.

Albertobsd said that it's possible to test a range : https://github.com/albertobsd/keyhunt/issues/47
But it doesn't find the pubkey...

Until now, with all my tests only, keyhunt (address and rmd160 modes) works fine.
The test with 1.000.000.000 has been always 100% fulfilled.
Today i make a test with 100.000.000.000 keys of keyrange (it should take around 7 hours), i need to be sure that the software finds the privkey with "large" keyrange, if not it's 100% a waste of time and money (electricity).

As you told me i wrote the address not rmd160: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

The keyspace is too big : 1:fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff (63f = N), the privkey is like a drop in the sea.
For puzzle 66 i think 0,66 bitcoin is not enough to cover electric bill, for the richest wallets they can try in random mode dividing the keyspace but it's a very hard, long and expensive challenge, and if it happens for lucky it's only once in a century and not for several wallets.


What are the commands on python only (windows)? too difficult?

Did you convert the rmd160 or the address of 64?
Can you show us what was written inside puzzle64.txt?

Now with the puzzle64.bin i can test keyhunt-cuda (cpu mode) with the same 260.000 keyspace used with clbitcrack, it's a very fast test, with a small keyspace it take less than 1 second :

C:\Keyhunt>KeyHunt-Cuda.exe -t 4 --gpui 0 -m address --coin BTC --range f7051f27b08d1800:f7051f27b09112d4 -i puzzle64.bin

KeyHunt-Cuda v1.08

COMP MODE    : COMPRESSED
COIN TYPE    : BITCOIN
SEARCH MODE  : Single Address
DEVICE       : CPU
CPU THREAD   : 4
SSE          : YES
RKEY         : 0 Mkeys
MAX FOUND    : 65536
BTC ADDRESS  :
OUTPUT FILE  : Found.txt


Bloom at 000001BE758F8EB0
  Version    : 2.1
  Entries    : 2
  Error      : 0.0000010000
  Bits       : 57
  Bits/Elem  : 28.755175
  Bytes      : 8 (0 MB)
  Hash funcs : 20

Start Time   : Sat Oct  1 22:44:29 2022
Global start : F7051F27B08D1800 (64 bit)
Global end   : F7051F27B09112D4 (64 bit)
Global range : 3FAD4 (18 bit)


[00:00:02] [CPU+GPU: 4.85 Mk/s] [GPU: 0.00 Mk/s] [C: 3825.571659 %] [R: 0] [T: 9,977,856 (24 bit)] [F: 0]

BYE

C:\Keyhunt>

Keyhunt-cuda DOESN'T find the privkey!!!!  

Let's try the same keyrange with the good old keyhunt (not CUDA) with the same range:

C:\Keyhunt>keyhunt -m rmd160 -f 64rmd160.txt -r f7051f27b08d1800:f7051f27b09112d4 -l compress -c btc -R -t 4 -q

• Version 0.2.211012 Chocolate ┬íBeta!, developed by AlbertoBSD(Win64 build by KV)
• Mode rmd160
• Search compress only
• Setting search for BTC adddress.
• Random mode
• Threads : 4
• Quiet thread output
• Opening file 64rmd160.txt
• Allocating memory for 1 elements: 0.00 MB
• Bloom filter for 1 elements.
• Loading data to the bloomfilter total: 0.00 MB
• Bloomfilter completed
• Sorting data ... done! 1 values were loaded and sorted

HIT!! PrivKey: f7051f27b09112d4
pubkey: 03100611c54dfef604163b8358f7b7fac13ce478e02cb224ae16d45526b25d9d4d

HIT!! PrivKey: f7051f27b09112d4
pubkey: 03100611c54dfef604163b8358f7b7fac13ce478e02cb224ae16d45526b25d9d4d

HIT!! PrivKey: f7051f27b09112d4
pubkey: 03100611c54dfef604163b8358f7b7fac13ce478e02cb224ae16d45526b25d9d4d

HIT!! PrivKey: f7051f27b09112d4
pubkey: 03100611c54dfef604163b8358f7b7fac13ce478e02cb224ae16d45526b25d9d4d
^C
C:\Keyhunt>

Keyhunt (not CUDA) finds the privkey 4 times!!!  (4 times because it's in random mode and it never finish until you stop it)


Can you please try the same test, just curious to see if keyhunt-cuda (cpu mode only and gpu) works differently with you.

I'VE DONE IT!!!!!!  
thanks again 7isce!!!!  

C:\>pip install base58
Collecting base58
  Downloading base58-2.1.1-py3-none-any.whl (5.6 kB)
Installing collected packages: base58
Successfully installed base58-2.1.1

C:\Keyhunt>python addresses_to_hash160.py puzzle64.txt puzzle64.bin
processed : 1 addresses
skipped   : 0 addresses

C:\Keyhunt>

It was not easy to understand what is the python "terminal".. it's the same terminal of windows!!!
It's enough to install only the latest version of Python for windows : https://www.python.org/downloads
No other downloads are necessary.

ah, this program can run one GPU per window. so you need to open multiple window.
like for in window1 --device 0. In window --device 1 ...etc

If you have Nvidia card then you should go with https://github.com/kanhavishva/KeyHunt-Cuda

cuBitcrack.exe

Which program you use?

hi,..
what command to use all available devices for job.
i have 8 devices on list, but when im using
--device 0,1,2,3,4,5,6,7
it running but it only show 1 device
thank you

Its a easy thing to do in python, just use pip(python package manager) to install any module you want.
type in terminal:
"pip install base58" OR "pip3 install base58" it depend on your system.

And that's it. now you can just run addresses_to_hash160.py without any error.

Thanks for your kind help!  

I did the steps but i got this error message:

PS C:\Users\me> python c:/keyhunt/addresses_to_hash160.py 64puzzle.txt 64puzzle.bin
Traceback (most recent call last):
  File "c:/keyhunt/addresses_to_hash160.py", line 4, in
    import base58
ModuleNotFoundError: No module named 'base58'

I installed in visual studio the Base58 module from https://marketplace.visualstudio.com/items?itemName=crossjs.base58&utm_source=www.vsixhub.com

I copied in c:/keyhunt the base58.cpp base58.h base58.obj toobut i got the same error.  

Can you help me to fix it?

You misunderstand, We are here talk about bitcoin puzzle address which have rules and hints.

The new address create by new wallet is 90% in range 250-bit to 256-bit which is impossible to crack it even for big bitcoin pool.

All you see in this forum is just "hypothesis" to try to recover lost bitcoin(2.5-4.5 Million lost bitcoin).
For bitcoin puzzle addresses, people found one or two in the year. For lost coins, no one did find it yet. but we are all work on it.
You can think it as hobby like play chess but in reality is playing THE hopelessness game.

The sign of bitcoin is no longer safe is when you see suddenly 2-4 million bitcoin move to new address that a red flag.

Is Bitcoin no longer safe? Have you hacked other addresses as well?

Download https://code.visualstudio.com/
open it, and then create new file addresses_to_hash160.py and copy its content from here https://github.com/secp8x32/KeyHunt-Cuda/blob/main/addresses_to_hash160.py ( OR you can download the file and copy it to your folder)

then create new file called it 64puzzle.txt and save the address "16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN"(the address not the rmd160)

lastly, type on terminal at the bottom "python addresses_to_hash160.py 64puzzle.txt 64puzzle.bin"(python OR python3 it depend on your system)
And your are have it, 64 rmd160 binary file.

About linux i will think about your suggestion, thanks.

Run the addresses_to_hash160.py on your file to convert it to binary(.bin)
How can i do it?