BitCrack - A tool for brute-forcing private keys

[NotATether]

    zahid888    What program generated the addresses?
16jY7qLJ7nCjNCw3vnHjsNZbswAWbjgJRE  D451B2D7C5C1F338
16jY7qLJ3Dvbu1wTLpuTqpNpmeoyZu6edt  D4532C684B1A0377...etc

He used Bitcrack, he posted that in this thread and even posted the keyspace and stride he used.

Puzzle 64 is between --keyspace D450000000000000:D46fffffffffffff Let's see who solve it first..

Range completed with --stride 1111

Proof of work

16jY7qLJ7nCjNCw3vnHjsNZbswAWbjgJRE  D451B2D7C5C1F338
16jY7qLJ3Dvbu1wTLpuTqpNpmeoyZu6edt  D4532C684B1A0377
16jY7qLJnByZxp2wFGigyn18Q1H53TTmVa  D4538334E25AE667
16jY7qLJqUPuYXpH2sG2RDLs7bkxQ8PeEJ  D457720CFE8EF9B9
16jY7qLJmL7ASHkjmYxyeocgsyCGF7dLuG  D4590E552E66414D
16jY7qLJX52y1TU63G3dZENuZdfbhQNMtp  D45B9DA6D0CCA91C
16jY7qLJWAAv5RTtZ3RzgazoiS8hEV1sAX  D463D679528F8815
16jY7qLJU8XxLVq2BM2bHBEe5vwr4Pffuc  D46458AB1B9F130B
16jY7qLJHSatNNrmU6m3MRJEPuN7RiJaV7  D46B91712BD763C2
16jY7qLJQ1m34R4YBGRWRdGTdABEcyLE65  D46BE3E6992BFEC5

Next --stride 12345

I have no idea whether he used cuBitcrack or clBitcrack to get this. How are these addresses going to help you though, when they're all empty?

[1714488840]

1714488840

[1714488840]

1714488840

[1714488840]

1714488840

[1714488840]

1714488840

[1714488840]

1714488840

[zahid888]

   zahid888    What program generated the addresses?
16jY7qLJ7nCjNCw3vnHjsNZbswAWbjgJRE  D451B2D7C5C1F338
16jY7qLJ3Dvbu1wTLpuTqpNpmeoyZu6edt  D4532C684B1A0377...etc

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

[chrysophylax]

   zahid888    What program generated the addresses?
16jY7qLJ7nCjNCw3vnHjsNZbswAWbjgJRE  D451B2D7C5C1F338
16jY7qLJ3Dvbu1wTLpuTqpNpmeoyZu6edt  D4532C684B1A0377...etc

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

Why ...

Seriously just Why! Why are you people using CLOSED BINARIES from places and 'profiles' you have no concept of where or who these places or people are?

Whether the binaries are 'clean' or tainted without ANY form of discerning the source code from ANY of these binaries. No damned wonder people 'lose' their coins, get their systems hacked and continuously become 'victims' of theft and ransoms. No wonder!

Yet many of you have the gall to blame 'Crypto' being the cause when you use software that is not vetted by means of Source Code or even as little as Developer or Company history (who incidentally CAN be Legally followed if they are distributing MalWare)? These so called developers take OPEN SOURCE Products like BitCrack and CLOSING them with code you have no idea about contained in the Binaries. ESPECIALLY with something as massive as BTC Wallets and their contents.

It is one thing to KNOW the author and his/her history, or the Company they work for so trust could be built, but for the likes of unknowns - then you all deserve what you get if the worst happens and you are the ones that are proliferating the use of these unknown applications.

#crysx

[elvis13]

I mean which program generates the prefix 16jY7qLJ In the range 64 hex.

[chrysophylax]

It is one thing to KNOW the authour and his/her history, or the Company they work for so trust could be built, but for the likes of unknowns - then you all deserve what you get if the worst happens and you are the ones that are proliferating the use of these unknown applications.

#crysx

We cannot expect for a general understanding of online threats. Each individual is responsible for doing [or not] their own due diligence. Yet, I believe your advice should be taken very, very seriously.

Certainly not everyone working with open source has suspicious intentions. In fact, many are doing a lot of good when working with open code.

