Bitcoin Forum

Bitcoin => Development & Technical Discussion => Topic started by: BitCrack on June 11, 2018, 02:39:00 AM



Title: BitCrack - A tool for brute-forcing private keys
Post by: BitCrack on June 11, 2018, 02:39:00 AM
Hi all,

I've been working on a tool for brute-forcing Bitcoin private keys. The main purpose of this tool is to contribute to the effort of solving the Bitcoin puzzle transactions: https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15 (https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15)

Screenshot:
https://i.imgur.com/xH3sU1O.png


It is open-source under the MIT licence and requires no external dependencies other than the CUDA toolkit. It builds on Windows using Visual Studio 2015, and Linux using Make (you might have to edit the Makefile and point it towards your CUDA toolkit directory).

It can search for compressed/uncompressed keys or both.

The performance is good, but can likely be improved. On my hardware (GeForce GT 640) it gets 9.4 million keys per second compressed, 7.3 million uncompressed.

Note:
-Currently it is CUDA only.
-It can only search one target key at a time


Features I would like to add if there is enough interest for the project:

-Support for searching multiple target keys at one time Done
-OpenCL/AMD device support
-CPU with AVX/AVX2/SHA support
-Checkpoints/Stop and resume
-Vanity address generation


Source and Win32/Win64 binaries available here:
https://github.com/brichard19/BitCrack (https://github.com/brichard19/BitCrack)
https://github.com/brichard19/BitCrack/releases/tag/v0.0.6 (https://github.com/brichard19/BitCrack/releases/tag/v0.0.6)


Thoughts?


Thanks!


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: bitmover on June 11, 2018, 03:43:01 AM
Hi all,

I've been working on a tool for brute-forcing Bitcoin private keys.

.....

The performance is good, but can likely be improved. On my hardware (GeForce GT 640) it gets 9.4 million keys per second compressed, 7.3 million uncompressed.

....

Thoughts?


Thanks!

what I am going to say is purely theoretical, as I have never tried to brute force private keys.

I don´t think you will have any success doing this.
If you have enough hash power, you would probably make more money working as an honest node, mining.

Bitcoin protocol is secure enough. If it were brute force-able, bitcoin wouldn't be worth anything.

What i think you could do is to find a collision. If someone made an insecure private key, by just hashing some passphrase... maybe you could have some luck. I tried to do this once, but never found anything. I tried those terms like "wallet" "bitcoin". I found some addresses which used to have balances, but not anymore. But I was doing manually, like 1 address/3 minutes lol

If you could somehow at the same time check if any of those 9.4 million keys/sec have any balance in btc/bch/btg etc...

But I don't think any of that will work, and will be a waste of time and resources.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: HCP on June 11, 2018, 04:15:31 AM
what I am going to say is purely theoretical, as I have never tried to brute force private keys.

I don´t think you will have any success doing this.
I think you misunderstand what it is that the OP is attempting to achieve...


Quote
What i think you could do is to find a collision. If someone made an insecure private key, by just hashing some passphrase... maybe you could have some luck.
That is exactly what the OP is trying to achieve:

The main purpose of this tool is to contribute to the effort of solving the Bitcoin puzzle transactions: https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15 (https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15)

The Bitcoin puzzle transactions were setup as an exercise to see how tough it is bruteforce BTC... and is essentially what the LBC is attempting to cash in on (aside from other "collateral damage" of people with weak keys).

What is interesting is that the addresses in the middle range of amounts (0.056 to 0.16 BTC), which were theoretically "easier" than the addresses with the larger amounts, have not yet been "cracked"??!?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: arulbero on June 11, 2018, 07:50:10 AM
I've been working on a tool for brute-forcing Bitcoin private keys. The main purpose of this tool is to contribute to the effort of solving the Bitcoin puzzle transactions: https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15 (https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15)

Other (more or less) similar projects :

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

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


The performance is good, but can likely be improved. On my hardware (GeForce GT 640) it gets 9.4 million keys per second compressed, 7.3 million uncompressed.

Try with other software to have a comparison.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Thirdspace on June 11, 2018, 08:19:19 AM
https://bitcointalk.org/index.php?topic=1877935.0
I've been working on a tool for brute-forcing Bitcoin private keys. The main purpose of this tool is to contribute to the effort of solving the Bitcoin puzzle transactions:
that's the main group effort for this btc puzzle, however the program is closed-source (cmiiw) :(
OP is trying to do the same effort, but without collective efforts this will be redundant

The Bitcoin puzzle transactions were setup as an exercise to see how tough it is bruteforce BTC... and is essentially what the LBC is attempting to cash in on (aside from other "collateral damage" of people with weak keys).

What is interesting is that the addresses in the middle range of amounts (0.056 to 0.16 BTC), which were theoretically "easier" than the addresses with the larger amounts, have not yet been "cracked"??!?
I think the higher amounts that already spent was not 'cracked' but moved by the creator
and I just noticed 1LzhS3k3e9Ub8i2W1V8xQFdB8n2MYCHPCa has just been found recently! on May 29th
However LBC site still show the task for finding its key ???
Did someone else find it? or was LBC site just slow on updating its stats page?
Time to hit #55 of the puzzle transaction (1LzhS3k3e9Ub8i2W1V8xQFdB8n2MYCHPCa) 0 to 112 days at current speed in sub-55bit search space.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Gerci on June 11, 2018, 08:38:28 AM
Hi all,

I've been working on a tool for brute-forcing Bitcoin private keys. The main purpose of this tool is to contribute to the effort of solving the Bitcoin puzzle transactions: https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15 (https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15)

Screenshot:
https://i.imgur.com/xH3sU1O.png


It is open-source under the MIT licence and requires no external dependencies other than the CUDA toolkit. It builds on Windows using Visual Studio 2015, and Linux using Make (you might have to edit the Makefile and point it towards your CUDA toolkit directory).

It can search for compressed/uncompressed keys or both.

The performance is good, but can likely be improved. On my hardware (GeForce GT 640) it gets 9.4 million keys per second compressed, 7.3 million uncompressed.

Note:
-Currently it is CUDA only.
-It can only search one target key at a time


Features I would like to add if there is enough interest for the project:

-Support for searching multiple target keys at one time
-OpenCL/AMD device support
-CPU with AVX/AVX2/SHA support
-Checkpoints/Stop and resume
-Vanity address generation


Source and Win32/Win64 binaries available here:
https://github.com/brichard19/BitCrack (https://github.com/brichard19/BitCrack)
https://github.com/brichard19/BitCrack/releases/tag/v0.0.6 (https://github.com/brichard19/BitCrack/releases/tag/v0.0.6)


Thoughts?


Thanks!
A set of tools for Bitcoin private keys that destroy. Currently the project requires a CUDA GPU. The main purpose of this project is to contribute to solving Bitcoin puzzle transactions: A transaction with 32 addresses becomes increasingly difficult to solve.

Currently this project is only CUDA, but I would like to bring it to another architecture if there is enough interest in the project.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: arulbero on June 11, 2018, 09:01:08 AM
I just noticed 1LzhS3k3e9Ub8i2W1V8xQFdB8n2MYCHPCa has just been found recently! on May 29th
However LBC site still show the task for finding its key ???
Did someone else find it? or was LBC site just slow on updating its stats page?

LBC will search any key in sub-55 bit space, its main goal is not related to the puzzle transaction.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Thirdspace on June 11, 2018, 10:25:15 PM
LBC will search any key in sub-55 bit space, its main goal is not related to the puzzle transaction.
on stats page, they put up a notice "Time to hit #55 of the puzzle transaction (1LzhS3k3e9Ub8i2W1V8xQFdB8n2MYCHPCa)"
so I thought they're aiming for those addresses listed in that puzzle transaction
https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15

@OP can your program work collectively in a pool?
running it individually without any means of cooperative works would be somewhat useless and waste of resources


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: monkeydominicorobin on June 13, 2018, 01:12:58 AM
Hi all,

I've been working on a tool for brute-forcing Bitcoin private keys. The main purpose of this tool is to contribute to the effort of solving the Bitcoin puzzle transactions: https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15 (https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15)

Screenshot:
https://i.imgur.com/xH3sU1O.png


It is open-source under the MIT licence and requires no external dependencies other than the CUDA toolkit. It builds on Windows using Visual Studio 2015, and Linux using Make (you might have to edit the Makefile and point it towards your CUDA toolkit directory).

It can search for compressed/uncompressed keys or both.

The performance is good, but can likely be improved. On my hardware (GeForce GT 640) it gets 9.4 million keys per second compressed, 7.3 million uncompressed.

Note:
-Currently it is CUDA only.
-It can only search one target key at a time


Features I would like to add if there is enough interest for the project:

-Support for searching multiple target keys at one time
-OpenCL/AMD device support
-CPU with AVX/AVX2/SHA support
-Checkpoints/Stop and resume
-Vanity address generation


Source and Win32/Win64 binaries available here:
https://github.com/brichard19/BitCrack (https://github.com/brichard19/BitCrack)
https://github.com/brichard19/BitCrack/releases/tag/v0.0.6 (https://github.com/brichard19/BitCrack/releases/tag/v0.0.6)


Thoughts?


Thanks!

Assuming that you are successful. What is the use of cracking keys when you are not scanning for balances. This is just another BIP39 social engineering clone tool. Yes BIP39 is a cool improvement but don't use it to fool the non-programmers.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: BitCrack on June 13, 2018, 01:56:38 AM

Other (more or less) similar projects :

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

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


The performance is good, but can likely be improved. On my hardware (GeForce GT 640) it gets 9.4 million keys per second compressed, 7.3 million uncompressed.

Try with other software to have a comparison.


I'm not touching LBC, as the client source code is not available.


My machine is getting ~1 million keys per second with oclVanityGen. Not sure if it's not using my GPU or not picking optimal parameters.



Assuming that you are successful. What is the use of cracking keys when you are not scanning for balances. This is just another BIP39 social engineering clone tool. Yes BIP39 is a cool improvement but don't use it to fool the non-programmers.

I imagine people would check the balance for an address before trying to crack it. But like I said, it's main purpose is for the puzzle addresses, which have balances.

It's not social engineering anything. It's simply a brute-force tool.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Coin-1 on June 13, 2018, 03:47:06 AM
My machine is getting ~1 million keys per second with oclVanityGen. Not sure if it's not using my GPU or not picking optimal parameters.
Yes, your program might be useful for creating a "beautiful" Bitcoin-addresses using VanityGen, but only for that.


It's not social engineering anything. It's simply a brute-force tool.
Please don't waste your time and resources to brute force a Bitcoin private key. Let's calculate how much time you need to crack one Bitcoin-address on your machine.

You said that your performance is 9 million BTC-addresses per second, i.e. approximately 223 BTC-addresses per second. Thus the brute forcing will take 2160-23 = 2137 seconds! I guess it is more than septillion (1024) years!

Note that this calculating is very approximate, because actually the private key length is 2256, but I think it is enough to stop making an attempts to crack Bitcoin-addresses.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: monkeydominicorobin on June 14, 2018, 02:46:31 AM

Other (more or less) similar projects :

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

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


The performance is good, but can likely be improved. On my hardware (GeForce GT 640) it gets 9.4 million keys per second compressed, 7.3 million uncompressed.

Try with other software to have a comparison.


I'm not touching LBC, as the client source code is not available.


My machine is getting ~1 million keys per second with oclVanityGen. Not sure if it's not using my GPU or not picking optimal parameters.



Assuming that you are successful. What is the use of cracking keys when you are not scanning for balances. This is just another BIP39 social engineering clone tool. Yes BIP39 is a cool improvement but don't use it to fool the non-programmers.

I imagine people would check the balance for an address before trying to crack it. But like I said, it's main purpose is for the puzzle addresses, which have balances.

It's not social engineering anything. It's simply a brute-force tool.

Once you try to get people involved in a crusade like yours. It is social engineering. Your asking them to use your tool which is wasting computing resources. How can you brute force something that has combinations that almost rivals the number of atoms in our universe which is sha256.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: MrCrank on June 15, 2018, 06:18:48 PM
This is good idea.
Do you think is it possible?
For this need many years.. or create worldwide GPU online pool


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: BitCrack on June 16, 2018, 12:14:36 PM
Good project idea.

How to deploy this to 100 CUDA cards?

thanks

It doesn't have distributed processing right now but it's on the to-do list.

For now you'll need to run it for each GPU on each machine. It shouldn't be too difficult if you have SSH access to your machines.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: butka on June 22, 2018, 05:44:59 AM
The main purpose of this tool is to contribute to the effort of solving the Bitcoin puzzle transactions: https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15 (https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15)
For all those (like me) wondering what the heck these puzzle transactions are, here is a link to an older tread trying to explain that:

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

Now at least you would have a clue what the OP is trying to achieve.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Kakmakr on June 22, 2018, 06:08:55 AM
Is there a way that this program can be changed to query every private key to see if it contains any bitcoins, instead of targeting specific predefined private keys?

I think the probability to find a private key that contains some coins are more likely than brute forcing a specific private key?

Looking at the odds, it might be easier to just save up the electricity cost to do this over years, than having enough luck to get 1 private key that contains some coins.  ::)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: butka on June 22, 2018, 08:25:22 AM
Hi all,

I've been working on a tool for brute-forcing Bitcoin private keys. The main purpose of this tool is to contribute to the effort of solving the Bitcoin puzzle transactions: https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15 (https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15)

Does your tool include the increasing bits of entropy with each consecutive address? This pattern was indicated before:

I see a pattern but I do not think it will help much.

My conjecture is that the sequence number (the BTC amount) simply states the number of random bits in the private key.

Check it out:

The 0.001 BTC output used a 1 bit key (already claimed obviously)

The 0.002 BTC output used a 2 bit key

The 0.003 BTC output used a 3 bit key

etc...

The 0.019 BTC output used a 19 bit key

So I would claim the next unclaimed output uses a 51 bit key.

Interesting.

Here's a thought.  What if that is the ONLY pattern.

Consider the possibility that the person that created this "puzzle" has done so as a form of "canary in the coal mine".

The idea would be to generate a bitcoin address completely randomly, but which only uses X bits of entropy.  Then progressively store large values of bitcoins for each increase in entropy to provide an incentive for someone to try and access it.

So:
  • The only possible address with 1 bit of entropy is the address associated with the private key having binary value 1
  • There are 3 possible addresses with 2 bits of entropy.  The addresses associated with the private keys having each of the following binary values (01, 10, 11), and one of them was chosen at random (11)
  • There are 7 possible addresses with 3 bits of entropy, The addresses associated with the private keys having each of the following values (001, 010, 011, 100, 101, 110,  and 111), and one of them was chosen at random (111)
  • There are 15 possible addresses with 4 bits of entropy, and one of them was chosen at random (1000)
  • There are 31 possible addresses with 5 bits of entropy, and one of them was chosen at random (10101)
  • There are 63 possible addresses with 6 bits of entropy, and one of them was chosen at random (110001)
  • There are 127 possible addresses with 7 bits of entropy, and one of them was chosen at random (1001100)
  • and so on

By looking at which addresses have been "claimed", the creator of the "puzzle" can get a feel for the current security of version 1 bitcoin addresses.

So, if there are 50 addresses that have been "claimed", perhaps they'll avoid using any bitcoin address that has a private key with less than 51 binary digits for storing large amounts (actually, I'd probably go a bit higher than that just to be safe), and would have a feel for how secure addresses with 160 or more bits of entropy would be.

If that is what's going on here, then there may not be a "formula" or "pattern" that can be used.  To get the 51st address, you'd just have to brute force try all addresses associated with private keys between 1125899906842624 and 2251799813685248 (which is only about 1.126 X 1015 addresses).


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: holy_ship on September 13, 2018, 05:28:55 AM
Hey! Still no benchmarks on good cards?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: giftseller8x on September 14, 2018, 10:30:56 AM
Hey! Still no benchmarks on good cards?
I have try with my 1060


Code:
D:\C\BitCrack>BitCrack64 1FshYsUh3mqgsG29XpZ23eLjWV8Ur3VwH
[2018-09-14.17:24:58] [Info] Compression: compressed
[2018-09-14.17:24:58] [Info] Starting at: 0000000000000000000000000000000000000000000000000000000000000001
[2018-09-14.17:24:58] [Info] Initializing GeForce GTX 1060 3GB
[2018-09-14.17:25:07] [Info] Generating 1,179,648 starting points (45.0MB)
[2018-09-14.17:25:08] [Info] 10.0%
[2018-09-14.17:25:08] [Info] 20.0%
[2018-09-14.17:25:08] [Info] 30.0%
[2018-09-14.17:25:08] [Info] 40.0%
[2018-09-14.17:25:09] [Info] 50.0%
[2018-09-14.17:25:09] [Info] 60.0%
[2018-09-14.17:25:09] [Info] 70.0%
[2018-09-14.17:25:09] [Info] 80.0%
[2018-09-14.17:25:10] [Info] 90.0%
[2018-09-14.17:25:10] [Info] 100.0%
[2018-09-14.17:25:10] [Info] Done
GeForce GTX 1060 381/3072MB | 1 target 60.61 MKey/s (1,875,640,320 total) [00:00:29]^C
D:\C\BitCrack>BitCrack64 -c -u 1FshYsUh3mqgsG29XpZ23eLjWV8Ur3VwH
[2018-09-14.17:25:48] [Info] Compression: both
[2018-09-14.17:25:48] [Info] Starting at: 0000000000000000000000000000000000000000000000000000000000000001
[2018-09-14.17:25:48] [Info] Initializing GeForce GTX 1060 3GB
[2018-09-14.17:25:48] [Info] Generating 1,179,648 starting points (45.0MB)
[2018-09-14.17:25:48] [Info] 10.0%
[2018-09-14.17:25:48] [Info] 20.0%
[2018-09-14.17:25:49] [Info] 30.0%
[2018-09-14.17:25:49] [Info] 40.0%
[2018-09-14.17:25:49] [Info] 50.0%
[2018-09-14.17:25:49] [Info] 60.0%
[2018-09-14.17:25:50] [Info] 70.0%
[2018-09-14.17:25:50] [Info] 80.0%
[2018-09-14.17:25:50] [Info] 90.0%
[2018-09-14.17:25:50] [Info] 100.0%
[2018-09-14.17:25:50] [Info] Done
GeForce GTX 1060 381/3072MB | 1 target 46.93 MKey/s (685,375,488 total) [00:00:12]

This result give the same speed of Vanitigen, but it not support multi GPU at now.

https://prnt.sc/kubfus (https://prnt.sc/kubfus)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: giftseller8x on September 16, 2018, 03:45:08 PM
Have a multi GPU version running 170mKeys/s on RX570 or 150mKeys/s on GTX 1060, a rig with 6 runs just above a billion/sec.

Windows 10
Your speed is double compare with mine.1060 3G win 7, 16G ram, core i5 ivy.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: holy_ship on September 17, 2018, 04:52:06 AM
I have try with my 1060
This result give the same speed of Vanitigen, but it not support multi GPU at now.

Default settings are not optimal. Play with -p -b -t settings
And it doesn't check uncompressed until you say so.

For gtx1070 I got 80MK instead of 40MK with vanitygen.
But I dig for collisions also, not only 32BTC bounty.

While searching for 32BTC bounty alone I get about 240MK on gtx1070 and that's impressive!



Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: nc50lc on September 17, 2018, 05:29:51 AM
Have a multi GPU version running 170mKeys/s on RX570 or 150mKeys/s on GTX 1060, a rig with 6 runs just above a billion/sec.
Your speed is double compare with mine.1060 3G win 7, 16G ram, core i5 ivy.
He's using his own fork/version. Question is: if it is free, open-source or real, he didn't shared the link.

-snip-
Is this the version that keychainX is talking about: Faster and Autonomous Large Bitcoin Collider upgrade (https://bitcointalk.org/index.php?topic=3102823.0)?
'Coz I'm seeing the same users from that thread.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: keychainX on September 17, 2018, 07:34:06 AM
Have a multi GPU version running 170mKeys/s on RX570 or 150mKeys/s on GTX 1060, a rig with 6 runs just above a billion/sec.
Your speed is double compare with mine.1060 3G win 7, 16G ram, core i5 ivy.
[/quote]
He's using his own fork/version. Question is: if it is free, open-source or real, he didn't shared the link.

-snip-
Is this the version that keychainX is talking about: Faster and Autonomous Large Bitcoin Collider upgrade (https://bitcointalk.org/index.php?topic=3102823.0)?
'Coz I'm seeing the same users from that thread.
[/quote]

No, I have a custom made version, you need to optimize the OpenCL drivers in order to get into that speed.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: vel12 on September 20, 2018, 09:20:53 AM
waiting version for AMD  ::)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: DevilOper on October 03, 2018, 10:26:55 AM
you need to optimize the OpenCL drivers in order to get into that speed.

What do you mean by 'optimize the OpenCL drivers'? What drivers?
(Once upon a time I found the SDK 3.0 is an insane registry eater while previous version, don't remember exactly was it 2.9 or 3.0beta, was faster but buggy.)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: successhalf on October 06, 2018, 12:57:53 PM
help me put a command
input address.txt
output result.txt

BitCrack64.exe  input address output result.txt


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: vel12 on October 06, 2018, 01:26:13 PM
help me put a command
input address.txt
output result.txt

BitCrack64.exe  input address output result.txt
https://github.com/brichard19/BitCrack     Look at the bottom of the page.
https://image.ibb.co/mbTGye/AAA.png


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: successhalf on October 06, 2018, 01:35:27 PM
help me put a command
input address.txt
output result.txt

BitCrack64.exe  input address output result.txt
https://image.ibb.co/mbTGye/AAA.png
does not work with that command
BitCrack64.exe -i address.txt -o result.txt  ???
help type command here




Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: The Healer on October 11, 2018, 02:45:16 PM
I would like to add more than one BTC address as TARGET.
How do I do that?

I know it's one address per line, but in the same BAT file we use to run BitCrack64.exe -b 32 -t 256 -p 16    ?
Or in another txt file?

Thank you for any help  :)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: ianek on October 11, 2018, 04:01:55 PM
I would like to add more than one BTC address as TARGET.
How do I do that?

I know it's one address per line, but in the same BAT file we use to run BitCrack64.exe -b 32 -t 256 -p 16    ?
Or in another txt file?

Thank you for any help  :)

bitcrack64 -b 32 -t 256 -p 16 -c -i addr.txt -o out.txt -s 0000000000000000000000000000000000000000000000000000000000000001 -r 100000000000


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: The Healer on October 11, 2018, 04:59:10 PM
Thank you for the answer.

 1. I have to run the .bat file with something like this:

     bitcrack64 -b 32 -t 256 -p 16 -c -i addr.txt -o out.txt -s
     0000000000000000000000000000000000000000000000000000000000000001 -r 100000000000

 2. But I need 1 file with this name "addr.txt" and another with "out.txt" in the same folder, right?

 3. In the file "addr.txt" I need BTC addresses (1 per line), correct?

 4. what do I need in the "out.txt" file?

 :)




Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: ianek on October 11, 2018, 10:39:01 PM
Thank you for the answer.
 1. I have to run the .bat file with something like this:
     bitcrack64 -b 32 -t 256 -p 16 -c -i addr.txt -o out.txt -s
     0000000000000000000000000000000000000000000000000000000000000001 -r 100000000000
 2. But I need 1 file with this name "addr.txt" and another with "out.txt" in the same folder, right?
 3. In the file "addr.txt" I need BTC addresses (1 per line), correct?
 4. what do I need in the "out.txt" file?
 :)

1. Yes, create .bat with this line
1.1. switch -s address from which to start checking;
       switch -r is the number of addresses to check starting from the -s parameter.
2. In the addr.txt file you insert the addresses you want to find, and the program will create the out.txt file when it finds a match.
3. Yes.
4. The out.txt file will be created by the program when a match is found.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: The Healer on October 12, 2018, 10:56:45 AM
Again, thank you for your help.  :)

I can do it with 1 address like this:
BitCrack.exe -s 6BBF8CCF80F8E184D1D300EF2CE45F7260E56766519C977831678F0000000000 1FshYsUh3mqgsG29XpZ23eLjWV8Ur3VwH

But I can't make it work with several addresses in the txt file.

When I run the bat file:
bitcrack64 -b 32 -t 256 -p 16 -c -i addr.txt -o out.txt -s 0000000000000000000000000000000000000000000000000000000000000001 -r 100000000000

it opens and almost instantly closes. I barely can see what does it say.

But I recorded the screen, and it gives an error: invalid address , because it assumes the target as "-i" and not the address it self on each line.

What do I need to change? Looks like some syntax mistake.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: ianek on October 12, 2018, 01:53:18 PM
Again, thank you for your help.  :)

I can do it with 1 address like this:
BitCrack.exe -s 6BBF8CCF80F8E184D1D300EF2CE45F7260E56766519C977831678F0000000000 1FshYsUh3mqgsG29XpZ23eLjWV8Ur3VwH

But I can't make it work with several addresses in the txt file.

When I run the bat file:
bitcrack64 -b 32 -t 256 -p 16 -c -i addr.txt -o out.txt -s 0000000000000000000000000000000000000000000000000000000000000001 -r 100000000000

it opens and almost instantly closes. I barely can see what does it say.

But I recorded the screen, and it gives an error: invalid address , because it assumes the target as "-i" and not the address it self on each line.

What do I need to change? Looks like some syntax mistake.

What version of bitcrack do you have?
Try to make a list of addresses in the program 'notepad'. For each line at the address without spaces, periods, commas, etc.
There was also a problem with reading the address list, the re-creation in the 'notepad' helped.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: The Healer on October 13, 2018, 01:10:50 PM
That solved it!! It was the version, I had a very old version.

I installed this release https://github.com/brichard19/BitCrack/releases/tag/0.21

Thank you for the help!


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: by rallier on October 15, 2018, 09:24:01 AM
another crack tool. Keep up work. Bitcoin will be more safe with the hack :)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: milewilda on October 15, 2018, 09:06:19 PM
another crack tool. Keep up work. Bitcoin will be more safe with the hack :)
Im surprised that these kind of tools do exist nowadays and been actively lurking on here.Just wondering on how many they had bruteforced already?  ;D


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on October 16, 2018, 08:54:32 AM
another crack tool. Keep up work. Bitcoin will be more safe with the hack :)
Im surprised that these kind of tools do exist nowadays and been actively lurking on here.Just wondering on how many they had bruteforced already?  ;D

People have probably been trying to crack keys from day 1. It's impractical to cover the entire search space - that's why crypto works - but if you have some (very) strong hints, it is possible to brute force only a small range and find some hits. As an example, there are several private keys used in the blockchain, hidden in plain sight, sitting at the very bottom of the private key range. The puzzle transactions referred to earlier in this thread also have private keys over a very limited (and known) range, so the chances of cracking them are much better.

For a key that's generated truly randomly the chances of discovering it via brute force are essentially zero. You'd probably be better off trying to mine a new Bitcoin block.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: arulbero on October 20, 2018, 04:29:41 PM
I don't have .exe file

Where can I find it?

https://github.com/brichard19/BitCrack/releases


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: fucilator_3000 on October 20, 2018, 04:32:32 PM
I don't have .exe file

Where can I find it?

https://github.com/brichard19/BitCrack/releases

Thank you :D


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: vel12 on October 20, 2018, 06:59:32 PM
I don't have .exe file

Where can I find it?
Choose,their 3
https://image.ibb.co/kX94ff/444.png


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: fucilator_3000 on October 20, 2018, 07:22:17 PM


Doesn't work :(


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: vel12 on October 21, 2018, 09:25:47 AM
Read the topic, here find an example batch file(The program doesn't know what you want from it.).So far the program works only on NVIDIA cards.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: stalker00075 on October 22, 2018, 03:06:16 PM
is it possible to brute

example

BitCrack64.exe -u -s 0000000000000000000000000000000000000000000000000000000000000000 1KDv
or
BitCrack64.exe -u -s 0000000000000000000000000000000000000000000000000000000000000000 1KDvs
or
BitCrack64.exe -u -s 0000000000000000000000000000000000000000000000000000000000000000 1KDvsa
.....
find
1KDv and save


similar to Vanitygen but there is random

and here with meaning
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000001
0000000000000000000000000000000000000000000000000000000000000002


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on October 22, 2018, 05:51:37 PM
is it possible to brute

example

BitCrack64.exe -u -s 0000000000000000000000000000000000000000000000000000000000000000 1KDv
or
BitCrack64.exe -u -s 0000000000000000000000000000000000000000000000000000000000000000 1KDvs
or
BitCrack64.exe -u -s 0000000000000000000000000000000000000000000000000000000000000000 1KDvsa
.....
find
1KDv and save

Wondering what the point of this feature would be? A partial match would have hundreds of bits that don't match any address in use. The key would still be impossible to crack.

If you were using it to generate your own address, by using a sequence in a small search space you would open yourself to easy cracking of the private key. You really need a vanity address (or any address!) to be generated from a 100% random key.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Remember remember the 5th of November on October 22, 2018, 08:28:27 PM
Also, it's actually wasteful checking for only one address, one should maintain a list of bitcoin addresses. Also, for a speed up, one can also use two loops, one for bitcoin addresses, whose pubkeys are unknown, and those who are known. This way you avoid doing unnecessary sha256+ripemd hashing giving some speed up.

Even compressed Bitcoin addresses, whose pubkeys are known can be uncompressed. Another thing to add, a user on the crypto stackexchange says he managed to create a more efficient OpenCL kernel just for this https://crypto.stackexchange.com/questions/54622/optimized-modular-multiplicative-inverse-for-bitcoin-secp256k1


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on October 23, 2018, 06:44:37 AM
Also, it's actually wasteful checking for only one address, one should maintain a list of bitcoin addresses. Also, for a speed up, one can also use two loops, one for bitcoin addresses, whose pubkeys are unknown, and those who are known. This way you avoid doing unnecessary sha256+ripemd hashing giving some speed up.

Brainflayer uses a Bloom filter so it can check hundreds of millions of RIPEMD160 addresses simultaneously, although these days with a lot (10%+) of false positives. I don't know whether it would be possible to shoehorn a Bloom filter implementation (including the filter data) into a GPU application. The Brainflayer implementation addresses 2^32 bits (512MB of RAM), but the filter is badly saturated by the large number of Bitcoin addresses, so you would need to use a lot more RAM for the filter data.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Remember remember the 5th of November on October 23, 2018, 04:46:04 PM
Also, it's actually wasteful checking for only one address, one should maintain a list of bitcoin addresses. Also, for a speed up, one can also use two loops, one for bitcoin addresses, whose pubkeys are unknown, and those who are known. This way you avoid doing unnecessary sha256+ripemd hashing giving some speed up.

Brainflayer uses a Bloom filter so it can check hundreds of millions of RIPEMD160 addresses simultaneously, although these days with a lot (10%+) of false positives. I don't know whether it would be possible to shoehorn a Bloom filter implementation (including the filter data) into a GPU application. The Brainflayer implementation addresses 2^32 bits (512MB of RAM), but the filter is badly saturated by the large number of Bitcoin addresses, so you would need to use a lot more RAM for the filter data.
Sorry I am not familiar with bloom filters.

Bitcoin addresses are indeed a lot, but not many of them are of interest. It's pointless to add a Bitcoin address with a balance of <0.01 or <0.10 to the list. Keep the list more or less small, I mean the first 200k blocks have enough coins I guess, if they aren't spent.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Stryfe on October 23, 2018, 05:31:25 PM
not to sound to ignorant - but I gotta ask, is this just to crack btc addresses with the intent of stealing the btc ?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Remember remember the 5th of November on October 23, 2018, 09:57:05 PM
not to sound to ignorant - but I gotta ask, is this just to crack btc addresses with the intent of stealing the btc ?
Not sure, I mean it's a fun pet project, but in reality it's actually infeasible. So nobody here can actually steal any bitcoins.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on October 23, 2018, 11:30:03 PM
Also, it's actually wasteful checking for only one address, one should maintain a list of bitcoin addresses. Also, for a speed up, one can also use two loops, one for bitcoin addresses, whose pubkeys are unknown, and those who are known. This way you avoid doing unnecessary sha256+ripemd hashing giving some speed up.

Brainflayer uses a Bloom filter so it can check hundreds of millions of RIPEMD160 addresses simultaneously, although these days with a lot (10%+) of false positives. I don't know whether it would be possible to shoehorn a Bloom filter implementation (including the filter data) into a GPU application. The Brainflayer implementation addresses 2^32 bits (512MB of RAM), but the filter is badly saturated by the large number of Bitcoin addresses, so you would need to use a lot more RAM for the filter data.
Sorry I am not familiar with bloom filters.

Bitcoin addresses are indeed a lot, but not many of them are of interest. It's pointless to add a Bitcoin address with a balance of <0.01 or <0.10 to the list. Keep the list more or less small, I mean the first 200k blocks have enough coins I guess, if they aren't spent.

https://en.wikipedia.org/wiki/Bloom_filter

Basically it's a compressed data structure that lets you do an efficient lookup to check whether a key (in this case, a used Bitcoin address) exists in a set. The return is either:

- This key is absolutely NOT in the set
- This key may be in the set (possible false positive)

The tradeoff is between memory usage and false positive rate. When Brainflayer was released, a Bloom filter with 2^32 bits was sufficient to keep the number of false positives low, but now that the number of addresses has increased significantly the false positive rate is too high.

You do make a good point that you would only need to try to crack addresses which are funded. I'm doing brainwallet cracking for interest, not criminal intent, so I want to cover the entire address space; even obscure wallets with zero balance that were last used years ago.

Random bruteforce cracking is unlikely to ever work anyway, so this discussion is largely academic. :)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on October 23, 2018, 11:46:56 PM
not to sound to ignorant - but I gotta ask, is this just to crack btc addresses with the intent of stealing the btc ?

Here's a reply I posted earlier in this thread:

People have probably been trying to crack keys from day 1. It's impractical to cover the entire search space - that's why crypto works - but if you have some (very) strong hints, it is possible to brute force only a small range and find some hits. As an example, there are several private keys used in the blockchain, hidden in plain sight, sitting at the very bottom of the private key range. The puzzle transactions referred to earlier in this thread also have private keys over a very limited (and known) range, so the chances of cracking them are much better.

For a key that's generated truly randomly the chances of discovering it via brute force are essentially zero. You'd probably be better off trying to mine a new Bitcoin block.

Here's a sample of some real private keys, which have had funds sent to them at some point. Since the set starts at '1' they'll be found by brute force pretty much instantly... but that's most likely the point. A randomly generated private key would be impossible to crack.

