BitCrack - A tool for brute-forcing private keys

[Lolo54]

no coding to enter the addresses you simply create a text file and you insert the addresses so it does not need any space at the end of the addresses and one per line that addresses in 1

Code:

18GD1XxYxoiDs4zrAP9xnZhuzjCDsoNVCZ
1JgC1U7RC1fivD6BwRe7sg2UrGoF6CiQvh
1PvizbqgxRiRdtfBpbSexRwTnY7T5V286i
15yq4fvcvfDVY4ZQfjHTYekh2iPjK41Stg
1KDiHQHnEw9dtH2mXakJ8T1cyDTcYKZHh8
1A2DL4Cubj8tBKV1piCMSLvkWZZATkYV2d
1KhPpNtT2KpnYF5UAn4kN5Ly2j8Ak9h2y8
1GQiJfCpC7axrrfxNM7FCMDXvMa8oNPkgN
1EPqn5hHuYniGKreV81ipH86LgdqRzqxpS	

check that your text files are only named check and resu and not check.txt and resu.txt otherwise your command line should be
C: \ CARD \ clBitCrack.exe -b 36 -t 128 -p 800 -c -u -i check.txt.txt -o resu.txt.txt --keyspace e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b845: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991c8962b865

[1714028403]

1714028403

[1714028403]

1714028403

[1714028403]

1714028403

[iparktur]

This text file (check.txt) I create in the software "NOTEBOOK"
I write only name of a file - check - This the software "NOTEBOOK" itself does(makes) expansion "txt" and the file "check.txt" turns out

**
1HZwkjkeaoZfTSaJxDw6aKkxp45agDiEzN
15UYGXPt1ak9WVGLgjmi63gqyGg3RZUZ7N
181hHek9W6CMFcav1jSrckijGFHdrcb4T7
15cDeUTgdHCoxDscMgowX5CVMrwpNUqfWf
**

In this text file (check.txt) I write to the one address in a line without blanks

[Lolo54]

it should work if the file is placed in c: \ card

[SuffaBit]

How much addresses i can add in one time?

[Lolo54]

How much addresses i can add in one time?

no limit on the number of addresses but it is the speed of calculation which will decrease according to the number

[anu1908]

How much addresses i can add in one time?

how many lost address that you have? or did you want to hack bitcoin addresses?

imo don't put to many addresses, just try several address at once. it should give you better calculation speed and on top of that decrease the rate of error/not responding.

[SuffaBit]

How much addresses i can add in one time?

how many lost address that you have? or did you want to hack bitcoin addresses?

imo don't put to many addresses, just try several address at once. it should give you better calculation speed and on top of that decrease the rate of error/not responding.

For starters, I want to understand all the functionality of the software.
For example, I unsuccessfully tried to find a known address with a known private key.
I tried all the values from this site https://gobittest.appspot.com/PrivateKey
What am I doing wrong?

For example, how can I find this address knowing the private key?
Address: 17Au1Abhw5BiTPChTEQhHmT6Bbw2DANH5G
Privkey: 5HzBMYTh4hQ9Hiy3AAY9ucUxwav93p6v1uGWGpLdSiJH7pNLnfS

My bat file:
cuBitCrack.exe -i 0llbtc.txt -o PrivatKeys.txt -d 0 --compression both --continue coninue.txt

coninue.txt: ()
start = 16766405262B269816DC6FD9A5D05B8815982A9786EC005BE3803AE1941529FB
next = 16766405262B269816DC6FD9A5D05B8815982A9786EC005BE3803AE1941529FC
end = FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
blocks = 32
threads = 256
points = 32
compression = compressed
device = 0
elapsed = 184235
stride = 000000000000000000000000000000000000000000000000000000000000



I tried all the values from this site https://gobittest.appspot.com/PrivateKey
What am I doing wrong?

[gaz1]

how to open options?

[iparktur]

it should work if the file is placed in c: \ card

