Topic: Vanitygen: Vanity bitcoin address generator/miner [v0.22] - page 100. (Read 1153678 times)

"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):
The private key for an uncompressed form always starts with a 5.

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:


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. )

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!

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

Thank!!

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
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:


Add a option for C
The add add the following case with conditions
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.

Normal ones. Compressed starts with "A"

Are the privkey of said coin compressed or normal ones?

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

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.

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

Check these out.

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:


and I get valid Pub/Priv addresses:


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




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

What is that I'm doing wrong?

Thank for any help.

Hi all!

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

Why does it fail checks during compilation?

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.

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

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:

it would work if i change my graphic card for a 7970? (i have a 6670 here )

if u use vanitygen it does it using the cpu,if u use oclvanitygen it will use ur gpu,by the lines u posted it means it doesnt work with ur gpu

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

im using a 5850 and a 7850 and am getting 35 Mh/s average on the 2 cards together

A graphics card would help a lot. For me it took just about 1 hour to generate six characters. Can you tell me how much keys are you getting per sec?

Kindly,
      MZ