0000000000000000000000000000000000000000000000000000000000000001
0000000000000000000000000000000000000000000000000000000000000002
0000000000000000000000000000000000000000000000000000000000000003
0000000000000000000000000000000000000000000000000000000000000004
0000000000000000000000000000000000000000000000000000000000000005
0000000000000000000000000000000000000000000000000000000000000006
0000000000000000000000000000000000000000000000000000000000000007
0000000000000000000000000000000000000000000000000000000000000008
0000000000000000000000000000000000000000000000000000000000000009
000000000000000000000000000000000000000000000000000000000000000a
000000000000000000000000000000000000000000000000000000000000000b
000000000000000000000000000000000000000000000000000000000000000c
000000000000000000000000000000000000000000000000000000000000000d
000000000000000000000000000000000000000000000000000000000000000e
000000000000000000000000000000000000000000000000000000000000000f
0000000000000000000000000000000000000000000000000000000000000010
0000000000000000000000000000000000000000000000000000000000000011
0000000000000000000000000000000000000000000000000000000000000012
0000000000000000000000000000000000000000000000000000000000000013
0000000000000000000000000000000000000000000000000000000000000015
0000000000000000000000000000000000000000000000000000000000000016
0000000000000000000000000000000000000000000000000000000000000017
0000000000000000000000000000000000000000000000000000000000000018
0000000000000000000000000000000000000000000000000000000000000019
000000000000000000000000000000000000000000000000000000000000001a
000000000000000000000000000000000000000000000000000000000000001b
000000000000000000000000000000000000000000000000000000000000001c
000000000000000000000000000000000000000000000000000000000000001e
000000000000000000000000000000000000000000000000000000000000001f


I know this looks like simple sequential counting, but if you look carefully you'll see one number missing. All of these private keys are valid.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Stryfe on October 24, 2018, 10:46:11 AM
well apparently it is against some moderators rule to question this apparent attempt to hack private keys - so carry on! seriously hope this never succeeds.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: bob123 on October 24, 2018, 11:59:46 AM
well apparently it is against some moderators rule to question this apparent attempt to hack private keys - so carry on! seriously hope this never succeeds.


This tool is to bruteforce private keys.
Bruteforcing means to try out every possible combination. You can't forbid someone to try out each number (since private keys are basically just big numbers).

The keyspace is big enough for a randomly generated private key to be never found by such a bruteforce tool.

This is not hacking in any way. It is just 'trying out numbers' (and it will not succeed in finding private keys generated by proper wallets/clients/etc..).


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Stryfe on October 24, 2018, 12:17:25 PM
well apparently it is against some moderators rule to question this apparent attempt to hack private keys - so carry on! seriously hope this never succeeds.


This tool is to bruteforce private keys.
Bruteforcing means to try out every possible combination. You can't forbid someone to try out each number (since private keys are basically just big numbers).

The keyspace is big enough for a randomly generated private key to be never found by such a bruteforce tool.

This is not hacking in any way. It is just 'trying out numbers' (and it will not succeed in finding private keys generated by proper wallets/clients/etc..).

Oh, I get that it wont succeed, however, several of the posts here are specifically about targeting specific wallets with high enough balances.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Remember remember the 5th of November on October 24, 2018, 03:36:09 PM
well apparently it is against some moderators rule to question this apparent attempt to hack private keys - so carry on! seriously hope this never succeeds.


This tool is to bruteforce private keys.
Bruteforcing means to try out every possible combination. You can't forbid someone to try out each number (since private keys are basically just big numbers).

The keyspace is big enough for a randomly generated private key to be never found by such a bruteforce tool.

This is not hacking in any way. It is just 'trying out numbers' (and it will not succeed in finding private keys generated by proper wallets/clients/etc..).

Oh, I get that it wont succeed, however, several of the posts here are specifically about targeting specific wallets with high enough balances.
Which is even worse!!! Do you know what the likelyhood is of getting 1 right out of 256 bit(well, slightly less than that) keys is?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Stryfe on October 24, 2018, 03:38:26 PM
well apparently it is against some moderators rule to question this apparent attempt to hack private keys - so carry on! seriously hope this never succeeds.


This tool is to bruteforce private keys.
Bruteforcing means to try out every possible combination. You can't forbid someone to try out each number (since private keys are basically just big numbers).

The keyspace is big enough for a randomly generated private key to be never found by such a bruteforce tool.

This is not hacking in any way. It is just 'trying out numbers' (and it will not succeed in finding private keys generated by proper wallets/clients/etc..).

Oh, I get that it wont succeed, however, several of the posts here are specifically about targeting specific wallets with high enough balances.
Which is even worse!!! Do you know what the likelyhood is of getting 1 right out of 256 bit(well, slightly less than that) keys is?