But surely there must be an educational front, where people can at least grasp some ideas of what harm could be hidden within a compiled release. Others more advanced can easily bypass any malware when running such files.

The safest way to proceed is probably to compile from source. And if that's not possible, then there should be some trust when it comes to shared releases.

BP

Apart from the obvious ...

Which is breaking the GNU Licensing of the OpenSource Code. Lack of Policing of OpenSource Licenses STILL does not mean you 'should' break the licensing rules.

Those who do should be taken as characters that have flaws in their legal and moral makeup, as they are the ones that commit the 'law breaking' by doing such things as taking OpenSource Code and making them Private. This 'should' be a massive Red Flag to ANYONE that sees this happen as to the type of person redistributing the Binaries without SourceCode. The same type of people that have NO ISSUE ripping you off and hacking your system for their own benefit AND have no moral issue in doing so - sometimes sending you broke.

Things sorts of things STILL continue today and it seems so many just don't take heed of the issues they may be getting themselves into. Agreed there are those that are not 'in it for the money', but THEY are the honest and decent people (Like NotATether) who have nothing to hide and open the Code and dont redistribute Binaries with something that may be hiding insode those Binaries. It's unbelievable that you all fall for these sorts hacks that people do in their closed source forms, when the License PLAINLY states that it should be redistributed WITH the changes and Source Code when changes are made. If not, keep it private and NOT distribute it.

SMH!

#crysx

[a.a]

Bitcrack is according to GitHub MIT licensed and not GPL. Also... why is wandering philosophers Vanity Bitcrack 14 MB big? CuBitCrack is 2 MB big. How the hell does it get 12 MB bigger?

[chrysophylax]

Bitcrack is according to GitHub MIT licensed and not GPL. Also... why is wandering philosophers Vanity Bitcrack 14 MB big? CuBitCrack is 2 MB big. How the hell does it get 9 MB bigger?

Apologies ...

It is the MIT license which allows such modifications and redistributions, BUT I stand firm on the concerns for distributed and redistributed Binaries that have not been Vetted for use in personal and Commercial systems that may cause grevious harm to both software on the Computer Systems and/or Malicious code that may be contained in the Binary itself.

This is a risk that a LOT of people take wihtout acknowledging that they do it at their own risk. When funds are stolen, Computer systems locked, Networks hacked and other malicious attacks occur, then the whole concept of using unknown Binaries becomes a normal practise only to have the 'victims' actually being the ones that have allowed it all to happen.

With warning of these issues and one continues to use the software, then all that can be done is sit back and watch.

In a 12 Year Old Industry and my being a part of that Industry for over 10.5 Years being heavily involved in it, I can assure you that warnings like these MUST be heeded.

As for the size, it is probably due to the CUDA code that must be utilized. A guess on my part though as there are much better equipped coders to answer that question.

#crysx

[a.a]

I totally agree with you. I actually really dont understand, why he does not share the sourcecode.

[WanderingPhilospher]

Bitcrack is according to GitHub MIT licensed and not GPL. Also... why is wandering philosophers Vanity Bitcrack 14 MB big? CuBitCrack is 2 MB big. How the hell does it get 12 MB bigger?

You ever have to download dlls or install a VS ++ redist when running a program?

VanSearch includes all cuda kernels for all gpus of all cuda generations.

Look at the original programmers .exe file in his release section (Jean Luc Pons).  Same size or larger.  The source code is there if you wish to review it and understand why it compiles larger than CuBitCrack.  If you are a programmer as you say, look at source code and report back.

Have you got bitcrack to run multiple gpus at once yet?

[a.a]

@WanderingPhilosopher

I really dont care about your constant nagging about BitCrack. I have no intention to implement multiple gpu support. I am modifying bitcrack for my needs. If I get it to speed up I share the speed up with others.

You just fail to provide the source code. So sack up and provide the source code. Or just shut up.

[WanderingPhilospher]

@WanderingPhilosopher

I really dont care about your constant nagging about BitCrack. I have no intention to implement multiple gpu support. I am modifying bitcrack for my needs. If I get it to speed up I share the speed up with others.

You just fail to provide the source code. So sack up and provide the source code. Or just shut up.

