BitCrack - A tool for brute-forcing private keys

[iceland2k14]

my idea try to calculate sort can possible
1. random X
2. calculate Y from X
3. hash SHA-256
4. hash RIPEMD-160
5. check the match search

There are already 2 Tools out there which can do exactly the same.

1. https://github.com/albertobsd/keyhunt in the pub2rmd mode. This is for CPU.

Code:

./keyhunt -m pub2rmd

2. https://github.com/kanhavishva/PubHunt This is for GPU

[1714749201]

1714749201

[1714749201]

1714749201

[1714749201]

1714749201

[1714749201]

1714749201

[1714749201]

1714749201

[sssergy2705]

my idea try to calculate sort can possible
1. random X
2. calculate Y from X
3. hash SHA-256
4. hash RIPEMD-160
5. check the match search

There are already 2 Tools out there which can do exactly the same.

1. https://github.com/albertobsd/keyhunt in the pub2rmd mode. This is for CPU.

Code:

./keyhunt -m pub2rmd

2. https://github.com/kanhavishva/PubHunt This is for GPU

The problem is that in this way it is impossible to set the range for generation. It's like pointing your finger at the sky to find the one star you need out of billions.

[fxsniper]

The problem is that in this way it is impossible to set the range for generation. It's like pointing your finger at the sky to find the one star you need out of billions.

thank you sssergy2705

right, it is very hard to find with 256-bit number

[fxsniper]

There are already 2 Tools out there which can do exactly the same.

1. https://github.com/albertobsd/keyhunt in the pub2rmd mode. This is for CPU.

Code:

./keyhunt -m pub2rmd

2. https://github.com/kanhavishva/PubHunt This is for GPU

thank iceland2k14
I will try keyhunt

[stanner.austin]

@fxsniper
Hello
You won't notice much speed difference on this case.
Only thing pubkey bruteforce fastest is BSGS, because it's come after only 1 step(value*G). no need double SHA2,RIPEMD160,BASE8
address or RIPEMD160 won't make much noticeable difference in bruteforce.

[fxsniper]

@fxsniper
Hello
You won't notice much speed difference on this case.
Only thing pubkey bruteforce fastest is BSGS, because it's come after only 1 step(value*G). no need double SHA2,RIPEMD160,BASE8
address or RIPEMD160 won't make much noticeable difference in bruteforce.

OK, I just think simple maybe calculate SHA-256 and RIPEMD160 it is maybe fast that Elliptic curve point calculate
I think with 1 step(value*G). it is calculated 256 times (loop) for each bit  maybe make full key brute-force slow

[bigvito19]

@fxsniper
Hello
You won't notice much speed difference on this case.
Only thing pubkey bruteforce fastest is BSGS, because it's come after only 1 step(value*G). no need double SHA2,RIPEMD160,BASE8
address or RIPEMD160 won't make much noticeable difference in bruteforce.

OK, I just think simple maybe calculate SHA-256 and RIPEMD160 it is maybe fast that Elliptic curve point calculate
I think with 1 step(value*G). it is calculated 256 times (loop) for each bit  maybe make full key brute-force slow

You can use this too for Hash160 https://github.com/phrutis/Rotor-Cuda you can use a GPU with this.

[math09183]

@fxsniper
Hello
You won't notice much speed difference on this case.
Only thing pubkey bruteforce fastest is BSGS, because it's come after only 1 step(value*G). no need double SHA2,RIPEMD160,BASE8
address or RIPEMD160 won't make much noticeable difference in bruteforce.

OK, I just think simple maybe calculate SHA-256 and RIPEMD160 it is maybe fast that Elliptic curve point calculate
I think with 1 step(value*G). it is calculated 256 times (loop) for each bit  maybe make full key brute-force slow

You can use this too for Hash160 https://github.com/phrutis/Rotor-Cuda you can use a GPU with this.

