Bitcoin Forum

Awesome! Thanks for the feedback... I just wanted to make sure I wasn't spinning my wheels and would have to start over again...

I loaded the vanitygen on one of my unused servers in my data center and turned it loose finding the pattern but when it was taking so long I was afraid I may have done something dumb and would have to start over again.

Whew!

i have a pretty specific address with 9 characters.

vanity is best outsourced, so when searching you are not just searching for your one address but for all requested ones at once

digits or characters?

1xxxxxxxx  (alpha characters)

That will reduce the search space significantly. (although the 1000k per second is quite a bit slower than the 250,000k that I had based my calculations on).

Good luck.  9 characters is a lot to match.  I don't think I've seen anyone yet with a 9 character vanity address.

it sounds like i can just run vanitygen and several machines to increase my odds and there isn't necessarily a duplication of work... just luck.

what do you mean??

AAAHHHHH!!!!! Bitcoin address generation is best never outsourced! Why did 10 replies not mention this? It is utterly stupid to trust any service to generate save addresses for you as there is no way of knowing if he deleted his copy or not. Once he gets cancer or turns into an asshole, he digs out these addresses and spends your money.

If you want address hello and I want Hallo, somebody could search for both and give you and me the respective results.

It is utterly stupid to trust any service to generate save addresses for you as there is no way of knowing if he deleted his copy or not. Once he gets cancer or turns into an asshole, he digs out these addresses and spends your money.

AAAHHHHH!!!!! Bitcoin address generation is best never outsourced! Why did 10 replies not mention this?

1) You generate a random 256-bit integer less than the SECP256k1 generator. You keep this secret. (Effectively, an ECDSA private key.)

2) You compute the corresponding EC point on the SECP256k1 curve. You share this with whoever is finding the vanity address for you. (This is the ECDSA public key that corresponds to the private key you generated in step one.)

3) The person working out the vanity address for you tries various 256-bit integers also less than the SECP256k1 generator. They compute the corresponding EC point and add it to the EC point you sent them (from step two). They then hash this and see if it produces the desired vanity address. They repeat this over and over until they find a 256-bit integer that works. They give this integer to you. (And the world, it need not be kept secret.)

4) You add the 256-bit integer they found to the 256-bit integer you generated in step 1 and reduce it modulo the SECP256k1 generator.

5) You now have the private key, and they don't. (And you can prove that they cannot generate the private key from just the information you gave them unless ECDSA is fundamentally broken.)

In ECDSA, you convert a private key to a public key by multiplying by the generator. Division is impossible.

The vanity address generation scheme above works because: (A+B)*G = AG + BG

You generate A and AG, but give them only AG.

They try various different B's, calculating the AG+BG for each one to find the right one for the vanity address.

They give you B. You can now compute A+B (the secret key corresponding to the public key AG+BG) but nobody else can since they do not know A.

Computing A from AG would mean breaking ECDSA fundamentally. All you gave them is AG, an ECDSA public key. If they could figure out the private key to your new account (A+B), they could also figure out A. So if they could figure out the private key to your vanity account, they could also figure out the private key you created in step 1. But all you gave them was the corresponding public key. So any compromise of the vanity account would mean they could compromise a private key given only its corresponding public key.

AAAHHHHH!!!!! Bitcoin address generation is best never outsourced!

AND...... I found it!

https://static.squarespace.com/static/53178407e4b0e91cea146c90/t/53645dece4b0dfd7136ac722/1399086583580/?format=300w

1BLackHAtGEKmcioF8pA88XPbEkBf8Hf12

It took about 25 days from start to finish...

Did you mean for it to say Black Hat Geek?

Or are you trying to find address with "blackhat" and find the "gek" part accidentally?

9 characters !? Good luck :)

I thought I was hard core when I searched for 6 lol.

Already found it. Took just 25 days. If I do it again I think I am going to distribute the job across many more servers in my data center to increase my luck and perhaps do it faster next time.

If I do it again I think I am going to distribute the job across many more servers in my data center to increase my luck and perhaps do it faster next time.

yeah this much is pretty obvious...

i was curious though if there was some time of secured service providing this... i still probably would never trust it, however i was curious.

i will continue to hash away at my own vanity address on my own servers..

after having the basic logic explained (which i probably should have grokked from the start) i will just disperse vanitygen across a few dozen servers and see which one comes up the winner.

Do you have a decent graphics card? If so, did you use the version of vanitygen that exploits it? Doing so can make a big difference. On my machine, generating 1Brangdon gets to 50% after 511 days with vanitygen, 310 days with vanitygen64, and 15 days with oclvanitygen. So 20 times faster with the graphics card.

i used vanitygen64

i didnt know about oclvanitygen. i have a whole slew of GPU miners that it should work on. i will try it sometime as i retire my gpu's but they are still hashing strong from me so i hesitate to take one offline.