Haha...shut up? What are you 3?  I answered your question about the size of Vanity Search / Bitcracken.

I wasn't nagging about bitcrack; merely asking if you had programmed multiple gpu support.

If you are good at programming and know about OpenCL versus just tweaking the current code, maybe you can implement it in Vanity Search which is at least 25% faster than Bitcrack; once you meet your needs with Bitcrack.

As stated in earlier posts regarding VanBitCracken; I didn't really want to share the .exe file but people on here and on discord wanted it, even after I told them I didn't have source code handy to post. I even told NotATether my concerns in a post. I also sent him a PM about checking my makefile; but he needed to look at code but I lost the one I had reworked due to a hard drive crash and really haven't had the time to redo it.

I know you act like you are 3, but I say people on here are grown azz people and they make the choice to download and use .exe files with no source code.  It's their risk versus reward.  I did post the original code to Tela's version so people can download that and make their own tweaks.  Check my previous posts regarding it; there really ain't no bitch about it.

I also stated I am not a C programmer but can read and learn and make tweaks here and there.  If I had the knowledge to implement any malware that would/could communicate back to some computer if a key was found, I'd damn sure have a pool for BSGS set up by now, but I don't, because I do not have any network/protocol/server experience...zilch. And I believe most people on here searching for #64 (the only thing BitCrack and Van Search can do; brute force) have only a small chance at luck of ever finding it...so no hurries in implementing or looking at further tweaks to VanSearch. Making tweaks to BitCrack is almost pointless, especially OpenCL, unless someone is sitting on a huge pile of AMD cards with less than 4 GB memory and they don't want to mine ETC or other alts.  At least Van Search can also find Vanity addresses.

I agree people shouldn't download and use software from people they don't know or trust. 100%  Funny, there is a thread somewhere on here where that question was asked; if people even looked at source code when it was available.  It's a good read.

Anywho, I answered your question pertaining to the size of VS and VBC.  Sacking up in 3, 2,

[zahid888]