next to zero - still disturbing that seems to be the goal here  for some - I get for others it is just the puzzle part of it. but when I see people asking how to target specific high value keys...


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: TrumenPack on November 05, 2018, 03:31:09 PM
Greetings to all !!! I had a problem with the launch ((when I ran the first time through the BitCrack.exe console I got an error:

Code:
---------------------------
BitCrack.exe - System Error
---------------------------
The code could not be continued because the system did not detect the cudart32_80.dll. To resolve this issue, try reinstalling the program.
---------------------------
OK
---------------------------


As I understand it, the error was related to the video card. I updated my nvideo

 
I have Windows 10 / 32bit / I use NVIDEO GeForce GT 650M

The error did not disappear !!

Something very much confused! How to fix it?
Be kindly help please with the launch!


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: bob123 on November 05, 2018, 03:53:26 PM
Greetings to all !!! I had a problem with the launch ((when I ran the first time through the BitCrack.exe console I got an error:

Code:
---------------------------
BitCrack.exe - System Error
---------------------------
The code could not be continued because the system did not detect the cudart32_80.dll. To resolve this issue, try reinstalling the program.
---------------------------
OK
---------------------------


As I understand it, the error was related to the video card. I updated my nvideo

 
I have Windows 10 / 32bit / I use NVIDEO GeForce GT 650M

The error did not disappear !!

Something very much confused! How to fix it?
Be kindly help please with the launch!


cudart32_80.dll is part of the CUDA toolkit. Do you have it installed?

If not, get it from nvidia.com (https://developer.nvidia.com/cuda-downloads?target_os=Windows (https://developer.nvidia.com/cuda-downloads?target_os=Windows))


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: TrumenPack on November 06, 2018, 06:57:35 PM
Greetings to All! If there are people who can help me? My task is to use the “BitCrack” program to find one private key from 10,000,000 Bitcoin Addresses. This is my scientific work. I created a theme and described:
https://bitcointalk.org/index.php?topic=5060735.msg47651430#msg47651430 (https://bitcointalk.org/index.php?topic=5060735.msg47651430#msg47651430)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: bob123 on November 07, 2018, 08:25:43 AM
Greetings to All! If there are people who can help me? My task is to use the “BitCrack” program to find one private key from 10,000,000 Bitcoin Addresses. This is my scientific work. I created a theme and described:
https://bitcointalk.org/index.php?topic=5060735.msg47651430#msg47651430 (https://bitcointalk.org/index.php?topic=5060735.msg47651430#msg47651430)


Did you even read this thread ?

What you are trying is NOT POSSIBLE. You won't be able to achieve what you are trying.

I don't know how often you need to hear it until you finally accept it. It already has been mentioned in your thread.


Your only option would be to try out every single possible private key (2^256) and check whether it resolves to your address.
But since the number is way too high to just test a fraction of the keyspace, you should just give up.

Your 'scientific work' is crap.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: arulbero on November 07, 2018, 10:17:39 AM
Greetings to All! If there are people who can help me? My task is to use the “BitCrack” program to find one private key from 10,000,000 Bitcoin Addresses. This is my scientific work. I created a theme and described:
https://bitcointalk.org/index.php?topic=5060735.msg47651430#msg47651430 (https://bitcointalk.org/index.php?topic=5060735.msg47651430#msg47651430)


This doesn't make any sense.
It is very simple to do what TrumenPack says, in this way:

1) I generate a random public key P1 (P1 is a point of secp256k1 curve)
    

2) Then I generate 10,000,000 consecutive public keys in this way:

    P2 = P1 + G
    P3 = P2 + G (= P1 + 2*G)
    P4 = P3 + G (= P1 + 3*G)
    ....
    P27589 = P1 + 27588*G
    ….
    P10000000 = P1 + 9999999*G

3) I get from each public key the address:

   address1 = hash160 (P1)
   address2 = hash160 (P2)
   address3 = hash160 (P3)
   ....
   address10000000 = hash160 (P10000000)


Let's say now that address27589 = "18HPzD22qaUvJL69yjF3vUXx7Kfg7o5q7F". If (it is a very big if) you find out that the private key is "100A" (hex format, try to put this value here --> http://gobittest.appspot.com/Address (http://gobittest.appspot.com/Address), i. e. private key = 1*2^12 +10 = 4106), then it would be very simple to get the private keys of all the other addresses*** too:


private key of address1 = (private key of address27589 - 27588)  mod n
.....
private key of address27588 = private key of address27589 - 1 = 4105
private key of address27589 = 4106
private key of address27590 = private key of address27589 + 1 = 4107
private key of address27591 = private key of address27589 + 2 = 4108
.....
private key of address10000000 = private key of address27589 + 9.972.411 = 9.976.517


***this is true only if you find the private key to the public key P27589. There are about 2^96 different valid private keys for the address27589!


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Thirdspace on November 07, 2018, 01:26:07 PM
Yes, I generated these Bitcoin Addresses through certain numerical coordinates.
2) Then I generate 10,000,000 consecutive public keys in this way:
he said his method of generation is "through certain numerical coordinates"
but he doesn't explain how he produced these numerical coordinates or its origin
his 10,000,000 addresses are not generated sequentially as you thought


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: arulbero on November 07, 2018, 01:43:15 PM
his 10,000,000 addresses are not generated sequentially as you thought

I didn't say that, I said that is simple to get the private keys for 10000000 addresses if you know one private key and if that addresses are related in some way. "Consecutive keys" are only an example.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: stalker00075 on November 08, 2018, 10:13:23 AM
who hacked 15c9mPGLku1HuW9LRtBf4jcHVpBUt8txKz



Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Thirdspace on November 08, 2018, 01:31:59 PM
who hacked 15c9mPGLku1HuW9LRtBf4jcHVpBUt8txKz
this one is part of bitcoin puzzle (https://www.blockchain.com/btc/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15?show_adv=true)
but the last recent three addresses looked like moved by the puzzle maker rather than cracked
1LzhS3k3e9Ub8i2W1V8xQFdB8n2MYCHPCa - (Spent) 0.055 BTC
17aPYR1m6pVAacXg1PTDDU7XafvK1dxvhi - (Spent) 0.056 BTC
15c9mPGLku1HuW9LRtBf4jcHVpBUt8txKz - (Spent) 0.057 BTC
fund on these three addresses moved to 1AqEgLuT4V2XL2yQ3cCzjMtu1mXtJLVvww (https://www.blockchain.com/btc/address/1AqEgLuT4V2XL2yQ3cCzjMtu1mXtJLVvww)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: timisis on November 11, 2018, 03:06:08 AM
I am not surprised the OP did a much better job than me with this :) What does surprise me is that the donation address is a 1x, I expected a Segwit address from such a sophisticated user. Or is it a case of his 1x address really being a Segwit or script of some kind, last year I remember researching you could translate a 3x to a 1x, but I cannot remember how :)

I am also not surprised  I cannot compile out of the box on my VS 2017, all kinds of errors. What does surprise me though is that some code in there, perhaps from the Cuda Toolkit, even tells me "this code will only work in VS 2010.... 2017", so it does not recognize my VS version, WTF!


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: DevilOper on November 16, 2018, 11:50:32 AM
this one is part of bitcoin puzzle (https://www.blockchain.com/btc/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15?show_adv=true)
but the last recent three addresses looked like moved by the puzzle maker rather than cracked
Nope, look at the other transactions from those addresses, all are to the vanity addresses, quite long vanity... Someone must be found really fast way to brute-force the BC PBKs.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: digitalcitizen on November 16, 2018, 08:28:44 PM
Has anyone tried to build this on Linux?

I have CUDA devices, and looked at the Makefile.  CUDA 9.2.  Installed that, but I'm not getting anything.  No errors, just no binaries.  The libraries seem to get built.  By default they go in CUR_DIR/bin CUR_DIR/lib.

Does anyone know what I can do to try and build the project on Linux?  As far as I know, there shouldn't be any real issues with differing CUDA versions 8 to 9.2.

Thanks,  looks interesting.  Nice rewards for trying the puzzles.  I wonder if there's a better method than just brute-forcing more and more?  Unless there is no point; they're just there to be claimed later as a measurement of compute power over the years and how quickly the BTC gets moved.  In that sense, not a real puzzle.  Just, how long until this gets cracked?

Interestingly, larger amounts have been claimed.  Ones in the middle not claimed yet.  Perhaps not worth the effort to figure out if there is a real method to the madness, or not enough reward for compute effort.

Thanks, if you've managed to compile on Ubuntu, and what did you have to tweak to get it working... :)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Thirdspace on November 17, 2018, 08:20:50 PM
Nope, look at the other transactions from those addresses, all are to the vanity addresses, quite long vanity... Someone must be found really fast way to brute-force the BC PBKs.
those vanity addresses are most likely burn addresses
such addresses can be generated without knowing their private keys
to proof my point, I just created these using a tool 
1Va1idAddressesCanBeCreatedupoTas (https://www.blockchain.com/btc/address/1Va1idAddressesCanBeCreatedupoTas)
1WithoutKnowingPrivateKeyst2H8dDk (https://www.blockchain.com/btc/address/1WithoutKnowingPrivateKeyst2H8dDk)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Elliptic23 on November 18, 2018, 10:41:11 PM
I am not surprised the OP did a much better job than me with this :) What does surprise me is that the donation address is a 1x, I expected a Segwit address from such a sophisticated user. Or is it a case of his 1x address really being a Segwit or script of some kind, last year I remember researching you could translate a 3x to a 1x, but I cannot remember how :)

I am also not surprised  I cannot compile out of the box on my VS 2017, all kinds of errors. What does surprise me though is that some code in there, perhaps from the Cuda Toolkit, even tells me "this code will only work in VS 2010.... 2017", so it does not recognize my VS version, WTF!

This is a bug in CUDA. It doesn't know what the latest version of Visual Studio is. Edit <Your CUDA toolkit path>/9.2/include/crc/host_config.h so that the header matches your Visual Studio version. e.g.:

Code:
#if _MSC_VER < 1600 || _MSC_VER > 1911

becomes:

Code:
#if _MSC_VER < 1600 || _MSC_VER > 1915


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: mechanikalk on November 18, 2018, 11:31:31 PM
How hard would it be to be able to brute force find a private key from a seed phrase given some number of words?

I was on twitter recently and Jameson Lopp inadvertently revealed 17 of 24 words of a seed phrase by posting a picture of the back of his recovery phrases which he was burning.

https://twitter.com/mechanikalk/status/1062388232804069376

It is likely possible to intuit some information for the remaining 6 words that would drastically decrease the space. Jameson has stated that this is a 3 of 5 seed, so if that is true the money behind the account is safe.  However, finding the address would potentially dox Jameson's account which could be interesting.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Elliptic23 on November 19, 2018, 12:35:11 AM
If it's a 2048 word list, then 6 words is 2048^6 = 2^66 possible combinations. Not impossible. That is just over 1 year at 2 trillion keys per second.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on November 19, 2018, 02:25:47 AM
If it's a 2048 word list, then 6 words is 2048^6 = 2^66 possible combinations. Not impossible. That is just over 1 year at 2 trillion keys per second.

2 trillion keys per second?

Okay, so which state funded supercomputer shall we use to embarrass this guy?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: ETFbitcoin on November 19, 2018, 03:07:51 AM
If it's a 2048 word list, then 6 words is 2048^6 = 2^66 possible combinations. Not impossible. That is just over 1 year at 2 trillion keys per second.

Now, give us example of wallet which uses 6 words as seed mnemonic since AFAIK most wallet uses either 12, 18 or 24 words which means time required is far longer.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on November 19, 2018, 05:51:09 AM
If it's a 2048 word list, then 6 words is 2048^6 = 2^66 possible combinations. Not impossible. That is just over 1 year at 2 trillion keys per second.

Now, give us example of wallet which uses 6 words as seed mnemonic since AFAIK most wallet uses either 12, 18 or 24 words which means time required is far longer.

An earlier post states that 17 of the 24 words were revealed, so only 6 words need to be brute forced.

If the positions of the revealed words are known then you could recover up to 187 bits of the 256 bit key, and instead you would brute force the unknown bits.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: ETFbitcoin on November 19, 2018, 07:03:53 AM
An earlier post states that 17 of the 24 words were revealed, so only 6 words need to be brute forced.

If the positions of the revealed words are known then you could recover up to 187 bits of the 256 bit key, and instead you would brute force the unknown bits.

Should've read the thread carefully, but there are 6 7 words need to be brute-forced.

Even if the position of 7 unknown words is known, it's still impossible as there's 1.25^44 possible combination if my calculation is right. (2048^7) * (17^17).
Jameson Lopp trying to make people understand why brute-force is impossible.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: DevilOper on November 19, 2018, 10:19:22 AM
Nope, look at the other transactions from those addresses, all are to the vanity addresses, quite long vanity... Someone must be found really fast way to brute-force the BC PBKs.
those vanity addresses are most likely burn addresses
Yes probably you are right but it's still highly doubtful the puzzle maker would do such transactions.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on November 19, 2018, 11:11:42 AM
An earlier post states that 17 of the 24 words were revealed, so only 6 words need to be brute forced.

If the positions of the revealed words are known then you could recover up to 187 bits of the 256 bit key, and instead you would brute force the unknown bits.

Should've read the thread carefully, but there are 6 7 words need to be brute-forced.

Even if the position of 7 unknown words is known, it's still impossible as there's 1.25^44 possible combination if my calculation is right. (2048^7) * (17^17).
Jameson Lopp trying to make people understand why brute-force is impossible.

Oops, it is 7 unknown, not 6.

I agree that even when knowing the majority of the words, the chance of brute forcing the remaining bits to recover the complete key is infinitesimal.

Assuming 11 bits per word (2^11=2048), 17 known words means you have 187 bits of a 256 bit key already. That leaves 69 bits (2^69) to brute force.

If you were able to test 2^32 keys per second (an incredibly optimistic rate which assumes massive scale) it would still take 2^37 seconds to cover the entire search space... which is about 4358 years.

Things would be more complicated if you didn't know the positions of the words, as you would have to try the known 17 binary sequences in various locations, as well as brute forcing the remaining bits.

And if there's any key stretching involved the time taken to test each key, and therefore search the whole space, goes up by a significant amount.

Kind of cool that even if you know nearly 75% of a 256 bit private key, the chances of cracking it are still virtually zero.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: mechanikalk on November 19, 2018, 07:21:16 PM
An earlier post states that 17 of the 24 words were revealed, so only 6 words need to be brute forced.

If the positions of the revealed words are known then you could recover up to 187 bits of the 256 bit key, and instead you would brute force the unknown bits.

Should've read the thread carefully, but there are 6 7 words need to be brute-forced.

Even if the position of 7 unknown words is known, it's still impossible as there's 1.25^44 possible combination if my calculation is right. (2048^7) * (17^17).
Jameson Lopp trying to make people understand why brute-force is impossible.

Oops, it is 7 unknown, not 6.

I agree that even when knowing the majority of the words, the chance of brute forcing the remaining bits to recover the complete key is infinitesimal.

Assuming 11 bits per word (2^11=2048), 17 known words means you have 187 bits of a 256 bit key already. That leaves 69 bits (2^69) to brute force.

If you were able to test 2^32 keys per second (an incredibly optimistic rate which assumes massive scale) it would still take 2^37 seconds to cover the entire search space... which is about 4358 years.

Things would be more complicated if you didn't know the positions of the words, as you would have to try the known 17 binary sequences in various locations, as well as brute forcing the remaining bits.

And if there's any key stretching involved the time taken to test each key, and therefore search the whole space, goes up by a significant amount.

Kind of cool that even if you know nearly 75% of a 256 bit private key, the chances of cracking it are still virtually zero.

From the https://github.com/bitcoin/bips/blob/71586487532d832ae4a3b0deae797d86ddebe3fc/bip-0039.mediawiki (https://github.com/bitcoin/bips/blob/71586487532d832ae4a3b0deae797d86ddebe3fc/bip-0039.mediawiki)BIP39 github

Quote
This checksum is appended to the end of the initial entropy. Next, these concatenated bits are split into groups of 11 bits, each encoding a number from 0-2047, serving as an index into a wordlist. Finally, we convert these numbers into words and use the joined words as a mnemonic sentence.

It is indeed 6 words not 7.  Also, if any other information can be recovered on the additional 6 words, 1 letter, approximate length, etc. the 2048 list becomes much much smaller very quickly.  For example, if we know a word is 3 letters it goes to 100 options.  If we know it is 4-5 letters it turns into 1000 options. If we know it has a "w" it turns into 166. Therefore, the partial information should also be accounted for when calculating the difficulty.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: digitalcitizen on November 20, 2018, 09:12:18 PM
Hi all,

I've been working on a tool for brute-forcing Bitcoin private keys.

.....

The performance is good, but can likely be improved. On my hardware (GeForce GT 640) it gets 9.4 million keys per second compressed, 7.3 million uncompressed.

....

Thoughts?


Thanks!

I tried to do this once, but never found anything. I tried those terms like "wallet" "bitcoin". I found some addresses which used to have balances, but not anymore. But I was doing manually, like 1 address/3 minutes lol

Haha! Yeah, I have tried very manual methods.  It's super hard now even when you have the "chainstate" i.e. addresses with balances, guaranteed at that point in time.  So you have to be quick.  It would be pure luck starting at some point and trying for a year and wrecking some GPUs to find a key I think.

Good grief, Bitcoin is plummeting right now.  Just checked my balance.  Oh well.  I hope it goes back up later... back to topic.

If you could somehow at the same time check if any of those 9.4 million keys/sec have any balance in btc/bch/btg etc...

It's coming (sort of).  It will be slow, so it will queue up a few to check over a few hours, a long time after brute-forcing, but only until some code to keep up with the chainstate is there.  It will still be slow, but it will work a lot better than thumping on a non-local API to get a balance.

And that entirely depends on a pull request later...


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: timisis on November 21, 2018, 04:08:47 AM
Can someone "donate" the address at some seed, eg the 0000.. seed? Since I could not compile, I could not extract with my own mod to the code.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Driltan on November 23, 2018, 11:18:46 AM
Hi everybody !
Currently testing OP's tool but I'm bad at maths.
How many thousand of years remaining until I could find the actual private key from the address I'm searching for ?

https://i.imgur.com/ac7NLBV.jpg

It's actually a 1080Ti not a 1080.
I don't trust the LBC code at all so I stay far from it but I'm surprised by the numbers I get here.
If only this project : https://github.com/Isaacdelly/Plutus (https://github.com/Isaacdelly/Plutus) was coded with CUDA...   :D


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: digitalcitizen on November 24, 2018, 02:34:31 AM
Hi everybody !
Currently testing OP's tool but I'm bad at maths.
How many thousand of years remaining until I could find the actual private key from the address I'm searching for ?

https://i.imgur.com/ac7NLBV.jpg

It's actually a 1080Ti not a 1080.
I don't trust the LBC code at all so I stay far from it but I'm surprised by the numbers I get here.
If only this project : https://github.com/Isaacdelly/Plutus (https://github.com/Isaacdelly/Plutus) was coded with CUDA...   :D

You might be able to get a rough estimate with your keys/s knowing how many bits of key you need in the private key you're looking for.

Bear in mind I'm no expert either, but using 8 GPUs similar to yours, you'd need to search through at least 4 quadrillion, hundreds of trillions, ... private keys from the first valid 58 bit key (if you're looking for key 58 in the puzzles).  That's 4 or 5 solid days of searching with 8 start points and a range -r of about 500 trillion, I think.

I could be wrong!  I can't try that, so I can't verify.

You're still looking at oodles of keys, so have a look at your keys/sec, call it S, and the range of valid N bit keys, call it R, and roughly speaking R/S.  Adjust R and S for units and then look at the result in minutes, hours, days, weeks, years...

So, as an example, if you were looking at a private key of 40 bits, the first one with a 1 bit is 0x8000000000 (549,755,813,888‬ decimal) your search space is up to the first 41 bit key (double the first 40-bit key, so up to 0x10000000000 (1,099,511,627,776 decimal). Minus 1.  So your R is 0xFFFFFFFFFF  (1,099,511,627,775 decimal).

If you can do 200 million keys/s, then you can expect to find the 40-bit key within 5,497 seconds. 91 minutes.

I might try to verify this with smaller numbers of keys/s, with e.g. 32 bit key.  I think that's correct, you could get lucky and find the key within half that search space of course.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on November 24, 2018, 06:26:25 AM
If you can do 200 million keys/s, then you can expect to find the 40-bit key within 5,497 seconds. 91 minutes.

I'm not able to verify your math, but to extrapolate: if breaking a 40 bit key takes 91 minutes, then I think finding a collision (not necessarily the original private key) for the 160 bit output of RIPEMD160 will take a maximum of 91 x 2^120 minutes?

Or more simply, 2^160 / 200,000,000 = 7.3075081866545145910184241635814e+39

Which I believe is 7,307,508,186,654,514,591,018,424,163,581,400,000,000 seconds, or 231,719,564,518,471,416,508,701,933,142,000 years.

Even if my answer is off by a few orders of magnitude, or someone manages to crack concurrently over a million GPUs, the chances of finding a collision (or match) are still close enough to nil to call it impossible.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: digitalcitizen on November 24, 2018, 08:34:17 AM
If you can do 200 million keys/s, then you can expect to find the 40-bit key within 5,497 seconds. 91 minutes.

I'm not able to verify your math, but to extrapolate: if breaking a 40 bit key takes 91 minutes, then I think finding a collision (not necessarily the original private key) for the 160 bit output of RIPEMD160 will take a maximum of 91 x 2^120 minutes?

Or more simply, 2^160 / 200,000,000 = 7.3075081866545145910184241635814e+39

Which I believe is 7,307,508,186,654,514,591,018,424,163,581,400,000,000 seconds, or 231,719,564,518,471,416,508,701,933,142,000 years.

Even if my answer is off by a few orders of magnitude, or someone manages to crack concurrently over a million GPUs, the chances of finding a collision (or match) are still close enough to nil to call it impossible.

I believe you are correct, yes.

I verified the result with 1x GPU at 200m k/s. Trying to find the 37th private key, using the above calculations, 687 seconds/~11 minutes at 200m k/s.  So the search space is 137,438,953,471 decimal.

Result:

Code:
james@research:~/BitCrack/bin$ ./cuBitCrack -s 0x1000000000 -r 0x1FFFFFFFFF -o ~/testcase.txt -d 1 14iXhn8bGajVWegZHJ18vJLHhntcpL4dex
[2018-11-24.08:24:46] [Info] Compression: compressed
[2018-11-24.08:24:46] [Info] Starting at: 0000000000000000000000000000000000000000000000000000001000000000
[2018-11-24.08:24:46] [Info] Initializing
[2018-11-24.08:24:46] [Info] Generating 262,144 starting points (10.0MB)
[2018-11-24.08:24:46] [Info] 10.0%
[2018-11-24.08:24:46] [Info] 20.0%
[2018-11-24.08:24:46] [Info] 30.0%
[2018-11-24.08:24:46] [Info] 40.0%
[2018-11-24.08:24:46] [Info] 50.0%
[2018-11-24.08:24:47] [Info] 60.0%
[2018-11-24.08:24:47] [Info] 70.0%
[2018-11-24.08:24:47] [Info] 80.0%
[2018-11-24.08:24:47] [Info] 90.0%
[2018-11-24.08:24:47] [Info] 100.0%
[2018-11-24.08:24:47] [Info] Done
Tesla V100-SXM2- 446/16130MB | 1 target 219.93 MKey/s (31,273,254,912 total) [00:02:22][2018-11-24.08:27:12] [Info] Found key for address '14iXhn8bGajVWegZHJ18vJLHhntcpL4dex'. Written to '/home/james/testcase.txt'

Of course, searching the entire keyspace here won't be necessary, so there will always be a result faster than the maximum time expected, at least for these puzzles.

Maybe adjust your calculations for e.g. 10 trillion keys/sec to see how safe it might be from a well-funded adversary?  50 trillion? 100 trillion?

I think you are correct, and either way, 10 trillion or 50 trillion or more, a collision or a match for 160-bit output of RIPEMD160 is going to be (probably) impossible for years to come.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Driltan on November 24, 2018, 01:17:17 PM
Thanks for those explanations.
I wish I were good at maths.
Maybe in 20 years we would have the technology. But the security will be strong enough to prevent a crack I think  ;D


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on November 24, 2018, 03:53:59 PM
Thanks for those explanations.
I wish I were good at maths.
Maybe in 20 years we would have the technology. But the security will be strong enough to prevent a crack I think  ;D

It will be interesting to see what happens to Satoshis Millions (and any other funds which haven't moved for years) when/if technology advances sufficiently that Bitcoin has to switch to a different hashing algorithm to properly secure funds. In that case, funds MUST be moved (via the new algorithm) to protect them; any historical unspent outputs would remain susceptible to cracking. Perhaps at some point that will become the new form of mining.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: PietCoin97 on November 24, 2018, 06:37:18 PM
Hello how can i use the --continue commmand please can someone describe me that ?

and what are the best settings for GTX 1070?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: gembitz on November 24, 2018, 09:34:16 PM
Thanks for those explanations.
I wish I were good at maths.
Maybe in 20 years we would have the technology. But the security will be strong enough to prevent a crack I think  ;D

It will be interesting to see what happens to Satoshis Millions (and any other funds which haven't moved for years) when/if technology advances sufficiently that Bitcoin has to switch to a different hashing algorithm to properly secure funds. In that case, funds MUST be moved (via the new algorithm) to protect them; any historical unspent outputs would remain susceptible to cracking. Perhaps at some point that will become the new form of mining.

so who found the first coins? ;) hehe


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: digitalcitizen on November 25, 2018, 02:08:19 AM
Thanks for those explanations.
I wish I were good at maths.
Maybe in 20 years we would have the technology. But the security will be strong enough to prevent a crack I think  ;D

It will be interesting to see what happens to Satoshis Millions (and any other funds which haven't moved for years) when/if technology advances sufficiently that Bitcoin has to switch to a different hashing algorithm to properly secure funds. In that case, funds MUST be moved (via the new algorithm) to protect them; any historical unspent outputs would remain susceptible to cracking. Perhaps at some point that will become the new form of mining.

I was reading somewhere that Bitcoin Core developers, and others (mathematicians, cryptologists, etc) were trying to make the case that 160 bits is not going to be enough at some point.  Eventually they convinced Gavin Andressen that 160 bits gives them the heebie jeebies.  I'm not sure what the result of that was, I'll have to look it up.  Maybe it can be found on Gavin's blog.  I don't recall the details off the top of my head, but I found it fascinating.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: btc-room101 on November 26, 2018, 06:32:23 AM
Hi all,

I've been working on a tool for brute-forcing Bitcoin private keys. The main purpose of this tool is to contribute to the effort of solving the Bitcoin puzzle transactions: https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15 (https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15)

Screenshot:
https://i.imgur.com/xH3sU1O.png


It is open-source under the MIT licence and requires no external dependencies other than the CUDA toolkit. It builds on Windows using Visual Studio 2015, and Linux using Make (you might have to edit the Makefile and point it towards your CUDA toolkit directory).

It can search for compressed/uncompressed keys or both.

The performance is good, but can likely be improved. On my hardware (GeForce GT 640) it gets 9.4 million keys per second compressed, 7.3 million uncompressed.

Note:
-Currently it is CUDA only.
-It can only search one target key at a time


Features I would like to add if there is enough interest for the project:

-Support for searching multiple target keys at one time Done
-OpenCL/AMD device support
-CPU with AVX/AVX2/SHA support
-Checkpoints/Stop and resume
-Vanity address generation


Source and Win32/Win64 binaries available here:
https://github.com/brichard19/BitCrack (https://github.com/brichard19/BitCrack)
https://github.com/brichard19/BitCrack/releases/tag/v0.0.6 (https://github.com/brichard19/BitCrack/releases/tag/v0.0.6)


Thoughts?


Thanks!

I wrote a package last year called 'inflection', its detailed on www.inflection.top, but I have been working on this problem since 2012, and I was an early miner, but I always found BTC-HACKING, e.g. solving the 'discrete log problem' more interesting than accumulating btc.

All the things you have asked for have been done,

But I might add that 'brute force' hunting is not the way to go about this problem, like the other guy 'LBC' linear collider, its stupid to search 1-N, where N is 2**256, as that is counting all the atoms in the universe, many times over. It can't be done, unless you have an infinite time-frame to solve the problem,

The way to go about this is INTELLIGENT selection of the seed for searching the frames ECDSA, also using SAGE and MSEIVE ( most powerful factoring tool on earth ), you can factor public-keys, and develop a good band for your search, also using FFT, and RNN-LSTM you can generate favorable regions for searching,

My software that supports all GPU HW, currently does 150M/sec calcs per 1060 class card, so on a typically GPU rig for mining, I can do over a Billion calc's per second, but that is still just 10***9, where our scope is say 10**77, and there are 10**71 atoms in the universe.

Also I don't think its possible to find a particular key for a particular address, the way to go about this problem, is I have 200 million addresses with value, and 100k with high-value, I use a four layer hierarchical bloom-filter that starts at 2*32, and goes up to 2**40, everytime I find a priv-key that matches my list, there is 0.0000001% chance of false-positive, that one in 10 million, but I'm doing a billion a second, so I'm geting a lot of false positive hits, so as candidates are found, they past to the next heirarchy of bloom filters, so I can kick out up to one in a billion false-positives, I usually dial this stuff in so I can about 100 candidates a day, then its easy to use the database online to check if the key found has a 'current value', if > 0, then I log, I have found lots of 0.001 BTC, but the odd's of finding > 0.01 BTC are low, as we're talking 2*22 in a space of 2**128

So in reality here I'm looking for 200 million keys at once, not looking for one, and I'm using best estimates of likelyness to search in spaces

I think the most progress will be made in the area of sage/msieve using the published papers on discrete-log problem solving, if you want to find a particular key for a particular public address. Right now I have it down to 2**42, which is still to long to search, but with 2**24 at once, my search space is only 2**22, which is no problem


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on November 26, 2018, 07:19:33 AM
But I might add that 'brute force' hunting is not the way to go about this problem, like the other guy 'LBC' linear collider, its stupid to search 1-N, where N is 2**256, as that is counting all the atoms in the universe, many times over. It can't be done, unless you have an infinite time-frame to solve the problem,

Wasn't LBC created to solve the puzzle transactions? Just like BitCrack was? Up to this point it has been a relatively small search space, so not impossible to brute force.

Cracking an arbitrary, 100% random private key is a different matter, of course.

One advantage of focusing on puzzle transactions is that finding (and taking) those funds presents no moral dilemma. It's meant to be a reward.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: vel12 on November 26, 2018, 08:28:09 AM
But I might add that 'brute force' hunting is not the way to go about this problem, like the other guy 'LBC' linear collider, its stupid to search 1-N, where N is 2**256, as that is counting all the atoms in the universe, many times over. It can't be done, unless you have an infinite time-frame to solve the problem,

Wasn't LBC created to solve the puzzle transactions? Just like BitCrack was? Up to this point it has been a relatively small search space, so not impossible to brute force.

Cracking an arbitrary, 100% random private key is a different matter, of course.

One advantage of focusing on puzzle transactions is that finding (and taking) those funds presents no moral dilemma. It's meant to be a reward.
that's what he wants
https://i.ibb.co/S03j4DN/photofacefun-com-1543241134.jpg
https://i.ibb.co/dc2pq3p/photofacefun-com-1543241598.jpg


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Stryfe on November 26, 2018, 03:14:50 PM

One advantage of focusing on puzzle transactions is that finding (and taking) those funds presents no moral dilemma. It's meant to be a reward.

please clarify - how is finding/taking funds (essentially stealing) found to have no moral dilemma? and why would stealing be a reward?

or am I misunderstanding and there is no stealing being done and these are just free funds floating out there?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: digitalcitizen on November 26, 2018, 04:50:41 PM

One advantage of focusing on puzzle transactions is that finding (and taking) those funds presents no moral dilemma. It's meant to be a reward.

please clarify - how is finding/taking funds (essentially stealing) found to have no moral dilemma? and why would stealing be a reward?

or am I misunderstanding and there is no stealing being done and these are just free funds floating out there?

Yes, my understanding is that you are supposed to try and brute-force an N-bit key for a reward of BTC.  So, if you found a 50-bit key, you'd get 0.05BTC.

It's now getting so difficult that I don't think keys 58 and up (until the larger claimed ones) are going to be found soon, unless it's just pure luck.  The search space is massive.  I can crack a single DES key (I search the entire 64-bit space) in less than a day, but there are additional more expensive steps to finding a valid private key.  So just keys/s is not really enough; other optimisations need to be done.  The distribution of rewards according to work with the LBC was a good idea.

So, essentially my understanding is that while you don't own the key, a) it's been made deliberately findable (at least for smaller keys!), b) there's a hint on where to search for a key for the BTC reward, and c) the transaction was created in a curious manner indicating this wasn't just any type of funds transfer.

I think we can make a reasonable inference that this is a puzzle, and if you get lucky and do some real work to find a key, you get some BTC.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on November 26, 2018, 05:13:02 PM
One advantage of focusing on puzzle transactions is that finding (and taking) those funds presents no moral dilemma. It's meant to be a reward.

please clarify - how is finding/taking funds (essentially stealing) found to have no moral dilemma? and why would stealing be a reward?

or am I misunderstanding and there is no stealing being done and these are just free funds floating out there?

The whole point of a puzzle transaction is that someone will solve it. The person who created the puzzle has donated those funds, and intends for the winner to claim them. Kind of like hiding a wad of bank notes in a local park, and publicly announcing clues on how to locate them.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Stryfe on November 26, 2018, 05:26:56 PM
One advantage of focusing on puzzle transactions is that finding (and taking) those funds presents no moral dilemma. It's meant to be a reward.

please clarify - how is finding/taking funds (essentially stealing) found to have no moral dilemma? and why would stealing be a reward?

or am I misunderstanding and there is no stealing being done and these are just free funds floating out there?

The whole point of a puzzle transaction is that someone will solve it. The person who created the puzzle has donated those funds, and intends for the winner to claim them. Kind of like hiding a wad of bank notes in a local park, and publicly announcing clues on how to locate them.

ok got it - you are not brute forcing an unknown person's account but one specifically set up for this challenge.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: timisis on November 26, 2018, 09:04:09 PM

One advantage of focusing on puzzle transactions is that finding (and taking) those funds presents no moral dilemma. It's meant to be a reward.

please clarify - how is finding/taking funds (essentially stealing) found to have no moral dilemma? and why would stealing be a reward?

or am I misunderstanding and there is no stealing being done and these are just free funds floating out there?

Why is solving cryptographic problems as a miner not stealing, while it is stealing as a key cracker exactly? Because you say so?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: PietCoin97 on November 26, 2018, 10:41:50 PM
Hi all,

I've been working on a tool for brute-forcing Bitcoin private keys. The main purpose of this tool is to contribute to the effort of solving the Bitcoin puzzle transactions: https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15 (https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15)

Screenshot:
https://i.imgur.com/xH3sU1O.png


It is open-source under the MIT licence and requires no external dependencies other than the CUDA toolkit. It builds on Windows using Visual Studio 2015, and Linux using Make (you might have to edit the Makefile and point it towards your CUDA toolkit directory).

It can search for compressed/uncompressed keys or both.

The performance is good, but can likely be improved. On my hardware (GeForce GT 640) it gets 9.4 million keys per second compressed, 7.3 million uncompressed.

Note:
-Currently it is CUDA only.
-It can only search one target key at a time


Features I would like to add if there is enough interest for the project:

-Support for searching multiple target keys at one time Done
-OpenCL/AMD device support
-CPU with AVX/AVX2/SHA support
-Checkpoints/Stop and resume
-Vanity address generation


Source and Win32/Win64 binaries available here:
https://github.com/brichard19/BitCrack (https://github.com/brichard19/BitCrack)
https://github.com/brichard19/BitCrack/releases/tag/v0.0.6 (https://github.com/brichard19/BitCrack/releases/tag/v0.0.6)


Thoughts?


Thanks!

I wrote a package last year called 'inflection', its detailed on www.inflection.top, but I have been working on this problem since 2012, and I was an early miner, but I always found BTC-HACKING, e.g. solving the 'discrete log problem' more interesting than accumulating btc.

All the things you have asked for have been done,

But I might add that 'brute force' hunting is not the way to go about this problem, like the other guy 'LBC' linear collider, its stupid to search 1-N, where N is 2**256, as that is counting all the atoms in the universe, many times over. It can't be done, unless you have an infinite time-frame to solve the problem,

The way to go about this is INTELLIGENT selection of the seed for searching the frames ECDSA, also using SAGE and MSEIVE ( most powerful factoring tool on earth ), you can factor public-keys, and develop a good band for your search, also using FFT, and RNN-LSTM you can generate favorable regions for searching,

My software that supports all GPU HW, currently does 150M/sec calcs per 1060 class card, so on a typically GPU rig for mining, I can do over a Billion calc's per second, but that is still just 10***9, where our scope is say 10**77, and there are 10**71 atoms in the universe.

Also I don't think its possible to find a particular key for a particular address, the way to go about this problem, is I have 200 million addresses with value, and 100k with high-value, I use a four layer hierarchical bloom-filter that starts at 2*32, and goes up to 2**40, everytime I find a priv-key that matches my list, there is 0.0000001% chance of false-positive, that one in 10 million, but I'm doing a billion a second, so I'm geting a lot of false positive hits, so as candidates are found, they past to the next heirarchy of bloom filters, so I can kick out up to one in a billion false-positives, I usually dial this stuff in so I can about 100 candidates a day, then its easy to use the database online to check if the key found has a 'current value', if > 0, then I log, I have found lots of 0.001 BTC, but the odd's of finding > 0.01 BTC are low, as we're talking 2*22 in a space of 2**128

So in reality here I'm looking for 200 million keys at once, not looking for one, and I'm using best estimates of likelyness to search in spaces

I think the most progress will be made in the area of sage/msieve using the published papers on discrete-log problem solving, if you want to find a particular key for a particular public address. Right now I have it down to 2**42, which is still to long to search, but with 2**24 at once, my search space is only 2**22, which is no problem

do you have an open source software ?

can you find the bounty transactions mabey faster with your strategy ?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on November 27, 2018, 02:41:47 AM

One advantage of focusing on puzzle transactions is that finding (and taking) those funds presents no moral dilemma. It's meant to be a reward.

please clarify - how is finding/taking funds (essentially stealing) found to have no moral dilemma? and why would stealing be a reward?

or am I misunderstanding and there is no stealing being done and these are just free funds floating out there?

Why is solving cryptographic problems as a miner not stealing, while it is stealing as a key cracker exactly? Because you say so?

Mining a block is essentially the same as solving a puzzle challenge: the winner is expected to claim the funds.

Cracking arbitrary addresses - funds that belong to other people - is completely different. IMHO.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on November 27, 2018, 02:46:07 AM

do you have an open source software ?

can you find the bounty transactions mabey faster with your strategy ?

Note the earlier post suggesting that this person may not be entirely legit.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: holy_ship on November 27, 2018, 03:06:57 AM
Cracking arbitrary addresses - funds that belong to other people - is completely different. IMHO.

If you find a large wallet in low addresspace (or address with collision to low addresspace) then actually you've done a security audit.
Whether you are thief or not is decided by your FOLLOWING actions, but not the fact that you bruteforced something.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on November 27, 2018, 03:18:15 AM
Cracking arbitrary addresses - funds that belong to other people - is completely different. IMHO.

If you find a large wallet in low addresspace (or address with collision to low addresspace) then actually you've done a security audit.
Whether you are thief or not is decided by your FOLLOWING actions, but not the fact that you bruteforced something.

Yes, I agree with that. You can still find something without actually taking possession of it. Since I started SHA256 brainwallet research I've been bitten by the password cracking bug, for no reason other than the rush of seeing my system spit out a new password. :D

To muddy the waters a little, some people may suggest that moving funds from an insecure address may actually benefit the owner of those funds. For a while there was a bot actively stealing sweeping SHA256 brainwallet funds, but the owner of that bot apparently returned the swept funds if asked nicely. I'm not sure what he did (or intended to do) with the funds that people never claimed...


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: btc-room101 on November 27, 2018, 10:50:25 PM

One advantage of focusing on puzzle transactions is that finding (and taking) those funds presents no moral dilemma. It's meant to be a reward.

please clarify - how is finding/taking funds (essentially stealing) found to have no moral dilemma? and why would stealing be a reward?

or am I misunderstanding and there is no stealing being done and these are just free funds floating out there?

Why is solving cryptographic problems as a miner not stealing, while it is stealing as a key cracker exactly? Because you say so?

Mining a block is essentially the same as solving a puzzle challenge: the winner is expected to claim the funds.

Cracking arbitrary addresses - funds that belong to other people - is completely different. IMHO.

Well its a HOBBY,

You can photograph stars, but so long as you don't travel there and steal the star its ok right?

How about photo-graphing a lion at the zoo? That's ok, so long as you don't just the fence and go into the den?

For many of us we do this because they said "IT CANT BE DONE", that is a mission for many people,

With regards to what do you do with an address/private-key combo once its found? I would say nothing really, when I find BTC addresses and match their physical key, I used to sweep, but that was years ago, but I don't even own an exchange account, I know it would be silly to even buy/sell BTC, as its all tracked.

Most of what we call BTC is BIG-LIE, that its secure, that its safe, that its private, ... its all a lie, the only thing real is the MATH, the SHA (NSA), the ECDSA (NSA) that is all real, so cracking the GOV's code is what makes this cool, but actually 'spending' btc would be like jumping the fence and going into the lions den.

www.inflection.top

For anybody here that wants to learn how to crack bitcoin, lets talk the talk, and I'll share the code.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: btc-room101 on November 27, 2018, 11:25:17 PM
Hi all,

I've been working on a tool for brute-forcing Bitcoin private keys. The main purpose of this tool is to contribute to the effort of solving the Bitcoin puzzle transactions: https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15 (https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15)

Screenshot:
https://i.imgur.com/xH3sU1O.png


It is open-source under the MIT licence and requires no external dependencies other than the CUDA toolkit. It builds on Windows using Visual Studio 2015, and Linux using Make (you might have to edit the Makefile and point it towards your CUDA toolkit directory).

It can search for compressed/uncompressed keys or both.

The performance is good, but can likely be improved. On my hardware (GeForce GT 640) it gets 9.4 million keys per second compressed, 7.3 million uncompressed.

Note:
-Currently it is CUDA only.
-It can only search one target key at a time


Features I would like to add if there is enough interest for the project:

-Support for searching multiple target keys at one time Done
-OpenCL/AMD device support
-CPU with AVX/AVX2/SHA support
-Checkpoints/Stop and resume
-Vanity address generation


Source and Win32/Win64 binaries available here:
https://github.com/brichard19/BitCrack (https://github.com/brichard19/BitCrack)
https://github.com/brichard19/BitCrack/releases/tag/v0.0.6 (https://github.com/brichard19/BitCrack/releases/tag/v0.0.6)


Thoughts?


Thanks!

I wrote a package last year called 'inflection', its detailed on www.inflection.top, but I have been working on this problem since 2012, and I was an early miner, but I always found BTC-HACKING, e.g. solving the 'discrete log problem' more interesting than accumulating btc.

All the things you have asked for have been done,

But I might add that 'brute force' hunting is not the way to go about this problem, like the other guy 'LBC' linear collider, its stupid to search 1-N, where N is 2**256, as that is counting all the atoms in the universe, many times over. It can't be done, unless you have an infinite time-frame to solve the problem,

The way to go about this is INTELLIGENT selection of the seed for searching the frames ECDSA, also using SAGE and MSEIVE ( most powerful factoring tool on earth ), you can factor public-keys, and develop a good band for your search, also using FFT, and RNN-LSTM you can generate favorable regions for searching,

My software that supports all GPU HW, currently does 150M/sec calcs per 1060 class card, so on a typically GPU rig for mining, I can do over a Billion calc's per second, but that is still just 10***9, where our scope is say 10**77, and there are 10**71 atoms in the universe.

Also I don't think its possible to find a particular key for a particular address, the way to go about this problem, is I have 200 million addresses with value, and 100k with high-value, I use a four layer hierarchical bloom-filter that starts at 2*32, and goes up to 2**40, everytime I find a priv-key that matches my list, there is 0.0000001% chance of false-positive, that one in 10 million, but I'm doing a billion a second, so I'm geting a lot of false positive hits, so as candidates are found, they past to the next heirarchy of bloom filters, so I can kick out up to one in a billion false-positives, I usually dial this stuff in so I can about 100 candidates a day, then its easy to use the database online to check if the key found has a 'current value', if > 0, then I log, I have found lots of 0.001 BTC, but the odd's of finding > 0.01 BTC are low, as we're talking 2*22 in a space of 2**128

So in reality here I'm looking for 200 million keys at once, not looking for one, and I'm using best estimates of likelyness to search in spaces

I think the most progress will be made in the area of sage/msieve using the published papers on discrete-log problem solving, if you want to find a particular key for a particular public address. Right now I have it down to 2**42, which is still to long to search, but with 2**24 at once, my search space is only 2**22, which is no problem

do you have an open source software ?

can you find the bounty transactions mabey faster with your strategy ?

Yes, sure I give out all the source to free to people in the third world, mostly India; The web-site is www.inflection.top, the github github.com/btc-room101, just tell me what you want,

I have 100's of tools I have written since 2012 when I started working on Bitcoin, most of the stuff is in python, and the gpu stuff of course is in C++;

I'm not inclined to put 100's of packages on github, so tell me what you want, I could make a list of what I have, best here is list what you want, and I'll tell you if  I have it, since I have done this crap for 6+ years ( hack bitcoin ), but I have been hacking crypto for 30+ years, so I have lots of code

I don't know what people want or need,

I think my site www.inflection.top discusses my areas of research, and the code, normally what I have done is from that site people ( usually students in 3rd world countrys ) send email and request code, I have found in the past that the 'guardians' of bitcointalk don't want anything real, they go out of their way to protect bitcoin, but as an intelligent person knows, knowing this stuff makes you strong, but instead the community prefers the continue the cannards and lies that has made them 'virtually rich', not unlike the little-prince ( a book ) where a man owned all the stars.

I would lke to see BITCOIN stronger, but the PTB want to keep it weak, just like FB,GOOG,TWITTER there is a concerted corporate effort to take away all notions of privacy and security. Here in BTC they tell us its secure, that its private, and anybody who steps forward with the truth is censored. This will be the downfall of BTC that it is over-lorded by imbeciles. In the meantime the RUSSIANS, CHINESE, and INDIANS will leave the west in the dust.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: The Healer on November 28, 2018, 01:57:55 PM
Where can I find a list of all BTC dormant addresses since 2011, with a balance?
Or how/where can I start to build one like this?

Thank you for any references


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: bob123 on November 28, 2018, 02:09:58 PM
Where can I find a list of all BTC dormant addresses since 2011, with a balance?
Or how/where can I start to build one like this?

Thank you for any references

You can take a look at this topic: https://bitcointalk.org/index.php?topic=5064946.msg47684089#msg47684089 (https://bitcointalk.org/index.php?topic=5064946.msg47684089#msg47684089)

There are several links to resources provided (and links to parser to do it yourself).


Another way would be to download and completely sync bitcoin core (with the -txindex parameter), then write a small script which parses each transaction and checks whether the receiving address still has funds.

Using a parser from the above link probably is easier and faster tho.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: The Healer on November 28, 2018, 02:22:42 PM
Where can I find a list of all BTC dormant addresses since 2011, with a balance?
Or how/where can I start to build one like this?

Thank you for any references

You can take a look at this topic: https://bitcointalk.org/index.php?topic=5064946.msg47684089#msg47684089 (https://bitcointalk.org/index.php?topic=5064946.msg47684089#msg47684089)

There are several links to resources provided (and links to parser to do it yourself).


Another way would be to download and completely sync bitcoin core (with the -txindex parameter), then write a small script which parses each transaction and checks whether the receiving address still has funds.

Using a parser from the above link probably is easier and faster tho.

Thank you!  ;)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: PietCoin97 on November 28, 2018, 09:37:55 PM

Yes, sure I give out all the source to free to people in the third world, mostly India; The web-site is www.inflection.top, the github github.com/btc-room101, just tell me what you want,

I have 100's of tools I have written since 2012 when I started working on Bitcoin, most of the stuff is in python, and the gpu stuff of course is in C++;

I'm not inclined to put 100's of packages on github, so tell me what you want, I could make a list of what I have, best here is list what you want, and I'll tell you if  I have it, since I have done this crap for 6+ years ( hack bitcoin ), but I have been hacking crypto for 30+ years, so I have lots of code

I don't know what people want or need,

I think my site www.inflection.top discusses my areas of research, and the code, normally what I have done is from that site people ( usually students in 3rd world countrys ) send email and request code, I have found in the past that the 'guardians' of bitcointalk don't want anything real, they go out of their way to protect bitcoin, but as an intelligent person knows, knowing this stuff makes you strong, but instead the community prefers the continue the cannards and lies that has made them 'virtually rich', not unlike the little-prince ( a book ) where a man owned all the stars.

I would lke to see BITCOIN stronger, but the PTB want to keep it weak, just like FB,GOOG,TWITTER there is a concerted corporate effort to take away all notions of privacy and security. Here in BTC they tell us its secure, that its private, and anybody who steps forward with the truth is censored. This will be the downfall of BTC that it is over-lorded by imbeciles. In the meantime the RUSSIANS, CHINESE, and INDIANS will leave the west in the dust.

Do you have Discord mabey we can write there a bit ?

i have some interesting questions

I am also interested in your long time experience in BTC


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: btc-room101 on November 29, 2018, 03:08:00 AM

Yes, sure I give out all the source to free to people in the third world, mostly India; The web-site is www.inflection.top, the github github.com/btc-room101, just tell me what you want,

I have 100's of tools I have written since 2012 when I started working on Bitcoin, most of the stuff is in python, and the gpu stuff of course is in C++;

I'm not inclined to put 100's of packages on github, so tell me what you want, I could make a list of what I have, best here is list what you want, and I'll tell you if  I have it, since I have done this crap for 6+ years ( hack bitcoin ), but I have been hacking crypto for 30+ years, so I have lots of code

I don't know what people want or need,

I think my site www.inflection.top discusses my areas of research, and the code, normally what I have done is from that site people ( usually students in 3rd world countrys ) send email and request code, I have found in the past that the 'guardians' of bitcointalk don't want anything real, they go out of their way to protect bitcoin, but as an intelligent person knows, knowing this stuff makes you strong, but instead the community prefers the continue the cannards and lies that has made them 'virtually rich', not unlike the little-prince ( a book ) where a man owned all the stars.

I would lke to see BITCOIN stronger, but the PTB want to keep it weak, just like FB,GOOG,TWITTER there is a concerted corporate effort to take away all notions of privacy and security. Here in BTC they tell us its secure, that its private, and anybody who steps forward with the truth is censored. This will be the downfall of BTC that it is over-lorded by imbeciles. In the meantime the RUSSIANS, CHINESE, and INDIANS will leave the west in the dust.

Do you have Discord mabey we can write there a bit ?

i have some interesting questions

I am also interested in your long time experience in BTC

Ask questions here, why not??? This is the BTC forum right?

Trouble is the PTB censor everything, they have their own 'myths' study joseph cambell, so why not discuss here, what do the PTB have to fail,

p.s. fuck discord, facebook, twitter, gab.io, and all the other corporate 'chat spots'

What do you have to fear? Just ask questions, and I will answer

Lastly, you asked "How can I get the private-key for 'x' address?" YOU can't its impossible, there are 10**77 keys, there are 10**72 atoms in the universe, you can't even find a mouse on the earth in your lifetime, you ain't going to find a particular atom in the know universe.

What I do is work with 200 milliion used addresses, all at once, using bloom-filters that are on the GPU board, 150M/sec escda transactions, on each the bloom is check on a single cycle, if there is a hit it is recorded and later verified,

Thus I'm 200M more times each day to find the 'atom' than you are, but that is still not much, so then we have to use smart ideas like where to look, in DLP there is giant-step/baby-step, many ways find pre-calculate and no where to look so you drop the odds to your favor.

FYI, there are 50k high-value bitcoin addresses, your not likely to find one even using my techniques daily, but just running through 1 to 10**77, even if everyone on earth had a computer, your not likely to ever find a 'hit' for your address; I get hits everyday, albeit most are 0.0001 bitcoin accounts, but at least their hits,

I think in time we will be able to solve the DLP problem A = D*P, where A is the address and D is the private key, and P is the prime for ecdsa, here secp256k1, log solution  form is A = D+P, so we're trying to find D = A-P, problem is the modula is cyclic, we don't know how many spins, but there are lots of papers on this subject, and now with GPU's we can put a lot of the DLP algos in the GPU memory and let this stuff rip.



Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: btc-room101 on November 29, 2018, 03:17:43 AM
Where can I find a list of all BTC dormant addresses since 2011, with a balance?
Or how/where can I start to build one like this?

Thank you for any references

You can take a look at this topic: https://bitcointalk.org/index.php?topic=5064946.msg47684089#msg47684089 (https://bitcointalk.org/index.php?topic=5064946.msg47684089#msg47684089)

There are several links to resources provided (and links to parser to do it yourself).


Another way would be to download and completely sync bitcoin core (with the -txindex parameter), then write a small script which parses each transaction and checks whether the receiving address still has funds.

Using a parser from the above link probably is easier and faster tho.

Thank you!  ;)

You have to build your own, this is easy, can be done with python, running a batch to date takes about 3 days, and then you need a mining-pool algo that run's every 15 minutes and updates your list forever, once you have the initial, you grab from the pool, that way you can get the new addresses before anyone else.

You need lots a bloom-filters, you don't check or search, you have a bloom-filter for every category and you run tools to check and see if that address have funds,

I can upload any python for any problem you want, but I need to know what people need.

The only time you go online is if you find an address that looks good, and then you want to see the value 'now' quite often you'll find the funds are already gone, as a lots addresses are used for 'spinning' or 'cleaning-coins', so the funds don't stay long, but these are the stuff you find the most frequent,

The pristine coins, like the original satatoshi, you can put in a list too, and call it pristine.blm, and then run your tools frequently, but again the odds of finding 1 in 50k is LOW, in your case the odd's of finding 1 in 10**77 is impossible

The problem with the address value bs, is all the code out there doesn't work, all the stuff was mostly written in 2013 and everytime that CORE changes the data-structure the programs get broken, and they're never maintained, that's why its best to have a small python routine that scrubs your own bitcoin server, and you do this ONCE, and then every 15 minutes forever. I like to keep all the different lists apart

like 100M satoshi, 10M satoshi, 1B satoshi ( 0.1 BTC )

Then for every such list you have a bloom filter for that list, some blooms must be 16gb, but these are the same blooms that get loaded into the GPU


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on November 29, 2018, 08:49:19 AM
FYI, there are 50k high-value bitcoin addresses, your not likely to find one even using my techniques daily, but just running through 1 to 10**77, even if everyone on earth had a computer, your not likely to ever find a 'hit' for your address; I get hits everyday, albeit most are 0.0001 bitcoin accounts, but at least their hits,

To be absolutely clear: are you suggesting that you are able to find the private keys of funded Bitcoin addresses, where the keys are 100% random, and are not:

- Generated with a weak PRNG
- Insecure brain wallets (eg SHA256 of dictionary word or common phrase)
- A deliberate pattern like 0x4200000000.... or 0xdeadbeef00000000....
- Already listed somewhere (some private keys appear in the Bitcoin source for testing)

???


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: bob123 on November 29, 2018, 08:52:37 AM
To be absolutely clear: are you suggesting that you are able to find the private keys of funded Bitcoin addresses, where the keys are 100% random, and are not:

- Generated with a weak PRNG
- Insecure brain wallets (eg SHA256 of dictionary word or common phrase)
- A deliberate pattern like 0x4200000000.... or 0xdeadbeef00000000....
- Already listed somewhere (some private keys appear in the Bitcoin source for testing)

???

That's what he claims. But obviously that's just a troll.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: PietCoin97 on November 29, 2018, 08:53:08 AM


Ask questions here, why not??? This is the BTC forum right?

Trouble is the PTB censor everything, they have their own 'myths' study joseph cambell, so why not discuss here, what do the PTB have to fail,

p.s. fuck discord, facebook, twitter, gab.io, and all the other corporate 'chat spots'

What do you have to fear? Just ask questions, and I will answer

Lastly, you asked "How can I get the private-key for 'x' address?" YOU can't its impossible, there are 10**77 keys, there are 10**72 atoms in the universe, you can't even find a mouse on the earth in your lifetime, you ain't going to find a particular atom in the know universe.

What I do is work with 200 milliion used addresses, all at once, using bloom-filters that are on the GPU board, 150M/sec escda transactions, on each the bloom is check on a single cycle, if there is a hit it is recorded and later verified,

Thus I'm 200M more times each day to find the 'atom' than you are, but that is still not much, so then we have to use smart ideas like where to look, in DLP there is giant-step/baby-step, many ways find pre-calculate and no where to look so you drop the odds to your favor.

FYI, there are 50k high-value bitcoin addresses, your not likely to find one even using my techniques daily, but just running through 1 to 10**77, even if everyone on earth had a computer, your not likely to ever find a 'hit' for your address; I get hits everyday, albeit most are 0.0001 bitcoin accounts, but at least their hits,

I think in time we will be able to solve the DLP problem A = D*P, where A is the address and D is the private key, and P is the prime for ecdsa, here secp256k1, log solution  form is A = D+P, so we're trying to find D = A-P, problem is the modula is cyclic, we don't know how many spins, but there are lots of papers on this subject, and now with GPU's we can put a lot of the DLP algos in the GPU memory and let this stuff rip.



Haha yes I know that that I never find a priv key for 1 special address. That was not the question.
But I have a list with 42k addresses with a ffund of 50 BTC these are the addresses from 2009 and 2010 where the miking reward of 50 BTC goes to a wallet. The entry of the wallet means "NO TRANSAKTION NEW GENERATED Coins" so mabey when we have one pub key for that we can mine these blocks or something. There are 42k addresses and there are also 25 BTC addresses you know because The halfing after 4 years.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: dejarumlights on November 30, 2018, 08:08:45 PM
Well, alternate methods and programs aside, is there any inkling of a chance for a cuda 8 build on the latest version? Figure it's a fun use of old-ass cards that couldn't mine their way out of a wet paper bag in the current era.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Daltonik on December 04, 2018, 01:54:25 PM
I tried RTX 2080ti not sure about the optimal settings for it, but it turned out the following

http://a.radikal.ru/a30/1812/a4/f13de1964397.jpg (http://radikal.ru)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Daltonik on December 04, 2018, 02:32:11 PM
To search for a compressed key, the speed is even higher.
bat file: cuBitCrack.exe -c address -b 112 -t 512 -p 512 -o key.txt    

http://d.radikal.ru/d24/1812/4a/5dea93514b6a.jpg (http://radikal.ru)



Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: AltcoinTradingSignal.com on December 04, 2018, 07:51:38 PM
Brute-force is one of the oldest methods of breaking security. However, the current hardware is not capable of brute-forcing the security of Bitcoin. It will take too many years to get a decent result which is not even worth. However, quantum computers can pose a threat to the current cryptography security.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: holy_ship on December 05, 2018, 03:04:09 AM
To search for a compressed key, the speed is even higher.

Great job, brichard!
bitcrack scales nice on top GPUs. It is 50% more effective, than 1070 (megakeys/bucks).


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: kknd on December 07, 2018, 03:09:29 PM
Please ! make a benchmark table !




Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: dymon on December 12, 2018, 04:06:15 AM
on one gtx 1050ti  64 Mkey/s
bat file ( -b 500 -t 128 -p 128 )

https://i.imgur.com/ncW62d3.png


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: The Healer on December 12, 2018, 03:15:17 PM
on one gtx 1080  130 Mkey/s (with 40k targets)
bat file ( -b 32 -t 512 -p 1024 )



Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: BitCrack on December 12, 2018, 03:58:54 PM
on one gtx 1050ti  64 Mkey/s
bat file ( -b 500 -t 128 -p 128 )

https://i.imgur.com/ncW62d3.png

You can probably get more than 64Mkeys/second. Try increasing the p parameter.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: racminer on December 13, 2018, 10:33:50 PM
Rx480 8Gb     107.04 MKey/s
clBitCrack  --b 72 -t 256 -p 2048

Rx480 4Gb     100.00 MKey/s
clBitCrack  --b 72 -t 256 -p 1024






Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: PietCoin97 on December 13, 2018, 10:37:25 PM
gtx 1070

-b 15 -t 512 -p 4120 both 80Mkeys with 87k file
 
only compressed 245 Mkeys with 4k file


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: mistercoin on December 14, 2018, 05:13:09 PM
Might just be quicker to hash out new addresses en-masse then use a checking script to check if any of your generated addresses have balances already. You have a better chance hitting the lottery 20 weeks in a row, than finding any sizable amount in billions of keys.

-MisterCoin


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: k2kaveh on December 14, 2018, 05:38:48 PM
on one gtx 1050ti  64 Mkey/s
bat file ( -b 500 -t 128 -p 128 )

https://i.imgur.com/ncW62d3.png

how can you manage 64 mkey/s with your 1050ti? :/

i've tried your parameter and my own parameters but all i get is 21mkey or 23 :/


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on December 14, 2018, 06:41:28 PM
Might just be quicker to hash out new addresses en-masse then use a checking script to check if any of your generated addresses have balances already. You have a better chance hitting the lottery 20 weeks in a row, than finding any sizable amount in billions of keys.

Any "sizable" amount?

Unless you're searching in the space where toy keys such as 1, 2, 3 etc are located, you are unlikely to find any keys, ever. And toy keys will have a zero balance.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: alex1560 on December 16, 2018, 03:20:35 PM
Nice job with the tool! It's perfect to work on something for hobby. It's modern lottery run by computer, I sent my thanks to your BTC wallet as well.. In case I find any lost wallet I will split proffits :)).


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: BitCrack on December 16, 2018, 08:20:17 PM
Nice job with the tool! It's perfect to work on something for hobby. It's modern lottery run by computer, I sent my thanks to your BTC wallet as well.. In case I find any lost wallet I will split proffits :)).

Very much appreciated! The donations are going towards new hardware, as I only have a GeForce GT 640 and Radeon 280X at the moment.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: alex1560 on December 16, 2018, 09:43:34 PM
Very much appreciated! The donations are going towards new hardware, as I only have a GeForce GT 640 and Radeon 280X at the moment.

You are welcome! I played a bit with the gpu code, that is rocketship code for me, but I managed to understand that I cannot change it easily to
do random addresses as the stride is set at the initialization of the GPU node (not even sure if it's possible or if it's pheasible with the way gpu work is done). So I will use at intended :). I set a random stride and nextKey using the generatePrivateKey(); so it generates a new set everytime the app is launched and counts at the random next key.

I am using GTX 690X, launched the app twice, with 1 app per node (gtx 690 has 2 nodes) and I am getting a total of 80 Mh/s.

I though it would be cool to link this with the blocksci, but I think the way you made it work with loading the list into the memory of the GPU is much more efficient than doing queries to blocksci.

Best of luck with your project, it's very nice of you that you shared the code, as I see it was a lot of work involved.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: btc-room101 on December 16, 2018, 11:06:30 PM
Might just be quicker to hash out new addresses en-masse then use a checking script to check if any of your generated addresses have balances already. You have a better chance hitting the lottery 20 weeks in a row, than finding any sizable amount in billions of keys.

-MisterCoin

That's how brainflayer works, does the address generation in batches, then turns it loose and compares the hits in a bloom filter which is a single cycle check, production of addresses from priv-key (guesses) is best done in 8192 batches, having a bloom filter on board GPU allows 150m/sec, no problem on 1060 class card

I suggest studying 'vanity gen' gutting all the vanity bullshit and hacking the gpu code to just generate batches and verify in the bloom-filter that a high-value address was found, then print the private-key, the hardest part of this task is getting the bloom filter on board the gpu, limit is 1/2mb for 1060, and about 1gb ( malloc() alloc per chunk ), so with a 1080 you bloom can do about 50 million addresse verification on one check.

www.inflection.top

The worst thing about 'bitcrack' is that you can't find anything doing a linear brute force search, you block-generation of private-key candidates must be an intelligent search, and the public key guesses must be based on a known DLP algo

It's impossible to hit specific private keys using linear brute force, if all the atoms in universe ( 10**72 ) were cpus using this code (bitcrack), they would still have difficulty find a key match, if you only have 10k gpu class machines running, then it would take 10**48 years to find your key.

There is a reason crypto scientists call it 'brute force', brute is code for moron, only a moron de-crypts in this manner.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: alex1560 on December 17, 2018, 05:36:09 PM
Might just be quicker to hash out new addresses en-masse then use a checking script to check if any of your generated addresses have balances already. You have a better chance hitting the lottery 20 weeks in a row, than finding any sizable amount in billions of keys.

-MisterCoin

