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

[TheRealSteve]

No problem

I haven't checked services lately, but these do accept split key generation using your own split key part:
https://vanitypool.appspot.com/
http://vircurvault.com/order/bitcoin/vanity/custom
https://bitcointalk.org/index.php?topic=270180.0

Example of a service that's doing it wrong, because they generate your part of the split key for you:
https://coinbit.tk/generate.php
Last I checked - which is almost a year ago now - they indeed did not send the key to their server.  BUT, here's why you still shouldn't trust services that generate your part of the split key anyway:
https://bitcointalk.org/index.php?topic=118968.0
( tl;dr: vanity address generation service operator says his site was hacked to send the split key part to a malicious actor's server, thus compromising the generated vanity addresses. )

[emrebey]

vanitygen on mac works fine with a little tweak.

that might help:
https://github.com/samr7/vanitygen/issues/45

[coinomat]

What command I need to use if I dont care that is with big or small letters?

Like 1DogEatOneCatxxxxxxxx.....

But for me is same if that is like 1dOGeaToNECAtxxxxx.....



"vanitygen64.exe -v -i 1dogeatonecat " right?



What command I need use to get first letter big and all other from my word small but after that random letter is same big or small..? like "1DogeatxXXxxXXxxX....."
Whit command "vanitygen64.exe -v 1Dogeat" I get error:

Invalid character 'l' in prefix '1Dogeat'



Are that possible stop project and continue later without start again from base?

[TheRealSteve]

What command I need to use if I dont care that is with big or small letters?

"vanitygen64.exe -v -i 1dogeatonecat " right?

Yes.  (See 1st post)

What command I need use to get first letter big and all other from my word small but after that random letter is same big or small..? like "1DogeatxXXxxXXxxX....."

You would need to use the -r (regular expression) option, although I'm not entirely certain what you're trying to achieve.  It may also be more economical to supply a list instead so that you can use oclvanitygen.

Whit command "vanitygen64.exe -v 1Dogeat" I get error:
Invalid character 'l' in prefix '1Dogeat'

Weird - that shouldn't happen.  Are you sure you're not introducing a lowercase letter 'L' somewhere in your prefix?

Are that possible stop project and continue later without start again from base?

This doesn't apply.  It's basically a random process.  The "[Prob N%][M% in Xtime]" is a probability estimator, not a 'progress'

[K1773R]

vanitygen problem it generate same address again
... removed crap ...

in this case, you have a serious problem.
either your PRNG implementation in OpenSSL is broken or your system RNG entroy sources is borked.
of course, both can be the case and are not mutually exclusive.

even worse, this is a good sign that very likely all of the crypto modules your software/OS uses will be weak! its not only vanitygen who is affected by this.

[TheRealSteve]

vanitygen problem it generate same address again

It's a mostly-random process, so that can happen.  In addition there's collisions on address space, though in this case it looks like it ended up with the same private key as well.

Could you share the command line you had used for those two runs?

I don't know off hand what the statistical odds are of that happening with vanitygen, but they should be very, very slim to the point that I'd wonder if somehow the RNG's entropy pool was weak (essentially what K1773R said while I wrote this)...but then it should be happening more often.   ( You can provide another source of entropy for the seed based on a file )

So, either something weird's going on, or you hit a one-in-a-largenumberhere fluke

[K1773R]

vanitygen problem it generate same address again

It's a mostly-random process, so that can happen.  In addition there's collisions on address space, though in this case it looks like it ended up with the same private key as well.

Could you share the command line you had used for those two runs?

I don't know off hand what the statistical odds are of that happening with vanitygen, but they should be very, very slim to the point that I'd wonder if somehow the RNG's entropy pool was weak (essentially what K1773R said while I wrote this)...but then it should be happening more often.   ( You can provide another source of entropy for the seed based on a file )

So, either something weird's going on, or you hit a one-in-a-largenumberhere fluke

If he has a bad PRNG implementation inside OpenSSL then using a different entropy source to seed the PRNG wont fix the problem.

[gmaxwell]

It's a mostly-random process, so that can happen.  In addition there's collisions on address space, though in this case it looks like it ended up with the same private key as well.

Not in any practical sense.

If something was broken that did do that on his system, both execution traces would be the same.

In this case the posts just clearly appeared to be an excuse to encourage people to run backdoored private key generating code (which I've removed from the thread).

[TheRealSteve]

In this case the posts just clearly appeared to be an excuse to encourage people to run backdoored private key generating code (which I've removed from the thread).

Ah that sneaky bugger.  Thanks for catching that, I didn't even bother with the chunk-o-code

If he has a bad PRNG implementation inside OpenSSL then using a different entropy source to seed the PRNG wont fix the problem.

True, it should only affect the seed - that's still important if you don't trust that part.

[K1773R]

It's a mostly-random process, so that can happen.  In addition there's collisions on address space, though in this case it looks like it ended up with the same private key as well.

Not in any practical sense.

If something was broken that did do that on his system, both execution traces would be the same.

In this case the posts just clearly appeared to be an excuse to encourage people to run backdoored private key generating code (which I've removed from the thread).

i've edited my post accordingly by just removing everything aside the headline.

[Just Magicmann]

I'm having issues using my GTX 660 to assist in generating a vanity address. I marked -d 1:0 (already determined correct device) and all it does is show me the commands for vanitygen. I'm using version .20 if that makes a difference.

Command I'm using:
>vanitygen64 -v -d 1:0 -X 115 oMagicmann

[Muhammed Zakir]

I'm having issues using my GTX 660 to assist in generating a vanity address. I marked -d 1:0 (already determined correct device) and all it does is show me the commands for vanitygen. I'm using version .20 if that makes a difference.

Command I'm using:
>vanitygen64 -v -d 1:0 -X 115 oMagicmann

Can you try this?

Code:

vanitygen64 -v -D 1:0 -X 115 oMagicmann

[Just Magicmann]

I'm having issues using my GTX 660 to assist in generating a vanity address. I marked -d 1:0 (already determined correct device) and all it does is show me the commands for vanitygen. I'm using version .20 if that makes a difference.

Command I'm using:
>vanitygen64 -v -d 1:0 -X 115 oMagicmann

Can you try this?

Code:

vanitygen64 -v -D 1:0 -X 115 oMagicmann

I've done both a lower and upper case D and get the same result.

[TheRealSteve]

I'm having issues using my GTX 660 [...]

Command I'm using:
>vanitygen64 -v -d 1:0 -X 115 oMagicmann

Is that the exact command you're using?  If so... you're trying to use the CPU binary to do GPU vanity generation.  Try again with oclvanitygen64

[Just Magicmann]

I'm having issues using my GTX 660 [...]

Command I'm using:
>vanitygen64 -v -d 1:0 -X 115 oMagicmann

Is that the exact command you're using?  If so... you're trying to use the CPU binary to do GPU vanity generation.  Try again with oclvanitygen64

Did it with oclvanitygen and it works. Thanks for correcting my mistake! 

[tspacepilot]

I've had vanitygen looking for a particular vanity prefix (6 letters) for about 5 days (not on the greatest hardware, admittedly, i'm getting 350Kkeys/s).  Nevertheless, I've been at 99.4% probability for 2 days now still with no results.  Could something be wrong or am I just unlucky?

Code:

[349.32 Kkey/s][total 144105239092][Prob 99.4%]

[TwinWinNerD]

I've had vanitygen looking for a particular vanity prefix (6 letters) for about 5 days (not on the greatest hardware, admittedly, i'm getting 350Kkeys/s).  Nevertheless, I've been at 99.4% probability for 2 days now still with no results.  Could something be wrong or am I just unlucky?

Code:

[349.32 Kkey/s][total 144105239092][Prob 99.4%]

Unlucky. The 99.4% doesn't that you are close to finding it. Acutally no matter how long you have already searched, it will always take the same average time from that moment on.

The 99.4% means that if you searched for the amount of time you did, the chance of you finding one key would be 99.4%. So you are just a few standarddeviations from your average. No need to be alarmed.

[tspacepilot]

I've had vanitygen looking for a particular vanity prefix (6 letters) for about 5 days (not on the greatest hardware, admittedly, i'm getting 350Kkeys/s).  Nevertheless, I've been at 99.4% probability for 2 days now still with no results.  Could something be wrong or am I just unlucky?

Code:

[349.32 Kkey/s][total 144105239092][Prob 99.4%]

Unlucky. The 99.4% doesn't that you are close to finding it. Acutally no matter how long you have already searched, it will always take the same average time from that moment on.

The 99.4% means that if you searched for the amount of time you did, the chance of you finding one key would be 99.4%. So you are just a few standarddeviations from your average. No need to be alarmed.

Ok, I think I understand you.  I have searched for this long and have .994 probability of having found one key.  However, I've actually found 0 keys and 1 key isn't that far away from 0 keys (these are the values which aren't so far apart in std.devs, yes?) so I guess I shall just let this thing keep on computing.

[TheRealSteve]

Just for kicks, what is the exact command line you're using?

[tspacepilot]

Just for kicks, what is the exact command line you're using?

Code:

tspacepilot@god:~/src/vanitygen$ ./vanitygen -v 1WALNUT
Prefix difficulty:          27763956579 1WALNUT
Difficulty: 27763956579
Using 2 worker thread(s)