pool crypto powers

[borgfish]

Hello,

out of curiosity i wonder if someone with knowledge about bitcoins hashing needs, crypto breaking needs of a gpu (cycles per operation and so on) and crypto used for the wallets insights could estimate
how long
-a pool with 2000gh/s
-with a alternative client capable of doing
-wallet private key brute force
would need

my totally uneducated guess is 2 weeks ?

[1715403270]

1715403270

[1715403270]

1715403270

[1715403270]

1715403270

[benjamindees]

Look into brute-forcing 256-bit ECDSA.  It's a bit more difficult than that.

e: My uneducated guess is 5,395,141,535,403,007,094 years.

[Sukrim]

-with a alternative client

Biggest problem right there:
Such a client would be of NO use to generate BTC, meaning it needs to be willingly installed. It's not that easy to convince people to do this!

Also it is quite hard to bruteforce a wallet, so this again could lead to "some" problems (like "the sun expanding to the surface to the earth sooner"-type problems!).

Aaaand there is the small (but not impossible) chance, that the wallet you crack as a combined effort is your own!

[Soros Shorts]

Somebody once made a calculation based on the fact that you'd need at least 1 erg of energy to represent a 1 bit transition. Based on this they estimated that it would be impossible to cycle a 256 bit counter through all its possible combinations using the available enery in the solar system. I.e., even at 0 degrees Kelvin there isn't enough energy in the solar system to cycyle through a 256-bit counter, let alone compute 2^256 hashes.

I wish I still had a link to the reference.

[borgfish]

thanks for the answers.
i thought since 2gh/s would represent like 6000 gfx cards with ~1400 cpu units it would go faster, what was i wrong ..

i should have looked at wikipedia first there is an article Brute_force which also mentions the energy thing.