Vanitygen: Vanity bitcoin address generator/miner [v0.22]

[andulolika]

What OS are you using? Do you have up-to-date drivers? Which GPU (specific ATI model)?

Windows 7 not genuine, yep all drivers. http://www.sapphiretech.com/presentation/product/product_index.aspx?cid=1&gid=3&sgid=1157&pid=1450&&lid=1
im 90% is this one, sapphire 7950.

[1714255473]

1714255473

[1714255473]

1714255473

[Cinnob0n]

Would be cool if you could use a Miner to find addresses.

[TheRealSteve]

Would be cool if you could use a Miner to find addresses.

Would, but (for ASIC-based ones) you can't - physically impossible.  Probably covered numerous times in this thread already, so hit up the search if you'd like to learn more

[luv2drnkbr]

Is it possible to use vanitygen to make a multisig key?  Like, two people give me their public keys for a 2- or 3- of 3 address, and it churns through redeem scripts until it finds a key that makes the redeem script hash to the pattern?

[tspacepilot]

Would be cool if you could use a Miner to find addresses.

Would, but (for ASIC-based ones) you can't - physically impossible.  Probably covered numerous times in this thread already, so hit up the search if you'd like to learn more

Well, I believe that search is temporarily disabled.  But, FWIW, I'm one of the people you explained this to above.  The sha256 algo used to mine blocks just isn't the same procedure as the one to find and address.  So, alas, even our old stick miners can't help us here.

[RustyNomad]

Following is a problem I had with vanitygen, not sure whether I did something wrong and or whether this is something that may happen from time to time...

a) I generated 5 Doge addresses making use of the oclvanity command and the -X 30 -e parameters to generate a addresses with encrypted private keys.

b) Some coins were sent to the one address and all seemed fine (luckily only about $1)

c) I used the keyconv command with the -X 30 parameter to decrypt the encrypted private key which worked without any problems and it gave me the correct Doge address

d) I tried to import the private key of this address into a Dogechain wallet but it does not accept the private key. Tried the Wif and Hex versions of the private key

e) Tried the Doge paper wallet generator where you enter the Wif/Hex keys and get details on the address and tried the other formats of the private key but none seems to work...

The above only happened with the one address, the other 4 all worked fine and I've been able to import them without problems. Is this something that happens or something I did wrong and if so how do I prevent this from happening or should I just test every address before use to make sure they work 100%?

I had no idea that vanitygen worked for any coin other than bitcoin.  Wish I could help?  Also, isn't keyconv command part of an external python lib?  Seems like there are several possible points of failure here.

Yes it works for other coins as well. You just need to make use of the -X parameter together with the right code for the specific kind of address you want to create. For example: Litecoin is -X 48, Doge -X 30, Dash -X 76 etc... So your command will look something like - c:\vanitygen -v -X 30 D8Test

See this reply to my earlier post for links to a site that will give you the codes:

https://bitcointalk.org/index.php?topic=25804.msg11399708#msg11399708

[tspacepilot]

Following is a problem I had with vanitygen, not sure whether I did something wrong and or whether this is something that may happen from time to time...

a) I generated 5 Doge addresses making use of the oclvanity command and the -X 30 -e parameters to generate a addresses with encrypted private keys.

b) Some coins were sent to the one address and all seemed fine (luckily only about $1)

c) I used the keyconv command with the -X 30 parameter to decrypt the encrypted private key which worked without any problems and it gave me the correct Doge address

d) I tried to import the private key of this address into a Dogechain wallet but it does not accept the private key. Tried the Wif and Hex versions of the private key

e) Tried the Doge paper wallet generator where you enter the Wif/Hex keys and get details on the address and tried the other formats of the private key but none seems to work...

The above only happened with the one address, the other 4 all worked fine and I've been able to import them without problems. Is this something that happens or something I did wrong and if so how do I prevent this from happening or should I just test every address before use to make sure they work 100%?

I had no idea that vanitygen worked for any coin other than bitcoin.  Wish I could help?  Also, isn't keyconv command part of an external python lib?  Seems like there are several possible points of failure here.

Yes it works for other coins as well. You just need to make use of the -X parameter together with the right code for the specific kind of address you want to create. For example: Litecoin is -X 48, Doge -X 30, Dash -X 76 etc... So your command will look something like - c:\vanitygen -v -X 30 D8Test

See this reply to my earlier post for links to a site that will give you the codes:

https://bitcointalk.org/index.php?topic=25804.msg11399708#msg11399708