I can not run "clBitCrack.exe" on my laptop - maybe a weak graphics card - AMD Radeon HD 6520G ?

[Bl@cK]

Which is you best options for nvidia gpus like 1060 1070 1080ti?
my 1070 at -b 300 -t 256 -p 800 gives ~200 mkeys which looks like far from the best

[Lolo54]

Which is you best options for nvidia gpus like 1060 1070 1080ti?
my 1070 at -b 300 -t 256 -p 800 gives ~200 mkeys which looks like far from the best

try this for the 1080 ti it should increase the speed
-b 36 -t 512 -p 2600

[kknd]

C:\Users\admin\Desktop\2019>clBitCrack.exe -d 0 -b 130 -t 512 -p 768 --keyspace 1000000000000000:2000000000000000 -o k.txt 1AVJKwzs9AskraJLGHAZPiaZcrpDr1U6AB --continue c.txt
[2019-05-05.00:27:37] [Info] Loading ' c.txt'
[2019-05-05.00:27:37] [Info] Compression: compressed
[2019-05-05.00:27:37] [Info] Starting at: 00000000000000000000000000000000000000000000000010000073D2000000
[2019-05-05.00:27:37] [Info] Ending at:   0000000000000000000000000000000000000000000000002000000000000000
[2019-05-05.00:27:37] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-05-05.00:27:37] [Info] Compiling OpenCL kernels...
[2019-05-05.00:27:37] [Info] Initializing GeForce RTX 2080
[2019-05-05.00:27:46] [Info] Generating 51,118,080 starting points (1950.0MB)
[2019-05-05.00:27:53] [Info] 10.0%
[2019-05-05.00:27:54] [Info] 20.0%
[2019-05-05.00:27:54] [Info] 30.0%
[2019-05-05.00:27:55] [Info] 40.0%
[2019-05-05.00:27:55] [Info] 50.0%
[2019-05-05.00:27:55] [Info] 60.0%
[2019-05-05.00:27:55] [Info] 70.0%
[2019-05-05.00:27:56] [Info] 80.0%
[2019-05-05.00:27:56] [Info] 90.0%
[2019-05-05.00:27:56] [Info] 100.0%
[2019-05-05.00:27:56] [Info] Done
GeForce RTX 2080 3120/8192MB | 1 target 687.44 MKey/s (525,508,280,320 total) [00:13:56][2019-05-05.00:28:37] [Info] Checkpoint
GeForce RTX 2080 3120/8192MB | 1 target 681.57 MKey/s (567,067,279,360 total) [00:14:57][2019-05-05.00:29:38] [Info] Checkpoint

[quantummachine]

For those who want to crack the most valuable BTC addresses, I've put up a sorted list on this website:

https://bitkeys.work

The top 50 addresses are on the 1st page, next top 50 addresses on the 2nd page, and so on...

You can see the #1 address has 125,804 BTC in it.

Good luck cracking. 

[iparktur]

I tried to add the function -d 1, i.e. so that the laptop worked on the processor.
This is now it works:

***

