Developer: Write code to generate all possible private keys

[cookiebro]

I'm looking for a developer to write a script to generate all possible private keys and write them to an SQL database. Payment available

[enzogla]

There are already websites that do that.

https://keys.lol

Good luck though, the chances of finding an active one are ridiculously low.

[cookiebro]

I know. It's not for anything nefarious. I need the data locally.

[PawGo]

What do you mean by "all possible private keys"?
All possible addresses from a given private key (so for one key to generate addresses bc1... 3... 1..., compressed/uncompressed) or you want to iterate each possible private key, one by one and generate address for that - then technically it is easy and doable, the problem I see is that you will need eons to have work finished, you will need a lot of energy and enormous amount of disk space.
But if you want, I may do it for you...

[pooya87]

I'm looking for a developer to write a script to generate all possible private keys and write them to an SQL database. Payment available

Code:

using AlienTechnologies.TimeTravel;
using Encoders;

public void Main()
{
  var storage = TimeTravelToFuture();
  var sql = new SqlDatabase(storage);
  for (BigInteger i = 1; i < 115792089237316195423570985008687907852837564279074904382605163141518161494337; i++)
  {
    sql.Write(Base58Encoder.GetWif(i));
  }
}

private Storage TimeTravelToFuture()
{
  TimeMachine.Engine.TurnOn();
  TimeMachine.Time.Set("2120-01-01-12-45-00");
  TimeMachine.Travel();
  return TimeMachine.RetreiveStorageDisk();
}

You're welcome.

[BlackHatCoiner]

I'm looking for a developer to write a script to generate all possible private keys and write them to an SQL database. Payment available

In Bitcoin? What to do the bitcoins if you know my private key? 

[...]

This will be insanely slow. Consider using Foxpup.TimeTravel; instead.

[o_e_l_e_o]

2²⁵⁶ private keys * 32 bytes each = 3.7*10⁵⁴ yottabytes.

The combined storage capacity of every device on the planet is not yet at 1 yottabyte. Good luck!

I'm also wondering where you are keeping the several million Dyson spheres you'll need to generate enough electricity to perform this?

Yes yes, I know it's not really 2²⁵⁶. I'm just making a point.

-snip-

I initially glossed over this because I assumed you had written the actual code knowing full well it would just fill his available storage space. Glad I went back and read it properly though.

Edit: @o_e_l_e_o beat me almost by a minute.

As BHC has said above, Foxpup.TimeTravel is the superior function.

[mamuu]

I'm looking for a developer to write a script to generate all possible private keys and write them to an SQL database. Payment available

Code:

using AlienTechnologies.TimeTravel;
using Encoders;

public void Main()
{
  var storage = TimeTravelToFuture();
  var sql = new SqlDatabase(storage);
  for (BigInteger i = 1; i < 115792089237316195423570985008687907852837564279074904382605163141518161494337; i++)
  {
    sql.Write(Base58Encoder.GetWif(i));
  }
}

private Storage TimeTravelToFuture()
{
  TimeMachine.Engine.TurnOn();
  TimeMachine.Time.Set("2120-01-01-12-45-00");
  TimeMachine.Travel();
  return TimeMachine.RetreiveStorageDisk();
}

You're welcome.

I'll be damned! to this answer 

[mynonce]

I'm looking for a developer to write a script to generate all possible private keys and write them to an SQL database. Payment available

You're too late. Someone else did it already.

https://allprivatekeys.com

'All private keys list
Whole range of Bitcoin and Bitcoin Cash Private Keys, compressed/ uncompressed, SegWit and HD wallet. Whole wallets including YOURS.
Don't believe?

Just open to see.'

[larry_vw_1955]

You're welcome.

you shouldn't be doing that pooya. that's a job for someone they could put food on the table but not now!

[NotATether]

It should be assumed that the first 2^40 private keys have already been broken and are inside some local database (330*64GB or about 21TB large uncompressed) so they must not be used for whatever reason.
Same for last 2^40 private keys, first 2^40 even PKs, first couple prime number PKs and so on.

[larry_vw_1955]

It should be assumed that the first 2^40 private keys have already been broken and are inside some local database (330*64GB or about 21TB large uncompressed) so they must not be used for whatever reason.
Same for last 2^40 private keys, first 2^40 even PKs, first couple prime number PKs and so on.

but how would someone know if their private key was in that range? especially with hd wallets and such they aren't checking things like that. hopefully their funds dont get stolen. oh also the middle 2^40 private keys whatever those are would probably be sitting inside some kid in their basement on their hard drive.

[PrimeNumber7]

It should be assumed that the first 2^40 private keys have already been broken and are inside some local database (330*64GB or about 21TB large uncompressed) so they must not be used for whatever reason.
Same for last 2^40 private keys, first 2^40 even PKs, first couple prime number PKs and so on.