Thanks, I never saw that parameter before (but then again, I'm not into altcoins).  Still, I'm right that keyconv is a separate python package, right?  That's not part of vanitygen is it?

[Kangaderoo]

Thanks, I never saw that parameter before (but then again, I'm not into altcoins).  Still, I'm right that keyconv is a separate python package, right?  That's not part of vanitygen is it?

The keyconv as can be found in the repositories that hold vanitygen is not a python package.
I have not checked if python holds a package with the same name, but that is pure coincidence.

This software can be used if you need or provide vanity address generation for a third party in a secure way.

The two keys that you end up with can be combined with this tool to the WIF key that generates the correct vanity address.

In short, it is part of the vanitygen package, but not needed if you only generate the keys for own use.

[RustyNomad]

In short, it is part of the vanitygen package, but not needed if you only generate the keys for own use.

Unless you make use of the -e parameter to encrypt the private key. It was my understanding that you then need to make use of keyconv.exe to decrypt that private key. There however seems to be some problems as I've had several keys where it worked i.e. the decrypted private key but I've also had about 5 keys now where the decrypted private key was shown as invalid when trying to import it into a wallet.

[Kangaderoo]

In short, it is part of the vanitygen package, but not needed if you only generate the keys for own use.

Unless you make use of the -e parameter to encrypt the private key. It was my understanding that you then need to make use of keyconv.exe to decrypt that private key. There however seems to be some problems as I've had several keys where it worked i.e. the decrypted private key but I've also had about 5 keys now where the decrypted private key was shown as invalid when trying to import it into a wallet.

I never actually looked at this decryption of the private key.
This is more or less a security action, I'm not sure how (or even if) this links into the actual vanitygen algoritms.

One thing that i found interesting, and I will look into this a bit further, is that both
vanitygen and keyconf have the -e and -E for password encryption.
None of these programs have a setting for the decryption.

The util.c source code holds a function to decrypt, but I cannot find where a call to this function is actually made.

[TheRealSteve]

The util.c source code holds a function to decrypt, but I cannot find where a call to this function is actually made.

Are you referring to vg_decode_privkey_any ?

That gets called from keyconv.  Usage is keyconv <encrypted key>.  Should prompt you for password.

[Kangaderoo]

The util.c source code holds a function to decrypt, but I cannot find where a call to this function is actually made.

Are you referring to vg_decode_privkey_any ?

That gets called from keyconv.  Usage is keyconv <encrypted key>.  Should prompt you for password.

Yep that's the one I was looking for 

[RustyNomad]

Yes keyconv is what is used to decrypt the keys but as I stated, I've had problems with this.

I generated several keys with vanitygen using the -e parameter to encrypt the private key. When I use keyconv to decrypt these private keys I'm asked for the password which I then entered. Once the decryption was done I was provided with the correct public key and the private key in Hex and Wif formats.

When I however try and import either the Wif or Hex private keys into a wallet it tells me that the format is not valid. This has now happened on about 3 keys. What I don't understand is why some private keys worked and some did not.

My logic tells me that if it worked for one key it should work for all as it's the same code being repeated so why did some keys decrypt properly while others gave me private keys which were invalid yet when decrypted it did give me the correct public keys?

[TheRealSteve]

If you're getting the correct public key - or rather, the vanity address you requested - then I doubt it's a problem with the decryption part.  More likely the generated key is simply invalid for the coin in question (in your case: Dogecoin).

If you could share one (encrypted + your decrypted output), might be easier to figure out what's wrong with it.

[RustyNomad]

If you could share one (encrypted + your decrypted output), might be easier to figure out what's wrong with it.

I unfortunately did not keep the ones that did not work. Tried recreating this by generating around 50 odd addresses but all worked. Looks like the problem might have been on my side i.e. I must have made a mistake somewhere with the copying of the address and encrypted keys.... but then again if I did, why did I still get the right address when decrypting.

In any case, will try a couple more later today and see whether I can recreate the problem I had before.

[andulolika]

I still need help to vanity with amd, sapphire 7950, windows 7 not geniunie (im thinking about moving to linux it may help?)  and drivers up to date.

[Muhammed Zakir]

I still need help to vanity with amd, sapphire 7950, windows 7 not geniunie (im thinking about moving to linux it may help?)  and drivers up to date.

I could never make OpenCL work in a fake Windows. I think it won't but if there is a way, I like to hear it too.

[andulolika]

I still need help to vanity with amd, sapphire 7950, windows 7 not geniunie (im thinking about moving to linux it may help?)  and drivers up to date.

I could never make OpenCL work in a fake Windows. I think it won't but if there is a way, I like to hear it too.

What about ubuntu?

[Muhammed Zakir]

I still need help to vanity with amd, sapphire 7950, windows 7 not geniunie (im thinking about moving to linux it may help?)  and drivers up to date.

I could never make OpenCL work in a fake Windows. I think it won't but if there is a way, I like to hear it too.

What about ubuntu?

OpenCL works in Ubuntu.

[Jude Austin]

I still need help to vanity with amd, sapphire 7950, windows 7 not geniunie (im thinking about moving to linux it may help?)  and drivers up to date.

Use lifeboats version with the 64 bit DLL.