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

Thanks for reply! 

I'd like to understand how to increase the Mkeys/s on cubitcrack/keyhunt-cuda.

I have a ASUSTeK CROSSHAIR VI HERO (AM4) motherboard with Multi-GPU SLI / CFX support :
2 x PCIe 3.0 x16 SafeSlots (CPU)

It means that i can install 2 GPUs.

Now I have one GTX 1060 3GB.
Can i add on the same motherboard another different video card like a 2080 or 3070 or 4090? 
Or do i need to install one similar like another 1060 or 1080? 

I read that 2 gpus can work in SLI mode, in cooperation mode. 
Or is it better to make them work independently with these softwares? 

The PSU is 850W so it should be enough.

What do you think?

Not a lot, but at least you could avoid wasting CPU cycles on M$hit.

Now I have a better computer to make tests (desktop Ryzen 7 1700 8 cores 16 threads + Geforce GTX 1060 3GB).
It's very silent and it doesn't heat up much (the case is a Cooler Master with 850W PSU).  

Here the stats:
Cubitcrack : 120 Mkeys/s (with peaks of 123/125 Mkeys/s)
keyspace of 500 billions keys is completed in 1,08 hour.

D:\BitCrack>cubitcrack -o out.txt --keyspace 20000000000000000:3ffffffffffffffff 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so -b 320 -t 256 -p 256 --share 25486986/74000000
[2022-10-13.14:35:01] [Info] Share 25486986 of 74000000
[2022-10-13.14:35:01] [Info] Compression: compressed
[2022-10-13.14:35:01] [Info] Starting at: 000000000000000000000000000000000000000000000002B057A6648D9C6210
[2022-10-13.14:35:01] [Info] Ending at:   000000000000000000000000000000000000000000000002B057A6D8A2242F9F
[2022-10-13.14:35:01] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2022-10-13.14:35:01] [Info] Initializing NVIDIA GeForce GTX 1060 3GB
[2022-10-13.14:35:01] [Info] Generating 20,971,520 starting points (800.0MB)
[2022-10-13.14:35:17] [Info] 10.0%
[2022-10-13.14:35:20] [Info] 20.0%
[2022-10-13.14:35:21] [Info] 30.0%
[2022-10-13.14:35:22] [Info] 40.0%
[2022-10-13.14:35:22] [Info] 50.0%
[2022-10-13.14:35:23] [Info] 60.0%
[2022-10-13.14:35:24] [Info] 70.0%
[2022-10-13.14:35:24] [Info] 80.0%
[2022-10-13.14:35:25] [Info] 90.0%
[2022-10-13.14:35:26] [Info] 100.0%
[2022-10-13.14:35:26] [Info] Done
NVIDIA GeForce G 2530 / 3071MB | 1 target 120.02 MKey/s (498,367,201,280 total) [01:07:37][2022-10-13.15:43:07] [Info] Reached end of keyspace

Keyhunt-cuda : 110 Mkeys/s (with peaks of 113 Mkeys/s)
keyspace of 500 billions keys is completed in 1,16 hour.

D:\Keyhunt>KeyHunt-Cuda.exe -g -m addresses --coin BTC --range 210717EF6CB7B4590:210717F6AE003131F -i puzzle66.bin

KeyHunt-Cuda v1.08

COMP MODE    : COMPRESSED
COIN TYPE    : BITCOIN
SEARCH MODE  : Multi Address
DEVICE       : GPU
CPU THREAD   : 0
GPU IDS      : 0
GPU GRIDSIZE : -1x128 (Auto grid size)
SSE          : YES
RKEY         : 0 Mkeys
MAX FOUND    : 65536
BTC HASH160s : puzzle66.bin
OUTPUT FILE  : Found.txt

Loaded       : 1 Bitcoin addresses

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

Start Time   : Thu Oct 13 10:20:11 2022
Global start : 210717EF6CB7B4590 (66 bit)
Global end   : 210717F6AE003131F (66 bit)
Global range : 741487CD8F (39 bit)

