1BitcoinEaterAddressDontSend

[BurtW]

NEVERMIND - I understand now this is just a bogus (but honest) address which states exactly what will happen if you send any Bitcoins to it.

I have been playing around with vanity address generation.  For fun I ran http://firstbits.com/1bitcoin thinking to myself that surely someone had already claimed that address (if not I was going to get it).  What I got really shocked me:

1BitcoinEaterAddressDontSendf59kuE  

I find this amazing and a bit concerning.  

I was very concerned because my first thought was that someone has enough hashing power to almost reproduce an entire public key address.

I am less concerned now that I figure the search was some sort of regular expression of English words.

Still, I wonder how long this took and how much computational power was used.

This also leads to my main question:  assuming someone could reproduce an entire public key address would they be able to steal the BTC from the original account with that same public key address?

Maybe the owner of this address can tell us how long this took and how they did it.

 

[1714972008]

1714972008

[jwzguy]

Or maybe no one has the private key for this address.

[etotheipi]

The address does not correspond to an actual ECDSA public key.  Remember than an address is just a hash of an ECSDA public key, which means the address can look like anything.  So there's nothing stopping me from creating the address 1BitcoinEaterAddressDontSendf59kuE with the appropriate checksum to make it look like a valid address, but I don't have the public-private keypair needed to spend money sent to that address.

In otherwords, vanity gen creates public/private keypairs and turns them into addresses looking for one that has your target word/phrase in it.  The output is a real address for which you have the private key and can spend the money.   In this case, though, the person can just make the address directly, but has no idea if there is a public/private keypair associated with it, and certainly doesn't have it.  The checksum at the end guarantees the client sees it as valid, but no one will ever be able to provide a public key to the network that hashes to that, and thus any coins sent there will be unrecoverable.

[BurtW]

Thanks.  That explains it.

[Ente]

..what really makes me mad about this address is not that there are already coins being sent to it, which now are unrecoverable.
This address is the address for the firstbits "1bitcoin", which would have been an awesome address in my wallet, on the phone, on my business card! :-)

Ente

[dayfall]

For the data point,  the longest I have found so far is 1Britteny3ZqYR5GPHuamR8HNm93saeVXT.  Correct capitalization makes matching very slow.

[BurtW]

Just curious.  Did you use a CPU or GPU?  How long did it take?

[MaxSan]

I got 1MaxSan in around 7 minutes.

1Chemistry on my CPU said it would take 1.1years xD

[BTCurious]

..what really makes me mad about this address is not that there are already coins being sent to it, which now are unrecoverable.

Nonsense! Some lucky fucker years from now will create this private key and be instantly surprised to see that he has a wallet with money already in it!

This is unlikely on an astronomical scale

[finway]

1BTCmsgZo1ef9nkx1eQMy5DsiaNfRQMVuR
is a good Address too.

[naima53]

The address does not correspond to an actual ECDSA public key.  Remember than an address is just a hash of an ECSDA public key, which means the address can look like anything.  So there's nothing stopping me from creating the address 1BitcoinEaterAddressDontSendf59kuE with the appropriate checksum to make it look like a valid address, but I don't have the public-private keypair needed to spend money sent to that address.

In otherwords, vanity gen creates public/private keypairs and turns them into addresses looking for one that has your target word/phrase in it.  The output is a real address for which you have the private key and can spend the money.   In this case, though, the person can just make the address directly, but has no idea if there is a public/private keypair associated with it, and certainly doesn't have it.  The checksum at the end guarantees the client sees it as valid, but no one will ever be able to provide a public key to the network that hashes to that, and thus any coins sent there will be unrecoverable.

http://blockchain.info/address/1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX
But this address is quite workable ... (it has an outgoing transaction). How to explain it? 

[CIYAM]

http://blockchain.info/address/1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX
But this address is quite workable ... (it has an outgoing transaction). How to explain it? 

You can use regular expressions with vanitygen - so the regex used probably was just [A-Z0-9]+* (or similar) which although difficult is not as difficult as a very long case sensitive specific prefix.

[RoxxR]

How do you explain those have owners?


http://blockchain.info/address/1ELECeJompinDox61L73eAUyaWpe3Q5HZB

http://blockchain.info/address/12345678googr7AWKah5kpLnx2h8zDS6NK

[CIYAM]

How do you explain those have owners?

http://blockchain.info/address/1ELECeJompinDox61L73eAUyaWpe3Q5HZB
http://blockchain.info/address/12345678googr7AWKah5kpLnx2h8zDS6NK

Once again regex's using vanitygen (assuming there are outgoing tx's from them which I haven't checked as I am assuming you have).

Understand that in the first case it could have been ^1ELEC* or perhaps *Jo*Dox* and the second case ^12345678*go* - unless you know exactly what regex the creator used it really is just speculation.

If you really think it is so easy to create any BTC address you like then please try creating 1hohohociyam1 (exact match) and I will send you 10 btc (after you've proved that you own the private key of course).

[BurtW]

How do you explain those have owners?


http://blockchain.info/address/1ELECeJompinDox61L73eAUyaWpe3Q5HZB

http://blockchain.info/address/12345678googr7AWKah5kpLnx2h8zDS6NK

Vanity bitcoin address generation.

https://bitcointalk.org/index.php?topic=25804.0

https://bitcointalk.org/index.php?topic=84569.0

Just like this one:  1BurtWEejbnKeBRsvcydJvsNztB1bXV5iQ

[naima53]

http://blockchain.info/address/1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX
But this address is quite workable ... (it has an outgoing transaction). How to explain it? 

You can use regular expressions with vanitygen - so the regex used probably was just [A-Z0-9]+* (or similar) which although difficult is not as difficult as a very long case sensitive specific prefix.

But as it is fucking hard! (besides vanitigen not working full-length address)

[CIYAM]

But as it is fucking hard! (besides vanitigen not working full-length address)

I have already seen another all upper case vanitygen address in a sig on this forum so I think this must not be correct (at least with the current version).

[mskwik]

Length alone doesn't necessarily make an address that hard to find if you aren't as picky about what exactly makes up that length.  Noticed that one of my machines spit out 1MAG1CALTUXueDaGWq8ozLGL5sutu6DxFq yesterday while it had switched to vanitygen mining for a little while (not that it does me much good).  From recent observations 9 digits is fairly common and even 10 not that unusual when searching against a large enough dictionary, it's when you're looking for something more specific that difficulty starts to get higher.

[etotheipi]

But as it is fucking hard! (besides vanitigen not working full-length address)

I have already seen another all upper case vanitygen address in a sig on this forum so I think this must not be correct (at least with the current version).

That's my address   1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX

The problem is not length, it's how specific of an address you are looking for.  There are about 58³³ possible address, so if you want to find a very specific one (such as 1BitcoinEaterAddressDontSend..), then you have a 1/58³³ chance of finding it on each guess (infeasible*).  However, my address was not a search for a single address, it was any address of all capital letters.  There are about 26³³ such addresses.  So the chances of finding one such address on each guess is 26³³/58³³ = (26/58)³³.  That is actually in the realm of feasibility -- it is about 1/300billion

*  1/58³³ = 1/15599970876632771988160814054146447252125923204784443097088

[nibor]

See https://bitcoinvanity.appspot.com to see how hard different addresses are to find...