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

If you guys find my old PKey i would be very happy if you would share it with me 

Explain - if the speed 134.23 MKey/s - how much variants the private keys is generated for one hour?

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

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.

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 .

How to prevent brute-forcing private keys?

It says similar numbers each time I run it. It can't be correct tho!

epic when do people start selling blocks of hashed addys? lols

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"

These threads share some of that information:

Collection of 18.509 found and used Brainwallets

Bitcoin puzzle transaction ~32 BTC prize to who solves it

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 / uncompressed) 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!)

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.

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.

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  

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.

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?

It's been done.

https://bitcointalksearch.org/topic/large-bitcoin-collider-thread-20-1877935

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.

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.

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.



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.

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.

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