That's how brainflayer works, does the address generation in batches, then turns it loose and compares the hits in a bloom filter which is a single cycle check, production of addresses from priv-key (guesses) is best done in 8192 batches, having a bloom filter on board GPU allows 150m/sec, no problem on 1060 class card

I suggest studying 'vanity gen' gutting all the vanity bullshit and hacking the gpu code to just generate batches and verify in the bloom-filter that a high-value address was found, then print the private-key, the hardest part of this task is getting the bloom filter on board the gpu, limit is 1/2mb for 1060, and about 1gb ( malloc() alloc per chunk ), so with a 1080 you bloom can do about 50 million addresse verification on one check.

www.inflection.top

The worst thing about 'bitcrack' is that you can't find anything doing a linear brute force search, you block-generation of private-key candidates must be an intelligent search, and the public key guesses must be based on a known DLP algo

It's impossible to hit specific private keys using linear brute force, if all the atoms in universe ( 10**72 ) were cpus using this code (bitcrack), they would still have difficulty find a key match, if you only have 10k gpu class machines running, then it would take 10**48 years to find your key.

There is a reason crypto scientists call it 'brute force', brute is code for moron, only a moron de-crypts in this manner.

Thanks for sharing! I think indeed that this might be a better approach. I am giving this a try as well.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Synthaconic on December 27, 2018, 06:32:57 PM
Hi,
I ran clBitCrack.exe on Win10 and when program started generating keys my computer became really slow. CPU utilization was only 8% but everything was really sloooow (youtube, web, windows). I tested multiple -b  -t -p and the only difference was that it generated more keys. Is there any solution for this? Does this happen with better cards too (like GTX 1080ti)?

Ryzen 2700x +  Radeon HD 5700

Thanks!


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: darosior on December 27, 2018, 06:50:24 PM
Hi,
I ran clBitCrack.exe on Win10 and when program started generating keys my computer became really slow. CPU utilization was only 8% but everything was really sloooow (youtube, web, windows). I tested multiple -b  -t -p and the only difference was that it generated more keys. Is there any solution for this? Does this happen with better cards too (like GTX 1080ti)?

Ryzen 2700x +  Radeon HD 5700

Thanks!
Hi,

the program makes use of the GPU in order to generate many addresses (which is done by hashing the public key, and GPUs are better at hashing than CPUs) so it makes sense that it affects programms which make use of your GPU too..


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Synthaconic on December 27, 2018, 07:38:13 PM
Hi,
I ran clBitCrack.exe on Win10 and when program started generating keys my computer became really slow. CPU utilization was only 8% but everything was really sloooow (youtube, web, windows). I tested multiple -b  -t -p and the only difference was that it generated more keys. Is there any solution for this? Does this happen with better cards too (like GTX 1080ti)?

Ryzen 2700x +  Radeon HD 5700

Thanks!
Hi,

the program makes use of the GPU in order to generate many addresses (which is done by hashing the public key, and GPUs are better at hashing than CPUs) so it makes sense that it affects programms which make use of your GPU too..

Yea, it does use 99% of GPU. That sucks though, can't do anything else on my PC. Would be nice to have option for GPU usage %.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Synthaconic on December 28, 2018, 04:25:39 PM
HI,
Does anyone know that is there similar software for Etherium??
Thanks!


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: darosior on December 28, 2018, 09:21:57 PM
HI,
Does anyone know that is there similar software for Etherium??
Thanks!
There is https://github.com/tmgroupsecurity/EthCrack but trying to generate many private keys is not viable and you won't find any pk with funds on it. Ever.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: MalRekkie on January 05, 2019, 08:51:10 AM
Can someone help me....?
I added my own address to bitcoin scan list of 8 million addresses.....ive set to start scan at the HEX of my address...but it dont list it in found list?  What setting is wrong?

Here is command i run in power shell. And this is my address i added to list  ... 1JAQdSSY9HE91Hs7ud4mVzUszfWsutizPw   ?

PS C:\Users\djfla\Desktop\BitCrack-0.23> ./clbitcrack.exe -s 6442bae903c8d27ddcd00***************03ebda825ecde678ab
84966 -o found.txt -i 1.txt -c -u
[2019-01-05.10:34:45] [Info] Compression: both
[2019-01-05.10:34:45] [Info] Starting at: 6442BAE903C8D27DDCD00C2****************A825ECDE678AB84966
[2019-01-05.10:34:45] [Info] Compiling OpenCL kernels...
[2019-01-05.10:35:03] [Info] Initializing Hawaii
[2019-01-05.10:35:03] [Info] Generating 262,144 starting points (10.0MB)
[2019-01-05.10:35:03] [Info] 10.0%
[2019-01-05.10:35:04] [Info] 20.0%
[2019-01-05.10:35:04] [Info] 30.0%
[2019-01-05.10:35:04] [Info] 40.0%
[2019-01-05.10:35:04] [Info] 50.0%
[2019-01-05.10:35:04] [Info] 60.0%
[2019-01-05.10:35:04] [Info] 70.0%
[2019-01-05.10:35:04] [Info] 80.0%
[2019-01-05.10:35:05] [Info] 90.0%
[2019-01-05.10:35:05] [Info] 100.0%
[2019-01-05.10:35:05] [Info] Done
[2019-01-05.10:35:05] [Info] Loading addresses from '1.txt'
[2019-01-05.10:36:03] [Info] 7,954,161 addresses loaded (151.7MB)
Hawaii           272/4096MB | 7954161 targets 14.03 MKey/s (37,863,817,216 total) [00:44:49]


Any help please?

Is their also a way to random scan instead of consistent...and a stop and cont at last key?

Regards


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Lolo54 on January 05, 2019, 09:42:41 PM
add in your command line -c -u and it will find


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: MalRekkie on January 05, 2019, 11:59:21 PM
u cant read?? see my post u will see i have it in...


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on January 06, 2019, 01:13:14 AM
Can someone help me....?
I added my own address to bitcoin scan list of 8 million addresses.....ive set to start scan at the HEX of my address...but it dont list it in found list?  What setting is wrong?


If you are passing it your exact private key to see what happens when it finds a match, what happens if you deduct 1 from it? (eg pass 6442bae903c8d27ddcd00***************03ebda825ecde678aa on the commandline)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: MalRekkie on January 06, 2019, 06:15:34 AM
last nr is 7 on hex key...i change that to a 6...stil dont match them,  tried with few other addresses also....none match i gotHEX  0000000000000000000000000000000000002 to match but thats it....


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: MalRekkie on January 06, 2019, 11:54:05 AM
TRYING TO USE --CONTINUE NOW ALSO..sorry caps. 

all work fine if i start at 00000000000000000000000000000000000000001 as here under:

start=0000000000000000000000000000000000000000000000000000000000000001
next=00000000000000000000000000000000000000000000000000000000D1640001
end=FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
blocks=32
threads=256
points=32
compression=both
device=0
elapsed=329750
stride=0000000000000000000000000000000000000000000000000000000000000001

BUT when i set custom key to start as NEXT as here under...it keep starting same key. the NEXT dont change:

start=858E3259E5E3EC8D6665E1BD8495AB1E559606596B89A451AA6865074010F722
next=858E3259E5E3EC8D6665E1BD8495AB1E559606596B89A451AA68651A6958F723
end=FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
blocks=32
threads=256
points=32
compression=both
device=0
elapsed=15621702
stride=0000000000000000000000000000000000000000000000000000000000000001


ALSO, my HEX and and addresses still don't match and not listed in found :( 


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: chan111 on January 25, 2019, 01:34:13 PM
Hi.
This looks like VERY GOOD piece of software, but I dont understand one thing :)

My tougths:

1.) Is it possible to recover part of private key, when I have valid address?

For example:
let's say one of my paper wallet is partialy destroyed, and I have lost 5 or more characters from private, like:

pub: 1DrqrF3JEYB9TXWymz4zGoEzM5i75JMLFB
priv: L3Wji4b***4Po3vo2gmi42Y2kbbxtnpAfQ5wJx11BgNr****8v3Q

Would be EXTREMALY usefull for paperwallet users!

Regards.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: ETFbitcoin on January 25, 2019, 06:18:30 PM
1.) Is it possible to recover part of private key, when I have valid address?

For example:
let's say one of my paper wallet is partialy destroyed, and I have lost 5 or more characters from private, like:

pub: 1DrqrF3JEYB9TXWymz4zGoEzM5i75JMLFB
priv: L3Wji4b***4Po3vo2gmi42Y2kbbxtnpAfQ5wJx11BgNr****8v3Q

It is possible as long as exact position of lost characters & it's public key/address are known since 58^5 (656.356.768) combination is small number for GPU these days. But AFAIK this software don't support such feature.

But if the exact position of lost characters & it's public key/address isn't known, time complexity would increase significantly because :
1. If it's public key/address isn't known, you need to check if generated address from bruteforce with partial private key contain Bitcoin and AFAIK it's far slower compared with bruteforce speed
2. If exact position of lost characters isn't known, total possible combination is far higher


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: chan111 on January 25, 2019, 07:00:52 PM

But AFAIK this software don't support such feature.


Yes, thanks for an answer. So it seemed to me. I could not find a suitable example. The position of the characters is known. It would be a great feature for the software.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: arulbero on January 25, 2019, 08:02:22 PM
1.) Is it possible to recover part of private key, when I have valid address?

For example:
let's say one of my paper wallet is partialy destroyed, and I have lost 5 or more characters from private, like:

pub: 1DrqrF3JEYB9TXWymz4zGoEzM5i75JMLFB
priv: L3Wji4b***4Po3vo2gmi42Y2kbbxtnpAfQ5wJx11BgNr****8v3Q

Would be EXTREMALY usefull for paperwallet users!

Regards.

If you know the public key (not the address) and the first ~ 180 bits of the private key, it is possible to retrieve the other 70 / 80 bits using smarter ways than brute force attack.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: chan111 on January 25, 2019, 08:43:07 PM
If you know the public key (not the address) and the first ~ 180 bits of the private key, it is possible to retrieve the other 70 / 80 bits using smarter ways than brute force attack.

Yes, I realize that finding the last bits of the private key would be much easier.
Unfortunately... I know only what I have shown: full addres, and private key with some randomly missing characters.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: HeRetiK on January 26, 2019, 12:00:38 AM
If you know the public key (not the address) and the first ~ 180 bits of the private key, it is possible to retrieve the other 70 / 80 bits using smarter ways than brute force attack.

Yes, I realize that finding the last bits of the private key would be much easier.
Unfortunately... I know only what I have shown: full addres, and private key with some randomly missing characters.

The address is not the public key. It's a hash of a hash of the public key plus a bit of error correction.

If there has been an outgoing transaction from the address in question one is able to extract the public key from the raw transaction like so:

https://bitcoin.stackexchange.com/questions/32305/how-does-the-ecdsa-verification-algorithm-work-during-transaction/32308#32308

If there never has been an outgoing transaction from the address in question it's pretty much impossible to get even just the public key.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: takemetothepub on February 01, 2019, 06:18:31 PM
I've got a 6GIG GTX1060 and can only get 2.1m/s

Tried loads of settings and can't get any higher than that, with default settings I get 1.3m/s.

Any idea what I should change the settings to?

My info is

ID:          0
Name:        GeForce GTX 1060 6GB
Capability:  6.1
MP:          10
Cores:       1280 (128 per MP)
Memory:      6144MB

Any help for -b -p -t would be great.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: dtoan1402 on February 12, 2019, 05:15:39 AM
Hi.
This looks like VERY GOOD piece of software, but I dont understand one thing :)

My tougths:

1.) Is it possible to recover part of private key, when I have valid address?

For example:
let's say one of my paper wallet is partialy destroyed, and I have lost 5 or more characters from private, like:

pub: 1DrqrF3JEYB9TXWymz4zGoEzM5i75JMLFB
priv: L3Wji4b***4Po3vo2gmi42Y2kbbxtnpAfQ5wJx11BgNr****8v3Q

Would be EXTREMALY usefull for paperwallet users!

Regards.
Is BitCrack have the option to recover address from a given 64 characters hex private key 'cause i have a paper wallet with faded private key but the address is still instact, it's look like this
Code:
privkey: *******4A875F34E5B11FA0453782E17F1B6FCBC77921614364E4AF62C7EF131
address (uncompressed): 1EGA57u7gQQTRgAy3D9q3n52Nw********
it's only lost 7 characters but seem possible to recover


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: arulbero on February 12, 2019, 05:03:17 PM
Is BitCrack have the option to recover address from a given 64 characters hex private key 'cause i have a paper wallet with faded private key but the address is still instact, it's look like this
Code:
privkey: *******4A875F34E5B11FA0453782E17F1B6FCBC77921614364E4AF62C7EF131
address (uncompressed): 1EGA57u7gQQTRgAy3D9q3n52Nw********
it's only lost 7 characters but seem possible to recover


(2^4) ^ 7 = 2^28 combinations, it is pretty simple to generate that number of addresses. But these keys are not consecutive, then you have to modify BitCrack or vanitygen. A Cpu is enough, 2^28 is a small number.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: BitCrack on February 12, 2019, 11:56:55 PM
Hi.
This looks like VERY GOOD piece of software, but I dont understand one thing :)

My tougths:

1.) Is it possible to recover part of private key, when I have valid address?

For example:
let's say one of my paper wallet is partialy destroyed, and I have lost 5 or more characters from private, like:

pub: 1DrqrF3JEYB9TXWymz4zGoEzM5i75JMLFB
priv: L3Wji4b***4Po3vo2gmi42Y2kbbxtnpAfQ5wJx11BgNr****8v3Q

Would be EXTREMALY usefull for paperwallet users!

Regards.
Is BitCrack have the option to recover address from a given 64 characters hex private key 'cause i have a paper wallet with faded private key but the address is still instact, it's look like this
Code:
privkey: *******4A875F34E5B11FA0453782E17F1B6FCBC77921614364E4AF62C7EF131
address (uncompressed): 1EGA57u7gQQTRgAy3D9q3n52Nw********
it's only lost 7 characters but seem possible to recover



This is possible.

Use these options with clBitCrack/cuBitCrack:

Code:
<your address> --keyspace 4A875F34E5B11FA0453782E17F1B6FCBC77921614364E4AF62C7EF131 --stride 1000000000000000000000000000000000000000000000000000000000


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: benjamin07 on February 13, 2019, 04:15:37 AM
This is a bit too advanced for me but I'm very interested if anyone knows of a 101 for dummies where to start from.

I have lost a few hundred $ in BTC on an Android wallet: i safeguarded the QR code before erasing the phone but that was only the wallet address. I lost the wallet.dat and therefore the private key. Is this software any help? I have a decent amount of GPU power but more AMD than NVIDIA.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: pooya87 on February 13, 2019, 04:26:32 AM
This is a bit too advanced for me but I'm very interested if anyone knows of a 101 for dummies where to start from.

I have lost a few hundred $ in BTC on an Android wallet: i safeguarded the QR code before erasing the phone but that was only the wallet address. I lost the wallet.dat and therefore the private key. Is this software any help? I have a decent amount of GPU power but more AMD than NVIDIA.

no, no software and no amount of GPU power exists on earth (combined) that can help you recover your private key if the only thing you have is your address. if that was possible then no coin was safe! people would have stolen other people's bitcoins by only knowing their address!

what you see here is a way to search in an extremely small range of numbers to find a private key that we know is already in that range.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: gembitz on February 13, 2019, 01:06:02 PM
This is a bit too advanced for me but I'm very interested if anyone knows of a 101 for dummies where to start from.

I have lost a few hundred $ in BTC on an Android wallet: i safeguarded the QR code before erasing the phone but that was only the wallet address. I lost the wallet.dat and therefore the private key. Is this software any help? I have a decent amount of GPU power but more AMD than NVIDIA.

no, no software and no amount of GPU power exists on earth (combined) that can help you recover your private key if the only thing you have is your address. if that was possible then no coin was safe! people would have stolen other people's bitcoins by only knowing their address!

what you see here is a way to search in an extremely small range of numbers to find a private key that we know is already in that range.

eventually "white listed" addys will be a thing? ;) lol


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: userghost on February 16, 2019, 01:36:53 PM
so I have a 1080 TI I would like to try at this. How do I generate a current address list? Did this a long time ago on LBC but forgot how. Also is there a way to check each private key generated to see if it has coin, or can I only search for the private key of X address?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: ETFbitcoin on February 16, 2019, 04:58:30 PM
so I have a 1080 TI I would like to try at this. How do I generate a current address list? Did this a long time ago on LBC but forgot how.

I don't really understand the question, but you don't need this tools if you just want to generate lots of bitcoin address.

Also is there a way to check each private key generated to see if it has coin, or can I only search for the private key of X address?

You'd need another software/library to check if generated private key contains coins, you only can search private key based on inputted bitcoin address.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on February 17, 2019, 02:55:42 AM
so I have a 1080 TI I would like to try at this. How do I generate a current address list? Did this a long time ago on LBC but forgot how.

I don't really understand the question, but you don't need this tools if you just want to generate lots of bitcoin address.

I think s/he is asking how to generate a list of addresses that have been used on the Bitcoin network.

As has been stated here before, for anyone who thinks they can "make a bit" by finding other people's funds: you're wasting your time, because the chances of matching the private key of a funded address by brute force is so small that we may as well call it impossible. Like, really, really, unlikely to happen; not in 100 years, not in 1000 years. (At least with current technology.)

This tool works well for its intended purpose - searching for 'puzzle' keys over a very limited range - but it cannot be used as a general purpose cracker. If cracking of arbitrary wallets was possible, the value of Bitcoin would quickly fall to zero.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: itod on February 17, 2019, 11:51:42 AM
so I have a 1080 TI I would like to try at this. How do I generate a current address list? Did this a long time ago on LBC but forgot how.

I don't really understand the question, but you don't need this tools if you just want to generate lots of bitcoin address.

I think s/he is asking how to generate a list of addresses that have been used on the Bitcoin network.

As has been stated here before, for anyone who thinks they can "make a bit" by finding other people's funds: you're wasting your time, because the chances of matching the private key of a funded address by brute force is so small that we may as well call it impossible. Like, really, really, unlikely to happen; not in 100 years, not in 1000 years. (At least with current technology.)

This tool works well for its intended purpose - searching for 'puzzle' keys over a very limited range - but it cannot be used as a general purpose cracker. If cracking of arbitrary wallets was possible, the value of Bitcoin would quickly fall to zero.

Anyone who would like to "try at this" to make some money should stop. The only reason to try this is NOT to make money meaning you are donating your resources, like electricity and GPU, to prove no one can make money on this. The whole point of the puzzle is to prove it can not be solved.

If it is ever solved we are all in big trouble, because BTC will be worth $0. Irony is that both ways you will never make money on the puzzle, if it is ever solved the coins you get will not be worth anything.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: kknd on February 17, 2019, 08:35:26 PM
benchmark


  • GeForce GT 640 = 9.11 MKeys/s
  • GeForce GTX 1060 3GB = compressed = 60.61 MKeys/s
  • GeForce GTX 1060 3GB = both = 46.93 MKeys/s
  • GeForce GTX 1070  = compressed = 109 MKeys/s
  • GeForce GTX 1070  = compressed = 85 MKeys/s (with 40k targets)
  • GeForce GTX 1070 TI = compressed = 80 MKeys/s (with 87k targets)
  • GeForce GTX 1080 TI = compressed = 1030 MKeys/s (with 40k targets)
  • GeForce GTX 1080 TI = compressed = 350.28 MKeys/s (-b 224 -t 128 -p 1024)
  • GeForce GTX 1080 TI = compressed = 350.28 MKeys/s
  • GeForce GTX 2070 TI = compressed = 805 MKeys/s (with 200 targets)
  • GeForce RXT 2080 TI = both = 631.57 MKeys/s
  • GeForce GTX 1050 TI = 64 MKeys/s (with 81 targets)
  • Tesla K80 = compressed = 39.76 MKeys/s
  • Tesla K80 = compressed = 68.21 MKeys/s (config)
  • Tesla P100 = compressed = 76 MKeys/s
  • Tesla P100 = compressed = 251 MKeys/s (config)
  • Tesla V100 = compressed = 174 MKeys/s
  • Tesla V100 = compressed = 603 MKeys/s (with 40k targets)  (config)
  • Tesla V100 = compressed = 715 MKeys/s (with 40k targets)  (config = -b 72 -t 512 -p 1024) =



http://kknd.com.br/etc/bitcrack.1.png
http://kknd.com.br/etc/bitcrack.2.png
http://kknd.com.br/etc/bitcrack.3.png
http://kknd.com.br/etc/bitcrack.4.png
http://kknd.com.br/etc/bitcrack.5.png
http://kknd.com.br/etc/bitcrack.6.png
http://kknd.com.br/etc/bitcrack.7.png
http://kknd.com.br/etc/bitcrack.8.png
http://kknd.com.br/etc/bitcrack.9.png
http://kknd.com.br/etc/bitcrack.10.png
http://kknd.com.br/etc/bitcrack.11.png


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: nc50lc on February 18, 2019, 04:00:54 AM
-snip-
The whole point of the puzzle is to prove it can not be solved.

If it is ever solved we are all in big trouble, because BTC will be worth $0. Irony is that both ways you will never make money on the puzzle, if it is ever solved the coins you get will not be worth anything.
Eh, Why does the Puzzle (https://www.blockchain.com/btc/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15) already has multiple "spent" outputs and still counting?

Yes, it's impossible to crack a randomly-created private keys but the puzzle's addresses were generated in a "simple" manner and with a limited difference
(from 0000000000000000000000000000000000000000000000000000000000000003 prv key in HEX onward)

Puzzle Prvkey List From: https://lbc.cryptoguru.org/dio (https://lbc.cryptoguru.org/dio)
Code:
Private Key                                            Address                            Compressed Address
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreAnchuDf  1EHNa6Q4Jz2uvNExL497mE43ikXhwF6kZm 1BgGZ9tcN4rm9KBzDn7KprQz87SZ26SAMH
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreAvUcVfH  1LagHJk2FyCV2VzrNHVqg3gYG4TSYwDV4m  1cMh228HTCiwS8ZsaakH8A8wze1JR5ZsP
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreB1FQ8BZ  1NZUP3JAc9JkmbvmoTv7nVgZGtyJjirKV1 1CUNEBjYrCn2y1SdiUMohaKUi4wpP326Lb
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreB4AD8Yi   1MnyqgrXCmcWJHBYEsAWf7oMyqJAS81eC 1JtK9CQw1syfWj1WtFMWomrYdV3W2tWBF9
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreBF8or94  1E1NUNmYw1G5c3FKNPd435QmDvuNG3auYk 17Vu7st1U1KwymUKU4jJheHHGRVNqrcfLD
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreBKdE2NK   1UCZSVufT1PNimutbPdJUiEyCYSiZAD6n 1Cf2hs39Woi61YNkYGUAcohL2K2q4pawBq
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreBR6zCMU  1BYbgHpSKQCtMrQfwN6b6n5S718EJkEJ41 19ZewH8Kk1PDbSNdJ97FP4EiCjTRaZMZQA
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreBbMaQX1  1JMcEcKXQ7xA7JLAMPsBmHz68bzugYtdrv 1EhqbyUMvvs7BfL8goY6qcPbD6YKfPqb7e
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreBd7uGcN  1CijKR7rDvJJBJfSPyUYrWC8kAsQLy2B2e 1HSxWThjiwbC4dJbXHMpBfwRenB12UguG5
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreBoNWTw6  1GDWJm5dPj6JTxF68WEVhicAS4gS3pvjo7 13DaZ9nfmJLfzU6oBnD2sdCiDmf3M5fmLx
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreBquB4Rj  1NokMRjkCGBmy8F3JRdX5XHyXqY8Yxvd4i 15wPJhwthAkBtUgx3qFEyCtnK7piuu6Xvr
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreC4p2u5o  1LWsLyY2j2mPtYcG9yG2bDFwTWryiJL6sp 1M9sZKsStVRZyBZSSVe13XMGRtCHkNj7VD
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreCAVyVnh  1Q2ndXEiSc1yevvPzEfQ4wuwKEhyyE1Nsj 18xiXDdYhapNJoAp4UAkJa1WZT9U9FmQiD
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreCHK2Zzv  1KgVr2GExouGLAeAt79KwxykCck4k9Cexk 1BS2vyPFUSDKfJKw35MyAAUvSzXpcBLgSJ
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreCMUnXUo  13xG3mC4TXUn8cRgqJG5eG9TDw4fFcztfE 1FZoTz4UBrfjpf7DdGGuLdPBqSMx65tKuy
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreCUtzTQw  18XrReT5ChW8qgXecNgKTU5T6MrMMLnV8H 19p7ktDbdJnmV4YLC7zQ37RsYczMZJmd6q
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreCXbRta3  1LwjY8QPCW46jXn79eeN5SfZDsYNB9qDj1 18FtYoEJipP5bCJnjgWdeeEbxSvozSjEUA
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreCh1de82  1BBwZVdBjoPxotHfrKLpHJBSy7vmc2pjex 1Ny3b8r8HhkQtwUBePqKdU31qBV1xWS64Q
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreCpWSv5Y  13zGBax475zUoLFatjye7Rp48vPrtiaeqs 1AmybvuPDrDpsqsgSzqbwALGcW1t6Yn9uN
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreCw2uZTA  1LWWyaRPtU7PHHEN67Zh8qhmZyAoaRubcw 1693NYwCPZYAdF1pYdVfrfCR6c9acpNGQd
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreD437Nay  19vxtDbLMNasSpbAEZd7va5Qge6d2zYWbp 1E6NuFjCi27W5zoXg8TRdcSRq84zJeBW3k
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreDAgeFqw  19WcSz4FxGH7CRqChvXaFW42UHnbQBicky 1GWqhXL1DGAEc6MVntAnmQe4GFnR9k2Ykd
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreDEUj22G   1MNagJqYUsWBD47QbsebCT2Lt7GwZtjkg 18JHgcWCoD1gbj6wpbDH5Us3HKaJozj6nt
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreDQbAmx9  145TcwDemMhjNiSAMxA5q14HTRuvNJFRx4 1KpKNLiZ4mQ6qdTwDrJBDLmBJDnD2n87NH
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreDSDY8dy  1JZC74Q76Ms8TSvB7H7Dc93SNRzRzNmYFc 1832sK2wWthm6z8vXaXTd8wUP4XaqrsPVu
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreDan2uta  1Gggh1qxKS7qSZJ8u3gKNqnSvHXQhQDyo2 12e2Zo4VFe2j4Cs3gru55H8JZ7PZXppHnd
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreDktNmBc  1LNLqCerQQ6j9iKs39VP6vNJHSpzNrFKJj 13zdFFdFn1LxfcXF8B6VBsnKxiLkZ7zBUU
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreDmLg88w  19HkpLyo2WQJ3SiCmFANVuoQvg4UAX43uG 1MFWqE6cZmmjvH22DEWmt1tKSms4iyASC7
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreDwUb9yY  1LYxTHbQLwmeTFa2dpYUFWwYZqoeJwAQmt 1Lh3oGDA7bxB7pQdJtgf29G3pf6rvxgNFU
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreE3Nwh9x  1DCYmXCRYXSPxsSFTRuveKRfqiCFmwNFbW 1DXNcbPEavwHQHtgPrjhkbG62f9SZBXp4v
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreE85b5kg  1KWj99Jwd9LGGC2Y1c9c4cmvWvYTQrLFVc 15MRQkVBF9crVPeHDjSEVEytCTVLJVGZSr
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreEGj3uXG  1GqHRfbwAtWc6zN4TL5xC5yNRwAXunfhUJ 1Q3pVMPLvKRNudhqz7uecd7C3iddUJLs21
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreEQTrFTY  1B7nMKLwh76G84u1xvk4CnhPK5YcPr2jvT 1HtFHz3q4fuhJj7paJAvtaNGmMbPnXRCa4
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreEYP1uta  1F83LVL8YKm4ugbNt2ePFVmsyoiHrx4NF7 1MY53uw7T3sLwL6FiGrM2LsiutSktmhSv2
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreEa9SGDP  1Cw4iTCkanJFZhLAQh3hBzD22QdBMrkPND 1FHVcojQZeZgw4dVFwAQiuArHdEw3p9j1Y
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreEhfUb47  1GgD7fHa8ZRczoMQagVzYc73ioTvoe3sZu 15N8R8QVgPWvBe6jBt3Rw492eoxZzGBvda
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreEnwTmuW  1EEp8e3dhdGc8MARVh9zPYqFGBdyGX6hxc 1N6RoUq8uYoJ8BKt7XHeruTJPgWMbi81gt
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreEttVnpm  17RjnQF8VWkcqyAHvY1QA1jNyx1xPVnB5d 1EtUHeLjh6oLgjCzyWJjgCtK7erRxArhJL
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreF5LqgkE  1Cyr9LQ7F3PZNjiJCcafLLh6F1RDireoCn 165dGfnEBRc9948oyFbhz5GSRibfTTrEzR
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreFAzJ4As  1Akt9SAP6Vvq1BfNcNWwvANgqXkNmZ2uz7 1BQTH1NYHXrQ8UDGcvD9q5b9pBTpx4muak
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreFGiZbKb  182WMwUZYz4vksjnhzU6GpCtKW3g3HKwhb 1KJyNjeZbGmH93D2yP36ViV8smdtAWv1E6
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreFMSs18A  1HGn3jxoSh8twi4mR3iaNmZr6pbHgjFJEg 1EMxdcJsfN5jwtZRVRvztDns1LgquGUTwi
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreFWRXmfT  1N6XDASWPttVf1yNCbZYgyE8trkM2k9RH7 1KknUTBcbmsPgkGuJANKeTu6UWW6R4AXkS
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreFeCCsFW  1Q9DQUn6aeWKEQFDVYSMNBjCcLYaQnRccB 15rDYUmonfHBL7efozxKwxY4L4JahvatuM
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreFjUrh8k  1MqWUyivo9sj323sirtbxZ1S23vPA36FDK 1LxerPZSoPQAH4iJFHJQPpbiCCsZzYpzQD
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreFtDpdAZ  1GTy3GAexCP74XVouxc7ZUP9s2qheQVDDz 136aNBmeiZY3Qq69BdBepmLTR9wQpr16eo
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreFufkfcw  1Baf2cr6Sh1va2mEjPnNMxeFtQ2p3u5bNe 12sR6SKoVv4wF75pAp2srPH73t9uXchgei
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreG7q5WCf  1EtppGCHU29KoJAwwU5sLdmeMim7GzBb5z 1LZ2gdtUzW9eUUEUXP4sGSHnsaCNYHuor3
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreGAk6qMH  18JVE1MSS7a2NEhtHJkxhwgvT4hLQYBw3w 1PitScNLyp2HCygzadCh7FveTnfmpPbfp8
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreGKdi6NZ  137DbqLHaL32CLg91FYStaGi99y3H5xHNS 1PHyTo7RGs9KMqa6xho8D2c8ezVcW726KV
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreGRmRFDZ  1GgWkqiKTYgZmWbx824AfKrHBLKHn71NL7 1MBnapr81FYkTBwcwGYwjEJw9fY9mHkQKf
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreGVpYN24  1Px5Kp4aZgPmVxJV9sWgLj6dEWcFMec9Fo 1HpEUoqUDw2k1KRiQskhLKUzkMUvBCQ8uA
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreGdtctZw   1GZnahwoL6K91sdzNEg1vxZ5LJogFSu1b 1P24SkyfwdPacGhAtDD8jqWf6H8NuqNZ2i
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreGhAGxmP   1L6qp71nqFbTTFTQYGQeLg94AkaeYJW1J 1B9dx79wc1wT29nrBGCXeB7Y6YRWwW1mGC
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreGv1DVzQ  1LPLZnAzj34AgehA56DvDahuyxinZgeM3e 1KWP2WSDLeCbkeWrSJG6B3ga61g9UFEink
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreGwFNuPr  1EYQRFJ1z1WzhPs17sZPzYnWxoYXUs8cKj 1N5SkxySaiSVFgWDXdBD7dWKQrHS6VVHfC
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreH48LE9C  1PnVcifB9EBwbaAauprqcucPgfUnrRLtWg 14qhMvWT1Fd7NFRgSgbEgHkm22pXmUi3X3
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreH9yDMyT  1DbZj2r2pSz8iq6MrMLENMusrar3YdhdaY 1HUHJ311k21Z6uaSqbV5bJBqeEV6ky9HQ2
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreHHanpkZ  16RwUYX9uRx3AttTa8zY6JvauPYSgLDoSy 1GVFSUerajQTuEJS1ewzd9KesAhNpVczRa
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreHP2DXbg  132vDcKDe96wL2GLLznueKnGVP4RnAX5xH 1AXSyzMK4Ft3HTmgmUQP62UBFwwCqyWwjg
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreHZ7dG6X  1HKvprhpBuuL5sbY6wkmgKcM97ggEG14Ab 1JnA9YikeoLtT4tVaBn4zNygFZWpVoneHN
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreHdeJUVG  1BHQRSk1X4ERn3UAMcsSgJzCkvw2wvE5CC  1GiA8LfZVP7J78yvC2qsvkH3NmAwLjBoY
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreHkaB6rR  15CHsSNH3SmEfoc2mau11z7inZiUZvRfyr 1M31Hk219DzWy8m1jfQ3jvvJa13SbaxaHZ
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreHsrkqUw  1FaxsybmpvrX4yDCt1R9mu2oGHpdpLzbkb 14raEyLewYMk4Xqg76xJQxEygnhWhx6mUQ
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreHyRyQVZ  1FHcYth4LRJMwNx2y8NR5DH7sYCiVzXs3Y 1AT4ES3ee1N6iBzzbdK8xvcAV3CBTRKcbS
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreJ58DM42  1QAALUJNskZWEbvwKXoTteowgs9xGGeAZR 1AUVEbt1um1kVPADWcgdCxabVhquHZsT36
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreJFuEycp  1B8EsE44dqKSbVdqgnd9aTQex7r4G6Bw1P 18939AFStuaLPGuuh9Eus2BYoswcPXSSmF
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreJMps1fr  1C77qaBvJ2mGAb9QmcuBHrD6sbYy9V8Rc7 1KPnwTRu1GCSjNTrZTLExcnbGbXweGWXuF
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreJQmdp3Y  1KFLggHezq3kiAtpaKMeQPcnoWsXuZHRyn 1NzpgnC9YtGDQbSU1gwAYJrrJT7xUmAbD4
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreJZrCr3e  17SNLYKhp1sacBNRQRJyfmh1ZLHdFYwhNC 1DqCvD3EhP8JJ1gjtezBLmM2ucN41P64hY
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreJf8B1SD  1Pnd4E94wguWsTWw8iGhyjdJ4FHUouTu7K 1JhZxqo9fSiTNt2tW2mZ7dnZzZhmTvVDyc
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreJkEG3cV  1PffYARJERxj2Y3wUpLY8LJ9hcRRRCkB5Z 1Eyyze6zJCKYXWXsmvRxFEyJZBeAPrSp5s
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreJwwNRRr  14sNbmEhgiGX6BZe9Q5PCgTQT3576mniZt 1JYHzX3ndZEcnjrWSQ9VC7324TJ9BAoGy4
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreJxh5nsg  1BLXTrgdmZfjk26ULK5FzdY9hHYcT9vGkY 1FGowKezKWnmh9Ls9PpUq9sNBYFX3Nz47A
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreKA9Sz8L  1AdaHxALc5jknZVmNtcduvkD33WBv3sX6i 1CoaYYNG9XDHjWcDDubUWoRoZXwNMEjxLK
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreKD614Nu  1ESJVfV5UVERkWgVNfMjsLwJT88yMJHi8R 1McVt1vMtCC7yn5b9wgX1833yCcLXzueeC
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreKLMhKmG  1P4C2RHfYZjU2Eca3mAwcHFwnYHcM4PxLn 1926m9AThSrsJ5hW6fJXSphvUgwePHZ8mz
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreKUmwqXK  1GX2tP5ds3LyFypjD1wnKapvwV1mgZos3G 1BXNXy36RFmnC5oKCWTCy2iJaZYXiB1N4B
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreKamq6aB  1BoH6QH9n2pftQYRU5kganogxaNtTCo5cJ 1AqrfBgT8fMPCmeu3kwEwXbDBYkG9stjRZ
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreKeQXCm1  1L2YxutDBfZ33e4mM7gxoDo7t8rj9UxB8z 1DpPdfN8kL9XGArEw4HfGNJDcEELyxVf5u
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreKnSXYds  16Uhv71wNqMeaTW6YZQ8L3SaeVuomoD3dX 1H2GoFDiFjmWitZMF46oGU1d6HtxHpaBQw
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreKuhp1DY  17fGEEDHbspV7xAxpjhsFFK4tkgfvonyEE 1K9A72aRqK1LKqu2rcowK5bHrqLeb1YnVB
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreL2F4Gjy  19tbjBguyRGMSq9EVSNhrCA23ZUx4Cgx23 1EcSNaF3RNNgJ1JdBHgADbYhmTdBsaLXHj
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreLAxEBPw  1FaFkutPqwakXYwS4umygTAa7ozUkKfxSp 1CvC4Hp8vend9hM9Fvrvc7ET8XPW39UtNN
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreLGUF4YR  1CKAkV2EVrPFF8oqKvCPGLvBVJ63wpChmD 15Y6VpFsK7RwRtjFkA1ZUceeT4Kv8zYSxX
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreLKXuCN4  1BsyFuJSKj58dmWXSt2EeE5PAp2EmyYwnJ 1HizJ1EUKsVnmbpbpWa4xuijDE8zf5Tamw
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreLRLivrj  1B5edeYL7WEmhkKP3FEkURjB9ZXVrc3FCQ 14jFzKqinNHjegYfF4FcpCxUs9PQK5WGfV
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreLch3pDc  1Mv7xTXisEUQZ4aeQmDmmYKqLVw3PoNGA1 1K2y6MDHB2tnp6MG4iMCbDMzwxpLTC8LmN
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreLem9Za7  15FPq6oDDn2sjtMZfnMn2QhvR7XeEMDYQS 1BfYrUZrZQZUfyaxQrc7hyjjpHadmHrKkJ
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreLp8VN4c  1MAieZnEeibHBCnSitY7ujKs4Gfi2RuZDy  1PB1BR8Xi6JybZ9x6DrrcUuDvnsqRpHac
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreLwB7DbW  1P1Dur122Pzey73fFyUgfSbcxDdedSSm4z 142FavKdwRb42h3Ziu4sZ61qFJTANjN5kP
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreM2VQnPJ  189mvaHbMhvah3JYYPk9TVZTBp4bDyZWxm 13VDs9j5XAG1zWuG7fE9C1GkypoSNP3MVM
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreM9y1taS  1ADtEbG5UAnrqSTz8CssEPXFLYTM6mfCiA 13uR4aqk9EKcWFznqfFrJdmsbYCXqmyxQ6
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreMEFkFWC  1LtUqEjvsTh4B5GtDmBV8upuRD6QcRTeCx 1Hwk14ik1TBtoghS2ByaiU6rnN8Qckrxxb
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreMQiR4w7  157RMZhbBLC1wucv3jxQqqHjbKezL1yy7g 1LutqRAJkLqS9J81SfrPySJNnBT2cBdvEt
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreMVM6PNC  13ogqrMb6hJK1tuD6xhiVzGepr3sWLUQJD 1JtkuYJMG2MGycQiAczUT1HQu4hka3q47q
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreMbi1WL5  1BiXAVzed7Ue5kG2ehnsWcfqQjdMcY2hqu 1NiTAKAVa3H6kqF4EUJmr87wSk1hahWd8D
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreMjo5bB4  17zHuCFs5WNBkFfH38RDN8NDCUZv34aUwE 1Df3nPzpQZaiViYvpEca5TeRewSJhUQeZy
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreMrbQN7V  1BAjqraowRUrDXbruNShnQ32Fwiy5m5M5v 1Kz7e3MBHzzq2XQiHgRgwcEuM9AbUVhLa9
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreMuv36HW  18CW9Zv8rC8UcLSMHJGZSJ2uTHcqBEoa7D 178sjmHYnWxjJtcH3StVeNNaYC3Q5TJy37
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreN3RLkWA  1PcTuSTm1UGK58YiuDir58ED7KnrNMUjpr 1NDTiygBwjhUwsK9n9qJqrKitDURg4csxP
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreN7qoa75  16g79Dj7FiAZ964LxqcoBFNjFbL6kJoisX  1GL37AoxoUj45fPNYf8Dq5CTncyRYLqo7
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreNL5cPwC  134hoUfpzKWFqLMgrELRnERQemU3FAiY3v 14zo8Big6cvCgDLqWTaKogBv4q6UBocrQN
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreNNCT2yY  1HxpsY48MpH4kvi2H23vDwdaBSa2paSipX 146mRcaq9xpYaMmzXYYbiLGJE5EGBbTmaA
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreNXqEJTk  1DerC5SzMPgBN4o6yaxcRZ7TMBCDus6nLT 1LpPxoDsckedWhBHppsbJciGSFH55oSUb2
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreNdjkc6L  1KeF7jzYkq8FdSnKwYLBEc3uJH7fwaxE8S 1PGL7QGU4vaGaBSHJG22CiuvKWXogkWd2v
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreNkcfT1c  18zQpC5g54xA6mWeLi8cucQjykHVNoeSJH 1FKP69FWiWEsZPr12aQRGBUBiXi49D4PsY
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreNqaKH8Y  1PFwKya5dQFrxE9XZ9LV24ASaq5v58WLEe 15wzWJ1ugjTsNi2P1LXrzLwdvrAfd5vcFJ
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreNxQWW7Y  18wkBZj5sTSUPT9Vvw66eb99ZvBA7STvBg 1Dxvnn9RX4gnSoNmSDn786zAWFkp2y2q7u
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreP4J74KK  179NZfVhPXssS42hs2o9ANABMcReQiovym 1NRwpE13WLhBSLRoDvEziu6iVntkRHpxpy
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreP9WciJJ  1Q4rfQLQF9yKN2Ay2NNBwLNPSy4sDbwNnd 17ZaizPFAB76bVXXDZNMHunzeoFjrwGtS2
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsrePJzmYK5  1MsUtV4HwbEX6pnPa1cAfzJTn7oNufW5p4 1G71CVQfwZgiNBW8V3xtYoBEnTbN9Gir36
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsrePTVqv3S  1EWCz4DrTShf9vFThywg2WfDyrdV4Wy2SN 18C8KbniMq6AMp4nCp6BChQDiPS5AgbS15
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsrePWp5Mt9  1LvbRi7aCjENKCzDMTsaoZ8sKsg1B9CqLQ 1HfvV6dgKqeLdLWKFU6RUHz5x6xyW6Ybuv
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsrePdw4eNk  1MNViv4dYbLkxH5UyiVxs9AZqYbPBwz995 1Hsomu9bgA6nprEba9n5FDiWntxCFuAp8t
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsrePng1DKR  13TQKnr3psXk7Zw9xi6hsrJcdqKRLidhux 19mtPnAJtpDb8gyHkKbAULJr25WFDBbT1o
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsrePsqVrAf  16NUWSmWh7K6e885kybvaDdBoFQPZeDUpy 13GiZRTmt4aYFE5rcjcKVPim4XXCKkwqJi
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsrePxLM2Uo  1Pt8N7xSic1oEKE8pPDEJ96KcnVFU69HRp 18Bus1K9FrT9A3ZEvvRf3zXFmW74yDmzBq
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreQ8Arh4e  1CSPhHszH4S4Hhrrx8ZdmJWC3GLTpuhsur 1DDhKRv1itpHoAFiCJuik2Zv3AjtX7sDCd
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreQDpvAKR  19JJNLkZkaV9Z6SpxUbPuJ7X6hBsgsQ8K6 1PFUoroEpx9ezgUTYJj7TfCTf5B5WANLs4
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreQM87c2m  1BfGgoPFwehgJxZKHnvm3ytCNv5ApD7vTu 1DnCXwubVKYBUM6cpHga6UFcPYWdcjYMdE
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreQTdvJta  1NwhxtuUW2dg7RPkaypDpLW9JS2dqfEzNb 15AJXitn6DuSC6ugSPqdsv2MxcNYdgVcbC
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreQYt2Gms  1HHKanEL28o5Nrui8byqTNwFtWpdVEPzw5 141fTonryMQxmkKcba9FstmyQv3tqdBzTY
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreQbpfitE  1KmobiUwSFcKyDX2z1Ss2TVL5yLq2BnxrS  1FFYArxgMbCLi366pCrgdXfzGBBMGssX9
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreQi1XfkP  1QCoHemDLMTaSJb7heXUHLsu6YPyu5iDEv 12muChUsDE5KRdkFDKhRxSAHe5JD9VoPA9
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreQuyVxqv  163bgHt747rfMKf7tM6XEoCzhKbvrYgZ6N 1EzjkMU8iGQThYVHdMSZGHwJNNH7DCg59v
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreQyNNN1W  1FB8cZijTpRQp3HX8AEkNuQJBqApqfTcX7 173M3yw1P1SfiPiDHABLGi5LLBAMohVQ7h
+ 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreR42AY81  1EoXPE6MzT4EnHvk2Ldj64M2ks2EAcZyH4 1CAE6ej7VyAhgTtL1AYKTEByRJaCZKg8XM

If you look at the puzzle transaction's link to a blockexplorer (https://www.blockchain.com/btc/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15) with "address meta", it has a name which suggest that one of its purpose might be for Promotion of that (now deadlink) "Bitcoin Manual Mining Helper".


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on February 18, 2019, 05:27:27 AM

Puzzle Prvkey List From: https://lbc.cryptoguru.org/dio (https://lbc.cryptoguru.org/dio)

With 904625697166532776746648320380374280100293470930272690489102837043110636675 pages, I'd say that the entire private key space, not just the special puzzle keys.

Here are the puzzle transaction keys found by LBC (is it still running?) : https://lbc.cryptoguru.org/trophies


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: kknd on February 18, 2019, 07:04:22 AM
Quote
[2019-02-18.07:03:10] [Info] Compression: uncompressed
[2019-02-18.07:03:10] [Info] Starting at: 0000000000000000000000000000000000000000000000000000000000000001
[2019-02-18.07:03:10] [Info] Ending at:   FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
[2019-02-18.07:03:10] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-02-18.07:03:10] [Info] Compiling OpenCL kernels...
[2019-02-18.07:03:10] [Info] Initializing Tesla V100-PCIE-16GB
[2019-02-18.07:03:15] [Info] Generating 33,030,144 starting points (1260.0MB)
[2019-02-18.07:03:20] [Info] 10.0%
[2019-02-18.07:03:20] [Info] 20.0%
[2019-02-18.07:03:20] [Info] 30.0%
[2019-02-18.07:03:20] [Info] 40.0%
[2019-02-18.07:03:20] [Info] 50.0%
[2019-02-18.07:03:21] [Info] 60.0%
[2019-02-18.07:03:21] [Info] 70.0%
[2019-02-18.07:03:21] [Info] 80.0%
[2019-02-18.07:03:21] [Info] 90.0%
[2019-02-18.07:03:21] [Info] 100.0%
[2019-02-18.07:03:21] [Info] Done
[2019-02-18.07:03:21] [Info] Loading addresses from '1.txt'
[2019-02-18.07:03:21] [Error] Invalid address '3645N22DDswRxV4BQGbuBrgHCAYUmzcHU6'
[2019-02-18.07:03:21] [Info] Error:


but

https://www.blockchain.com/btc/address/3645N22DDswRxV4BQGbuBrgHCAYUmzcHU6

???


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on February 18, 2019, 07:50:57 AM
[2019-02-18.07:03:21] [Error] Invalid address '3645N22DDswRxV4BQGbuBrgHCAYUmzcHU6'

but

https://www.blockchain.com/btc/address/3645N22DDswRxV4BQGbuBrgHCAYUmzcHU6

???

An address starting with '3' is a pay to script hash address, which is based on a script and related data, rather than (simpler) hashing of a public key. I'd guess that BitCrack is only able to brute force Bitcoin addresses starting with 1.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: CreateCryptoCo.in on February 18, 2019, 11:47:50 PM
Does anyone actually made more then a 100 bucks?
i bet you can make some cash on stuff like brainwallet things, cuz ppl dont normally think twice before creating wallets.


Would be fun to know if it actually works(and not just eating power)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on February 19, 2019, 05:53:48 AM
Does anyone actually made more then a 100 bucks?

Doubtful. This is not a general Bitcoin cracking tool. You will not 'accidentally' find funds. If it was that easy, everyone would be doing it, and Bitcoin (in its current form) would cease to be valuable.

i bet you can make some cash on stuff like brainwallet things, cuz ppl dont normally think twice before creating wallets.

Here's a separate thread on SHA256 brainwallets. There are 20000+ known brainwallets, but the tl;dr is that if you're looking to steal funds you are wasting your time.

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


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: pooya87 on February 19, 2019, 06:00:06 AM
[2019-02-18.07:03:21] [Error] Invalid address '3645N22DDswRxV4BQGbuBrgHCAYUmzcHU6'

but

https://www.blockchain.com/btc/address/3645N22DDswRxV4BQGbuBrgHCAYUmzcHU6

???

An address starting with '3' is a pay to script hash address, which is based on a script and related data, rather than (simpler) hashing of a public key. I'd guess that BitCrack is only able to brute force Bitcoin addresses starting with 1.

ever since August 2017 this statement is not always true. with introduction of SegWit you have the option to use a new way of creating addresses which is still using script but in case of P2SH-P2WPKH your address starts with 3 but you are using the hash of your public key as your "script".
(the address he posted seems to be the legacy P2SH one though).


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: elplum on February 19, 2019, 03:40:19 PM
i dont understand

https://www.blockchain.com/ru/btc/address/1BYxpKKfTcZN9H5Jziqab7pySwaMcziZbL (https://www.blockchain.com/ru/btc/address/1BYxpKKfTcZN9H5Jziqab7pySwaMcziZbL)

1BYxpKKfTcZN9H5Jziqab7pySwaMcziZbL - compressed address or not?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: ETFbitcoin on February 19, 2019, 03:56:15 PM
i dont understand

https://www.blockchain.com/ru/btc/address/1BYxpKKfTcZN9H5Jziqab7pySwaMcziZbL (https://www.blockchain.com/ru/btc/address/1BYxpKKfTcZN9H5Jziqab7pySwaMcziZbL)

1BYxpKKfTcZN9H5Jziqab7pySwaMcziZbL - compressed address or not?

You can't determine whether it's compressed or not only by it's address. You would need public/private key of that address.

- Uncompressed public key has 130 character
- Compressed public key has 66 character
- Uncompressed private key have prefix 5
- Compressed private key have prefix K or L


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: elplum on February 19, 2019, 04:18:13 PM
What config need for bitcrack for brute this address?

-c - compressed?
-u - uncompressed?
both?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: ETFbitcoin on February 19, 2019, 04:26:33 PM
What config need for bitcrack for brute this address?

-c - compressed?
-u - uncompressed?
both?

Since we don't know the address comes from uncompressed/compressed keys, you should use both parameter. But most wallet generate compressed key/address these days.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: nikitios on February 20, 2019, 01:02:22 PM
privkey: *******4A875F34E5B11FA0453782E17F1B6FCBC77921614364E4AF62C7EF131
address (uncompressed): 1EGA57u7gQQTRgAy3D9q3n52Nw********

uncom: 1EGA57u7gQQTRgAy3D9q3n52NweeS9UgGc
compr: 1Kyn3487XcJ26LeXEzCFMZcgyWXeYR47Nk


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: elplum on February 21, 2019, 09:58:11 AM
What optimal settings for 1080 Ti (both mode) and 5, 10, 15k addresses?

Thanks!


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Stryfe on February 21, 2019, 01:47:40 PM
I have read thru a lot of the pages and I have said it before and will say it again -  I am confused as to what the goal is here? Is it just to find the addresses? or is the actual attempt here to find a way to take btc from a wallet?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Indamuck on February 21, 2019, 03:41:25 PM
I have read thru a lot of the pages and I have said it before and will say it again -  I am confused as to what the goal is here? Is it just to find the addresses? or is the actual attempt here to find a way to take btc from a wallet?

It is a tremendous waste of power and time spent unless you have a partial key or some other known parameters about the key.  Obviously if cracking truly random keys was even remotely possible bitcoin would be worthless.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: ETFbitcoin on February 21, 2019, 03:57:22 PM
I have read thru a lot of the pages and I have said it before and will say it again -  I am confused as to what the goal is here? Is it just to find the addresses? or is the actual attempt here to find a way to take btc from a wallet?

The goal depends on the one who use it. For example OP/the creator create this software to solve Bitcoin puzzle.

There's 2^256 combination of private key, so take/steal from an address is very unlikely goal unless people don't know this fact.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: arulbero on February 21, 2019, 04:07:27 PM
I have read thru a lot of the pages and I have said it before and will say it again -  I am confused as to what the goal is here? Is it just to find the addresses? or is the actual attempt here to find a way to take btc from a wallet?

The goal depends on the one who use it. For example OP/the creator create this software to solve Bitcoin puzzle.

There's 2^256 combination of private key, so take/steal from an address is very unlikely goal unless people don't know this fact.

Not completely true.

It would be enough to try "only" 2^160 combinations (for example from key = 1 to key = 2^160) to be able to move the funds from all addresses (P2PKH utxo).  With about 2^135 combinations you should get access at one address with funds. (1 random)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Stryfe on February 21, 2019, 04:16:59 PM

Not completely true.

It would be enough to try "only" 2^160 combinations (for example from key = 1 to key = 2^160) to be able to move the funds from all addresses (P2PKH utxo).  With about 2^135 combinations you should get access at one address with funds. (1 random)

and that is what concerns me - theft. while improbable I find it disturbing that it is the goal of a few on here - to steal.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: ETFbitcoin on February 21, 2019, 04:28:28 PM
I have read thru a lot of the pages and I have said it before and will say it again -  I am confused as to what the goal is here? Is it just to find the addresses? or is the actual attempt here to find a way to take btc from a wallet?

The goal depends on the one who use it. For example OP/the creator create this software to solve Bitcoin puzzle.

There's 2^256 combination of private key, so take/steal from an address is very unlikely goal unless people don't know this fact.

Not completely true.

It would be enough to try "only" 2^160 combinations (for example from key = 1 to key = 2^160) to be able to move the funds from all addresses (P2PKH utxo).  With about 2^135 combinations you should get access at one address with funds. (1 random)

True, but :
1. I was talking about private key combination
2. You still need to generate public key (whether it's compressed or not) from generated private key just to check if the public key has been generated previously
3. There are 4 address type (legacy, legacy P2SH, Bech32 and P2WSH Bech32) and software need to check each addresses contain bitcoin

and that is what concerns me - theft. while improbable I find it disturbing that it is the goal of a few on here - to steal.

There's bigger concern than brute-force, such as :
1. Bad PRNG/CSPRNG
2. Vulnerability within wallet software (such as private key or wallet password is kept on RAM)
3. Weak wallet encryption


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Jean_Luc on February 25, 2019, 04:26:57 AM
Hello,
If you want to attack SecpK1 key you'd better try Pollard rho on "reused" addresses (you can get the public key coordinates). It will drastically improve your chance of finding the private key but will nevertheless remains very unlikely.
The technique is very well described here: https://arxiv.org/ftp/arxiv/papers/1607/1607.05901.pdf


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Jean_Luc on February 25, 2019, 10:35:00 AM
I just compiled this tool and I reach ~15MKey/sec on my hardware using compressed key only (after playing a bit with options to find optimal setting).
I reach ~25MKey/sec with VanitySearch using compressed key.
First I think that trying to brute forcing bitcoin addresses is utopian and the performance seems far from optimal...
https://github.com/JeanLucPons/VanitySearch



Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: SuffaBit on February 28, 2019, 11:33:24 AM
how to start at the same time 3 RX570  ???


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Lolo54 on March 01, 2019, 05:57:52 AM
it would be great to also be able to use / associate the CPU to help the GPU a little as vanitysearch allows to allow an increase in speed


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on March 20, 2019, 07:21:50 PM


do you have an open source software ?

can you find the bounty transactions mabey faster with your strategy ?
[/quote]

Yes, sure I give out all the source to free to people in the third world, mostly India; The web-site is www.inflection.top, the github github.com/btc-room101, just tell me what you want,

I have 100's of tools I have written since 2012 when I started working on Bitcoin, most of the stuff is in python, and the gpu stuff of course is in C++;

I'm not inclined to put 100's of packages on github, so tell me what you want, I could make a list of what I have, best here is list what you want, and I'll tell you if  I have it, since I have done this crap for 6+ years ( hack bitcoin ), but I have been hacking crypto for 30+ years, so I have lots of code

I don't know what people want or need,

I think my site www.inflection.top discusses my areas of research, and the code, normally what I have done is from that site people ( usually students in 3rd world countrys ) send email and request code, I have found in the past that the 'guardians' of bitcointalk don't want anything real, they go out of their way to protect bitcoin, but as an intelligent person knows, knowing this stuff makes you strong, but instead the community prefers the continue the cannards and lies that has made them 'virtually rich', not unlike the little-prince ( a book ) where a man owned all the stars.

I would lke to see BITCOIN stronger, but the PTB want to keep it weak, just like FB,GOOG,TWITTER there is a concerted corporate effort to take away all notions of privacy and security. Here in BTC they tell us its secure, that its private, and anybody who steps forward with the truth is censored. This will be the downfall of BTC that it is over-lorded by imbeciles. In the meantime the RUSSIANS, CHINESE, and INDIANS will leave the west in the dust.
[/quote]

Hi btc-room101 !
Can you help set up my computer for better speed?
If "YES" - write to me in PM


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on March 22, 2019, 08:22:23 AM
Hi btc-room101 !
Can you help set up my computer for better speed?
If "YES" - write pls to me in PM
I cannot find yor web-site  www.inflection.top
This web-site  www.inflection.top  worked ?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on March 28, 2019, 01:20:48 PM
Have a multi GPU version running 170mKeys/s on RX570 or 150mKeys/s on GTX 1060, a rig with 6 runs just above a billion/sec.

Windows 10
Your speed is double compare with mine.1060 3G win 7, 16G ram, core i5 ivy.

Tell me - can I use the CPU, not the video card (for software clBitCrack.exe )?
If "YES", then how to turn it on?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: RobertPaulig on March 29, 2019, 01:01:38 AM
This is the maximum that I can get with these settings. But this is a very low speed compared to VanitySearch. There is a speed of about 960 mk\s. What am I missing? Or is it the ultimate dream?

Code:
cuBitCrack -b 224 -t 128 -p 1024 1FshYsUh3mqgsG29XpZ23eLjWV8Ur3VwH
GeForce GTX 1080 4627/11264MB | 1 target 340.08 MKey/s (18,115,198,976 total) [00:00:51]

Video GeForce GTX 1080ti


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Lolo54 on March 29, 2019, 03:53:01 AM
Test the following parameters -b 36 -t 512 -p 2900 or only -p 2900 or 3400 Otherwise check using cudaInfo.exe for the best settings for your configuration.
Regarding the performance optimization of cubitcrack compared to vanitysearch it is not so comparable in that their usefulness is different but also because the author here is no present unlike on the vanitysearch file. It is obvious that cubitcrack could be very much optimized in terms of speed of execution by using both the CPU and Gpu but also in its calculation way that could without worry be increased by 50% ... this is not However, it would in no way endanger private keys farther than the one already discovered even if the beach was known for it must be used another way of doing that brute force. Vanitysearch even if much faster is absolutely not done for that either!


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on March 29, 2019, 04:40:29 PM
And if a weak graphics card on a laptop?
What can be the optimal settings for the AMD Radeon HD 6520G ?

AMD Radeon HD 6520G


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Lolo54 on March 30, 2019, 01:12:09 AM
And if a weak graphics card on a laptop?
What can be the optimal settings for the AMD Radeon HD 6520G ?

AMD Radeon HD 6520G
try this
-p 400 -c -u 1Dg98F1x115vkgL9cHh4fqhpQpY2dXz83u


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on March 31, 2019, 10:38:30 AM

AMD Radeon HD 6520G
try this
-p 400 -c -u 1Dg98F1x115vkgL9cHh4fqhpQpY2dXz83u
[/quote]

Thanks Lolo54 !

If has started the software clBitCrack Starting at: 0000000000000000000000000000000000000000000000000000000000000001
Now she has checked up approximately 37,863,817,216 total
Whether it is possible to put this software (clBitCrack) on a pause, to check up as the position (Starting at) 0000000000000000000000000000000000000000000000000000000000000001 has changed, and then to continue job by this software clBitCrack?



Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on April 07, 2019, 06:30:37 PM
Dear connoisseurs!

I to try to test the software clBitCrack on a mine laptop
For this purpose I have found any in open access four bitcoin of the address

Address 1 - 1HZwkjkeaoZfTSaJxDw6aKkxp45agDiEzN
Private Key - 5KYZdUEo39z3FPrtuX2QbbwGnNP5zTd7yyr2SC1j299sBCnWjss
keyspace - e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

Address 2 - 15UYGXPt1ak9WVGLgjmi63gqyGg3RZUZ7N
Private Key - 5KYZdUEo39z3FPrtuX2QbbwGnNP5zTd7yyr2SC1jkxg4jqxnJWV
keyspace - e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991c7852b855

Address 3 - 181hHek9W6CMFcav1jSrckijGFHdrcb4T7
Private Key - 5KYZdUEo39z3FPrtuX2QbbwGnNP5zTd7yyr2SC1joobVycGDGJ9
keyspace - e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991c8952b855

Address 4 - 15cDeUTgdHCoxDscMgowX5CVMrwpNUqfWf
Private Key - L4rK1yDtCWekvXuE6oXD9jCYfFNV2cWRpVuPLBcFwdLVekkxBLsb
keyspace - e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991c8962b855

Mine laptop works slowly, therefore I selected these addresses in a small range keyspace
From - e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b845
Up to - e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991c8962b865

So I have written down the task in a command line

**
C:\CARD\clBitCrack.exe -c -u --keyspace e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b845:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991c8962b865 1HZwkjkeaoZfTSaJxDw6aKkxp45agDiEzN 15UYGXPt1ak9WVGLgjmi63gqyGg3RZUZ7N 181hHek9W6CMFcav1jSrckijGFHdrcb4T7 15cDeUTgdHCoxDscMgowX5CVMrwpNUqfWf
[2019-04-07.09:57:58] [Info] Compression: both
[2019-04-07.09:57:58] [Info] Starting at: E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B845
[2019-04-07.09:57:58] [Info] Ending at:   E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991C8962B865
[2019-04-07.09:57:58] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-04-07.09:57:58] [Info] Compiling OpenCL kernels...
[2019-04-07.10:10:30] [Info] Initializing BeaverCreek
[2019-04-07.10:10:30] [Info] Generating 262,144 starting points (10.0MB)
[2019-04-07.10:10:48] [Info] 10.0%
[2019-04-07.10:11:05] [Info] 20.0%
[2019-04-07.10:11:22] [Info] 30.0%
[2019-04-07.10:11:39] [Info] 40.0%
[2019-04-07.10:11:56] [Info] 50.0%
[2019-04-07.10:12:13] [Info] 60.0%
[2019-04-07.10:12:31] [Info] 70.0%
[2019-04-07.10:12:47] [Info] 80.0%
[2019-04-07.10:13:04] [Info] 90.0%
[2019-04-07.10:13:21] [Info] 100.0%
[2019-04-07.10:13:21] [Info] Done
BeaverCreek      16/1655MB | 4 targets 0.15 MKey/s (4,581,490,688 total) [09:09:54][2019-04-07.19:23:21] [Info] Reached end of keyspace
**


In a result I have received such - [Info] Reached end of keyspace

QUESTION - why the software clBitCrack after a closing -up has not written to the information of any concurrence to addresses?
What I have made incorrectly?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Lolo54 on April 07, 2019, 11:42:54 PM
QUESTION - why the software clBitCrack after a closing -up has not written to the information of any concurrence to addresses?
What I have made incorrectly?
Try to do that and your problem should be fixed and you should increase your speed
create a text file in C: \ CARD that you name "resu" or otherwise and a second text file that corresponds to the file in which you mention all the addresses you want (one address per line) the syntax is important otherwise you will have a error message call this file "check"
so it will load all your addresses and as soon as it will find one you will be able to find all the details in your file resu
tapes the following commands to launch
-b 36 -t 128 -p 800 -c -u -i check.txt -o resu.txt --keyspace e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b845: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991c8962b865 
or only
-p 900 -c -u -i check.txt -o resu.txt --keyspace e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b845: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991c8962b865


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on April 08, 2019, 06:50:05 PM
Constantly I gives out a [Error] Unable to open 'check.txt'

***
C:\CARD\clBitCrack.exe -b 36 -t 128 -p 800 -c -u -i check.txt -o resu.txt --keyspace e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b845:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991c8962b865
[2019-04-08.20:28:04] [Info] Compression: both
[2019-04-08.20:28:04] [Info] Starting at: E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B845
[2019-04-08.20:28:04] [Info] Ending at:   E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991C8962B865
[2019-04-08.20:28:04] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-04-08.20:28:04] [Info] Compiling OpenCL kernels...
[2019-04-08.20:33:52] [Info] Initializing BeaverCreek
[2019-04-08.20:33:53] [Info] Generating 3,686,400 starting points (140.6MB)
[2019-04-08.20:34:24] [Info] 10.0%
[2019-04-08.20:34:58] [Info] 20.0%
[2019-04-08.20:35:27] [Info] 30.0%
[2019-04-08.20:35:57] [Info] 40.0%
[2019-04-08.20:36:27] [Info] 50.0%
[2019-04-08.20:36:59] [Info] 60.0%
[2019-04-08.20:37:29] [Info] 70.0%
[2019-04-08.20:38:02] [Info] 80.0%
[2019-04-08.20:38:31] [Info] 90.0%
[2019-04-08.20:38:59] [Info] 100.0%
[2019-04-08.20:38:59] [Info] Done
[2019-04-08.20:39:00] [Error] Unable to open 'check.txt'
[2019-04-08.20:39:00] [Info] Error:
***


I somewhere read about the decision of this problem.
The man created a text file with addresses with expansion "txt", but the software clBitCrack could not open this file.
Then the man changed expansion of a file "txt" for another (but I do not remember on what)
After that changes the software clBitCrack could work without a mistake.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on April 09, 2019, 06:18:51 AM
P.S.
And matters in what coding to create a text file with addresses?

ANSI
UNICODE
UNICODE BIG ENDIAN
UTF-8


At me a text file with addresses in the coding UNICODE


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Lolo54 on April 09, 2019, 03:04:45 PM
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



Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on April 09, 2019, 06:56:49 PM
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


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Lolo54 on April 09, 2019, 07:53:33 PM
it should work if the file is placed in c: \ card


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: SuffaBit on April 16, 2019, 11:00:55 PM
How much addresses i can add in one time?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Lolo54 on April 18, 2019, 12:10:37 AM
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


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: anu1908 on April 18, 2019, 03:27:45 AM
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.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: SuffaBit on April 19, 2019, 01:24:53 AM
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?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: gaz1 on April 19, 2019, 08:33:31 AM
how to open options?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on April 24, 2019, 06:17:51 PM
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 ?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Bl@cK on April 30, 2019, 11:56:57 PM
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


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Lolo54 on May 01, 2019, 08:51:42 AM
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


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: kknd on May 05, 2019, 03:52:57 AM
Quote
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


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: quantummachine on May 06, 2019, 04:10:14 AM
For those who want to crack the most valuable BTC addresses, I've put up a sorted list on this website:

https://bitkeys.work (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.  :)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: dtoan1402 on May 06, 2019, 05:16:48 AM
Is BitCrack have option to generate & compare many random hex instead of multiply one hex to public keys. I see this method work the same in vanitygen but since its purpose to find vanity address & BitCrack is to find collision addresses so this would fit bitcrack more. In vanitygen you modify the rekey_max value to make it generate single new key after amount of public keys (10000000 by default). In bitcrack, where does this function work? I'd like to see if i could modify it


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on May 15, 2019, 11:23:31 AM
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 ?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Abdolreza20 on May 18, 2019, 04:42:42 PM
has anyone been able to get bitcoin from this method?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Trancefan on May 18, 2019, 11:39:51 PM
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


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on May 19, 2019, 04:25:53 AM
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.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: schmuddelkind on May 19, 2019, 10:47:01 AM
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.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: TimeBits on May 23, 2019, 06:25:33 PM
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.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on May 23, 2019, 06:55:26 PM
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.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: TimeBits on May 24, 2019, 10:26:00 PM
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.

ohh that rico666 is the same guy as DannyHamilton I am pretty sure, both last login march 10th around the same time.  I wonder why dooglus is on his block list, dooglus is a cool dood.
He has a pool to get private keys? Shit is crazy. We need blockPOP Proof of person, fingerprint and eye captcha keys pronto.

Heck I would jerk off into the blockchain and give it my sperm if it made my keys safe, give some blood, spit on my computer and pee on it, if it meant stuff was more safe.
I would do a Breathalyzer that checked my carbon inprint to make sure it was me to unlock me wallet.