Use whatever you want, just not from that russian thief. All he does is copy/paste from other repos (not fork), he changes name and says like it belongs to him.

[bigvito19]

You can use this too for Hash160 https://github.com/phrutis/Rotor-Cuda you can use a GPU with this.

Use whatever you want, just not from that russian thief. All he does is copy/paste from other repos (not fork), he changes name and says like it belongs to him.

I also cannot recommend his tools, especially when he ran shady brute-force challenge[1]. But i'm not sure he can be called thief when AFAIK he don't violate original repository license. Although i can understand uneasiness that he don't use GitHub fork feature when the original source code also hosted on GitHub.

[1] https://bitcointalk.org/index.php?topic=5394745.0

If his tools work, they work. If the challenge is fake or if you think its fake just don't participate in it.

[math09183]

If his tools work, they work. If the challenge is fake or if you think its fake just don't participate in it.

There is no single tool which he is the author. There is no one single program written by him.
If you want reliability - go and find the original version, from the tool's author, not from that xero guy.
Maybe he has small dick or other complexes and that's why he is not using "fork" option on source repos, he wants projects to look like they were made by him?

copy	original
https://github.com/phrutis/Rotor-Cuda	https://github.com/kanhavishva/KeyHunt-Cuda
https://github.com/phrutis/Fialka	again https://github.com/kanhavishva/KeyHunt-Cuda
https://github.com/phrutis/WifSolverCuda	https://github.com/PawelGorny/WifSolverCuda
https://github.com/phrutis/Minikeys	https://github.com/PawelGorny/MinikeyCuda
https://github.com/phrutis/Collider	https://github.com/Etayson/BSGS-cuda
https://github.com/phrutis/VanitySearch2	https://github.com/phrutis/VanitySearch2
https://github.com/phrutis/BSGS	https://github.com/Mezantrop74/BSGS
https://github.com/phrutis/BIPsImplementation	https://github.com/BilawalAhmed0900/BIPsImplementation
https://github.com/phrutis/PubHunt	https://github.com/kanhavishva/PubHunt

I respect him for amount of time he must spend to monitor source repos and copy/paste diffs 
So guys, you do not need to worry about virus or other bug hidden in his closed wif500 program, he is not able to do something like that.

[WanderingPhilospher]

If his tools work, they work. If the challenge is fake or if you think its fake just don't participate in it.

There is no single tool which he is the author. There is no one single program written by him.
If you want reliability - go and find the original version, from the tool's author, not from that xero guy.
Maybe he has small dick or other complexes and that's why he is not using "fork" option on source repos, he wants projects to look like they were made by him?

copy	original
https://github.com/phrutis/Rotor-Cuda	https://github.com/kanhavishva/KeyHunt-Cuda
https://github.com/phrutis/Fialka	again https://github.com/kanhavishva/KeyHunt-Cuda
https://github.com/phrutis/WifSolverCuda	https://github.com/PawelGorny/WifSolverCuda
https://github.com/phrutis/Minikeys	https://github.com/PawelGorny/MinikeyCuda
https://github.com/phrutis/Collider	https://github.com/Etayson/BSGS-cuda
https://github.com/phrutis/VanitySearch2	https://github.com/phrutis/VanitySearch2
https://github.com/phrutis/BSGS	https://github.com/Mezantrop74/BSGS
https://github.com/phrutis/BIPsImplementation	https://github.com/BilawalAhmed0900/BIPsImplementation
https://github.com/phrutis/PubHunt	https://github.com/kanhavishva/PubHunt

I respect him for amount of time he must spend to monitor source repos and copy/paste diffs 
So guys, you do not need to worry about virus or other bug hidden in his closed wif500 program, he is not able to do something like that.

I've looked at two of his repos; they are different than the originals and he gave credit to original programmer.
If you take an existing program and change it to different things, is that a fork or a new master? I do not know...I imagine you could fork and make changes.
It will be interesting to see/read about the wif500 and if they solve it.

[CryptoSh1va]

