Selling Bitcoin public address and privatekey pairs

[PanizJosGerces]

Hello,

I have created nice program, which generate Bitcoin Addresses and PrivateKeys pairs for given
"Secret exponent" range. Program also "sorting" Bitcoin addresses to one file (only the three first characters per file).
This is not actually sorting, but if the first three characters match, address will go to same file.
Address will be more easily to find, if file size is not so huge and "same kind of" addresses are on own file.

See this web page: http://directory.io/
I have same idea, but "sorting" BTC address.
My program need quite a lot CPU power and huge amount of pairs take time and disk space.
So the biggest order amount is now 130 millions pairs and this take time. (days)

You could buy these pairs from me and I will send the link to you, where the pairs are located.
The output files are compressed to ZIP -format and the ZIP -file is password protected.

Possible BTC address-Privatekey pairs order amounts and prices
===============================================================
===============================================================

Pairs amount      BTC Price
===================================
  1,000,000      0,001 BTC
  2,500,000      0,002 BTC
  6,000,000      0,004 BTC
 13,000,000     0,008 BTC
 28,000,000     0,016 BTC
 60,000,000     0,032 BTC
130,000,000    0,064 BTC

Ask offer request, if you like to do bigger offer than 130 millions pairs.


Order instructions
==================

My BTC address: 1D6sXae5un83KRWg85zGLQiD7wjTsEkgKE
My E-mail: btcprivatekey@gmail.com

Send "Secret exponent" start value to me by email and pairs amount.
example: "345356787643456765430965042656434564643124765 and pairs amount is 2,500,000"
Min "secret exponent" is "1" and Max is "115792089237316195423570985008687907852837564279074904382605163141518161494336".
So select secret exponent between minimum and maximum.
After that transfer correct amount of BTC to my BTC address (1D6sXae5un83KRWg85zGLQiD7wjTsEkgKE).
When I get mail and BTC, then I will start to generate address and privatekey pairs to you.
When this is ready, I'll send link to you where you can download zipped file (file hosting web page)
and also I'll send password to that zip -file.

Here is example -file:
http://www.filehosting.org/file/details/457812/example.zip
This is not password protected. Just download and unzip.

Best Regards,
PanizJosGerces

[1715105904]

1715105904

[1715105904]

1715105904

[1715105904]

1715105904

[1715105904]

1715105904

[Dmined]

Very obvious scam here people... firstly Bitcoin addresses are free to generate, secondly he holds the private key so can access the wallet at any time. Avoid.

[Parsons]

I think the idea is that OP creates a huge amount of addresses... not sure what the point is mind.

[webbrowser]

I can't fathom what this is for.

Clearly, it's not useful to pick your preferred vanity address from this range, because OP (and other buyers) will know the private key.

Perhaps the point of this is to set 130 million watch addresses, and the moment some poor sod transfers bitcoins into it, you sweep the address? What are the chances of this happening anyway?

[dougg]

Is this a normal service offered here? I haven't seen this before and can't work out a single purpose of it?

[Muhammed Zakir]

You will have to ask public key part. Asking privatekey part points that this is a perfect scam. So maybe you are mistaken how this works, so ask public key part and send them the private key part without a hosting site, i.e., by PM or email. Anyway, I don't think it works well as there are users and sites which will generate free vanity address(es) if you send them the public key part. If you can generate an address with 10+ letters, you may have chance.

  ~~MZ~~

[shorena]

I can't fathom what this is for.

Clearly, it's not useful to pick your preferred vanity address from this range, because OP (and other buyers) will know the private key.

Perhaps the point of this is to set 130 million watch addresses, and the moment some poor sod transfers bitcoins into it, you sweep the address? What are the chances of this happening anyway?

This is exactly the point. Chance of a collision is 1 in 2¹⁶⁰ for a single key, slightly "better" for 130 Million keys. This is the most expensive lottery with the worst chance of winning, esp. since OP can check if there is anything spendable before selling.

[redsn0w]

I don't trust him....  . Pay attention guys .

[richierich]

How much to create every possible bitcoin address?

[Taras]

How much to create every possible bitcoin address?

There are exactly 1,461,501,637,330,902,918,203,684,832,716,283,019,655,932,542,976 possible addresses as long as we keep using RIPE-MD160.

It'll never happen, not with all the computers of fifty million earths

[owazer]

This has been discussed several times in the forum, the possibility to generate an used address is so small that it can be considered impossible.

[Ramones]

How much to create every possible bitcoin address?

There are exactly 1,461,501,637,330,902,918,203,684,832,716,283,019,655,932,542,976 possible addresses as long as we keep using RIPE-MD160.

It'll never happen, not with all the computers of fifty million earths

That's a pretty long number....

And for clarity it's

one quindecillion,
four hundred sixty-one quattuordecillion,
five hundred one tredecillion,
six hundred thirty-seven duodecillion,
three hundred thirty undecillion,
nine hundred two decillion,
nine hundred eighteen nonillion,
two hundred three octillion,
six hundred eighty-four septillion,
eight hundred thirty-two sextillion,
seven hundred sixteen quintillion,
two hundred eighty-three quadrillion,
nineteen trillion,
six hundred fifty-five billion,
nine hundred thirty-two million,
five hundred forty-two thousand,
nine hundred seventy-six

