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

[OgNasty]

oclengine.c:37:19 fatal error: CL/cl.h: No such file or directory

Does someone know what is that error? i cant compile :/

EDIT: i installed opencl-headers that seems i needed. now i have another problem, posting photo
EDIT2: solved the other problem. Now i dont understand what i see:

"~/Downloads/vanity $ ./oclvanitygen -d 0 1Test
Difficulty: 264104224
[8.40 Mkey/s][total 264241152][Prob 63.2%][75% in 12.1s]                       Match idx: 0
CPU hash: ed853c685dd4195eb6c1f8d7c4bd612963696eca
GPU hash: 050a6ef3ae74c30032afaebb41cfce39c15f43b5
Found delta: 1439972 Start delta: 73924609
[8.52 Mkey/s][total 424673280][Prob 80.0%][80% in 0.0s]                        Match idx: 0
CPU hash: 3b7a7c01a5cfbe973125b859c9f31d0ae9824b9e
GPU hash: 050a6ef5932b2871b68a46bdbbaceb1237ebea8c
Found delta: 504296 Start delta: 53477377
Match idx: 0
CPU hash: d360ef49bbd7c5be871d3786eb5a94781a7ab5d7
GPU hash: 050a6ef0ffdb85b40c87c53d13a6464523ce814f
Found delta: 1270427 Start delta: 3145729
[8.36 Mkey/s][total 635437056][Prob 91.0%][95% in 18.6s]  "

when I use "./vanitygen ....  " it gives me the private key and the public. Why here it doesn't ? Thanks for your time

It looks like you're using Linux yes?  If so, here's a simple guide of how to get it working provided by user nonnakip:

I spend several hours getting oclvanitygen working with AMD Radeon 7xxx on 64-bit Linux - Ubuntu 12.04 and Ubuntu 14.04. In the end only the following is needed:

• Ubuntu drivers
• vanitygen patch
• 1 userspace library file from AMD APP SDK v2.7

I created a minimal instruction text file. Maybe this will save someone some hours of searching the internet.

https://nastyfans.org/download/oclvanitygen.txt

[Loco]

It looks like you're using Linux yes?  If so, here's a simple guide of how to get it working provided by user nonnakip:

thanks for answering. Im using linux mint. im gona check that now (.

[K1773R]

oclengine.c:37:19 fatal error: CL/cl.h: No such file or directory

Does someone know what is that error? i cant compile :/

EDIT: i installed opencl-headers that seems i needed. now i have another problem, posting photo
EDIT2: solved the other problem. Now i dont understand what i see:

"~/Downloads/vanity $ ./oclvanitygen -d 0 1Test
Difficulty: 264104224
[8.40 Mkey/s][total 264241152][Prob 63.2%][75% in 12.1s]                       Match idx: 0
CPU hash: ed853c685dd4195eb6c1f8d7c4bd612963696eca
GPU hash: 050a6ef3ae74c30032afaebb41cfce39c15f43b5
Found delta: 1439972 Start delta: 73924609
[8.52 Mkey/s][total 424673280][Prob 80.0%][80% in 0.0s]                        Match idx: 0
CPU hash: 3b7a7c01a5cfbe973125b859c9f31d0ae9824b9e
GPU hash: 050a6ef5932b2871b68a46bdbbaceb1237ebea8c
Found delta: 504296 Start delta: 53477377
Match idx: 0
CPU hash: d360ef49bbd7c5be871d3786eb5a94781a7ab5d7
GPU hash: 050a6ef0ffdb85b40c87c53d13a6464523ce814f
Found delta: 1270427 Start delta: 3145729
[8.36 Mkey/s][total 635437056][Prob 91.0%][95% in 18.6s]  "

when I use "./vanitygen ....  " it gives me the private key and the public. Why here it doesn't ? Thanks for your time

It looks like you're using Linux yes?  If so, here's a simple guide of how to get it working provided by user nonnakip:

I spend several hours getting oclvanitygen working with AMD Radeon 7xxx on 64-bit Linux - Ubuntu 12.04 and Ubuntu 14.04. In the end only the following is needed:

• Ubuntu drivers
• vanitygen patch
• 1 userspace library file from AMD APP SDK v2.7

I created a minimal instruction text file. Maybe this will save someone some hours of searching the internet.

https://nastyfans.org/download/oclvanitygen.txt

You should add a note to remove *.oclbin, since ppl with problems already have a compiled OpenCL binary and it wont be regenerated unless the file is missing.

[audereyy]

Why does it fail checks during compilation?

[alfa12]

Why does it fail checks during compilation?

Hi all!

vanitygen parameter "-F" in what format pubkey need?

[AbraxasCcs]

First: I'm very sorry for my English! Second: Sorry if I post my question in a wrong place.

I have a Piperwallet and I want to add into it the code to generate "Choco-paper wallets". I meant paperwallets for the chococoin altcoin.

I know that I have to handle the code of the vanitygen's commands to adjust the properly generations of the privkey and pubkey of the chococoin.
I looked for some examples and I understood all of them. But when I try to do the same with the chococoin something goes wrong. 

If I do a Pub/Priv address generation for Dogecoin:

Code:

./vanitygen -X 30 D

and I get valid Pub/Priv addresses:

Difficulty: 1
Pattern: D                                                                     
Address: D65ggd5gVVQTy27PvAWV6efZ4F89cz6wYd
Privkey: 6JCejZtYD4PBququxsDG2BgQo1xLL1EvJa3sLDr8KE3TSLVoT5B

But if I try to do the same to generate a valid Pub/Priv couple of addresses for the chococoin it fail:

Code:

./vanitygen -X 16 7

Difficulty: 1
Pattern: 7                                                                     
Address: 7c6LDvfnyMYJE126HYNrYUuxvT4euDcUwQ
Privkey: 5qejeCS5BaV2jHRzGzdFceBvgFafN53mbdZmNt2uXdjWb4Vmn5S

Because the privkey of a chococoin address must begging with 8.

What is that I'm doing wrong?

Thank for any help.

[foroplus]

The decimal code for an address that starts with 8 is 17, 18 or 19; not 16.

Check these out.

[AbraxasCcs]

The decimal code for an address that starts with 8 is 17, 18 or 19; not 16.

Check these out.

I meant the chococoin's privkey starts with "8" but the Address starts with "7"

This an example of what I expect for output from Vanitygen.

Address: 77DHHNisauaocU724yoXCKcos5okNBQdhq
Privkey:  8WUfx7PjHZDe4US6tmoUPMnEix3LdM8uuZDHS93746vNh9Bx4Cq

[K1773R]

The decimal code for an address that starts with 8 is 17, 18 or 19; not 16.

Check these out.

https://en.bitcoin.it/wiki/List_of_address_prefixes

[K1773R]

First: I'm very sorry for my English! Second: Sorry if I post my question in a wrong place.

I have a Piperwallet and I want to add into it the code to generate "Choco-paper wallets". I meant paperwallets for the chococoin altcoin.

I know that I have to handle the code of the vanitygen's commands to adjust the properly generations of the privkey and pubkey of the chococoin.
I looked for some examples and I understood all of them. But when I try to do the same with the chococoin something goes wrong. 

If I do a Pub/Priv address generation for Dogecoin:

Code:

./vanitygen -X 30 D

and I get valid Pub/Priv addresses:

Difficulty: 1
Pattern: D                                                                     
Address: D65ggd5gVVQTy27PvAWV6efZ4F89cz6wYd
Privkey: 6JCejZtYD4PBququxsDG2BgQo1xLL1EvJa3sLDr8KE3TSLVoT5B

But if I try to do the same to generate a valid Pub/Priv couple of addresses for the chococoin it fail:

Code:

./vanitygen -X 16 7

Difficulty: 1
Pattern: 7                                                                     
Address: 7c6LDvfnyMYJE126HYNrYUuxvT4euDcUwQ
Privkey: 5qejeCS5BaV2jHRzGzdFceBvgFafN53mbdZmNt2uXdjWb4Vmn5S

Because the privkey of a chococoin address must begging with 8.

What is that I'm doing wrong?

Thank for any help.

Are the privkey of said coin compressed or normal ones?

[AbraxasCcs]

Are the privkey of said coin compressed or normal ones?

Normal ones. Compressed starts with "A"

[Kangaderoo]

The decimal code for an address that starts with 8 is 17, 18 or 19; not 16.

Check these out.

I meant the chococoin's privkey starts with "8" but the Address starts with "7"

This an example of what I expect for output from Vanitygen.

Address: 77DHHNisauaocU724yoXCKcos5okNBQdhq
Privkey:  8WUfx7PjHZDe4US6tmoUPMnEix3LdM8uuZDHS93746vNh9Bx4Cq

I did a check on the source of the generator @ chococoin(.)org and it seems this coin does not follow the vanitygen software.
When using the -X prefix the following settings are made active

Code:

case 'X':
			addrtype = atoi(optarg);
			privtype = 128 + addrtype;
			scriptaddrtype = addrtype;
			break;

The address type is set to 15 (0x0F) and the privtype to 143 (0x8F)
The source code has these numbers fixed at 15 (0x0F) and 224 (0xE0)
I added a test section in my code, change the following:

Code:

	while ((opt = getopt(argc, argv, "CLvqnrik1eE:P:NTX:F:t:h?f:o:s:")) != -1) {

Add a option for C
The add add the following case with conditions

Code:

----.... snip ....----
case 'C':
			addrtype = 15;
			privtype = 224;
			scriptaddrtype = 224; // I'm not sure what number this must be...
			break;

and rebuild the project.

this is the result
~/vanitygen$ ./vanitygen -C 7

Difficulty: 1
Pattern: 7
Address: 7A2QfyN7GZWs9ca1BsFP2ahew58T1gWd43
Privkey: 8XUzPjTpDaRbfiNGzMUcF2D3bKxXxULQANqYUCyLyXYZDRkK5Qh

Since I don't have a choco-wallet you will need to verify if this private key generates the correct wallet.

[AbraxasCcs]

The decimal code for an address that starts with 8 is 17, 18 or 19; not 16.

Check these out.

I meant the chococoin's privkey starts with "8" but the Address starts with "7"

This an example of what I expect for output from Vanitygen.

Address: 77DHHNisauaocU724yoXCKcos5okNBQdhq
Privkey:  8WUfx7PjHZDe4US6tmoUPMnEix3LdM8uuZDHS93746vNh9Bx4Cq

I did a check on the source of the generator @ chococoin(.)org and it seems this coin does not follow the vanitygen software.
When using the -X prefix the following settings are made active

Code:

case 'X':
			addrtype = atoi(optarg);
			privtype = 128 + addrtype;
			scriptaddrtype = addrtype;
			break;

The address type is set to 15 (0x0F) and the privtype to 143 (0x8F)
The source code has these numbers fixed at 15 (0x0F) and 224 (0xE0)
I added a test section in my code, change the following:

Code:

	while ((opt = getopt(argc, argv, "CLvqnrik1eE:P:NTX:F:t:h?f:o:s:")) != -1) {

Add a option for C
The add add the following case with conditions

Code:

----.... snip ....----
case 'C':
			addrtype = 15;
			privtype = 224;
			scriptaddrtype = 224; // I'm not sure what number this must be...
			break;

and rebuild the project.

this is the result
~/vanitygen$ ./vanitygen -C 7

Difficulty: 1
Pattern: 7
Address: 7A2QfyN7GZWs9ca1BsFP2ahew58T1gWd43
Privkey: 8XUzPjTpDaRbfiNGzMUcF2D3bKxXxULQANqYUCyLyXYZDRkK5Qh

Since I don't have a choco-wallet you will need to verify if this private key generates the correct wallet.

It's is a correct pair ok keys!!!! It does works in the client chococoin-qt.

Thank!!

[CoinBucks.IO]

Just wanted to say thanks for this tool, it is very cool, and I was able to easily use it and get a vanity address.  Cheers!

[TheRealSteve]

Hi all!

vanitygen parameter "-F" in what format pubkey need?

"pubkey" is already the default.  The -F parameter would be used as following:
.exe -F pubkey 1...
.exe -F compressed 1...
.exe -F script 3...

Each bitcoin address is the result of an encoding of a hash the public key.  That public key can be expressed in two ways, uncompressed (equivalent to X and Y coordinates) and compressed (equivalent to X coordinate and a sign, from which the Y coordinate can be derived).
Say you generate '1abc' using both (don't actually use these keys/addresses!):
Uncompressed (default):

Code:

vanitygen.exe -F pubkey 1abc
Difficulty: 4553521
Pattern: 1abc
Address: 1abcCjhme96hnPDe3pDc3Ch1EnEj5Rjv7
Privkey: 5KG6rYdSopgYo1rejJAdPfbS6RgqhtAecg7EA19mJi9P9s2Ftru

The private key for an uncompressed form always starts with a 5.

Code:

vanitygen.exe -F compressed 1abc
Difficulty: 4553521
Pattern: 1abc
Address: 1abcRZRi2Gh4tZHJNbAyVyjSRx8uB67jk
Privkey: L2i2dzuR7CtDTkXQeh2m9jKiBtuxFNTTCHobBb3bySaHhxDFf6WK

The private key for a compressed form starts with a K or an L.

This is generally how wallet clients etc. recognize which form to use, and that's important because of what I mentioned earlier.  Let's say I use the private key 5KG6rY, once with the correct uncompressed public key, and once with an incorrectly assumed compressed public key:

Code:

private: 5KG6rYdSopgYo1rejJAdPfbS6RgqhtAecg7EA19mJi9P9s2Ftru
public key (uncompressed): 04C57E907AEC9BA14D377EA1627672197A87D38A0BB12A390B1504FF9A6A941772D052906B5A5AFB908E096C1C884C0E14096BB47EAC617C99DEDADBC4AE5241F7
hash: 065A9D7AD12CA8C1962FB0E21C4E92DB86BE137E
address: 1abcCjhme96hnPDe3pDc3Ch1EnEj5Rjv7

Code:

private: 5KG6rYdSopgYo1rejJAdPfbS6RgqhtAecg7EA19mJi9P9s2Ftru
public key (compressed): 03C57E907AEC9BA14D377EA1627672197A87D38A0BB12A390B1504FF9A6A941772
hash: D4BEAF01D5E007F63FB28BF262DF1E9E3A68132B
address: 1LPtgbhspbUKVxmntmRSYzUMkpkZiHJH6w

So you can see that if you make an incorrect assumption, you end up with the alternate (non-vanity) address.
( You'd probably be searching quite a while to find a private key that yields a vanity prefix in both uncompressed and compressed, let alone the same vanity prefix )

As a general rule, you should probably be using "-F compressed", as the blockchain ends up being smaller if everybody used compressed public keys (even if it does get negated by dust, comment spam, tumblers, etc.), but either pubkey or compressed will work.

The "script" one is a parameter you can ignore unless you really want to muck about with BIP13 type transactions

( Note that the above applies to Bitcoin addresses - if you're generating for an altcoin, the -F parameter may or may not apply depending on that coin's details. )

[alfa12]

Hi all!

vanitygen parameter "-F" in what format pubkey need?

"pubkey" is already the default.  The -F parameter would be used as following:
.exe -F pubkey 1...
.exe -F compressed 1...
.exe -F script 3...

Each bitcoin address is the result of an encoding of a hash the public key.  That public key can be expressed in two ways, uncompressed (equivalent to X and Y coordinates) and compressed (equivalent to X coordinate and a sign, from which the Y coordinate can be derived).
Say you generate '1abc' using both (don't actually use these keys/addresses!):
Uncompressed (default):

Code:

vanitygen.exe -F pubkey 1abc
Difficulty: 4553521
Pattern: 1abc
Address: 1abcCjhme96hnPDe3pDc3Ch1EnEj5Rjv7
Privkey: 5KG6rYdSopgYo1rejJAdPfbS6RgqhtAecg7EA19mJi9P9s2Ftru

The private key for an uncompressed form always starts with a 5.

Code:

vanitygen.exe -F compressed 1abc
Difficulty: 4553521
Pattern: 1abc
Address: 1abcRZRi2Gh4tZHJNbAyVyjSRx8uB67jk
Privkey: L2i2dzuR7CtDTkXQeh2m9jKiBtuxFNTTCHobBb3bySaHhxDFf6WK

The private key for a compressed form starts with a K or an L.

This is generally how wallet clients etc. recognize which form to use, and that's important because of what I mentioned earlier.  Let's say I use the private key 5KG6rY, once with the correct uncompressed public key, and once with an incorrectly assumed compressed public key:

Code:

private: 5KG6rYdSopgYo1rejJAdPfbS6RgqhtAecg7EA19mJi9P9s2Ftru
public key (uncompressed): 04C57E907AEC9BA14D377EA1627672197A87D38A0BB12A390B1504FF9A6A941772D052906B5A5AFB908E096C1C884C0E14096BB47EAC617C99DEDADBC4AE5241F7
hash: 065A9D7AD12CA8C1962FB0E21C4E92DB86BE137E
address: 1abcCjhme96hnPDe3pDc3Ch1EnEj5Rjv7

Code:

private: 5KG6rYdSopgYo1rejJAdPfbS6RgqhtAecg7EA19mJi9P9s2Ftru
public key (compressed): 03C57E907AEC9BA14D377EA1627672197A87D38A0BB12A390B1504FF9A6A941772
hash: D4BEAF01D5E007F63FB28BF262DF1E9E3A68132B
address: 1LPtgbhspbUKVxmntmRSYzUMkpkZiHJH6w

So you can see that if you make an incorrect assumption, you end up with the alternate (non-vanity) address.
( You'd probably be searching quite a while to find a private key that yields a vanity prefix in both uncompressed and compressed, let alone the same vanity prefix )

As a general rule, you should probably be using "-F compressed", as the blockchain ends up being smaller if everybody used compressed public keys (even if it does get negated by dust, comment spam, tumblers, etc.), but either pubkey or compressed will work.

The "script" one is a parameter you can ignore unless you really want to muck about with BIP13 type transactions

( Note that the above applies to Bitcoin addresses - if you're generating for an altcoin, the -F parameter may or may not apply depending on that coin's details. )

Good afternoon.
Thank you for an answer.
but I however to the end understood how to use pubkey.
here line with the key over brought by you.

vanitygen64.exe  -F 04C57E907AEC9BA14D377EA1627672197A87D38A0BB12A390B1504FF9A6A941772D052906B5A5AF B908E096C1C884C0E14096BB47EAC617C99DEDADBC4AE5241F7 1abc

result : of Invalid format

[TheRealSteve]

but I however to the end understood how to use pubkey.
here line with the key over brought by you.

vanitygen64.exe  -F 04C57E907AEC9BA14D377EA1627672197A87D38A0BB12A390B1504FF9A6A941772D052906B5A5AF B908E096C1C884C0E14096BB47EAC617C99DEDADBC4AE5241F7 1abc

result : of Invalid format

You don't actually specify a public key, it's just the word "pubkey":

Code:

vanitygen64.exe  -F pubkey 1abc

If you are trying to generate a vanity address for somebody else, and they gave you a public key to use for a 'split key' generation (the way the vanity pool websites work, or at least should work), then you actually need to use the -P parameter:

Code:

vanitygen64.exe -P 04C57E907AEC9BA14D377EA1627672197A87D38A0BB12390B1504FF9A6A941772D052906B5A5AFB908E096C1C884C0E14096BB47EAC617C99DEDADBC4AE5241F7 1abc
Difficulty: 4553521
Pattern: 1abc
Address: 1abcwLjVjwdqf6PeEmNiBhNoARTZSn193
PrivkeyPart: 5JnhiD6kAxkQiWBmJqupkS5qR2PFUwCQWq1DAyqcWj2wkU1HYqz

They would then combine the PrivkeyPart with their PrivkeyPart to get the Private key for the generated vanity address.

[Professor James Moriarty]

 I know it will sound stupid but is there a way to get an address online like we used to from a trustworthy place? Something small like 1bitcoin.... so and so , is it possible to get it online like that?

[LtPaxIV]

 I know it will sound stupid but is there a way to get an address online like we used to from a trustworthy place? Something small like 1bitcoin.... so and so , is it possible to get it online like that?

do u mean u want someone to "hire" so he makes u the 1bitcoin address? if so just go to this website https://vanitypool.appspot.com/

it uses ur public key to generate ur new address.but keep in mind 1bitcoin or even longer will takes some time to finish.

[gadman2]

 I know it will sound stupid but is there a way to get an address online like we used to from a trustworthy place? Something small like 1bitcoin.... so and so , is it possible to get it online like that?

Use split key, no trust involved. See my signature.