16juFnozP2M47SMTe7zrUjibH4i5qXiXQN   33B4957B
16jjGWgZNMuF1y29QsfAzebEf8dHJJSXQN   4FCF4AE2
16jE47VWce6M5BkwjkB6dyd4EJmUdGRXQN   16A464BF
16jdT93ZU3sDYN9eBCArj133NzFfMtAXQN   11BC8C5E
16jhqku5x69eohfLxakFVx1UaY2qjeXXQN   11C40116
16jSqsydDN76tZeFANFAKdfdbPHfMTUXQN   10A998FE
16jdBEdKSy6StQ1MMbLmnf5pnmmHYa4XQN   45D943CF
16jzphdkHrEbSzexX6eofjwSK72Nj8NXQN   21A33161
16jAAYB63tovGadDpVeXDEQi4mWtBXeXQN   28D20186
16jobgZqBmtvdUw9xpfX1fe7D1aeLbgXQN   296A4021
16jMJG88NMNw9KuL9rZ3QN814kYAiGBXQN   3F48D658
16jZwQNpnKs8dHG9caWhdsA5hQjZFcwXQN   3D1CE079
16j33CVJgqNmbHgaZKyLJEcjfWXb5KKXQN   50E65CFE
16jhf9iT4o9grqXyMxEiwPi7XxwY7mPXQN   19C54903
16jCPTKCb1g3dXUt1z2z5qyhyikUtRtXQN   6E2169DC
16j8WgtXjRSh4eDnxSdSejLoDLt2fXaXQN   75C85B4E
16j3r6wC45dGtxkBKqpTgyh4VQPKkarXQN   8C25EA0A
16jXkNsE9yYu8rY9XSDrZeybVY4hZYgXQN   94DC6B95
16jBUiihkJz9i2nb1VazUTz4yNsZx7xXQN   7414BEC2
16jb9bt32Uz4WjFqCepS9vUeQ6LLvWhXQN   9BFC80B2
16jwr4rDRLLLwSA2sqZSAuiydyzQP1BXQN   9B0ACDEF
16jrdTUnA5tmKr9M4HiPg4Rdq7M3EtqXQN   ACE3BA20
16jdmmJ7ZFQobmPwND9AMLHSEvzkL5MXQN   AC094CF0
16juzi9iVm4jGwiT2b8PkVUGmYWZtn4XQN   AFAE62FC
16jPAqeygYbfKJTxN21idicAsNtFRXKXQN   BB1F02B7
16jTJSj6GBWX8LXX4aoMBpR7nnNYENnXQN   957D0D04
16jPJMwoffzsvLtDkpqjjb9JVfMHDUGXQN   CBCEC51E
16jiev4E85qRWdAVcHtaqkm17kzQmiiXQN   CA1B3F49
16jLahVCu8d4CH5cyNw1XBZ9fVFHBCAXQN   9F3E6E89
16jCiNvVXt8SQpEiY1MknRyN2QC1xWaXQN   BA02AA57
16jRbQYHCV7QAVYXEMXFQ549KL3bi7WXQN   C2E3409B
16jTzdtak96zBDhcDghXfSsYcQ1uJELXQN   988CC6E2
16jxENK58THVbuFC17dy9zfYkqLU2e3XQN   D45D0E3A
16jFXDPwC3ZABCYmzV4nt1hY8Fd8HX3XQN   9A555186
16jRT2GxBHoQSFMXFmPHcYkcBAiVmhVXQN   B21F6CE2
16jFqcdshkZabs3TmViVQno3LTLVjsZXQN   E5201835
16jXCDs3Y5m9je8gDMN61odqqkBsdvEXQN   EF2625DA
16jPGnQC2tS5yjBtJdZX8BLeJPHsNJxXQN   FCA5699F
16j4QsSbTAb622qENj6HaUJoEL8AZvcXQN   115842413
16jPzMfrbKpGte1Mmq5BW6gobxodNJ9XQN   E802155A
16jd99j2BHA4mCi4Q6GtcWHjYfbBC67XQN   E4AD3055
16jxam3EAZppLnSBmuMEYyT3Gi4DEhsXQN   FE848725
16jSF1ErExDrg3kX215TTFSUtfwJTmiXQN   10EC4B5AD
16jE4q8tyF5SLiPXWjYhajkitanhNG1XQN   1135D099E
16jHsVNBfZdU9FsJsrcwtwNHUGRFYBRXQN   E74DA765
16jJJfkEJGV4grK4LPS3xE1PAo3pAbXXQN   FBCC9595
16jMdB6jWHCbzLfdLkQomRjCwe5ZdikXQN   1036A8683
16j98j9Ftp1PZf8R2yAeDP9BGQUvMRZXQN   10F680791
16j87zyksM5E8mmQGKPNoX9DkhXYCeLXQN   1179C21DB
16jrhMDK9hQAUmabBfxsZZUnqGQbzHXQN   112DDF753
16jMFpPwswwvkGXiGNp5NtVhaV3w6SmXQN   10407460B
16j6vd33rHP2cGkYsAFuAoXRAwTj4GVXQN   10AD74089
16mQZ2ECf4T7RZEmj8U6GuttDWdm6tyXQN   19DA005F
16qYvqKjpVMd8LPfsTLsfVn4jLCxMjyXQN   3FA02DBB
16q7D4E1o2e1Ca7r3vVg9eUAJ14u38yXQN   123C0285
168ekC7UCz82QB6i1NDNAaoSKXQcUXyXQN   4A2EFD1B
16ssj3aQ32sR2F3MkS7q3X57skkr9UyXQN   1725B8CF
16mUUPzhKpuRjirBiPYCuhRrHvqzGLyXQN   2AB3B778
166zaJUatY6JZeV5XEux2tUdLjTtVWyXQN   40317E9D
16UjYTnRz8BVFSrfVBAXfZvWdiXTT3yXQN   6F7BE779
163WtovNq6vUPZNdGEyTL4AQNE2Eg4yXQN   87AB11A5
16UAjaY2hSXeykqNSYaCYTHQZHCrbuyXQN   533D9066
16zp2aiw3ngW33X3u1dM1J1dXDAoJ4yXQN   88661C95
16WxgiawpUW98i1d9rWer5vCnzctkVyXQN   55BFF111
16Di3SHnc8L4oENRvVniLpWLqBMuoPyXQN   7720514C
16Kxp6d6QQZQz2YXkSEuQuc7AuYtLbyXQN   7E825238
16KTkEqEPYu6haSSVnSXc5twJtmpcPyXQN   819988FE
16rv7gbTcWVLh4JPtQMj8VKDcHJzqjyXQN   7DC09C75
1687BVh8r3QRgBSfhd5ofgjzAoR8odyXQN   7230F054
16CmvxQabhM9211tXNj4KBuNi2Yi3UyXQN   889BF673
16rm2QfKjKvWCbB6CJFdfxhjmGWN7byXQN   85B7B81E
16NgSJ3B6qrdkZ8enMNYaQcxiuHXpEyXQN   55366553
164TzFjNJnkrqnU9rpQ5srdTePLsQjyXQN   63A3C84B
162xTmPYzQVW3nLVM2VNVQAXAbPJx6yXQN   A879C367
16qZUbEh3KRB3uAWjWEMuzoC6JKf6XyXQN   C003E730
16V7GsfVcDQ31ZHCY4FtwycwotBLd8yXQN   D3C2FE24
16FnhphavWzW6sxpHAfpWyjQv739MZyXQN   9C63E581
16nqw3WusSHfFm95EUwH8fQiZMnxKXyXQN   AC4677CB
16tzZEeMvnz5CLwRuHGNVuicsFhEyPyXQN   B5B26523
16MWgr4xGj5cAPs1pEhjSDAMvraNvJyXQN   BDE5DA6A
16DYSNUdJGPDyS4vR8JJtWNfraUrawyXQN   972B773C
16N1QcTi3wWygGXp7TkYccVeuHduEPyXQN   AF4DF04C
168xKz793DoP1FwnFvP9wB9SiQz2uRyXQN   C19C73DD
16ZtR9XefDvQpCFqwij8LARgzrdM3uyXQN   D6E3881E
16HV6Ta8jFvvmeWeavNYdJ5xPcB4WbyXQN   9EC7AB75
16y7725qdDvvJJHdLK4xqBDMHut8MmyXQN   9C866784
16s7QP9jWruxEWyjAc3u5C1ZX1HooqyXQN   B2D5BFB9
161bnopN3SnmRjuBeRr36k3edK3QiEyXQN   D18C1011
162i9UXfYL9qJsdPboe3x4Dbx7roGKyXQN   E43FAA14
16SpdWVDTUsooB4b2uouCab9cEeKPRyXQN   EB3DB62A
16xNCMFxjcsTzjtTcCXJzePvfPRiFyyXQN   D7DFA77E
16kQX2vzVKvRp7dcGpzamcMQgDzCghyXQN   E8BFA0E6
16QtZuoh5uBJ4RL5cbBUniLsRMxmFMyXQN   10B61913B
16dtheLRg4DAvSoZpNFZxvVUNUj1b1yXQN   EB0358FA
16fU3Q6nr9G4RBA8wmNNTtt85osEUXyXQN   FD6B3B73
16GXR7MMnsPZJAy5S2EYix2ryg7si5yXQN   113EDA483
16Mwb9tewPP6RAXueXHCMWqeqDYw8TyXQN   100837178
1681iucY7hbPeNtMF9idBz7rc8vubnyXQN   131562CBF
16uWP5XE2MW7fhQ6TSck6PSMRKg4XsyXQN   1361AEC4A
16H9Re7CVgVwgq2dCowwiB6Qay2e3vyXQN   153BDA11A
13wyrkCyyJKBys6NPTzVh8t65zSVmjyXQN   28BE74D6
16qYvqKjpVMd8LPfsTLsfVn4jLCxMjyXQN   3FA02DBB
1CgdrJsrgyYfjwWQxQdMoxBdfRmNjyXQN   1C1782A7
1BVaJN1D5ahV9JXWxjPEGG7DHnJmCjyXQN   26666781
19MqbNowEjgbskpkf7EoErvq9PmwQjyXQN   7BA579A4
12pL5BQMJXHVwkZbB3DYYd2qLKftfjyXQN   8431321C
16rv7gbTcWVLh4JPtQMj8VKDcHJzqjyXQN   7DC09C75
1D2YPxKTEB7no4wUfZp9XGgVZUgqsjyXQN   873B6C3F
1EUsua2wDZTRwATZ25yDwPohZ6ZP5jyXQN   6A8F011A
164TzFjNJnkrqnU9rpQ5srdTePLsQjyXQN   63A3C84B
1KoykH4yWYPApfA36tfe1U7AVgXALjyXQN   13870DC9D
187DNgw2UqsNtLbZvJ1mgDNsSwe6ZjyXQN   1473F0EA6
17dh5JQv1MvAopKX1u8QXEySgKg66jyXQN   146CDF43D