exactly

[webbrowser]

I can't fathom what this is for.

Clearly, it's not useful to pick your preferred vanity address from this range, because OP (and other buyers) will know the private key.

Perhaps the point of this is to set 130 million watch addresses, and the moment some poor sod transfers bitcoins into it, you sweep the address? What are the chances of this happening anyway?

This is exactly the point. Chance of a collision is 1 in 2¹⁶⁰ for a single key, slightly "better" for 130 Million keys. This is the most expensive lottery with the worst chance of winning, esp. since OP can check if there is anything spendable before selling.

But hey, it's not just "slightly better".  It's 130 million times better! 

[Vortex20000]

Why the hell would I pay you to steal my money, ahem?

[onezerobit]

Its like here is the lock and key to your bank locker....and there is only one more person who has the key.
NICE :/

[deepceleron]

The wealth of ignorance in the first post was nearly incorrigible, but I managed to glean what he thinks he's doing.

1. From a starting private key integer you specify,
2. generate sequentially addresses from that point,
3. append them to filenames starting with the first three letters of the address.

Scam. Besides never using an address where a third-party knows the private key, you should not use an address where the private key is not randomly generated, and you should not use addresses where the private key is related to another in any way.

Nevertheless, I wrote everybody a program to do the same thing as OP, except without the python list cruft the OP left in the files in his example. You can save this as "stupidwallet.py". Warning, you will quickly approach 58² files in the directory where you run it.

Code:

#!/usr/bin/python

# Paste here: https://raw.githubusercontent.com/vbuterin/pybitcointools/master/bitcoin/main.py
# and comment out the line "import ripemd"

privstart = int(raw_input('Enter start private key in decimal:\n>'))
iterations = int(raw_input('Enter number of addresses:\n>'))
for i in xrange(0, iterations):
    privwif = encode_privkey(privstart + i, 'wif_compressed', vbyte=0)
    addrwif = privkey_to_address(privwif)
    #print(addrwif + ", " + privwif)
    if not i % 1000:
        print(i)
    file = open(addrwif[:3] + '.txt', 'a')
    file.write(addrwif + ", " + privwif + '\n')
    file.close()

[tres_commas]

Hey, reviving old topic...I know. The value in this is that someone like me that's creating a table of key pairs that are sorted by public address, with enough, can derive patterns of offset that the private keys are, assuming they wrap around. 


On the subject of RSA's:

To encrypt a number you multiply it by itself pub times, making sure to wrap around when you hit the maximum. To decrypt a message, you multiply it by itself priv times and you get back to the original number. It sounds surprising, but it actually works. This property was a big breakthrough when it was discovered.

Source: https://blog.cloudflare.com/a-relatively-easy-to-understand-primer-on-elliptic-curve-cryptography/ 

Eventually there will be a breakthrough when it comes to priv, pub keypairs with bitcoin. This idea can be used as a bitcoin recovery business for what was once forever lost bitcoins. This will also mean bitcoin will be broken unless it adapts. I for one would love to create this recovery service for the bitcoin community. If I get close to the breakthrough, I'll be sure to quitly tell whichever devs are working on the main bitcoin development. What good would it be to crash the price of bitcoin to nothing and hold all the coins, but there's value in being the first to make it to recover any current lost coins to re-enter into circulation (a recovery miner), and any new wallets of course would be migrated into newer wallet formats as long as the owner is still alive, thus revealing lost coins.

[hexafraction]

Hey, reviving old topic...I know. The value in this is that someone like me that's creating a table of key pairs that are sorted by public address, with enough, can derive patterns of offset that the private keys are, assuming they wrap around. 


On the subject of RSA's:

To encrypt a number you multiply it by itself pub times, making sure to wrap around when you hit the maximum. To decrypt a message, you multiply it by itself priv times and you get back to the original number. It sounds surprising, but it actually works. This property was a big breakthrough when it was discovered.

Source: https://blog.cloudflare.com/a-relatively-easy-to-understand-primer-on-elliptic-curve-cryptography/ 

Eventually there will be a breakthrough when it comes to priv, pub keypairs with bitcoin. This idea can be used as a bitcoin recovery business for what was once forever lost bitcoins. This will also mean bitcoin will be broken unless it adapts. I for one would love to create this recovery service for the bitcoin community. If I get close to the breakthrough, I'll be sure to quitly tell whichever devs are working on the main bitcoin development. What good would it be to crash the price of bitcoin to nothing and hold all the coins, but there's value in being the first to make it to recover any current lost coins to re-enter into circulation (a recovery miner), and any new wallets of course would be migrated into newer wallet formats as long as the owner is still alive, thus revealing lost coins.

This is mathematically nonsense. EC is NOT RSA. The concept is faulty since EC point addition does not work in this way.

[superpanos2]

On top of what users said, some people tend to hash their password multiple times
in order to achieve a higher level of security.(Brainwallet.org doesn't)
So your chances of finding even a satoshi are zero

[b!z]

This is satire, right.... ?