GPU          : GPU #0 NVIDIA GeForce GTX 1060 3GB (9x128 cores) Grid(72x128)

[01:15:51] [CPU+GPU: 110.09 Mk/s] [GPU: 110.09 Mk/s] [C: 100.512239 %] [R: 0] [T: 501,114,470,400 (39 bit)] [F: 0]

BYE

Thanks to the faster gpu i divided the puzzle 66 keyspace in 74 millions parts, each part can be tested in a little more than an hour). Below the keyspaces already checked (so it's not necessary for you to check it twice):

3D7C470AF46D1A840:3D7C471235B5975CF

3A7553158FC497D08:3A755315DA4614500

3158E4602CA7CB207:3158E4607729479FF

2F66D24710E82C359:2F66D2475B69A8B51

2E10B72ADDC0CC811:2E10B72B284249009

2CE5D68FBACFAD341:2CE5D690055129B39

2C1203CAB547C3796:2C1203CAFFC93FF8E

2B057A6648D9C6210:2B057A6D8A2242F9F

2611D6D7C835A9FE9:2611D6D812B7267E1

24D0BBA9A6B947FBF:24D0BBA9F13AC47B7

247EFB4B3458D250B:247EFB4B7EDA4ED03

239DA36E8CA682EEF:239DA36ED727FF6E7

213FA19B123A46984:213FA19B5CBBC317C

210717EF6CB7B4590:210717F6AE003131F

Now i do the tests in the windows 10 terminal.
Do you think that with linux (like Ubuntu) i could increase a lot the Mkeys/s performance?

It depends on the computational resources of the participants, with a large participation maybe in a couple of years we will solve it! 

We would have on average 1 billion posts here before solving puzzle 66 

I suggest a method to try to solve puzzle 66 together using bitcrack 0.30 (not other versions)
Use this version ONLY because I have verified that it finds the private key:
https://github.com/brichard19/BitCrack/releases/tag/0.30

Obviously, whoever resolves it will keep the prize for himself without sharing it with anyone.
The collaboration of several people will be useful to get closer to identifying the private key.

The method proposed in this post is within the reach of almost any computer (desktop or laptop) of the last ten years, even without a gpu card.
I divided the total space of the possible keys into 1,844,674,408 sessions of 20 billion keys each, each session can be completed with a 7-year-old computer like mine in about 1 hour, in a few minutes with a newer computer.

To randomly choose the session (from 1 to 1844674408) you can use: https://xoomer.virgilio.it/roberto-ricci/variabilialeatorie/esperimenti/numeriacaso2.htm

The command to use is the following:

clbitcrack -o out.txt --keyspace 20000000000000000: 3ffffffffffffffff 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so -b 96 -t 256 -p 256 --share 1000000000/1844674408

Substitute 1000000000 with the number of the session you want to verify.

You can modify the parameters -b 96 -t 256 -p 256 to speed up, with my laptop I reach 5,41 Mkeys/s with these parameters.

DON'T add the --continue option because it's not sure that it works fine (there is the risk that it skip the private key).

In a few days I should have a much more powerful PC (Ryzen7+gtx1060) so I can increase the sessions.

These are the portions of keyspace that I have already checked:

259178020/1844674408
247EFB4B3458D250B:247EFB4B7EDA4ED03

695809479/1844674408
2C1203CAB547C3796:2C1203CAFFC93FF8E

810809050/1844674408
2E10B72ADDC0CC811:2E10B72B284249009

1000000000/1844674408
3158E4602CA7CB207:3158E4607729479FF

It's like choosing a lottery ticket, with the advantage that you only pay for it with some electricity. The prize is 0.66 bitcoins !!!

I invite you to publish your tested sessions with a post, so they will not be repeated by others who want to try their hand at the challenge.

thank you @stanner.austin and @italiandigger
 

Open www.bitaddress.org
Click in "wallet details" button
Copy and paste the complete privkey: 000000000000000000000000000000000000000000000000f7051f27b09112d4
Click the "view details" button
Copy the Private Key WIF Compressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ6FxoaD5r1kYegmtbaT

Install last windows desktop Exodus wallet : https://www.exodus.com/download/
Register your wallet with a password, save the seed phrase, etc...
Select btc asset.
Open settings panel (clickin on the right 3 points)
Select : Move funds
Paste the Key WIF Compressed: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ6FxoaD5r1kYegmtbaT
Click the OK button.
Exodus reply:
Unable to move funds. There is nothing to move from 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN, bc1q8mjpx0veraf0ma4ztjvrfcr5ttr5yj9yvgkf7q, or 384DBhzwx6ch6oiRT9S8TJByq9vA6AZ2zQ

@KudilCumil
Raw data is what we call hex or binary.
maxim 256 bit supported to be as bitcoin private key.
Most wallets support WIF keys or SEED etc
For you such case you need to convert answer from hex private key to compressed WIF private key to get compressed address
For example puzzle 64 key is
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ6FxoaD5r1kYegmtbaT

PrivKey: f7051f27b09112d4
pubkey: 03100611c54dfef604163b8358f7b7fac13ce478e02cb224ae16d45526b25d9d4d
address: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN

i tried to use electrum on that found private key, but electrum doesn't recognise the format of that private key.
how we use found private key? is there any other process to change format of the private key so it can be use on electrum or any wallet?

If the wallet (like the puzzle 64) is empty you cannot sign new transactions. Zero bitcoin means zero transactions available.  
Here you can find an archive of private keys, all empty wallets : https://privatekeys.pw/keys/bitcoin/3
If you are lucky and you find a privkey with bitcoins inside you can use a wallet like Exodus (there are tutorials online how to importing a paper wallet).

hallo,..
needs explanation what is the next step after found private key?
cant open wallet address using above private key found,.. is there anything else to be done after found private key,..
thanks

I was thinking to a cheap Xeon low energy workstation:

CPU
2x Intel Xeon E5-2630L v3 - 1.80GHz / Eight Core / QPi 8 / Cache 20MB / TDP 55W P/N: SR209

Heatsink
2x heatsink

Geheugen
8GB 2Rx8 PC4-2133P Hynix P/N: HMA41GR7MFR8N-TF

HDD
300GB 15K SAS 2.5" DP, 6G, DELL P/N: 0H8DVC

FlexRom NIC Adapter
HP FlexRom 533FLB P/N: 647586-B21

PSU
HP 500W HPE 500W Power Supply Platinum, HSTNS-PD40 P/N: 723594-001, 723595-101, 754377-001

This workstation could be better than my laptop with i7 4500U 1,80 - 2,40 Ghz. Could I reach a better performance (Keys/s) with keyhunt (cpu mode)?
Xeon E5-2630L v3 has 8 cores and 16 threads.
My i7 only 2 cores 4 threads.

Hi 7isce, about bsgs I tested it with a short and fast keyspace (post #1601) but  it cannot find the puzzle 64 pubkey..
Have you done other tests to verify that the bsgs mode really works fine?

hallo,..
need an explanation about multiple addresses.
how is it work?
is it :
1. search key for the first address of the list >> found >> move to 2nd address of the list?
2. search key randomly and match to any addresses on the list?
thanks

If the operator wants to hack into your own box then why are you renting from them in the first place?

Private key searching is sensitive business, how can you be sure that there aren't a bunch of oscilloscopes hooked up to your server to measure secp256k1 timing frequency, if you have to resort to locking the operator out?

Do you try mainly random or secuential with keyspace small portions?

When accessing the server you can disable any account created by hoster and you can change root password...etc
So the only thing owner/employees can read is the hard disk/SSD without access system.
They can hack you system but you will be know that because you can't access it anymore.

It means that the server owner/employees can read the privkey too.. maybe faster than you (you cannot check it h24)

I agree with that because the data must be available any time uncle sam request it