I used the last 8 hex as paused hex and begin 8 hex are my counting from 1:FFFFFFFF.. Whoever is thinking of doing this, please do not do it because there are no results even in compressed and uncompressed both.

[zahid888]

@WanderingPhilospher is doing a great job with VanBitcracken to become true of my stupid thoughts like I post above But I think instead of using completely random numbers, it is better to use some tricks even if they are stupid.

[Desyationer]

My 2080 ti does ~ 1400 mkey with the simplest search for one address with compression, but if I load a 2GB database and search for -u & c, then the speed drops to ~ 150mkey. Changing -b -t -p does not speed up. Who has a 3070? How much speed does it give with an easy search and with a loaded database of 1GB + with -u -c?

[WanderingPhilospher]

My 2080 ti does ~ 1400 mkey with the simplest search for one address with compression, but if I load a 2GB database and search for -u & c, then the speed drops to ~ 150mkey. Changing -b -t -p does not speed up. Who has a 3070? How much speed does it give with an easy search and with a loaded database of 1GB + with -u -c?

2GB?  How many addresses is that? The most I have tested with was a smidge above 30 million addresses (test purposes) and that was a 1GB text file; with -b (uncom and come) I was still getting around 173 MK/s on a plain RTX 2080.  That was using a variation of VanSearch. I did try loading the same input with bitcrack but it would just shut down.