but how would someone know if their private key was in that range? especially with hd wallets and such they aren't checking things like that. hopefully their funds dont get stolen. oh also the middle 2^40 private keys whatever those are would probably be sitting inside some kid in their basement on their hard drive.

The chances of a private key being in any 2^40 range is approximately 1 in 10^67, or approximately zero.

Wallets could potentially black list those private keys, but if that was a mainstream thing, crackers could simply monitor the next 2^40 set of keys (and this process would continue).

I seriously doubt that the key 2^35 is being actively monitored, and I doubt that someone that naturally generates this key is going to have their coin stolen.

Sure, if you say to send coin to an address associated with a key in that range in the next month, there would be a guarantee that monitoring those addresses would present an opportunity to see coin stolen. But monitoring all those addresses for years, or even decades would be much more expensive, with no assurance that the attacker would be able to receive any coin as a result of monitoring all those addresses.

[NotATether]

It should be assumed that the first 2^40 private keys have already been broken and are inside some local database (330*64GB or about 21TB large uncompressed) so they must not be used for whatever reason.
Same for last 2^40 private keys, first 2^40 even PKs, first couple prime number PKs and so on.

but how would someone know if their private key was in that range? especially with hd wallets and such they aren't checking things like that. hopefully their funds dont get stolen. oh also the middle 2^40 private keys whatever those are would probably be sitting inside some kid in their basement on their hard drive.

I meant if the private key was generated directly, or you're using a wallet that allows you to see the private key of your address.

[dextronomous]

was thinking 
how much is it gonna be in data TB , if range 64 would be safed uncompressed,
raw txt file, and only this range is it doable?

[pooya87]

was thinking 
how much is it gonna be in data TB , if range 64 would be safed uncompressed,
raw txt file, and only this range is it doable?

It would be silly to store things in string form, for example in this case it would be 51-52 bytes versus 32. So to compute the total size needed you just multiply the number of items by the raw-byte size which is 32.

Code:

32 * 2^64 = 2^69 = 5.9E+20 bytes = 590,000,000 terabytes

[larry_vw_1955]

Code:

32 * 2^64 = 2^69 = 5.9E+20 bytes = 590,000,000 terabytes

when will that be feasible? probably not in the next 10 years right?

[pooya87]

when will that be feasible? probably not in the next 10 years right?

I don't really follow hardware development to be able to give an informed response but considering that over past 10 years we've gone from about 60 TB to the maximum 100 TB SSDs which is roughly a 2x rise, I don't see how a revolution could occur in the next 10 years that could increase this maximum capacity 5.9 million times!

[PrimeNumber7]

Code:

32 * 2^64 = 2^69 = 5.9E+20 bytes = 590,000,000 terabytes

when will that be feasible? probably not in the next 10 years right?

Storing all private keys is pretty pointless, IMO. Simply storing a list of private keys without the ability to a) quickly access the corresponding public key and address, and b) quickly check if the associated address in "a" has received any transactions, will not provide much value to anyone.

As an example, I currently have all possible private keys stored in my head. This includes all of your private keys (although I have no way of filtering out all private keys that do not belong to you). However, my brain cannot quickly calculate an associated address from a private key, so the process of obtaining an address from any private key in my head is very slow. The process for me to look up if an address has received a transaction is even slower.

The above concept can be applied to a computer that is able to store all private keys on a hard drive. Even if a computer could quickly check many private keys to see if a private key's associated address has received a transaction, in order to check n private keys, the computer would need to perform n calculations. The number of private keys is too large for any computer to ever perform any calculation on all possible private keys, given theoretical computational limits.

was thinking 
how much is it gonna be in data TB , if range 64 would be safed uncompressed,
raw txt file, and only this range is it doable?

It would be silly to store things in string form, for example in this case it would be 51-52 bytes versus 32. So to compute the total size needed you just multiply the number of items by the raw-byte size which is 32.

Code:

32 * 2^64 = 2^69 = 5.9E+20 bytes = 590,000,000 terabytes

If I am not mistaken, you are describing the amount of space required to store all private keys as 32 bit integers. Most private keys are numbers that are greater than 32 bits.

[BlackHatCoiner]

The question is why would one save 2⁶⁴ private keys in their hard drive? I mean what's the point? Do you also want to store the addresses after each key, just to make searching easier for the first 2⁶⁴ uncompressed addresses? There's no reason to store only the keys.

If I am not mistaken, you are describing the amount of space required to store all private keys as 32 bit integers. Most private keys are numbers that are greater than 32 bits.

He's talking about the [1, 2⁶⁴] range. Storing all the private keys would cost much much more space.