Is there a hot wallet like private key mixer thing? so it keeps changing your keys every second?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: TimeBits on May 24, 2019, 10:40:46 PM
wait I just thought of something, what if you made it so you can only use someones address in which device it was created from or certain devices you allowed. Like if I tried to make a trillion^22 addresses and got someones on my wallet.dat it still would not work even if I had there private key and public address because It was not the device that created the address. Like a picture of satoshi pops up and gives you the finger or something. I mean something needs to be done. I dunno I am a not a coder man guy dude.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Thirdspace on May 24, 2019, 10:59:02 PM
Like if I tried to make a trillion^22 addresses and got someones on my wallet.dat it still would not work even if I had there private key and public address because It was not the device that created the address.
and when whoever, as a legitimate owner/creator, loses the device will also lose access to coins in it
would you like that to happen to you? losing device = losing your coins :P 


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on May 25, 2019, 07:30:25 AM
wait I just thought of something, what if you made it so you can only use someones address in which device it was created from or certain devices you allowed. Like if I tried to make a trillion^22 addresses and got someones on my wallet.dat it still would not work even if I had there private key and public address because It was not the device that created the address. Like a picture of satoshi pops up and gives you the finger or something. I mean something needs to be done. I dunno I am a not a coder man guy dude.

Anyone who has access to the private key can autonomously reassign any funds associated with that key. There's no way for the "rightful" owner to block any transactions which did not originate from his/her device. All that is needed is a transaction signed by the private key.

Sidechain solutions like Lightning complicate things, but in general, if someone possesses a private key, they can do whatever they like with the funds. The key itself is the authorization.

The chances of any individual, or even a collaborative effort like LBC, ever finding a properly generated key (not one which is deliberately weak), are so small as to be effectively 0.00000. In fact if someone were to do the calculations of the probability, 0.00000 (rounded up to 5 decimals) would probably be accurate. :)

You would be more likely to lose funds due to some event somewhat within your control, like a hard drive dying, or a trojan stealing your wallet.dat file, rather than someone on the other side of the world brute force cracking your private key.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Btceon on May 27, 2019, 12:54:13 PM
Tell me please, I heard that on this forum or GitHub there is a large list of found Bitcoin private keys where BTC transactions have ever been. (with Balance: 0 BTC)
Please share this information.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on May 27, 2019, 03:41:02 PM
Tell me please, I heard that on this forum or GitHub there is a large list of found Bitcoin private keys where BTC transactions have ever been. (with Balance: 0 BTC)
Please share this information.

These threads share some of that information:

Collection of 18.509 found and used Brainwallets (https://bitcointalk.org/index.php?topic=4768828.0)

Bitcoin puzzle transaction ~32 BTC prize to who solves it (https://bitcointalk.org/index.php?topic=1306983.0)

As well as finding SHA256 brainwallets I have also discovered 5000+ miscellaneous private keys. Some of them are deliberately weak (eg private key 0x1 compressed (https://www.blockchain.com/btc/address/751e76e8199196d454941c45d1b3a323f1433bd6) / uncompressed (https://www.blockchain.com/btc/address/91b24bf9f5288532960ac687abb035127b1d28a5)) but many of them look just like a properly generated random key. I can't release them because some of those keys belong to my own wallets. (Before anyone asks, NO, they do not have funds, and NO, apart from the really weak ones they were not brute force cracked. That doesn't work!)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: joepappa123456 on June 04, 2019, 06:41:23 PM

https://imgur.com/CoFCSa7
Is this 2123626 million or 2,123,626?
I'm using a Vega 64 with "clBitCrack.exe -b 500 -t 256 -p 1024 -c -u"


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: gembitz on June 04, 2019, 07:29:12 PM
Tell me please, I heard that on this forum or GitHub there is a large list of found Bitcoin private keys where BTC transactions have ever been. (with Balance: 0 BTC)
Please share this information.

These threads share some of that information:

Collection of 18.509 found and used Brainwallets (https://bitcointalk.org/index.php?topic=4768828.0)

Bitcoin puzzle transaction ~32 BTC prize to who solves it (https://bitcointalk.org/index.php?topic=1306983.0)

As well as finding SHA256 brainwallets I have also discovered 5000+ miscellaneous private keys. Some of them are deliberately weak (eg private key 0x1 compressed (https://www.blockchain.com/btc/address/751e76e8199196d454941c45d1b3a323f1433bd6) / uncompressed (https://www.blockchain.com/btc/address/91b24bf9f5288532960ac687abb035127b1d28a5)) but many of them look just like a properly generated random key. I can't release them because some of those keys belong to my own wallets. (Before anyone asks, NO, they do not have funds, and NO, apart from the really weak ones they were not brute force cracked. That doesn't work!)

epic when do people start selling blocks of hashed addys? :) lols


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: joepappa123456 on June 04, 2019, 10:00:23 PM
It says similar numbers each time I run it. It can't be correct tho!


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: alott_win on June 07, 2019, 10:06:06 PM
How to prevent brute-forcing private keys?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: AndreuSmetanin on June 08, 2019, 06:05:29 AM
there is no way to prevent the bruteforce of private keys, and with the development of a quantum computer it will be millions of orders of magnitude faster.Satoshi himself was laid in its algorithm that opportunity . ;D ;D ;D ;D


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: aplistir on June 08, 2019, 10:10:33 PM
there is no way to prevent the bruteforce of private keys, and with the development of a quantum computer it will be millions of orders of magnitude faster.

Yep, but even quantum computers cannot get private keys if the public key is not available. ie. if the address has no transactions out.

So if you are using bitcoin correctly you wont have a problem even with QC:s in use.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Thirdspace on June 09, 2019, 01:13:29 AM
How to prevent brute-forcing private keys?
you can't really prevent brute forcing, but perhaps make it harder... :-\
I think using a multisig address will add some degree of difficulty to brute forcing attempts


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: kknd on June 21, 2019, 09:20:14 PM
GeForce RTX 2080 3232/8192MB | 1681330 targets 134.23 MKey/s (142,544,994,304,000 total) [12:06:01:53][2019-06-27.20:35:53] [Info] Checkpoint
GeForce RTX 2080 3232/8192MB | 1681330 targets 135.27 MKey/s (142,553,120,768,000 total) [12:06:02:54][2019-06-27.20:36:53] [Info] Checkpoint
GeForce RTX 2080 3232/8192MB | 1681330 targets 134.23 MKey/s (142,561,247,232,000 total) [12:06:03:54][2019-06-27.20:37:54] [Info] Checkpoint
GeForce RTX 2080 3232/8192MB | 1681330 targets 135.27 MKey/s (142,569,373,696,000 total) [12:06:04:55][2019-06-27.20:38:54] [Info] Checkpoint
GeForce RTX 2080 3232/8192MB | 1681330 targets 136.39 MKey/s (142,577,500,160,000 total) [12:06:05:55][2019-06-27.20:39:55] [Info] Checkpoint
GeForce RTX 2080 3232/8192MB | 1681330 targets 135.34 MKey/s (142,585,626,624,000 total) [12:06:06:55][2019-06-27.20:40:55] [Info] Checkpoint
GeForce RTX 2080 3232/8192MB | 1681330 targets 135.34 MKey/s (142,593,753,088,000 total) [12:06:07:56][2019-06-27.20:41:55] [Info] Checkpoint
GeForce RTX 2080 3232/8192MB | 1681330 targets 135.27 MKey/s (142,601,879,552,000 total) [12:06:08:56][2019-06-27.20:42:56] [Info] Checkpoint

this :)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on June 26, 2019, 05:09:50 PM
GeForce RTX 2080 3232/8192MB | 1681329 targets 134.23 MKey/s   (85,816,508,416,000 total) .... and running
GeForce RTX 2080 3232/8192MB | 1681329 targets 134.16 MKey/s (109,259,259,904,000 total).... and running

Explain - if the speed 134.23 MKey/s - how much variants the private keys is generated for one hour?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Kriptonian1661 on June 26, 2019, 11:50:05 PM
If you guys find my old PKey i would be very happy if you would share it with me  ;D


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Firebox on June 26, 2019, 11:51:35 PM
Quote
Explain - if the speed 134.23 MKey/s - how much variants the private keys is generated for one hour?
134.23 MKey/s * 60 * 60 = 483228 MKey/h


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on June 27, 2019, 06:03:35 AM
Quote
Explain - if the speed 134.23 MKey/s - how much variants the private keys is generated for one hour?
134.23 MKey/s * 60 * 60 = 483228 MKey/h

Thanks!
But I can multiply numbers.
Me the dimension of size MKey / s interests.
For example, 1 MKey / s - is how much the private keys are: 1, 10, 100, 1000, 10000, 100000, 1000000 or other meaning ?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on June 27, 2019, 06:57:14 AM
Thanks!
But I can multiply numbers.
Me the dimension of size MKey / s interests.
For example, 1 MKey / s - is how much the private keys are: 1, 10, 100, 1000, 10000, 100000, 1000000 or other meaning ?

Author can correct me if necessary, but I presume 1 MKey/s would mean mega-keys, ie it's trying 1 000 000 (one million) key combinations per second?

It's brute forcing so every raw private key attempt has to be mapped (through public key generation plus hashing) to an address.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Firebox on June 27, 2019, 11:13:25 AM
Thanks!
But I can multiply numbers.
Me the dimension of size MKey / s interests.
For example, 1 MKey / s - is how much the private keys are: 1, 10, 100, 1000, 10000, 100000, 1000000 or other meaning ?
Author can correct me if necessary, but I presume 1 MKey/s would mean mega-keys, ie it's trying 1 000 000 (one million) key combinations per second?
What's wrong with you, folks? Read the first page of the topic again! The author had CLEARLY mentioned:
On my hardware (GeForce GT 640) it gets 9.4 million keys per second compressed, 7.3 million uncompressed.
with the screenshot attached:
https://i.imgur.com/xH3sU1O.png

Also you may see this table (https://en.wikipedia.org/wiki/Template:SI_prefixes_(infobox)) of SI prefixes from wiki.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on June 27, 2019, 02:59:09 PM
Thanks!
But I can multiply numbers.
Me the dimension of size MKey / s interests.
For example, 1 MKey / s - is how much the private keys are: 1, 10, 100, 1000, 10000, 100000, 1000000 or other meaning ?

Author can correct me if necessary, but I presume 1 MKey/s would mean mega-keys, ie it's trying 1 000 000 (one million) key combinations per second?

It's brute forcing so every raw private key attempt has to be mapped (through public key generation plus hashing) to an address.

Thanks!
I know many different units of measurements: meters, kilometers, minute, seconds, ft, km / hour, the mile / hour etc., with this unit (MKey/s) has met for the first time.
I assumed, that 1 MKey/s it can be 1 000 000 Key/s, but has decided to ask the connoisseurs.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: dptrdm on June 27, 2019, 07:29:02 PM
Hi
BitCrack Doesn't work for me on Tahiti r280x
For test i searching for 19ZewH8Kk1PDbSNdJ97FP4EiCjTRaZMZQA
privKEY from  000000000000007


C:\BitCrack>clBitCrack -c --keyspace 00002:000FF 19ZewH8Kk1PDbSNdJ97FP4EiCjTRaZMZQA -o keys.txt
[2019-06-27.19:05:12] [Info] Compression: compressed
[2019-06-27.19:05:12] [Info] Starting at: 0000000000000000000000000000000000000000000000000000000000000002
[2019-06-27.19:05:12] [Info] Ending at:   00000000000000000000000000000000000000000000000000000000000000FF
[2019-06-27.19:05:12] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-06-27.19:05:12] [Info] Compiling OpenCL kernels...
[2019-06-27.19:05:38] [Info] Initializing Tahiti
[2019-06-27.19:05:38] [Info] Generating 262,144 starting points (10.0MB)
[2019-06-27.19:05:38] [Info] 10.0%
[2019-06-27.19:05:38] [Info] 20.0%
[2019-06-27.19:05:39] [Info] 30.0%
[2019-06-27.19:05:39] [Info] 40.0%
[2019-06-27.19:05:39] [Info] 50.0%
[2019-06-27.19:05:39] [Info] 60.0%
[2019-06-27.19:05:39] [Info] 70.0%
[2019-06-27.19:05:39] [Info] 80.0%
[2019-06-27.19:05:40] [Info] 90.0%
[2019-06-27.19:05:40] [Info] 100.0%
[2019-06-27.19:05:40] [Info] Done
[2019-06-27.19:05:40] [Info] Reached end of keyspace

Not found

clBitCrack from latest version 0.30
Any solutions for Tahiti? r280x



Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on July 06, 2019, 07:41:41 AM
It's weird how messages saying this tool cannot be used as a general purpose cracker (ie: Bitcoin is safe regardless of this program) get deleted from this thread.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: gembitz on July 08, 2019, 12:45:03 AM
It's weird how messages saying this tool cannot be used as a general purpose cracker (ie: Bitcoin is safe regardless of this program) get deleted from this thread.

"I've been working on a tool for brute-forcing Bitcoin private keys." --nsa  8) 8) 8) Lol!!


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: byyuans on July 08, 2019, 10:00:29 PM
For RX 570, what are CLBitcrack -b -t and -p?  Please... :)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: racminer on July 11, 2019, 02:15:16 PM
For RX 570, what are CLBitcrack -b -t and -p?  Please... :)

Rx570 has 32 compute units , try this
-b 64 -t 256 -p 1024


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: miningforprofit on July 12, 2019, 06:37:32 PM
Anyone can help me to run this tool on my PC?
How much do you ask for that? please send me a PM with your price.

I get this error: http://prntscr.com/oe8wz9

I have upgraded to latest framework, is there any video with instructions for Windows?

My PC have Intel and AMD Video cards.

thank you


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on July 12, 2019, 06:42:19 PM
My PC have Intel and AMD Video cards.

From the OP: "Currently it is CUDA only."

CUDA is for Nvidia cards.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: miningforprofit on July 12, 2019, 06:54:50 PM
My PC have Intel and AMD Video cards.

From the OP: "Currently it is CUDA only."

CUDA is for Nvidia cards.

Note: clBitCrack.exe is still EXPERIMENTAL, as users have reported critial bugs when running on some AMD and Intel devices.

So still working with Intel and AMD too or it should...


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: A-Bolt on July 12, 2019, 07:50:05 PM
I get this error: http://prntscr.com/oe8wz9

Have you installed Microsoft Visual C++ Redistributable (https://aka.ms/vs/16/release/vc_redist.x64.exe) ?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: miningforprofit on July 13, 2019, 09:17:40 AM
I get this error: http://prntscr.com/oe8wz9

Have you installed ]Microsoft Visual C++ Redistributable (http://https[Suspicious link removed) ?

Installed it now and got the same error.

EDIT: I had only Intel drivers installed, installed AMD drivers now and is WORKING !!!
Thanks guys!


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: mrxtraf on July 13, 2019, 03:37:30 PM
Now to modify application for getted ranges private keys from list?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: valleraz on July 24, 2019, 07:22:10 AM
who has a successful experience of bruteforce attack on private keys?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: avw on July 24, 2019, 09:37:14 AM
who has a successful experience of bruteforce attack on private keys?
Nobody.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: ETFbitcoin on July 24, 2019, 05:44:28 PM
who has a successful experience of bruteforce attack on private keys?

Most likely only Puzzle/Challenge where user must guess private key where possible private key combination permutation is bruteforce-able if the users could find correct hint, which already mentioned as goal of this software on 1st page.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: bad-miner on July 24, 2019, 07:44:55 PM
How to make several video cards work? ???

BitCrack64 --continue -b 112 -t 512 -p 512 -c -u -i addr.txt -o out.txt -s 0000000000000000000000000000000000000000000000000000000000000001 -r 100000000000

4 Nvidia 1060 6gb


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Telariust on August 09, 2019, 03:12:00 AM
1.) Is it possible to recover part of private key, when I have valid address?

For example:
let's say one of my paper wallet is partialy destroyed, and I have lost 5 or more characters from private, like:

pub: 1DrqrF3JEYB9TXWymz4zGoEzM5i75JMLFB
priv: L3Wji4b***4Po3vo2gmi42Y2kbbxtnpAfQ5wJx11BgNr****8v3Q

It is possible as long as exact position of lost characters & it's public key/address are known since 58^5 (656.356.768) combination is small number for GPU these days. But AFAIK this software don't support such feature.
This software does support such feature.

(post moved from bitcointalk.org/index.php?topic=5112311.msg51532763#msg51532763)

FAQ, How to recover a bitcoin PaperWallet using BitCrack.

We need a program
github.com/brichard19/BitCrack
Our task is to correctly specify the options "--keyspace" and "--stride".

Show how to recover
Code:
17GD2bc5b7SvU7bzN7CYUSc6h4zBJ36Rx6
5KVzbojiLkuTHwJQsKr6W9prrHx4XYfzjwsstfqjdembMEUsY42
dddb314fa4915afbcc75edc4a8d37de912dd9de86e9b0ba365eca5c0d676e50c


1) Calculate "--keyspace"

The private key of the paper wallet is in WIF format (base58check encoding).
We need to convert it to HEX format (base16 encoding)
For this we will use an online converter, for example
brainwalletx.github.io/#converter

Code:
for
5KVzbojiLku?????sKr6W9prrHx4XYfzjwsstfqjdembMEUsY42
the min range key will be(1)
5KVzbojiLku11111sKr6W9prrHx4XYfzjwsstfqjdembMEUsY42
the min range key +1 will be(2)
5KVzbojiLku11112sKr6W9prrHx4XYfzjwsstfqjdembMEUsY42
the max range key will be(3)
5KVzbojiLkuzzzzzsKr6W9prrHx4XYfzjwsstfqjdembMEUsY42


Request the key(1) into the converter
"Source Text"->"5KVzbojiLku11111sKr6W9prrHx4XYfzjwsstfqjdembMEUsY42"
"Source Encoding"->"Base58"
Response
"Convert To"->"Hex"
"Result"->"80dddb314fa49158b8a43cae43cc017003a9ce0b2c43b407c4cbbb533d532a64a4186b7dab"
Save the number(1) in a notepad
80dddb314fa49158b8a43cae43cc017003a9ce0b2c43b407c4cbbb533d532a64a4186b7dab

Request the key(2) into the converter
"Source Text"->"5KVzbojiLku11112sKr6W9prrHx4XYfzjwsstfqjdembMEUsY42"
"Source Encoding"->"Base58"
Response
"Convert To"->"Hex"
"Result"->"80dddb314fa49158b8a43cceec129f5caa5f74de940f749841d3a1f8959aa342cc186b7dab"
Save the number(2) in a notepad
80dddb314fa49158b8a43cceec129f5caa5f74de940f749841d3a1f8959aa342cc186b7dab

Request the key(3) into the converter
"Source Text"->"5KVzbojiLkuzzzzzsKr6W9prrHx4XYfzjwsstfqjdembMEUsY42"
"Source Encoding"->"Base58"
Response
"Convert To"->"Hex"
"Result"->"80dddb314fa4915db64236699367f258926fcbd827398fc02deccb5d58bc12a77c186b7dab"
Save the number(3) in a notepad
80dddb314fa4915db64236699367f258926fcbd827398fc02deccb5d58bc12a77c186b7dab


We remove the left 2 digits ("80" is a bitcoin network label)
(1')dddb314fa49158b8a43cae43cc017003a9ce0b2c43b407c4cbbb533d532a64a4186b7dab
(2')dddb314fa49158b8a43cceec129f5caa5f74de940f749841d3a1f8959aa342cc186b7dab
(3')dddb314fa4915db64236699367f258926fcbd827398fc02deccb5d58bc12a77c186b7dab
Save the number(1') and the number(2') (they are needed to get "--stride")

We remove the right 8 digits ("186b7dab" - this is the checksum base58check)
(1'')dddb314fa49158b8a43cae43cc017003a9ce0b2c43b407c4cbbb533d532a64a4
(2'') for "--keyspace" number(2'') is not needed, skip
(3'')dddb314fa4915db64236699367f258926fcbd827398fc02deccb5d58bc12a77c

ATTENTION!
If your WIF key starts with "5" - this is an uncompressed key, and you can skip this warning.
If your WIF key starts with "L" or "K" - this is a compressed key, read the warning.
WIF "L"/"K" compressed keys are labeled "01" before the checksum - this also needs to be removed.
Ie, we remove the right 10 digits ("01" + 8 digit checksum base58check)

In fact, the number(1'') and number(3'') is the range of candidates for private keys in HEX.
Then the option "--keyspace (1''):(3'')" like
Code:
--keyspace dddb314fa49158b8a43cae43cc017003a9ce0b2c43b407c4cbbb533d532a64a4:dddb314fa4915db64236699367f258926fcbd827398fc02deccb5d58bc12a77c


2) Calculate "--stride".

Convert number(1') and number(2') to DEC (base10 encoding)

Request the key(1') into the converter
"Source Text"->"dddb314fa49158b8a43cae43cc017003a9ce0b2c43b407c4cbbb533d532a64a4186b7dab"
"Source Encoding"->"Hex"
Response
"Convert To"->"Dec"
"Result"->"4309931794287609088053274827537810492913374270149990123844761122944746242931016 15414699"
Save the number(1''') in a notepad
4309931794287609088053274827537810492913374270149990123844761122944746242931016 15414699

Request the key(2') into the converter
"Source Text"->"dddb314fa49158b8a43cceec129f5caa5f74de940f749841d3a1f8959aa342cc186b7dab"
"Source Encoding"->"Hex"
Response
"Convert To"->"Dec"
"Result"->"4309931794287609088053275352320830782839823951879774905331246684460802851879681 94018731"
Save the number(2''') in a notepad
4309931794287609088053275352320830782839823951879774905331246684460802851879681 94018731

Why do we need the (1''') and (2''') in DEC? We need the difference (2')-(1') (not all calculators can count in hex)
For this, we will use an online high precision calculator, for example
www.ttmath.org/online_calculator
subtract from the larger (2''') the smaller (1'''),
Code:
430993179428760908805327535232083078283982395187977490533124668446080285187968194018731
-
430993179428760908805327482753781049291337427014999012384476112294474624293101615414699
=
The result is:
5.2478302028992644968172978478148648556151605660894866578604032e+61
i.e
52478302028992644968172978478148648556151605660894866578604032

Convert  to HEX

Request into the converter
"Source Text"->"52478302028992644968172978478148648556151605660894866578604032"
"Source Encoding"->"Dec"
Response
"Convert To"->"Hex"
"Result"->"20a8469deca6b5a6d367cbc0907d07e6a5584778de2800000000"

If your WIF key starts with "5" - we remove 8 digits from the right.
If your WIF key starts with "L" or "K" - we remove 10 numbers from the right.
20a8469deca6b5a6d367cbc0907d07e6a5584778de28

now option "--stride" as
Code:
--stride 20a8469deca6b5a6d367cbc0907d07e6a5584778de28


3) Run BitCrack and restore PrivateKey

Code:
D:\BitCrack\0.30>cuBitCrack -u --keyspace dddb314fa49158b8a43cae43cc017003a9ce0b2c43b407c4cbbb533d532a64a4:dddb314fa4915db64236699367f258926fcbd827398fc02deccb5d58bc12a77c  --stride 20a8469deca6b5a6d367cbc0907d07e6a5584778de28  17GD2bc5b7SvU7bzN7CYUSc6h4zBJ36Rx6

[2019-06-20.09:48:12] [Info] Compression: uncompressed
[2019-06-20.09:48:12] [Info] Starting at: DDDB314FA49158B8A43CAE43CC017003A9CE0B2C43B407C4CBBB533D532A64A4
[2019-06-20.09:48:12] [Info] Ending at:   DDDB314FA4915DB64236699367F258926FCBD827398FC02DECCB5D58BC12A77C
[2019-06-20.09:48:12] [Info] Counting by: 0000000000000000000020A8469DECA6B5A6D367CBC0907D07E6A5584778DE28
[2019-06-20.09:48:12] [Info] Initializing GeForce GTX 980
[2019-06-20.09:48:12] [Info] Generating 262,144 starting points (10.0MB)
[2019-06-20.09:48:12] [Info] 10.0%
[2019-06-20.09:48:12] [Info] 20.0%
[2019-06-20.09:48:12] [Info] 30.0%
[2019-06-20.09:48:12] [Info] 40.0%
[2019-06-20.09:48:12] [Info] 50.0%
[2019-06-20.09:48:12] [Info] 60.0%
[2019-06-20.09:48:12] [Info] 70.0%
[2019-06-20.09:48:13] [Info] 80.0%
[2019-06-20.09:48:13] [Info] 90.0%
[2019-06-20.09:48:13] [Info] 100.0%
[2019-06-20.09:48:13] [Info] Done
GeForce GTX 980  492 / 8192MB | 1 target 69.95 MKey/s (253,493,248 total)
[00:00:01][2019-06-20.09:48:17] [Info] Address:     17GD2bc5b7SvU7bzN7CYUSc6h4zBJ36Rx6
                             Private key: DDDB314FA4915AFBCC75EDC4A8D37DE912DD9DE86E9B0BA365ECA5C0D676E50C
                             Compressed:  no
                             Public key:
                             566465A2FA23C1983ED1968029E48C318ACF6FEB6B9A949B33FACA7E7803F03B
                             6F514ADC66D41F5A31E6187FD8F3419601F22A930B9BE7204E9BCC551C81A836

[2019-06-20.09:48:17] [Info] No targets remaining


4) BitCrack Performance Tips.
BitCrack may not optimally calculate the -t and -p parameters (halving the speed).
run with the option "--continue sess.txt", any address, for example
xxBitCrack --continue sess.txt 17GD2bc5b7SvU7bzN7CYUSc6h4zBJ36Rx6
wait a little longer than a minute until the file of saving the progress will not be created, turn off;
open sess.txt, for example, "threads = 256" (this is the -t option) and "points = 32" (this is the -p option)
try to double the value, the speed should double; try double again..
remember them and always add when running BitCrack, for example
xxBitCrack -t 512 -p 1024 17GD2bc5b7SvU7bzN7CYUSc6h4zBJ36Rx6


5) Repeat the calculations for the compressed key

Code:
19BoCbK9SMQ2GeHRo5h5HFMDXsWAe5DJu4
L4eyEdHXUCnX3kfrM8BhHfxF2Zp2Zpo7rZDZd4S7AmhpcFvTBi3o
dddb314fa4915afbcc75edc4a8d37de912dd9de86e9b0ba365eca5c0d676e50c

Code:
for
L4eyEd?????X3kfrM8BhHfxF2Zp2Zpo7rZDZd4S7AmhpcFvTBi3o
the min range key will be(1)
L4eyEd11111X3kfrM8BhHfxF2Zp2Zpo7rZDZd4S7AmhpcFvTBi3o
the min range key +1 will be(2)
L4eyEd11112X3kfrM8BhHfxF2Zp2Zpo7rZDZd4S7AmhpcFvTBi3o
the max range key will be(3)
L4eyEdzzzzzX3kfrM8BhHfxF2Zp2Zpo7rZDZd4S7AmhpcFvTBi3o

"Base58"->"Hex"
(1)80dddb31430a12ceca48afa7302db7c16d048111b4490ef5aba1c538656e935576019027ecb6
(2)80dddb31430a12cfebbe7a4306570c1dbb22845e0aa8ec5e2fc70d1c25a48956f0019027ecb6
(3)80dddb316f464e913be304a3096441652fbe6bb3ee73e4b2dd88117af6a472823c019027ecb6

(1')dddb31430a12ceca48afa7302db7c16d048111b4490ef5aba1c538656e935576019027ecb6
(2')dddb31430a12cfebbe7a4306570c1dbb22845e0aa8ec5e2fc70d1c25a48956f0019027ecb6
(3')dddb316f464e913be304a3096441652fbe6bb3ee73e4b2dd88117af6a472823c019027ecb6

(1'')dddb31430a12ceca48afa7302db7c16d048111b4490ef5aba1c538656e935576
(2'') for "--keyspace" number(2'') is not needed, skip
(3'')dddb316f464e913be304a3096441652fbe6bb3ee73e4b2dd88117af6a472823c

Code:
--keyspace dddb31430a12ceca48afa7302db7c16d048111b4490ef5aba1c538656e935576:dddb316f464e913be304a3096441652fbe6bb3ee73e4b2dd88117af6a472823c

(1')"Hex"->"Dec"
"Source Text"->"dddb31430a12ceca48afa7302db7c16d048111b4490ef5aba1c538656e935576019027ecb6"
"Result"->"1103342535601602776525285853177912161262361522527439740718572909944271817096236 43576200374"

(2')"Hex"->"Dec"
"Source Text"->"dddb31430a12cfebbe7a4306570c1dbb22845e0aa8ec5e2fc70d1c25a48956f0019027ecb6"
"Result"->"1103342535601602796503089304906835914569619353461138982851022867509637813984017 46502937782"

(2')-(1')
1103342535601602796503089304906835914569619353461138982851022867509637813984017 46502937782
-
1103342535601602776525285853177912161262361522527439740718572909944271817096236 43576200374
=
The result is:
1.997780345172892375330725783093369924213244995756536599688778102926737408e+72
i.e
1997780345172892375330725783093369924213244995756536599688778102926737408

"Source Text"->"1997780345172892375330725783093369924213244995756536599688778102926737408"
"Dec"->"Hex"
"Result"->"012175ca9bd629545c4e1e034c565fdd68842547e3c035f6017a0000000000"

012175ca9bd629545c4e1e034c565fdd68842547e3c035f6017a

Code:
--stride 012175ca9bd629545c4e1e034c565fdd68842547e3c035f6017a


Code:
D:\BitCrack\0.30>cuBitCrack -c --keyspace dddb31430a12ceca48afa7302db7c16d048111b4490ef5aba1c538656e935576:dddb316f464e913be304a3096441652fbe6bb3ee73e4b2dd88117af6a472823c  --stride 012175ca9bd629545c4e1e034c565fdd68842547e3c035f6017a  19BoCbK9SMQ2GeHRo5h5HFMDXsWAe5DJu4

[2019-06-20.10:12:55] [Info] Compression: compressed
[2019-06-20.10:12:55] [Info] Starting at: DDDB31430A12CECA48AFA7302DB7C16D048111B4490EF5ABA1C538656E935576
[2019-06-20.10:12:55] [Info] Ending at:   DDDB316F464E913BE304A3096441652FBE6BB3EE73E4B2DD88117AF6A472823C
[2019-06-20.10:12:55] [Info] Counting by: 000000000000012175CA9BD629545C4E1E034C565FDD68842547E3C035F6017A
[2019-06-20.10:12:55] [Info] Initializing GeForce GTX 980
[2019-06-20.10:12:56] [Info] Generating 262,144 starting points (10.0MB)
[2019-06-20.10:12:56] [Info] 10.0%
[2019-06-20.10:12:56] [Info] 20.0%
[2019-06-20.10:12:56] [Info] 30.0%
[2019-06-20.10:12:56] [Info] 40.0%
[2019-06-20.10:12:56] [Info] 50.0%
[2019-06-20.10:12:56] [Info] 60.0%
[2019-06-20.10:12:56] [Info] 70.0%
[2019-06-20.10:12:56] [Info] 80.0%
[2019-06-20.10:12:56] [Info] 90.0%
[2019-06-20.10:12:57] [Info] 100.0%
[2019-06-20.10:12:57] [Info] Done
GeForce GTX 980  492 / 8192MB | 1 target 78.25 MKey/s (141,557,760 total)
[00:00:00][2019-06-20.10:12:59] [Info] Address:     19BoCbK9SMQ2GeHRo5h5HFMDXsWAe5DJu4
                             Private key: DDDB314FA4915AFBCC75EDC4A8D37DE912DD9DE86E9B0BA365ECA5C0D676E50C
                             Compressed:  yes
                             Public key:
                             02566465A2FA23C1983ED1968029E48C318ACF6FEB6B9A949B33FACA7E7803F03B

[2019-06-20.10:12:59] [Info] No targets remaining


#######################

python3 script, automate calc --keyspace and --stride

Code:
#python3

import sys

#######################

def int_to_unknown_bytes(num, byteorder='big'):
"""Converts an int to the least number of bytes as possible."""
return num.to_bytes((num.bit_length() + 7) // 8 or 1, byteorder)


BASE58_ALPHABET = '123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz'
BASE58_ALPHABET_LIST = list(BASE58_ALPHABET)
BASE58_ALPHABET_INDEX = {char: index for index, char in enumerate(BASE58_ALPHABET)}


def b58decode(string):

alphabet_index = BASE58_ALPHABET_INDEX

num = 0

try:
for char in string:
num *= 58
num += alphabet_index[char]
except KeyError:
raise ValueError('"{}" is an invalid base58 encoded '
'character.'.format(char))

bytestr = int_to_unknown_bytes(num)

pad = 0
for char in string:
if char == '1':
pad += 1
else:
break

return b'\x00' * pad + bytestr

#######################
# Main


if __name__ == '__main__':

print('########')

if len(sys.argv)<2 :
print('[usage] BitCrackPaperWalletRecovery.py 5KYZdUEo39z*****uX2QbbwGnNP5zTd7yyr2SC1j299sBCnWjss')
exit(1)

privkey0 = sys.argv[1];
print('[WIFprivkey] {}'.format(privkey0));

if len(sys.argv[1]) < 50 or len(sys.argv[1]) > 52 :
print('[error] wrong len(50..52)');
exit(1);

if privkey0.find("5",0,1) == 0:
#print("[compress] off")
flag_compress = False
elif privkey0.find("L",0,1) == 0 or privkey0.find("K",0,1) == 0 :
#print("[compress] on")
flag_compress = True
else:
print("[error] wif privkey should start with 5,K,L")
exit(1);


marker   = privkey0.rfind("*")
if  marker == -1 :
print("[error] marker(*) not found" )
exit(1);

print('########')

privkey1 = privkey0.replace("*","1")
print("(1)[minimal] {}".format(privkey1.upper()));

privkey2 = privkey1[:marker]+"2"+privkey1[marker+1:]
print("(2)[minim+1] {}".format(privkey2.upper()));

privkey3 = privkey0.replace("*","z")
print("(3)[maximal] {}".format(privkey3.upper()));

print('########')

privkey1hex = hex(int.from_bytes(b58decode(privkey1),"big"))[4:]
print("(1')  {}".format(privkey1hex.upper()));

privkey2hex = hex(int.from_bytes(b58decode(privkey2),"big"))[4:]
print("(2')  {}".format(privkey2hex.upper()));

privkey3hex = hex(int.from_bytes(b58decode(privkey3),"big"))[4:]
print("(3')  {}".format(privkey3hex.upper()));

checksum = privkey1hex[-8:]
if checksum == privkey2hex[-8:] and checksum == privkey3hex[-8:] :
print("[checksum] {}".format(checksum.upper()));
else:
print("[error] checksum corrupted")
print(" --stride should be integer, not float! recovery impossible!")
exit(1);

if flag_compress:
if privkey1hex[-10:-8] != "01" or privkey2hex[-10:-8] != "01" or privkey3hex[-10:-8] != "01":
print("[error] byte of compress - corrupted")
print(" --stride should be integer, not float! recovery impossible!")
exit(1);


print('########')

privkey11hex = privkey1hex[:64]
privkey22hex = privkey2hex[:64]
privkey33hex = privkey3hex[:64]

print("(1'') {}".format(privkey11hex.upper()));
print("(2'') {}".format(privkey22hex.upper()));
print("(3'') {}".format(privkey33hex.upper()));

print('########')
print("[ --keyspace {}:{} ]".format(privkey11hex.upper(),privkey33hex.upper()))
print('########')

strideint = int(privkey2hex,16) - int(privkey1hex,16)
strideraw = hex(strideint)[2:]
#print("[strideraw] {}".format(strideraw));

if flag_compress == False:
stridehex = strideraw[:-8]
elif flag_compress == True :
stridehex = strideraw[:-10]

print("[stride] {}".format(stridehex.upper()));

print('########')
print("[ --stride {} ]".format(stridehex.upper()));
print('########')

#######################

if the checksum(or/and flag compress x01) is corrupted, than recovery now is impossible.
(--stride opt becomes float but must be integer!)
Recovery of these keys is possible only if brichard19 implements support float for --stride opt.

if it is easier to explain..
In WIFbase58privkey, each lost symbol(*/?) to the right is a division stride by 58.
Already from the middle, the stride no longer divides completely.
What does checksum have to do with it? In fact, the checksum forms the float part.
While it is equal, then when subtracting it is reset.
As soon as it becomes different for lowerKey and lowerKey+1, this indicates - stride becomes float.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: chan111 on August 11, 2019, 03:55:46 PM
1.) Is it possible to recover part of private key, when I have valid address?

For example:
let's say one of my paper wallet is partialy destroyed, and I have lost 5 or more characters from private, like:

pub: 1DrqrF3JEYB9TXWymz4zGoEzM5i75JMLFB
priv: L3Wji4b***4Po3vo2gmi42Y2kbbxtnpAfQ5wJx11BgNr****8v3Q

It is possible as long as exact position of lost characters & it's public key/address are known since 58^5 (656.356.768) combination is small number for GPU these days. But AFAIK this software don't support such feature.
This software does support such feature.

(post moved from bitcointalk.org/index.php?topic=5112311.msg51532763#msg51532763)

FAQ, How to recover a bitcoin PaperWallet using BitCrack.

We need a program
github.com/brichard19/BitCrack
Our task is to correctly specify the options "--keyspace" and "--stride".

Show how to recover
Code:
17GD2bc5b7SvU7bzN7CYUSc6h4zBJ36Rx6
5KVzbojiLkuTHwJQsKr6W9prrHx4XYfzjwsstfqjdembMEUsY42
dddb314fa4915afbcc75edc4a8d37de912dd9de86e9b0ba365eca5c0d676e50c


1) Calculate "--keyspace"

The private key of the paper wallet is in WIF format (base58check encoding).
We need to convert it to HEX format (base16 encoding)
For this we will use an online converter, for example
brainwalletx.github.io/#converter

Code:
for
5KVzbojiLku?????sKr6W9prrHx4XYfzjwsstfqjdembMEUsY42
the min range key will be(1)
5KVzbojiLku11111sKr6W9prrHx4XYfzjwsstfqjdembMEUsY42
the min range key +1 will be(2)
5KVzbojiLku11112sKr6W9prrHx4XYfzjwsstfqjdembMEUsY42
the max range key will be(3)
5KVzbojiLkuzzzzzsKr6W9prrHx4XYfzjwsstfqjdembMEUsY42


Request the key(1) into the converter
"Source Text"->"5KVzbojiLku11111sKr6W9prrHx4XYfzjwsstfqjdembMEUsY42"
"Source Encoding"->"Base58"
Response
"Convert To"->"Hex"
"Result"->"80dddb314fa49158b8a43cae43cc017003a9ce0b2c43b407c4cbbb533d532a64a4186b7dab"
Save the number(1) in a notepad
80dddb314fa49158b8a43cae43cc017003a9ce0b2c43b407c4cbbb533d532a64a4186b7dab

Request the key(2) into the converter
"Source Text"->"5KVzbojiLku11112sKr6W9prrHx4XYfzjwsstfqjdembMEUsY42"
"Source Encoding"->"Base58"
Response
"Convert To"->"Hex"
"Result"->"80dddb314fa49158b8a43cceec129f5caa5f74de940f749841d3a1f8959aa342cc186b7dab"
Save the number(2) in a notepad
80dddb314fa49158b8a43cceec129f5caa5f74de940f749841d3a1f8959aa342cc186b7dab

Request the key(3) into the converter
"Source Text"->"5KVzbojiLkuzzzzzsKr6W9prrHx4XYfzjwsstfqjdembMEUsY42"
"Source Encoding"->"Base58"
Response
"Convert To"->"Hex"
"Result"->"80dddb314fa4915db64236699367f258926fcbd827398fc02deccb5d58bc12a77c186b7dab"
Save the number(3) in a notepad
80dddb314fa4915db64236699367f258926fcbd827398fc02deccb5d58bc12a77c186b7dab


We remove the left 2 digits ("80" is a bitcoin network label)
(1')dddb314fa49158b8a43cae43cc017003a9ce0b2c43b407c4cbbb533d532a64a4186b7dab
(2')dddb314fa49158b8a43cceec129f5caa5f74de940f749841d3a1f8959aa342cc186b7dab
(3')dddb314fa4915db64236699367f258926fcbd827398fc02deccb5d58bc12a77c186b7dab
Save the number(1') and the number(2') (they are needed to get "--stride")

We remove the right 8 digits ("186b7dab" - this is the checksum base58check)
(1'')dddb314fa49158b8a43cae43cc017003a9ce0b2c43b407c4cbbb533d532a64a4
(2'') for "--keyspace" number(2'') is not needed, skip
(3'')dddb314fa4915db64236699367f258926fcbd827398fc02deccb5d58bc12a77c

ATTENTION!
If your WIF key starts with "5" - this is an uncompressed key, and you can skip this warning.
If your WIF key starts with "L" or "K" - this is a compressed key, read the warning.
WIF "L"/"K" compressed keys are labeled "01" before the checksum - this also needs to be removed.
Ie, we remove the right 10 digits ("01" + 8 digit checksum base58check)

In fact, the number(1'') and number(3'') is the range of candidates for private keys in HEX.
Then the option "--keyspace (1''):(3'')" like
Code:
--keyspace dddb314fa49158b8a43cae43cc017003a9ce0b2c43b407c4cbbb533d532a64a4:dddb314fa4915db64236699367f258926fcbd827398fc02deccb5d58bc12a77c


2) Calculate "--stride".

Convert number(1') and number(2') to DEC (base10 encoding)

Request the key(1') into the converter
"Source Text"->"dddb314fa49158b8a43cae43cc017003a9ce0b2c43b407c4cbbb533d532a64a4186b7dab"
"Source Encoding"->"Hex"
Response
"Convert To"->"Dec"
"Result"->"4309931794287609088053274827537810492913374270149990123844761122944746242931016 15414699"
Save the number(1''') in a notepad
4309931794287609088053274827537810492913374270149990123844761122944746242931016 15414699

Request the key(2') into the converter
"Source Text"->"dddb314fa49158b8a43cceec129f5caa5f74de940f749841d3a1f8959aa342cc186b7dab"
"Source Encoding"->"Hex"
Response
"Convert To"->"Dec"
"Result"->"4309931794287609088053275352320830782839823951879774905331246684460802851879681 94018731"
Save the number(2''') in a notepad
4309931794287609088053275352320830782839823951879774905331246684460802851879681 94018731

Why do we need the (1''') and (2''') in DEC? We need the difference (2')-(1') (not all calculators can count in hex)
For this, we will use an online high precision calculator, for example
www.ttmath.org/online_calculator
subtract from the larger (2''') the smaller (1'''),
Code:
430993179428760908805327535232083078283982395187977490533124668446080285187968194018731
-
430993179428760908805327482753781049291337427014999012384476112294474624293101615414699
=
The result is:
5.2478302028992644968172978478148648556151605660894866578604032e+61
i.e
52478302028992644968172978478148648556151605660894866578604032

Convert  to HEX

Request into the converter
"Source Text"->"52478302028992644968172978478148648556151605660894866578604032"
"Source Encoding"->"Dec"
Response
"Convert To"->"Hex"
"Result"->"20a8469deca6b5a6d367cbc0907d07e6a5584778de2800000000"

If your WIF key starts with "5" - we remove 8 digits from the right.
If your WIF key starts with "L" or "K" - we remove 10 numbers from the right.
20a8469deca6b5a6d367cbc0907d07e6a5584778de28

now option "--stride" as
Code:
--stride 20a8469deca6b5a6d367cbc0907d07e6a5584778de28


3) Run BitCrack and restore PrivateKey

Code:
D:\BitCrack\0.30>cuBitCrack -u --keyspace dddb314fa49158b8a43cae43cc017003a9ce0b2c43b407c4cbbb533d532a64a4:dddb314fa4915db64236699367f258926fcbd827398fc02deccb5d58bc12a77c  --stride 20a8469deca6b5a6d367cbc0907d07e6a5584778de28  17GD2bc5b7SvU7bzN7CYUSc6h4zBJ36Rx6

[2019-06-20.09:48:12] [Info] Compression: uncompressed
[2019-06-20.09:48:12] [Info] Starting at: DDDB314FA49158B8A43CAE43CC017003A9CE0B2C43B407C4CBBB533D532A64A4
[2019-06-20.09:48:12] [Info] Ending at:   DDDB314FA4915DB64236699367F258926FCBD827398FC02DECCB5D58BC12A77C
[2019-06-20.09:48:12] [Info] Counting by: 0000000000000000000020A8469DECA6B5A6D367CBC0907D07E6A5584778DE28
[2019-06-20.09:48:12] [Info] Initializing GeForce GTX 980
[2019-06-20.09:48:12] [Info] Generating 262,144 starting points (10.0MB)
[2019-06-20.09:48:12] [Info] 10.0%
[2019-06-20.09:48:12] [Info] 20.0%
[2019-06-20.09:48:12] [Info] 30.0%
[2019-06-20.09:48:12] [Info] 40.0%
[2019-06-20.09:48:12] [Info] 50.0%
[2019-06-20.09:48:12] [Info] 60.0%
[2019-06-20.09:48:12] [Info] 70.0%
[2019-06-20.09:48:13] [Info] 80.0%
[2019-06-20.09:48:13] [Info] 90.0%
[2019-06-20.09:48:13] [Info] 100.0%
[2019-06-20.09:48:13] [Info] Done
GeForce GTX 980  492 / 8192MB | 1 target 69.95 MKey/s (253,493,248 total)
[00:00:01][2019-06-20.09:48:17] [Info] Address:     17GD2bc5b7SvU7bzN7CYUSc6h4zBJ36Rx6
                             Private key: DDDB314FA4915AFBCC75EDC4A8D37DE912DD9DE86E9B0BA365ECA5C0D676E50C
                             Compressed:  no
                             Public key:
                             566465A2FA23C1983ED1968029E48C318ACF6FEB6B9A949B33FACA7E7803F03B
                             6F514ADC66D41F5A31E6187FD8F3419601F22A930B9BE7204E9BCC551C81A836

[2019-06-20.09:48:17] [Info] No targets remaining


4) BitCrack Performance Tips.
BitCrack may not optimally calculate the -t and -p parameters (halving the speed).
run with the option "--continue sess.txt", any address, for example
xxBitCrack --continue sess.txt 17GD2bc5b7SvU7bzN7CYUSc6h4zBJ36Rx6
wait a little longer than a minute until the file of saving the progress will not be created, turn off;
open sess.txt, for example, "threads = 256" (this is the -t option) and "points = 32" (this is the -p option)
try to double the value, the speed should double;
remember them and always add when running BitCrack, for example
xxBitCrack -t 512 -p 64 17GD2bc5b7SvU7bzN7CYUSc6h4zBJ36Rx6


5) Repeat the calculations for the compressed key

Code:
19BoCbK9SMQ2GeHRo5h5HFMDXsWAe5DJu4
L4eyEdHXUCnX3kfrM8BhHfxF2Zp2Zpo7rZDZd4S7AmhpcFvTBi3o
dddb314fa4915afbcc75edc4a8d37de912dd9de86e9b0ba365eca5c0d676e50c

Code:
for
L4eyEd?????X3kfrM8BhHfxF2Zp2Zpo7rZDZd4S7AmhpcFvTBi3o
the min range key will be(1)
L4eyEd11111X3kfrM8BhHfxF2Zp2Zpo7rZDZd4S7AmhpcFvTBi3o
the min range key +1 will be(2)
L4eyEd11112X3kfrM8BhHfxF2Zp2Zpo7rZDZd4S7AmhpcFvTBi3o
the max range key will be(3)
L4eyEdzzzzzX3kfrM8BhHfxF2Zp2Zpo7rZDZd4S7AmhpcFvTBi3o

"Base58"->"Hex"
(1)80dddb31430a12ceca48afa7302db7c16d048111b4490ef5aba1c538656e935576019027ecb6
(2)80dddb31430a12cfebbe7a4306570c1dbb22845e0aa8ec5e2fc70d1c25a48956f0019027ecb6
(3)80dddb316f464e913be304a3096441652fbe6bb3ee73e4b2dd88117af6a472823c019027ecb6

(1')dddb31430a12ceca48afa7302db7c16d048111b4490ef5aba1c538656e935576019027ecb6
(2')dddb31430a12cfebbe7a4306570c1dbb22845e0aa8ec5e2fc70d1c25a48956f0019027ecb6
(3')dddb316f464e913be304a3096441652fbe6bb3ee73e4b2dd88117af6a472823c019027ecb6

(1'')dddb31430a12ceca48afa7302db7c16d048111b4490ef5aba1c538656e935576
(2'') for "--keyspace" number(2'') is not needed, skip
(3'')dddb316f464e913be304a3096441652fbe6bb3ee73e4b2dd88117af6a472823c

Code:
--keyspace dddb31430a12ceca48afa7302db7c16d048111b4490ef5aba1c538656e935576:dddb316f464e913be304a3096441652fbe6bb3ee73e4b2dd88117af6a472823c

(1')"Hex"->"Dec"
"Source Text"->"dddb31430a12ceca48afa7302db7c16d048111b4490ef5aba1c538656e935576019027ecb6"
"Result"->"1103342535601602776525285853177912161262361522527439740718572909944271817096236 43576200374"

(2')"Hex"->"Dec"
"Source Text"->"dddb31430a12cfebbe7a4306570c1dbb22845e0aa8ec5e2fc70d1c25a48956f0019027ecb6"
"Result"->"1103342535601602796503089304906835914569619353461138982851022867509637813984017 46502937782"

(2')-(1')
1103342535601602796503089304906835914569619353461138982851022867509637813984017 46502937782
-
1103342535601602776525285853177912161262361522527439740718572909944271817096236 43576200374
=
The result is:
1.997780345172892375330725783093369924213244995756536599688778102926737408e+72
i.e
1997780345172892375330725783093369924213244995756536599688778102926737408

"Source Text"->"1997780345172892375330725783093369924213244995756536599688778102926737408"
"Dec"->"Hex"
"Result"->"012175ca9bd629545c4e1e034c565fdd68842547e3c035f6017a0000000000"

012175ca9bd629545c4e1e034c565fdd68842547e3c035f6017a

Code:
--stride 012175ca9bd629545c4e1e034c565fdd68842547e3c035f6017a


Code:
D:\BitCrack\0.30>cuBitCrack -c --keyspace dddb31430a12ceca48afa7302db7c16d048111b4490ef5aba1c538656e935576:dddb316f464e913be304a3096441652fbe6bb3ee73e4b2dd88117af6a472823c  --stride 012175ca9bd629545c4e1e034c565fdd68842547e3c035f6017a  19BoCbK9SMQ2GeHRo5h5HFMDXsWAe5DJu4

[2019-06-20.10:12:55] [Info] Compression: compressed
[2019-06-20.10:12:55] [Info] Starting at: DDDB31430A12CECA48AFA7302DB7C16D048111B4490EF5ABA1C538656E935576
[2019-06-20.10:12:55] [Info] Ending at:   DDDB316F464E913BE304A3096441652FBE6BB3EE73E4B2DD88117AF6A472823C
[2019-06-20.10:12:55] [Info] Counting by: 000000000000012175CA9BD629545C4E1E034C565FDD68842547E3C035F6017A
[2019-06-20.10:12:55] [Info] Initializing GeForce GTX 980
[2019-06-20.10:12:56] [Info] Generating 262,144 starting points (10.0MB)
[2019-06-20.10:12:56] [Info] 10.0%
[2019-06-20.10:12:56] [Info] 20.0%
[2019-06-20.10:12:56] [Info] 30.0%
[2019-06-20.10:12:56] [Info] 40.0%
[2019-06-20.10:12:56] [Info] 50.0%
[2019-06-20.10:12:56] [Info] 60.0%
[2019-06-20.10:12:56] [Info] 70.0%
[2019-06-20.10:12:56] [Info] 80.0%
[2019-06-20.10:12:56] [Info] 90.0%
[2019-06-20.10:12:57] [Info] 100.0%
[2019-06-20.10:12:57] [Info] Done
GeForce GTX 980  492 / 8192MB | 1 target 78.25 MKey/s (141,557,760 total)
[00:00:00][2019-06-20.10:12:59] [Info] Address:     19BoCbK9SMQ2GeHRo5h5HFMDXsWAe5DJu4
                             Private key: DDDB314FA4915AFBCC75EDC4A8D37DE912DD9DE86E9B0BA365ECA5C0D676E50C
                             Compressed:  yes
                             Public key:
                             02566465A2FA23C1983ED1968029E48C318ACF6FEB6B9A949B33FACA7E7803F03B

[2019-06-20.10:12:59] [Info] No targets remaining

Hi, thanks for advice! Sometimes it works, but sometimes NOT.
Let's say we have that pair:

Code:
//full key = "5Hvqe4cm3iaHiaVvyyRj2vEQGY2kR23Q987NZ1BroCExQb3Hbfg";
address = "1HfPVDokgJQMtcT1d9qUt7UAEpfZyUhH1V";
key = "5Hvqe4cm3iaHiaVvyyRj2vEQGY????3Q987NZ1BroCExQb3Hbfg";

Now, when we do all the steps like...

Code:
(first) 5Hvqe4cm3iaHiaVvyyRj2vEQGY11113Q987NZ1BroCExQb3Hbfg
(second) 5Hvqe4cm3iaHiaVvyyRj2vEQGY11123Q987NZ1BroCExQb3Hbfg
(last) 5Hvqe4cm3iaHiaVvyyRj2vEQGYzzzz3Q987NZ1BroCExQb3Hbfg

(1) 800ee0f755f620249a6075b9511db7756e74c5ceb29bb48f2a1db0772fb0722c0d447e9fab
(2) 800ee0f755f620249a6075b9511db7756e74c5ceb2a3cdb2a956476a22bc2a5edb821e9fab
(3) 800ee0f755f620249a6075b9511db7756e74cb450feba4a247ac02d21afd23ed4800de9fab

(1') 0ee0f755f620249a6075b9511db7756e74c5ceb29bb48f2a1db0772fb0722c0d447e9fab
(2') 0ee0f755f620249a6075b9511db7756e74c5ceb2a3cdb2a956476a22bc2a5edb821e9fab
(3') 0ee0f755f620249a6075b9511db7756e74cb450feba4a247ac02d21afd23ed4800de9fab

(1'') 0ee0f755f620249a6075b9511db7756e74c5ceb29bb48f2a1db0772fb0722c0d
(2'') 0ee0f755f620249a6075b9511db7756e74c5ceb2a3cdb2a956476a22bc2a5edb
(3'') 0ee0f755f620249a6075b9511db7756e74cb450feba4a247ac02d21afd23ed48


--keyspace 0ee0f755f620249a6075b9511db7756e74c5ceb29bb48f2a1db0772fb0722c0d:0ee0f755f620249a6075b9511db7756e74cb450feba4a247ac02d21afd23ed48

(1''') 28904531490897711561887749949132137249603104743452438178887896886416998027619028869035
(2''') 28904531490897711561887749949132137249603104743463202530239465997930007122425245769643

difference(2''')-(1'''): 10764351351569111513009094806216900608

--stride 0819237f3896f2f30bb832ce

We have command like...

Code:
.\xxBitCrack -u --keyspace 0ee0f755f620249a6075b9511db7756e74c5ceb29bb48f2a1db0772fb0722c0d:0ee0f755f620249a6075b9511db7756e74cb450feba4a247ac02d21afd23ed48  --stride 819237f3896f2f30bb832ce  1HfPVDokgJQMtcT1d9qUt7UAEpfZyUhH1V

and...

Code:
[Info] Compression: uncompressed
[Info] Starting at: 0EE0F755F620249A6075B9511DB7756E74C5CEB29BB48F2A1DB0772FB0722C0D
[Info] Ending at:   0EE0F755F620249A6075B9511DB7756E74CB450FEBA4A247AC02D21AFD23ED48
[Info] Counting by: 00000000000000000000000000000000000000000819237F3896F2F30BB832CE
[Info] Compiling OpenCL kernels...
[Info] Initializing Ellesmere
(...)
[Info] 100.0%
[Info] Done
[Info] Reached end of keyspace

Nothing found.. any clues what is going on / what Im doing wrong?
Thanks!


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on August 12, 2019, 07:14:58 AM
Code:
[quote author=Telariust link=topic=4453897.msg52106273#msg52106273 date=1565320320]


4) BitCrack Performance Tips.
BitCrack may not optimally calculate the -t and -p parameters (halving the speed).
run with the option "--continue sess.txt", any address, for example
xxBitCrack --continue sess.txt 17GD2bc5b7SvU7bzN7CYUSc6h4zBJ36Rx6
wait a little longer than a minute until the file of saving the progress will not be created, turn off;
open sess.txt, for example, "threads = 256" (this is the -t option) and "points = 32" (this is the -p option)
try to double the value, the speed should double;
remember them and always add when running BitCrack, for example
xxBitCrack -t 512 -p 64 17GD2bc5b7SvU7bzN7CYUSc6h4zBJ36Rx6


[/quote]

In which folder is the sess.txt file saved - in the one where BitCrack is located OR in some other?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: chan111 on August 12, 2019, 08:33:24 AM
Code:
[quote author=Telariust link=topic=4453897.msg52106273#msg52106273 date=1565320320]


4) BitCrack Performance Tips.
BitCrack may not optimally calculate the -t and -p parameters (halving the speed).
run with the option "--continue sess.txt", any address, for example
xxBitCrack --continue sess.txt 17GD2bc5b7SvU7bzN7CYUSc6h4zBJ36Rx6
wait a little longer than a minute until the file of saving the progress will not be created, turn off;
open sess.txt, for example, "threads = 256" (this is the -t option) and "points = 32" (this is the -p option)
try to double the value, the speed should double;
remember them and always add when running BitCrack, for example
xxBitCrack -t 512 -p 64 17GD2bc5b7SvU7bzN7CYUSc6h4zBJ36Rx6



In which folder is the sess.txt file saved - in the one where BitCrack is located OR in some other?
[/quote]

Probably in location where you run the script. I think you can specify full path for session file, which would be probably the best option.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on August 12, 2019, 10:51:52 AM
C:\Users\Alex>F:\BRichard\clBitCrack.exe -d 1 -c -u --keyspace 001:180 --continue sess.txt 12FotmxA4hT2dbsibS8SmB4fXbLk8rtSpU
[2019-08-12.13:33:06] [Info] Compression: both
[2019-08-12.13:33:06] [Info] Starting at: 0000000000000000000000000000000000000000000000000000000000000001
[2019-08-12.13:33:06] [Info] Ending at:   0000000000000000000000000000000000000000000000000000000000000180
[2019-08-12.13:33:06] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-08-12.13:33:06] [Info] Compiling OpenCL kernels...
[2019-08-12.13:33:22] [Info] Initializing AMD A6-3420M APU with Radeon(tm) HD Graphics
[2019-08-12.13:33:22] [Info] Generating 262,144 starting points (10.0MB)
[2019-08-12.13:33:40] [Info] 10.0%
[2019-08-12.13:33:55] [Info] 20.0%
[2019-08-12.13:34:09] [Info] 30.0%
[2019-08-12.13:34:24] [Info] 40.0%
[2019-08-12.13:34:38] [Info] 50.0%
[2019-08-12.13:34:53] [Info] 60.0%
[2019-08-12.13:35:08] [Info] 70.0%
[2019-08-12.13:35:23] [Info] 80.0%
[2019-08-12.13:35:38] [Info] 90.0%
[2019-08-12.13:35:52] [Info] 100.0%
[2019-08-12.13:35:52] [Info] Done
[2019-08-12.13:35:53] [Info] Address:     12FotmxA4hT2dbsibS8SmB4fXbLk8rtSpU
                             Private key: 0000000000000000000000000000000000000000000000000000000000000168
                             Compressed:  no
                             Public key:
                             953365CF99092ECDB2F9A546E05CB0119CB012D173167742943296B9AEBB30D8
                             87AECB174E5018B2D7E5F7ECC00FFF007548DF4996FBA1C7132EDA351B0E6A8B

[2019-08-12.13:35:53] [Info] No targets remaining
[2019-08-12.13:35:53] [Info] Reached end of keyspace



Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Telariust on August 12, 2019, 12:57:35 PM
please, do not use quoting huge messages

Quote
4) BitCrack Performance Tips.
...
run with the option "--continue sess.txt", any address, for example
xxBitCrack --continue sess.txt 17GD2bc5b7SvU7bzN7CYUSc6h4zBJ36Rx6
wait a little longer than a minute until the file of saving the progress will not be created, turn off;
Quote
In which folder is the sess.txt file saved - in the one where BitCrack is located OR in some other?

in xxBitCrack.exe folder
u can direct run cmd shell in folder using trick: Shift+RightClickMouse -> Open Shell

https://github.com/brichard19/BitCrack/releases/tag/0.24
Quote
...FILE is updated every 60 seconds.

Nothing found.. any clues what is going on / what Im doing wrong?

hmm.. it not u.

when I wrote this I wanted to demonstrate that this is generally possible.
Now I see that I did not take into account special cases ...
need to consider and complement
.. manually calculating this is inconvenient, it's time to write a script


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on August 13, 2019, 08:31:26 AM
I thought that all addresses and the keys are located in space
From - 0000000000000000000000000000000000000000000000000000000000000001
Up to - FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

For the processor AMD A6-3420M APU with HD Graphics AMD Radeon HD 6520G I can use only software clBitCrack

Completely casually I have found out that this software clBitCrack can work in space
From - 0000000000000000000000000000000000000000000000000000000000000001
Up to - FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFebaaedce 6af48a03bbfd25e8cd0364140

Can someone explain, why software clBitCrack is limited?
Or I incorrectly have understood something?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on August 13, 2019, 08:55:50 AM
Completely casually I have found out that this software clBitCrack can work in space
From - 0000000000000000000000000000000000000000000000000000000000000001
Up to - FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFebaaedce 6af48a03bbfd25e8cd0364140

Can someone explain, why software clBitCrack is limited?
Or I incorrectly have understood something?

FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140 is the upper limit of the secp256k1 curve. Bitcrack is correctly refusing to go beyond this, because you cannot create a valid public key from a private key value above that. Some software will just wrap around back to zero, which is not a good thing, because (for example) :

A private key of FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364142

When wrapped, actually evaluates to a private key of 0000000000000000000000000000000000000000000000000000000000000001

(Not that having a private key right near the upper limits of the curve is safe, anyway...)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: avw on August 13, 2019, 09:38:31 AM
Why not add the ability to search by ripemd160 or known public key to speed up ::)
And which bitcrack version supports random key space function ?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on August 13, 2019, 10:02:17 AM
Why not add the ability to search by ripemd160 or known public key to speed up ::)
And which bitcrack version supports random key space function ?

From a cursory look at the source, it appears that it uses ripemd160 internally, converting from base58 at init, so that speed optimization is already done.

Matching against pubkey would be handy (if it doesn't already do this?)

Why would you want to search random key space?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on August 13, 2019, 10:15:46 AM

almightyruler   -   It is clear, THANKS!


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: avw on August 13, 2019, 01:06:46 PM
Why would you want to search random key space?
Someone mentioned in this topic(OP?) that there is a possibility, but I have not found..
At first glance, a random start in a given range seems more promising than a long straight road.
Something like Vanitygen, where the number changes every 1000000 passed keys


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Telariust on August 14, 2019, 03:55:07 AM
Why not add the ability to search by ripemd160 [...] to speed up
ripemd160(base16) <--> btcaddr(base58) <--> Int/Dec(base10) <--> Hex(base16) <--> Binary(base2)
it's the same thing, just the bases are different, converting
Why not add the ability to search by [...] known public key to speed up
Matching against pubkey would be handy (if it doesn't already do this?)
..because main target(puzzle) assumes a public key unknown (only its ripemd160 hash is known).
and if pubkey is known then sequential key search in a limited space (which uses bitcrack) is the stupidest and slowest way to search compared to baby-step-gigant-step algo and pollard-rho/kangaroo algo
when BitCrack compute 10M keys, its checked 10M keys
when BSGS/Pollard compute 10M keys, its checked (10M)^2 = 100000000M keys (!!!..undestand?)

And which bitcrack version supports random key space function ?
This fork https://github.com/pikachunakapika/BitCrack
Code:
-r, --random
    Each point will start in random KEYSPACE


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: tync on August 14, 2019, 04:16:05 AM

https://imgur.com/CoFCSa7
Is this 2123626 million or 2,123,626?
I'm using a Vega 64 with "clBitCrack.exe -b 500 -t 256 -p 1024 -c -u"
???? 2123626 Mkey/s . this is unrealistic speed. looks like a bug.
guys how much gives vega56?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: avw on August 14, 2019, 04:50:14 AM
Telariust, thank you very much ;)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on August 14, 2019, 07:26:46 AM
This function


-r, --random
    Each point will start in random KEYSPACE



must work in software clBitCrack.exe ?

I tried running on my laptops ( AMD A6-3420M APU with HD Graphics AMD Radeon HD 6520G ) - getting an error.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: chan111 on August 14, 2019, 09:40:11 AM
I tried running on my laptops ( AMD A6-3420M APU with HD Graphics AMD Radeon HD 6520G ) - getting an error.

You sure are using this fork of software?

Quote from: Telariust
(...)This fork https://github.com/pikachunakapika/BitCrack
Code:
-r, --random
    Each point will start in random KEYSPACE


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on August 14, 2019, 10:01:36 AM
If not I am mistaken took software clBitCrack.exe from this page - https://github.com/brichard19/BitCrack/releases

It absolutely other version software clBitCrack.exe?
In her there is no function "-r  --randoom"  ?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: avw on August 14, 2019, 10:34:26 AM
https://github.com/brichard19/BitCrack/
Description does not specify this function, so it is only in this fork - https://github.com/pikachunakapika/BitCrack


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on August 14, 2019, 11:24:13 AM
Here it is necessary to load completely (green button " Clone or download ") all in ZIP archive, and then to open archive on the computer?

in this fork - https://github.com/pikachunakapika/BitCrack

***

Whether and there is a combined variant of use of functions " - keyspace " and " -r, - randoom ", i.e. that worked so:

For example - we write -- keyspace 100000000000:500000000000 and -- random OR -- random 100000000000:500000000000 then The search is made only in a range 100000000000:500000000000, but casual (random like a flea or a kangaroo ) by jumps?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Angelo1710 on August 14, 2019, 11:49:47 AM
Can OP please add random (-r) function in the latest version of bitcrack?

Cheers

This version: https://github.com/pikachunakapika/BitCrack
Does not save private keys in txt at all, it is broken.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: avw on August 14, 2019, 12:55:04 PM
Here it is necessary to load completely (green button " Clone or download ") all in ZIP archive, and then to open archive on the computer?
This is the source code, you need to compile it in executable file (section "Building in Windows/Linux")

Whether and there is a combined variant of use of functions " - keyspace " and " -r, - randoom ", i.e. that worked so:

For example - we write -- keyspace 100000000000:500000000000 and -- random OR -- random 100000000000:500000000000 then The search is made only in a range 100000000000:500000000000, but casual (random like a flea or a kangaroo ) by jumps?
-r, --random
  Each point will start in random KEYSPACE


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Angelo1710 on August 14, 2019, 01:02:07 PM
Here it is necessary to load completely (green button " Clone or download ") all in ZIP archive, and then to open archive on the computer?
This is the source code, you need to compile it in executable file (section "Building in Windows/Linux")

Whether and there is a combined variant of use of functions " - keyspace " and " -r, - randoom ", i.e. that worked so:

For example - we write -- keyspace 100000000000:500000000000 and -- random OR -- random 100000000000:500000000000 then The search is made only in a range 100000000000:500000000000, but casual (random like a flea or a kangaroo ) by jumps?
-r, --random
  Each point will start in random KEYSPACE

https://github.com/pikachunakapika/BitCrack This version does not save key text file at all, just tested it, it's broken. Can someone add -r to the latest Bitcrack version, please?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: avw on August 14, 2019, 02:25:44 PM
This version does not save key text file at all, just tested it, it's broken.
Maybe bitcrack writing output file to the wrong directory where you're looking?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Angelo1710 on August 14, 2019, 03:41:45 PM
This version does not save key text file at all, just tested it, it's broken.
Maybe bitcrack writing output file to the wrong directory where you're looking?

Well I tried with -o file command and without and no file was saved when the key was found, then I tried the same in the latest version and it worked perfectly.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: avw on August 14, 2019, 04:49:31 PM
Well I tried with -o file command and without and no file was saved when the key was found, then I tried the same in the latest version and it worked perfectly.
When I tried on Windows to run the original bitcrack, it saved output file in windows/system32.
Try naming the file non-standard way, run bc, and then searching for the file in system.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Angelo1710 on August 15, 2019, 06:26:26 AM
Well I tried with -o file command and without and no file was saved when the key was found, then I tried the same in the latest version and it worked perfectly.
When I tried on Windows to run the original bitcrack, it saved output file in windows/system32.
Try naming the file non-standard way, run bc, and then searching for the file in system.

Tried and no textfile was found in system32. I really wish someone can add -r to the latest version.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on August 15, 2019, 06:54:11 AM
If to add function " -r, - randoom " in last version, it is desirable to make two variants it is functions:

1 - " -r, - randoom " - the search by casual jumps in all space is made;
2 - " -r START:END, - randoom START:END " - the search by casual jumps in the given (desirable) space is made

OR

1 - if not the function - keyspace - is given then the search by casual jumps in all space is made;
2 - if the function - keyspace - is specified then the search by casual jumps only in the specified space is made;


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Angelo1710 on August 15, 2019, 08:17:04 PM
Well I tried with -o file command and without and no file was saved when the key was found, then I tried the same in the latest version and it worked perfectly.
When I tried on Windows to run the original bitcrack, it saved output file in windows/system32.
Try naming the file non-standard way, run bc, and then searching for the file in system.

Tried and no textfile was found in system32. I really wish someone can add -r to the latest version.

Got it to work but it seems it just randomly searching in 252-256 space, so it is not 'really' random.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: avw on August 15, 2019, 08:45:48 PM
It looks like it can work random in the specified keyspace:
https://github.com/pikachunakapika/BitCrack/issues/13
https://github.com/pikachunakapika/BitCrack/issues/3
Try "--keyspace START:END" and "-r" flags together


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Angelo1710 on August 15, 2019, 08:57:36 PM
It looks like it can work random in the specified keyspace:
https://github.com/pikachunakapika/BitCrack/issues/13
https://github.com/pikachunakapika/BitCrack/issues/3
Try "--keyspace START:END" and "-r" flags together

Tnx man, that did the trick. It works


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on August 15, 2019, 11:49:08 PM
I'm still not sure how randomly hopping around a massive search space will improve your chances of finding a match.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on August 16, 2019, 11:59:29 AM
     avw  -  This is the source code, you need to compile it in executable file (section "Building in Windows/Linux")

How to install is understandable.

How to compile -  https://github.com/pikachunakapika/BitCrack ?
Maybe somewhere there is a step-by-step explanation of how to COMPILE -?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Telariust on August 19, 2019, 01:34:02 PM
Quote from: Telariust
Quote from: chan111
Nothing found.. any clues what is going on / what Im doing wrong?

hmm.. it not u.

when I wrote this I wanted to demonstrate that this is generally possible.
Now I see that I did not take into account special cases ...
need to consider and complement
.. manually calculating this is inconvenient, it's time to write a script

python3 script success wrote and add to faq post:
bitcointalk.org/index.php?topic=4453897.msg52106273#msg52106273

if the checksum(or/and flag compress x01) is corrupted, than recovery now is impossible.
(--stride opt becomes float but must be integer!)
Recovery of these keys is possible only if brichard19 implements support float for --stride opt.

if it is easier to explain..
In WIFbase58privkey, each lost symbol(*/?) to the right is a division stride by 58.
Already from the middle, the stride no longer divides completely.
What does checksum have to do with it? In fact, the checksum forms the float part.
While it is equal, then when subtracting it is reset.
As soon as it becomes different for lowerKey and lowerKey+1, this indicates - stride becomes float.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Angelo1710 on September 01, 2019, 03:05:32 PM
Anyone can fork the latest version of Bitcrack to do random searches on each point?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on September 02, 2019, 06:20:43 AM
Where to take for AMD the ready version clBitcrack.exe (which it is not necessary to compile and simply to start from a command line) with functions -r, --random
    Each point will start in random KEYSPACE :

xxBitCrack.exe [OPTIONS] [TARGETS]

Where [TARGETS] are one or more Bitcoin address

Options:

-i, --in FILE
    Read addresses from FILE, one address per line. If FILE is "-" then stdin is read

-o, --out FILE
    Append private keys to FILE, one per line

-d, --device N
    Use device with ID equal to N

-b, --blocks BLOCKS
    The number of CUDA blocks

-t, --threads THREADS
    Threads per block

-p, --points NUMBER
    Each thread will process NUMBER keys at a time

-r, --random
    Each point will start in random KEYSPACE


--keyspace KEYSPACE
    Specify the range of keys to search, where KEYSPACE is in the format,

   START:END start at key START, end at key END
   START:+COUNT start at key START and end at key START + COUNT
    :END start at key 1 and end at key END
   :+COUNT start at key 1 and end at key 1 + COUNT

-c, --compressed
    Search for compressed keys (default). Can be used with -u to also search uncompressed keys

-u, --uncompressed
    Search for uncompressed keys, can be used with -c to search compressed keys

--compression MODE
    Specify the compression mode, where MODE is 'compressed' or 'uncompressed' or 'both'

--list-devices
    List available devices

--stride NUMBER
    Increment by NUMBER

--share M/N
    Divide the keyspace into N equal sized shares, process the Mth share

--continue FILE
    Save/load progress from FILE


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: vimp666 on September 02, 2019, 03:09:49 PM
Where to take for AMD the ready version clBitcrack.exe (which it is not necessary to compile and simply to start from a command line) with functions -r, --random
    

and if you click on the releases on the page you will definitely find it https://github.com/pikachunakapika/BitCrack/releases


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on September 02, 2019, 07:13:13 PM
 vimp666  -  THANK !!! It works, this is what I was looking for.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: MercyLu on September 03, 2019, 06:17:50 AM
How to compile, anyone know?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on September 03, 2019, 06:55:50 AM
How to compile, anyone know?

This does not need to be compiled  - https://github.com/pikachunakapika/BitCrack/releases .
Download to your hard drive software  "clBitCrack.exe" .
You start from the command line (cmd) - you specify the path to clBitCrack.exe and search parameters.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: tync on September 03, 2019, 01:38:33 PM
Hello My rx470 4gb gives only 80Mkey/s it's normal?
I tested with these parameters in Windows 10 : clBitCrack.exe -b 32 -t 256 -p 4096 -c 1FRoHA9xewq7DjrZ1psWJVeTer8gHRqEvR
as I understand it for cards from AMD this program is poorly optimized  :(


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: ETFbitcoin on September 03, 2019, 05:13:21 PM
Hello My rx470 4gb gives only 80Mkey/s it's normal?
I tested with these parameters in Windows 10 : clBitCrack.exe -b 32 -t 256 -p 4096 -c 1FRoHA9xewq7DjrZ1psWJVeTer8gHRqEvR
as I understand it for cards from AMD this program is poorly optimized  :(

You might want to check earlier posts :

  • RX 480 is have 20% faster speed, but few websites (such as UserBenchmark (http://=https://gpu.userbenchmark.com/Compare/AMD-RX-480-vs-AMD-RX-470/3634vs3640) report RX 480 generally only 10% faster on non-gaming benchmark

Rx480 8Gb     107.04 MKey/s
clBitCrack  --b 72 -t 256 -p 2048

Rx480 4Gb     100.00 MKey/s
clBitCrack  --b 72 -t 256 -p 1024

  • A user with RX 570 (which is rebrand of RX 470) recommend these parameter, you might get better speed with this parameter

For RX 570, what are CLBitcrack -b -t and -p?  Please... :)

Rx570 has 32 compute units , try this
-b 64 -t 256 -p 1024

TLDR : looks like the speed is nearly normal, but it could be faster or optimized


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: tync on September 03, 2019, 05:45:25 PM
ETFbitcoin thanks
but I already tried it and got no difference -b 64
rx470 only 32 compute units . I noticed that the speed is affected by the core clock. 
but since my video card has poor cooling, I think the 83Mkey/s limit is for me. I wanted to try the VanitySearch, but as it turned out, it works only with Nvidia ;D
i am going to buy GTX 1080.
I’m very interested in what speed the vega(56,64) has


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: tync on September 03, 2019, 06:41:47 PM
https://docs.google.com/spreadsheets/d/1Xy0kkwB6Jkqo7CEprS-GtcUp3dZFWzV_FvZqWNHWmBM/edit#gid=785768233


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: tync on September 03, 2019, 06:46:58 PM
https://docs.google.com/spreadsheets/d/1Xy0kkwB6Jkqo7CEprS-GtcUp3dZFWzV_FvZqWNHWmBM/edit#gid=785768233
in this benchmark hashcat amd vega 64 better than gtx 1080 for algoritms RIPEMD-160(14%) and SHA-256(30%)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Angelo1710 on September 05, 2019, 07:24:19 PM
Can some1 fork latest version of bitcrack so it does -r random on every point across selected keyspace. So every jump/try is random. Not like in pikachunakapika version where it chooses random staring points and then starts doing them in 1 increment at a time. Kinda like generating random hex key on each try within selected keyspace.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Telariust on September 05, 2019, 11:11:03 PM
Quote
..random on every point across selected keyspace. So every jump/try is random. Not like in pikachunakapika version where it chooses random staring points and then starts doing them in 1 increment at a time..

The Engine of these programs is divided into two types:

1) optimized point addition (for quick calculation of sequential keys)
 sample programs: vanitygen, bitcrack, vanitysearch, break_short;
 methods:
 - calc only X coordinates (for compressed keys);
 - use of functions without protection against side channel attacks (openssl/secp256k1);
main problem - inversion calculation is very expensive, ~20mult per 1 point;
can use batch inversion (Simultaneous algorithm, 1 inversion per 1000 keys) + Affines coordinates + symmetry(only full range) + endomorphism(only full range);

2) optimized point multiplication (for quick calculation of random keys)
 sample programs: brainflayer;
 methods:
 - secp256k1 library with pre-calculated mult table in ram;
 - Jacobian coordinates;
main problem random mult - inversion need too, but can not use batch inversion because each key is random.

BitCrack is optimized for sequentially calculating points in a limited range using addition.
VanitySearch is optimized for sequentially calculating points in the full range using addition (and 4 multiplication algorithms that work only for the full range).
BrainFlayer (cpu only) is optimized for random calculating points in a full range using multiplication.
You want to get random points in a limited range using multiplication.
These are fundamentally different tasks.

If you delve into the study of random generators, you will find that they have top speed.
Typically, the problem is that the overhead of generating random numbers is greater than the useful calculation itself.

PS:
about multiplication
At start BitCrack, pre-computes the starting points using multiplication.
It is so slow that starting from version 0.15 the author transferred the procedure to gpu.

see 1post - v0.0.6...  the author does not come here for more than a year


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Angelo1710 on September 06, 2019, 01:01:27 PM
Quote
..random on every point across selected keyspace. So every jump/try is random. Not like in pikachunakapika version where it chooses random staring points and then starts doing them in 1 increment at a time..

The Engine of these programs is divided into two types:

1) optimized point addition (for quick calculation of sequential keys)
 sample programs: vanitygen, bitcrack, vanitysearch, break_short;
 methods:
 - calc only X coordinates (for compressed keys);
 - use of functions without protection against side channel attacks (openssl/secp256k1);
main problem - inversion calculation is very expensive, ~20mult per 1 point;
can use batch inversion (Simultaneous algorithm, 1 inversion per 1000 keys) + Affines coordinates + symmetry(only full range) + endomorphism(only full range);

2) optimized point multiplication (for quick calculation of random keys)
 sample programs: brainflayer;
 methods:
 - secp256k1 library with pre-calculated mult table in ram;
 - Jacobian coordinates;
main problem random mult - inversion need too, but can not use batch inversion because each key is random.

BitCrack is optimized for sequentially calculating points in a limited range using addition.
VanitySearch is optimized for sequentially calculating points in the full range using addition (and 4 multiplication algorithms that work only for the full range).
BrainFlayer (cpu only) is optimized for random calculating points in a full range using multiplication.
You want to get random points in a limited range using multiplication.
These are fundamentally different tasks.

If you delve into the study of random generators, you will find that they have top speed.
Typically, the problem is that the overhead of generating random numbers is greater than the useful calculation itself.

PS:
about multiplication
At start BitCrack, pre-computes the starting points using multiplication.
It is so slow that starting from version 0.15 the author transferred the procedure to gpu.

see 1post - v0.0.6...  the author does not come here for more than a year

Ty for your explanation, I can't pm u back because of messaging limits. So basically there is no way to combine really fast random hex generator to work with the calculation process? So all we can do is randomly get starting points and from there work in increments.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Telariust on September 06, 2019, 05:09:37 PM
Quote from: Angelo1710
..Ty for your explanation, I can't pm u back because of messaging limits. So basically there is no way to combine really fast random hex generator to work with the calculation process? So all we can do is randomly get starting points and from there work in increments.
True, according to my knowledge after 1 year of research.

In fact, you want a gpu BrainFlayer. Everyone wants it)
Ryan refuses to write it because he is a WhiteHat.

If successful, it will be slower than sequentially calculating points.

##########################
heuristic calculate the hashrate for BrainFlayer cuda/opencl

BrainFlayer cpu sse
0,1 Mk/s - 1core i7-6820
8core - 4core real, 4core hyper-threading, so x6 instead x8
0,6 Mk/s - 8core i7-6820

VanityGen x64 opencl
60.7 Mk/s - gtx980
0,52 Mk/s - 8core i7-6820

60.7/0,52 = x116,7 (vg opencl gpu/cpu)

VanityGen x64 cpu sse
1,38 Mk/s - 8core i7-6820

1,38/0,52 = x2,6 (vg sse/opencl)

now if imagine
BrainFlayer opencl
0,6x(1/2,6) = 0,23 Mk/s - 8core i7-6820
0,23x116,7 = 26,8 Mk/s - gtx980

if
clBitCrack opencl
67.7 Mk/s - gtx980
cuBitCrack cuda
153.5 Mk/s - gtx980
241.3 Mk/s - gtx1070

153.5/67.7 = x2,26 (bc cuda/opencl)

then
BrainFlayer cuda
26,8x2,26 = 60,5 Mk/s  - gtx980
60,5x(241.3/153.5) = 94,9 Mk/s  - gtx1070


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Angelo1710 on September 06, 2019, 06:47:52 PM
Quote from: Angelo1710
..Ty for your explanation, I can't pm u back because of messaging limits. So basically there is no way to combine really fast random hex generator to work with the calculation process? So all we can do is randomly get starting points and from there work in increments.
True, according to my knowledge after 1 year of research.

In fact, you want a gpu BrainFlayer. Everyone wants it)
Ryan refuses to write it because he is a WhiteHat.

If successful, it will be slower than sequentially calculating points.

##########################
heuristic calculate the hashrate for BrainFlayer cuda/opencl

BrainFlayer cpu sse
0,1 Mk/s - 1core i7-6820
8core - 4core real, 4core hyper-threading, so x6 instead x8
0,6 Mk/s - 8core i7-6820

VanityGen x64 opencl
60.7 Mk/s - gtx980
0,52 Mk/s - 8core i7-6820

60.7/0,52 = x116,7 (vg opencl gpu/cpu)

VanityGen x64 cpu sse
1,38 Mk/s - 8core i7-6820

1,38/0,52 = x2,6 (vg sse/opencl)

now if imagine
BrainFlayer opencl
0,6x(1/2,6) = 0,23 Mk/s - 8core i7-6820
0,23x116,7 = 26,8 Mk/s - gtx980

if
clBitCrack opencl
67.7 Mk/s - gtx980
cuBitCrack cuda
153.5 Mk/s - gtx980
241.3 Mk/s - gtx1070

153.5/67.7 = x2,26 (bc cuda/opencl)

then
BrainFlayer cuda
26,8x2,26 = 60,5 Mk/s  - gtx980
60,5x(241.3/153.5) = 94,9 Mk/s  - gtx1070


Thanks, nice info. What about pollard-rho versions of this people talk in other threads, but there is no publicly available tool to try it (to my knowledge)?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on September 07, 2019, 01:40:14 AM
Quote from: Angelo1710
..Ty for your explanation, I can't pm u back because of messaging limits. So basically there is no way to combine really fast random hex generator to work with the calculation process? So all we can do is randomly get starting points and from there work in increments.
True, according to my knowledge after 1 year of research.

In fact, you want a gpu BrainFlayer. Everyone wants it)
Ryan refuses to write it because he is a WhiteHat.

If successful, it will be slower than sequentially calculating points.

##########################
heuristic calculate the hashrate for BrainFlayer cuda/opencl

BrainFlayer cpu sse
0,1 Mk/s - 1core i7-6820
8core - 4core real, 4core hyper-threading, so x6 instead x8
0,6 Mk/s - 8core i7-6820

You'd probably need to perform string mangling on the GPU to keep the cores working as much as possible, because the transfer of each and every candidate phrase from CPU/system memory to the GPU could end up being a severe bottleneck. Perhaps a deliberately slower algorithm like warp may work better, since the GPU will spend most of its time calculating rather than transferring to/from the host... but how common are non SHA256 brainwallets? As you state, any passphrase based search (which is essentially a set of random keys) will be slower than a sequential search.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Telariust on September 07, 2019, 10:58:04 AM
Quote
What about pollard-rho versions of this people talk in other threads, but there is no publicly available tool to try it (to my knowledge)?
https://bitcointalk.org/index.php?topic=5166284.msg52318676#msg52318676

You'd probably need to perform string mangling on the GPU to keep the cores working as much as possible, because the transfer of each and every candidate phrase from CPU/system memory to the GPU could end up being a severe bottleneck. Perhaps a deliberately slower algorithm like warp may work better, since the GPU will spend most of its time calculating rather than transferring to/from the host... but how common are non SHA256 brainwallets? As you state, any passphrase based search (which is essentially a set of random keys) will be slower than a sequential search.

I also thought so for a long time.
not really if the size does not exceed 49152
Code:
 size_t stackSize = 49152;
  err = cudaDeviceSetLimit(cudaLimitStackSize, stackSize);
..For VanitySearch, having a smaller group size is better (This is a reason why I worked a lot on this DRS62 ModInv implementation). I can double the size of the group (I will definitely do it) but not more. The GPU kernel performs one group per thread and send back hash160 to the CPU. If the group size is too large, memory transfer and allocation become a problem. Divide and rule ;)
VanitySearch restarts the kernel about 1000 times per second (!!!), and it works fine.
opencl unknow

..and this is one of the main technical reasons why gpu BF do not.
cpu BF checks huge dictionaries in a few hours. loading such volumes into gpu is problematic.
therefore gpu BF should work using the built-in generator, e.g. brute force seed.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Serj88 on September 13, 2019, 09:11:45 AM
How to prevent brute-forcing private keys?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Archi606 on September 15, 2019, 02:11:20 PM
C:\Users\Mashine-5\source\repos\BitCrack2\x64\Debug>cuBitCrack.exe -i key.txt -o key1.txt
[2019-09-15.17:02:27] [Info] Compression: compressed
[2019-09-15.17:02:27] [Info] Starting at: 0000000000000000000000000000000000000000000000000000000000000001
[2019-09-15.17:02:27] [Info] Ending at:   FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
[2019-09-15.17:02:27] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-09-15.17:02:27] [Info] Initializing GeForce GTX 1060 6GB
[2019-09-15.17:02:27] [Info] Generating 262,144 starting points (10.0MB)
[2019-09-15.17:02:30] [Info] 10.0%
[2019-09-15.17:02:32] [Info] 20.0%
[2019-09-15.17:02:35] [Info] 30.0%
[2019-09-15.17:02:37] [Info] 40.0%
[2019-09-15.17:02:39] [Info] 50.0%
[2019-09-15.17:02:41] [Info] 60.0%
[2019-09-15.17:02:43] [Info] 70.0%
[2019-09-15.17:02:46] [Info] 80.0%
[2019-09-15.17:02:48] [Info] 90.0%
[2019-09-15.17:02:50] [Info] 100.0%
[2019-09-15.17:02:50] [Info] Done
[2019-09-15.17:02:50] [Info] Loading addresses from 'key.txt'
[2019-09-15.17:02:50] [Info] 1 addresses loaded (0.0MB)
GeForce GTX 1060 1083 / 6144MB | 1 target 1.25 MKey/s (11,796,480 total) [00:00:07]




Hello!

Why such a low rate?
There is a detailed setting, please tell me)
Maybe something is installed incorrectly


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: bartekjagoda on September 15, 2019, 03:27:42 PM
Quote from: Angelo1710
..Ty for your explanation, I can't pm u back because of messaging limits. So basically there is no way to combine really fast random hex generator to work with the calculation process? So all we can do is randomly get starting points and from there work in increments.
True, according to my knowledge after 1 year of research.

In fact, you want a gpu BrainFlayer. Everyone wants it)
Ryan refuses to write it because he is a WhiteHat.

If successful, it will be slower than sequentially calculating points.

##########################
heuristic calculate the hashrate for BrainFlayer cuda/opencl

BrainFlayer cpu sse
0,1 Mk/s - 1core i7-6820
8core - 4core real, 4core hyper-threading, so x6 instead x8
0,6 Mk/s - 8core i7-6820

VanityGen x64 opencl
60.7 Mk/s - gtx980
0,52 Mk/s - 8core i7-6820

60.7/0,52 = x116,7 (vg opencl gpu/cpu)

VanityGen x64 cpu sse
1,38 Mk/s - 8core i7-6820

1,38/0,52 = x2,6 (vg sse/opencl)

now if imagine
BrainFlayer opencl
0,6x(1/2,6) = 0,23 Mk/s - 8core i7-6820
0,23x116,7 = 26,8 Mk/s - gtx980

if
clBitCrack opencl
67.7 Mk/s - gtx980
cuBitCrack cuda
153.5 Mk/s - gtx980
241.3 Mk/s - gtx1070

153.5/67.7 = x2,26 (bc cuda/opencl)

then
BrainFlayer cuda
26,8x2,26 = 60,5 Mk/s  - gtx980
60,5x(241.3/153.5) = 94,9 Mk/s  - gtx1070


I have a GPU brainflayer, 1 billion hashes /sec on 8 x RX570

You can send me PM if interested


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: thunderclouds on September 17, 2019, 03:42:14 PM
Hi all, im currently getting only around 3 MKey/s using a GTX 1080 8GB, ive seen others getting 300 MKey/s, i have tried the card on two different PC's with a fresh install(win10), yet both give the same rate.

This is my config,
Code:
-b 36 -t 128 -p 800

I have tried to play with the numbers but crash the card if i go too high, could anyone suggest a soloution.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on September 17, 2019, 05:06:45 PM

I have a GPU brainflayer, 1 billion hashes /sec on 8 x RX570

You can send me PM if interested
[/quote]

bartekjagoda  

How to send you PM if you have "closed"?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: RPL_Ryan on September 19, 2019, 02:26:39 PM
Is anyone else having issues running multiple instances?  I have a 7 card gpu rig, if initiate 2+ instances I get a computer crash. Windows 10, cl initiate.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: balskiy on October 03, 2019, 10:25:05 PM
Hi, how to use cuBitCrack.exe on multiple gpu?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on October 08, 2019, 08:51:18 AM
Probably at I have very weak laptop there is no large difference on speed from change of parameters - t - p (in clBitCrack.exe)
The quantity Generating starting points depends on parameters - t - p
Than meanings of parameters - t - p by that more will be more generated Generating starting points
I think, probably, than will be more generated Generating starting points - the better?
Who knows precisely - explain.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: balskiy on October 08, 2019, 10:52:33 AM
Probably at I have very weak laptop there is no large difference on speed from change of parameters - t - p (in clBitCrack.exe)
The quantity Generating starting points depends on parameters - t - p
Than meanings of parameters - t - p by that more will be more generated Generating starting points
I think, probably, than will be more generated Generating starting points - the better?
Who knows precisely - explain.
Hi, read the link https://bitcointalk.org/index.php?topic=5166284.msg52255756#msg52255756


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: bartekjagoda on October 08, 2019, 04:57:00 PM

I have a GPU brainflayer, 1 billion hashes /sec on 8 x RX570

You can send me PM if interested

bartekjagoda  

How to send you PM if you have "closed"?
[/quote]

I have opened my box for newbies
I usually get 160-220Mkeys per second depending on the size of addresses to check. Has been doing 100lists


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on October 08, 2019, 07:26:27 PM
Probably at I have very weak laptop there is no large difference on speed from change of parameters - t - p (in clBitCrack.exe)
The quantity Generating starting points depends on parameters - t - p
Than meanings of parameters - t - p by that more will be more generated Generating starting points
I think, probably, than will be more generated Generating starting points - the better?
Who knows precisely - explain.
Hi, read the link https://bitcointalk.org/index.php?topic=5166284.msg52255756#msg52255756

I so have understood, that cuBitCrack and CUDA for processors Intel witch a video cards NVIDA
Mine laptop - AMD A6-3420M APU with AMD Radeon HD 6520G
Therefore I use OpenCL and clBitCrack
Unless cuBitCrack and CUDA will work with such configuration?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: balskiy on October 08, 2019, 08:07:05 PM
Probably at I have very weak laptop there is no large difference on speed from change of parameters - t - p (in clBitCrack.exe)
The quantity Generating starting points depends on parameters - t - p
Than meanings of parameters - t - p by that more will be more generated Generating starting points
I think, probably, than will be more generated Generating starting points - the better?
Who knows precisely - explain.
Hi, read the link https://bitcointalk.org/index.php?topic=5166284.msg52255756#msg52255756

I so have understood, that cuBitCrack and CUDA for processors Intel witch a video cards NVIDA
Mine laptop - AMD A6-3420M APU with AMD Radeon HD 6520G
Therefore I use OpenCL and clBitCrack
Unless cuBitCrack and CUDA will work with such configuration?

You need clBitCrack, but the setup principle is the same as for cuBitCrack.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on October 08, 2019, 08:09:38 PM

I have a GPU brainflayer, 1 billion hashes /sec on 8 x RX570

You can send me PM if interested

bartekjagoda  

How to send you PM if you have "closed"?

I have opened my box for newbies
I usually get 160-220Mkeys per second depending on the size of addresses to check. Has been doing 100lists
[/quote]

I send PM to you


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: bartekjagoda on October 09, 2019, 05:21:18 PM
Hi all, im currently getting only around 3 MKey/s using a GTX 1080 8GB, ive seen others getting 300 MKey/s, i have tried the card on two different PC's with a fresh install(win10), yet both give the same rate.

This is my config,
Code:
-b 36 -t 128 -p 800

I have tried to play with the numbers but crash the card if i go too high, could anyone suggest a soloution.

Your CUDA drivers might be wrong, which version do you use?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on October 11, 2019, 07:35:53 AM
Hey guys, newbie here glad I found this thread. I'm not a programmer or know how to brute force these bitcoin wallets.

Iv'e been working on a new way to store your private keys privately and securely out in the open. Essentially if somebody can have access to your private key, They will be unable to unlock the wallet.

In this image I put a private key that is missing 13 characters. If you can guess the password, you can have access to decrypting the characters needed to unlock the private key.

If anyone can crack this private key, they can have access to some Bitcoin I sent to it.

I'm trying to understand why you would want to store a private key "out in the open"? With 13 characters to brute force, the key is still going to be 'difficult' to break, but certainly a lot easier than if the entire key was kept private. Since the password appears to map letters and numbers to the missing base58 parts of the key, based on statistical analysis of language, the search space could be narrowed down considerably.

Can you reveal the address and sign a message to prove this is a real challenge?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on October 11, 2019, 08:34:19 AM
Sure, the Bitcion Address is 1C2SvZUDaSr6zzTTZr7vNeCo5jbz1bwiGe


I will send 0.00007185 BTC in the next couple of minutes to prove I signed the transaction.

Yeah, but again: why?

Is this simply a fun challenge, or are you planning to use (and promote) this method of storing private keys?

As has been proven in the puzzle challenge thread, brute forcing ~76 bits (in this case) of key is not impossible.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: nc50lc on October 11, 2019, 08:38:12 AM
In this image I put a private key that is missing 13 characters. If you can guess the password, you can have access to decrypting the characters needed to unlock the private key.
IDK what you're making but it's so wrong in so many levels.

First, it's missing 14 characters (not 13)  :-\
Next, looks like the private key is in compressed WIF format which should be in base58 encoding,
means that there shouldn't be any zero, capital "o", lower-case "L" and capital "i" in the list; but there's an "O" and a "0" in the table.

Lastly, why all caps? Is your 1C2SvZUDaSr6zzTTZr7vNeCo5jbz1bwiGe address' WIF private key all-caps?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Breadyfreddy on October 11, 2019, 08:41:00 AM
Im planning on implementing this in my notebook that is launching this year. A notebook to store private keys. Shieldfolio.com

The goal is to help users store private keys privately in case somebody stumbles upon these private keys.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on October 11, 2019, 09:05:14 AM
Im planning on implementing this in my notebook that is launching this year. A notebook to store private keys. Shieldfolio.com

The goal is to help users store private keys privately in case somebody stumbles upon these private keys.

Make a secret less secret by default just in case someone stumbles upon that secret?

How does revealing part of a private key make it more private?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Breadyfreddy on October 11, 2019, 09:16:35 AM
true but would you rather have somebody find your paper wallet private keys in plain sight or give a challenge to the perp to securely prevent lost bitcoins. Of course I recommend you have another back up in a different location to prevent the central point of failure.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Breadyfreddy on October 11, 2019, 09:43:13 AM
Im actually redoing the formula, noticed that bitcoin private keys are case sensitive.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: nc50lc on October 11, 2019, 09:50:49 AM
Im actually redoing the formula, noticed that bitcoin private keys are case sensitive.
Also the "decryption table" below,
you're accidentally giving away clues that those characters pointing to invalid characters shouldn't be used.
(read my post above)

You get what I mean?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: iparktur on October 11, 2019, 10:50:10 AM
Hey guys, newbie here glad I found this thread. I'm not a programmer or know how to brute force these bitcoin wallets.

Iv'e been working on a new way to store your private keys privately and securely out in the open. Essentially if somebody can have access to your private key, They will be unable to unlock the wallet.

In this image I put a private key that is missing 13 characters. If you can guess the password, you can have access to decrypting the characters needed to unlock the private key.

If anyone can crack this private key, they can have access to some Bitcoin I sent to it.



       Good luck guys. Freddy.



https://imgur.com/a/qZgDBF3

You want, that for 0.00136069 BTC (it is less than $ 12 on a today's rate) someone seriously has engaged in your riddle?


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: Breadyfreddy on October 11, 2019, 11:03:00 AM
Here is the updated Shieldcrypt with 16 hidden characters.


https://imgur.com/a/wl9lwgs


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: pooya87 on October 11, 2019, 11:14:53 AM
In this image I put a private key that is missing 13 characters. If you can guess the password, you can have access to decrypting the characters needed to unlock the private key.

If anyone can crack this private key, they can have access to some Bitcoin I sent to it.

that's not a private key because as other user pointed out you capitalized all the letters which means you yourself won't be able to recover it without brute forcing!
secondly, when you put up a challenge like this there has to be enough incentive for anybody to even bother looking into it. it is a work versus reward thing. 10 bucks reward would only be worth it if only 3 characters were missing :D

true but would you rather have somebody find your paper wallet private keys in plain sight or give a challenge to the perp to securely prevent lost bitcoins. Of course I recommend you have another back up in a different location to prevent the central point of failure.

the "somebody" first has to
- come to my home be able to enter it
- then go through all my shit and find the keys wherever i have written them
- then has to figure out whether it is a key or not since it doesn't look like it
- then he has to sit down for a million years trying to break the AES encryption i have used on it ;)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: rosengold on October 11, 2019, 01:51:14 PM
Quote
10 bucks reward would only be worth it if only 3 characters were missing

For 10 bucks you can power up my computer for 10 minutes  :P

c'mon bro put a decent bitcoin on that and we'll start to play, 16 char long to guess a private key it's a good challenge, even with bitcrack and a 2080Ti GPU.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: bounty0z on October 12, 2019, 11:34:49 AM
I don't know more about btc, but about ETH I have an idea if its true . your program take as input the public key and try to generate private key. why not create program that generate private keys randomly, and tried to know if your private key generated is linked to a user wallet ? I think this may be possible than tried to generate private key of unique wallet.
If I make any error about understanding please correct me. I am still understanding how blockchain work


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: rosengold on October 12, 2019, 08:40:19 PM
I don't know more about btc, but about ETH I have an idea if its true . your program take as input the public key and try to generate private key. why not create program that generate private keys randomly, and tried to know if your private key generated is linked to a user wallet ? I think this may be possible than tried to generate private key of unique wallet.
If I make any error about understanding please correct me. I am still understanding how blockchain work
Nope, he's trying to create a security layer for the private key in case of lost, where to access the funds you need to guess the password, very like a type of brainwallet, the problem is: since you reveal parts of your private key, the key isn't too private anymore and it's a matter of time to anyone with knowledge and computer power (Home PC, Google Cloud Engine, whatever) access the funds.
I'm totally sure that no one still did that because of tiny ammount of money on wallet, put more money on that and you see how the magic happens  :P


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: bellicose on October 12, 2019, 08:45:19 PM
Absolutely useless program. No matter how lucky you are, you can never find a single private key with bitcoins in address. This is the same as looking for a grain of sand in the universe. By the way, there is an explanation, but now I can’t find the link to the site.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: rosengold on October 12, 2019, 08:55:47 PM
Absolutely useless program. No matter how lucky you are, you can never find a single private key with bitcoins in address. This is the same as looking for a grain of sand in the universe. By the way, there is an explanation, but now I can’t find the link to the site.

Unless for weak private keys like on 100 BTC Challenge (https://bitcointalk.org/index.php?topic=5166284.0)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: almightyruler on October 13, 2019, 08:17:19 AM
Absolutely useless program. No matter how lucky you are, you can never find a single private key with bitcoins in address. This is the same as looking for a grain of sand in the universe. By the way, there is an explanation, but now I can’t find the link to the site.

The first paragraph in the OP states why this program exists (and is useful for that purpose)

I've been working on a tool for brute-forcing Bitcoin private keys. The main purpose of this tool is to contribute to the effort of solving the Bitcoin puzzle transactions: https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15 (https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15)


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: bounty0z on October 13, 2019, 03:10:20 PM
Absolutely useless program. No matter how lucky you are, you can never find a single private key with bitcoins in address. This is the same as looking for a grain of sand in the universe. By the way, there is an explanation, but now I can’t find the link to the site.

Unless for weak private keys like on 100 BTC Challenge (https://bitcointalk.org/index.php?topic=5166284.0)
Thank you for your information, You have any idea about this tool in linux ?
I don't know why I can't "make" always problem in code.
Please if you have any similar program that can be run in linux share it with me.
Thanks


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: pilosopotasyo on October 14, 2019, 02:50:00 AM
Absolutely useless program. No matter how lucky you are, you can never find a single private key with bitcoins in address. This is the same as looking for a grain of sand in the universe. By the way, there is an explanation, but now I can’t find the link to the site.

There will be people trying an impossible task, what if they can, what if they found a method to crack any address, what if they can steal from these addresses, let's just pray no genius finds a way to do this, or everything will be over, all dreams will be shattered.


Title: Re: BitCrack - A tool for brute-forcing private keys
Post by: ewaspiro on October 14, 2019, 11:55:40 AM
Absolutely useless program. No matter how lucky you are, you can never find a single private key with bitcoins in address. This is the same as looking for a grain of sand in the universe. By the way, there is an explanation, but now I can’t find the link to the site.

There will be people trying an impossible task, what if they can, what if they found a method to crack any address, what if they can steal from these addresses, let's just pray no genius finds a way to do this, or everything will be over, all dreams will be shattered.

tell that to people who won powerball.

If there is a possibility, even if its tiny, it will happen if many enough try. You should possibly read Hitchhikers Guide to the Galaxy

12