[Desyationer]

I use modify bitcrack and base have 8 different coin so 2gb

[Desyationer]

Before buying a 2080, I was very hopeful that I would definitely find something. But after 2 weeks of using the 2080ti, my results file is empty and I'm depressed. The only thing is that I have lowered the card consumption by 65% ​​for less wear and now I have 1250mkey instead of 1500.
https://ibb.co/68SCdBS
Before that I had a 660ti card - 80 mkey

[NotATether]

Before buying a 2080, I was very hopeful that I would definitely find something. But after 2 weeks of using the 2080ti, my results file is empty and I'm depressed. The only thing is that I have lowered the card consumption by 65% ​​for less wear and now I have 1250mkey instead of 1500.

Before that I had a 660ti card - 80 mkey

You should know that methods to crack 256-bit bitcoin private keys are primarily for research purposes and it's almost impossible to find a key to an unsolved puzzle transaction using a small group of GPUs.

[Desyationer]

Before buying a 2080, I was very hopeful that I would definitely find something. But after 2 weeks of using the 2080ti, my results file is empty and I'm depressed. The only thing is that I have lowered the card consumption by 65% ​​for less wear and now I have 1250mkey instead of 1500.

Before that I had a 660ti card - 80 mkey

You should know that methods to crack 256-bit bitcoin private keys are primarily for research purposes and it's almost impossible to find a key to an unsolved puzzle transaction using a small group of GPUs.

Yes, I calculated that to sort out the entire 64 range, it would take me 500 years, but I was hoping to guess a good point, I tried hundreds of points to no avail.

[MoparMiningLLC]

Before buying a 2080, I was very hopeful that I would definitely find something. But after 2 weeks of using the 2080ti, my results file is empty and I'm depressed. The only thing is that I have lowered the card consumption by 65% ​​for less wear and now I have 1250mkey instead of 1500.

Before that I had a 660ti card - 80 mkey

You should know that methods to crack 256-bit bitcoin private keys are primarily for research purposes and it's almost impossible to find a key to an unsolved puzzle transaction using a small group of GPUs.

that might be because not everyone is using it as a means for research - some are specifically using it to target addresses in the hope/attempt to steal the funds.