BitCrack - A tool for brute-forcing private keys - page 87.

iparktur

jr. member

Activity: 119

Merit: 1

Quote from: almightyruler on June 27, 2019, 01:57:14 AM

Quote from: iparktur on June 27, 2019, 01:03:35 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.

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.

Firebox

jr. member

Activity: 59

Merit: 3

Quote from: iparktur on June 27, 2019, 01:03:35 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 ?

Quote from: almightyruler on June 27, 2019, 01:57:14 AM

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:

Quote from: BitCrack on June 10, 2018, 09:39:00 PM

On my hardware (GeForce GT 640) it gets 9.4 million keys per second compressed, 7.3 million uncompressed.

with the screenshot attached:

Also you may see this table of SI prefixes from wiki.

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: iparktur on June 27, 2019, 01:03:35 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.

iparktur

jr. member

Activity: 119

Merit: 1

Quote from: Firebox on June 26, 2019, 06: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

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 ?

Firebox

jr. member

Activity: 59

Merit: 3

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

Kriptonian1661

jr. member

Activity: 42

Merit: 2

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

iparktur

jr. member

Activity: 119

Merit: 1

Quote from: ?? on ??

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?

Thirdspace

hero member

Activity: 1232

Merit: 738

Mixing reinvented for your privacy | chipmixer.com

Quote from: alott_win on June 07, 2019, 05:06:06 PM

How to prevent brute-forcing private keys?

you can't really prevent brute forcing, but perhaps make it harder... Undecided

I think using a multisig address will add some degree of difficulty to brute forcing attempts

aplistir

full member

Activity: 378

Merit: 197

Quote from: AndreuSmetanin on June 08, 2019, 01: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.

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.

AndreuSmetanin

jr. member

Activity: 138

Merit: 2

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 . Grin

alott_win

newbie

Activity: 1

Merit: 0

How to prevent brute-forcing private keys?

joepappa123456

newbie

Activity: 2

Merit: 0

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

gembitz

hero member

Activity: 1848

Merit: 640

*Brute force will solve any Bitcoin problem*

Quote from: almightyruler on May 27, 2019, 10:41:02 AM

Quote from: Btceon on May 27, 2019, 07:54:13 AM

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

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

epic when do people start selling blocks of hashed addys?

lols

joepappa123456

newbie

Activity: 2

Merit: 0

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"

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: Btceon on May 27, 2019, 07:54:13 AM

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

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

Btceon

newbie

Activity: 11

Merit: 3

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.

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: TimeBits on May 24, 2019, 05: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.

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.

Thirdspace

hero member

Activity: 1232

Merit: 738

Mixing reinvented for your privacy | chipmixer.com

Quote from: TimeBits on May 24, 2019, 05:40:46 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 Tongue

TimeBits

member

Activity: 224

Merit: 62

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.

TimeBits

member

Activity: 224

Merit: 62

Quote from: almightyruler on May 23, 2019, 01:55:26 PM

Quote from: TimeBits on May 23, 2019, 01:25:33 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 Roll Eyes

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://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.

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?

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