C:\CARD\clBitCrack.exe -c -u -d 1 --keyspace 2:4 1LagHJk2FyCV2VzrNHVqg3gYG4TSYwDV4m 1cMh228HTCiwS8ZsaakH8A8wze1JR5ZsP 1NZUP3JAc9JkmbvmoTv7nVgZGtyJjirKV1 1CUNEBjYrCn2y1SdiUMohaKUi4wpP326Lb
[2019-05-15.13:41:01] [Info] Compression: both
[2019-05-15.13:41:01] [Info] Starting at: 0000000000000000000000000000000000000000000000000000000000000002
[2019-05-15.13:41:01] [Info] Ending at:   0000000000000000000000000000000000000000000000000000000000000004
[2019-05-15.13:41:01] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-05-15.13:41:01] [Info] Compiling OpenCL kernels...
[2019-05-15.13:41:07] [Info] Initializing AMD A6-3420M APU with Radeon(tm) HD Graphics
[2019-05-15.13:41:07] [Info] Generating 262,144 starting points (10.0MB)
[2019-05-15.13:41:16] [Info] 10.0%
[2019-05-15.13:41:23] [Info] 20.0%
[2019-05-15.13:41:30] [Info] 30.0%
[2019-05-15.13:41:38] [Info] 40.0%
[2019-05-15.13:41:45] [Info] 50.0%
[2019-05-15.13:41:53] [Info] 60.0%
[2019-05-15.13:42:00] [Info] 70.0%
[2019-05-15.13:42:07] [Info] 80.0%
[2019-05-15.13:42:14] [Info] 90.0%
[2019-05-15.13:42:22] [Info] 100.0%
[2019-05-15.13:42:22] [Info] Done
[2019-05-15.13:42:22] [Info] Address:     1LagHJk2FyCV2VzrNHVqg3gYG4TSYwDV4m
                             Private key: 0000000000000000000000000000000000000000000000000000000000000002
                             Compressed:  no
                             Public key:
                             C6047F9441ED7D6D3045406E95C07CD85C778E4B8CEF3CA7ABAC09B95C709EE5
                             1AE168FEA63DC339A3C58419466CEAEEF7F632653266D0E1236431A950CFE52A

[2019-05-15.13:42:22] [Info] Address:     1cMh228HTCiwS8ZsaakH8A8wze1JR5ZsP
                             Private key: 0000000000000000000000000000000000000000000000000000000000000002
                             Compressed:  yes
                             Public key:
                             02C6047F9441ED7D6D3045406E95C07CD85C778E4B8CEF3CA7ABAC09B95C709EE5

[2019-05-15.13:42:22] [Info] Address:     1NZUP3JAc9JkmbvmoTv7nVgZGtyJjirKV1
                             Private key: 0000000000000000000000000000000000000000000000000000000000000003
                             Compressed:  no
                             Public key:
                             F9308A019258C31049344F85F89D5229B531C845836F99B08601F113BCE036F9
                             388F7B0F632DE8140FE337E62A37F3566500A99934C2231B6CB9FD7584B8E672

[2019-05-15.13:42:22] [Info] Address:     1CUNEBjYrCn2y1SdiUMohaKUi4wpP326Lb
                             Private key: 0000000000000000000000000000000000000000000000000000000000000003
                             Compressed:  yes
                             Public key:
                             02F9308A019258C31049344F85F89D5229B531C845836F99B08601F113BCE036F9

[2019-05-15.13:42:22] [Info] No targets remaining
[2019-05-15.13:42:22] [Info] Reached end of keyspace


***
But the function -i and - o does not perform.
Tell me what are the optimal parameters  ( -b -t -p  ) for the processor AMD A6-3420M APU with HD Graphics AMD Radeon HD 6520G ?

[Abdolreza20]

has anyone been able to get bitcoin from this method?

[Trancefan]

Why do I get two different private keys for the same BTC address?

C:\bitcrack>test -u  -i taddress.txt
[2019-05-18.18:30:32] [Info] Compression: uncompressed
[2019-05-18.18:30:32] [Info] Starting at: 0000000000000000000000000000000000000000000000000000000000000001
[2019-05-18.18:30:32] [Info] Ending at:   FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
[2019-05-18.18:30:32] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-05-18.18:30:32] [Info] Initializing GeForce GTX 1050
[2019-05-18.18:30:32] [Info] Generating 262,144 starting points (10.0MB)
[2019-05-18.18:30:33] [Info] 10.0%
[2019-05-18.18:30:33] [Info] 20.0%
[2019-05-18.18:30:33] [Info] 30.0%
[2019-05-18.18:30:33] [Info] 40.0%
[2019-05-18.18:30:33] [Info] 50.0%
[2019-05-18.18:30:33] [Info] 60.0%
[2019-05-18.18:30:33] [Info] 70.0%
[2019-05-18.18:30:33] [Info] 80.0%
[2019-05-18.18:30:34] [Info] 90.0%
[2019-05-18.18:30:34] [Info] 100.0%
[2019-05-18.18:30:34] [Info] Done
[2019-05-18.18:30:34] [Info] Loading addresses from 'taddress.txt'
[2019-05-18.18:30:34] [Info] 1 addresses loaded (0.0MB)
[2019-05-18.18:30:34] [Info] Address:     1KWj99Jwd9LGGC2Y1c9c4cmvWvYTQrLFVc
                             Private key: 0000000000000000000000000000000000000000000000000000000220082201
                             Compressed:  no
                             Public key:
                             6A245BF6DC698504C89A20CFDED60853152B695336C28063B61C65CBD269E6B4
                             E022CF42C2BD4A708B3F5126F16A24AD8B33BA48D0423B6EFD5E6348100D8A82