It will be interesting to see/read about the wif500 and if they solve it.

I think it's just a clever scam.
The author claims that the photo is from a burnt diary in 2017, but the Ethereum address in the same photo was used in 2021, and just one day.
Why write this address and key in a diary if there was no balance on it at the time?
And even more so to use it after so many years..

0x428d88b326748ebd55c4a7f89fd3bc08378dc0d2

[WanderingPhilospher]

It will be interesting to see/read about the wif500 and if they solve it.

I think it's just a clever scam.
The author claims that the photo is from a burnt diary in 2017, but the Ethereum address in the same photo was used in 2021, and just one day.
Why write this address and key in a diary if there was no balance on it at the time?
And even more so to use it after so many years..

0x428d88b326748ebd55c4a7f89fd3bc08378dc0d2

Well, outside looking in, whoever's address, they could still use it because they had the full private key and normally you create a wallet before there is a balance on it, whereas the btc address in question is missing the first part of the wif private key. I dunno...it will be interesting to see if the coins move anytime soon. As well as #64 and #120

[NotATether]

There is no single tool which he is the author. There is no one single program written by him.
If you want reliability - go and find the original version, from the tool's author, not from that xero guy.
Maybe he has small dick or other complexes and that's why he is not using "fork" option on source repos, he wants projects to look like they were made by him?

I respect him for amount of time he must spend to monitor source repos and copy/paste diffs 
So guys, you do not need to worry about virus or other bug hidden in his closed wif500 program, he is not able to do something like that.

I didn't check the repos (Github is a PITA to browse through lynx) but I can conclude two things from this:

a  - if the programs are open-source, then he just coppied the Git tree - anyone can do that. The commits still appear (unless you destroy the tree and create a new one - in which case nobody would really think you wrote the whole thing in 1 commit anyway) if you do a git log, so it's just a nuisance.
b  - the programs are all closed source like that sp-mod guy. In which case the most risk that would come from using it would be the code sending the rewards to some baked address inside the code (or if he is sufficiently insane, maybe he includes a piece of malware like the node-ipc maintainer).

[fxsniper]

Why do all programs/tools about bitcoin all-time download chrome browser warning to download and recommend deleting a file?
What algorithms or some code makes the browser check it and think can be harm the computer.
it happens with tools download from Github and open source code, bitcrack, kangaroo all get warning all-time download it.

[albert0bsd]

Never run exe files of untrusted sources, if there are source available is better to compile it by yourself

[COBRAS]

Why do all programs/tools about bitcoin all-time download chrome browser warning to download and recommend deleting a file?
What algorithms or some code makes the browser check it and think can be harm the computer.
it happens with tools download from Github and open source code, bitcrack, kangaroo all get warning all-time download it.

Because they have your BTC stealer inside...

[zahid888]

someone have any information about this transaction https://www.blockchain.com/btc/tx/d9a86250b7f93a112cb93903f44c6943464c546a703b58b6b852d59e3102b64d what he was trying to do ??

[NotATether]

Why do all programs/tools about bitcoin all-time download chrome browser warning to download and recommend deleting a file?
What algorithms or some code makes the browser check it and think can be harm the computer.
it happens with tools download from Github and open source code, bitcrack, kangaroo all get warning all-time download it.

Whenever you download a file, Google check its hash against a bunch of signatures that are known to belong to malware - the database is stored on Google's servers - and then presents a warning if it matches a hash of malware (whether it's EXE, ZIP or whatever).

Firefox would actually block you from downloading the file in such a case, and delete it instead.

[bigvito19]

I try
kanhavishva/KeyHunt-Cuda
and
phrutis/Rotor-Cuda

AND DONT FIND THE KEYS !

FAKE ? SCAM ?

https://github.com/phrutis/Rotor-Cuda/issues/38
https://github.com/kanhavishva/KeyHunt-Cuda/issues/59

They both work, it just depends on what key you are looking for.