C:\bitcrack>cubitcrack -u --keyspace 1e -i taddress.txt
[2019-05-18.18:16:36] [Info] Compression: uncompressed
[2019-05-18.18:16:36] [Info] Starting at: 000000000000000000000000000000000000000000000000000000000000001E
[2019-05-18.18:16:36] [Info] Ending at:   FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
[2019-05-18.18:16:36] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-05-18.18:16:36] [Info] Initializing
[2019-05-18.18:16:36] [Info] Generating 262,144 starting points (10.0MB)
[2019-05-18.18:16:36] [Info] 10.0%
[2019-05-18.18:16:36] [Info] 20.0%
[2019-05-18.18:16:36] [Info] 30.0%
[2019-05-18.18:16:36] [Info] 40.0%
[2019-05-18.18:16:36] [Info] 50.0%
[2019-05-18.18:16:37] [Info] 60.0%
[2019-05-18.18:16:37] [Info] 70.0%
[2019-05-18.18:16:37] [Info] 80.0%
[2019-05-18.18:16:37] [Info] 90.0%
[2019-05-18.18:16:37] [Info] 100.0%
[2019-05-18.18:16:37] [Info] Done
[2019-05-18.18:16:37] [Info] Loading addresses from 'taddress.txt'
[2019-05-18.18:16:37] [Info] 1 addresses loaded (0.0MB)
[2019-05-18.18:16:37] [Info] Address:     1KWj99Jwd9LGGC2Y1c9c4cmvWvYTQrLFVc
                             Private key: 000000000000000000000000000000000000000000000000000000000000001F
                             Compressed:  no
                             Public key:
                             6A245BF6DC698504C89A20CFDED60853152B695336C28063B61C65CBD269E6B4
                             E022CF42C2BD4A708B3F5126F16A24AD8B33BA48D0423B6EFD5E6348100D8A82

[almightyruler]

Why do I get two different private keys for the same BTC address?

[2019-05-18.18:30:34] [Info] Address:     1KWj99Jwd9LGGC2Y1c9c4cmvWvYTQrLFVc
                             Private key: 0000000000000000000000000000000000000000000000000000000220082201
                             Compressed:  no
                             Public key:
                             6A245BF6DC698504C89A20CFDED60853152B695336C28063B61C65CBD269E6B4
                             E022CF42C2BD4A708B3F5126F16A24AD8B33BA48D0423B6EFD5E6348100D8A82


[2019-05-18.18:16:37] [Info] Address:     1KWj99Jwd9LGGC2Y1c9c4cmvWvYTQrLFVc
                             Private key: 000000000000000000000000000000000000000000000000000000000000001F
                             Compressed:  no
                             Public key:
                             6A245BF6DC698504C89A20CFDED60853152B695336C28063B61C65CBD269E6B4
                             E022CF42C2BD4A708B3F5126F16A24AD8B33BA48D0423B6EFD5E6348100D8A82

Something strange going on there. Using Brainflayer, I see those two keys generate completely different addresses:

cb11810873f23140fba2c0d6715315fac23ebbab:u:(hex)priv:000000000000000000000000000000000000000000000000000000000000001F (1KWj99Jwd9LGGC2Y1c9c4cmvWvYTQrLFVc)
2fbd32c8dd59ee7c17e66cb6ebea7e9846c3040f:c:(hex)priv:000000000000000000000000000000000000000000000000000000000000001F (15MRQkVBF9crVPeHDjSEVEytCTVLJVGZSr)

f1c48962e20933c35cdcd4f9328fcd8ab587520b:u:(hex)priv:0000000000000000000000000000000000000000000000000000000220082201 (1P3MHqc6mWZvaaTE6WToE7mZ4gympSTYKd)
ce7355919e7ac1b58e9493700f42bc14032183b6:c:(hex)priv:0000000000000000000000000000000000000000000000000000000220082201 (1KpcN5j4Gpyd41Zy5gxtwDmmXArnWdUVdd)

(I have included both compressed and uncompressed keys for completeness.)

Note your output also provides the same public key, despite the private keys being drastically different. 1KWj99Jwd9LGGC2Y1c9c4cmvWvYTQrLFVc is the correct address associated with public key 6A245BF6DC698504C89A20CFDED60853152B695336C28063B61C65CBD269E6B4E022CF42C2BD4A7 08B3F5126F16A24AD8B33BA48D0423B6EFD5E6348100D8A82.

[schmuddelkind]

Good program, solid work.

I placed several addresses randomly in a database, specified a keyspace somewhere nearby and got a hit on every single one - 100% reliable.

Using a RTX 2080 with -b 224 -t 256 -p 1024 (compressed) gives me 820MKey/s with up to 50k addresses, and 370MKey/s at a 400k database.
Well, the MKey/s counter is bugged, it doesn't match the elapsed in the "--continue FILE", which doesn't match with the overall progress, but that's not a problem at all.

has anyone been able to get bitcoin from this method?

NOPE. And i am damn sure that i am not speaking just for myself, because the possibility is like winning the lottery 50 times in a row. Get a calculator and find out for yourself.

But it is interesting, as a hobby, and you can replace the database with whatever you like, so, maybe it's useful someday.

[TimeBits]

Good program, solid work.

I placed several addresses randomly in a database, specified a keyspace somewhere nearby and got a hit on every single one - 100% reliable.

Using a RTX 2080 with -b 224 -t 256 -p 1024 (compressed) gives me 820MKey/s with up to 50k addresses, and 370MKey/s at a 400k database.
Well, the MKey/s counter is bugged, it doesn't match the elapsed in the "--continue FILE", which doesn't match with the overall progress, but that's not a problem at all.

has anyone been able to get bitcoin from this method?

NOPE. And i am damn sure that i am not speaking just for myself, because the possibility is like winning the lottery 50 times in a row. Get a calculator and find out for yourself.

But it is interesting, as a hobby, and you can replace the database with whatever you like, so, maybe it's useful someday.

Have you tried to multi box millions of these scripts at the same time? and have them in cahoots with each other so they don`t try the same key
If you had slush pools cpu power it would not take long you could probably run a trillion at the same time and if they are storing used keys to a blockchain or data base, it will cut the time down by a shit load.

Infact cold wallet keys might be less safe than a hot wallet with a key mixer that changes the password every few seconds.

At least until they add blockPOP or blockPOH where you become the key. https://www.youtube.com/watch?v=l4x0vOAu0lQ You could also use fingerprint captcha`s.

[almightyruler]

Have you tried to multi box millions of these scripts at the same time? and have them in cahoots with each other so they don`t try the same key
If you had slush pools cpu power it would not take long you could probably run a trillion at the same time and if they are storing used keys to a blockchain or data base, it will cut the time down by a shit load.

It's been done.

https://bitcointalk.org/index.php?topic=1877935.0

https://lbc.cryptoguru.org/trophies

It has found several keys in the (very) low range of 256 bit integers, but to search the entire space is essentially impossible.