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

[TrueBeliever]

Yep, added - thanks

I also recently updated the Vanitygen article in general with some general info on pattern difficulty and any delusions of trying to use Vanitygen to attack addresses

I would like to say a gtx 780ti does 50-60Mkey/s highest was 62Mkey/s

just for documenting purposes.

which version is your card? I assume it is the faster 3GB RAM, DDR5, 384bit bus version?

[1713925324]

1713925324

[1713925324]

1713925324

[1713925324]

1713925324

[1713925324]

1713925324

[ezeminer]

Yep, added - thanks

I also recently updated the Vanitygen article in general with some general info on pattern difficulty and any delusions of trying to use Vanitygen to attack addresses

I would like to say a gtx 780ti does 50-60Mkey/s highest was 62Mkey/s

just for documenting purposes.

which version is your card? I assume it is the faster 3GB RAM, DDR5, 384bit bus version?

Yea
http://www.newegg.com/Product/Product.aspx?Item=N82E16814487001

[jacktheking]

Hey guys (and girls). I have been trying to use the keyconv utility as stated in first post. However, my machine dont seem to understand. When I run ./keyconv -G it gave me the following error.

Code:

Invalid character '-' in prefix './keyconv'

Code:

Invalid character 'G' in prefix '-G'

How can I fix it?

Edit: Found out that I dont have keyconv.exe installed. Not sure why. Downloaded the latest version and it's working now.

[tspacepilot]

Hey guys (and girls). I have been trying to use the keyconv utility as stated in first post. However, my machine dont seem to understand. When I run ./keyconv -G it gave me the following error.

Code:

Invalid character '-' in prefix './keyconv'

Code:

Invalid character 'G' in prefix '-G'

How can I fix it?

Edit: Found out that I dont have keyconv.exe installed. Not sure why. Downloaded the latest version and it's working now.

Glad you figured it out.  For the record it's nicer if you can put the entire comand line (including your invocation, not just the error message).  I was looking at your error message thinking, there must be some syntax error in the command he wrote, but since I couldn't see the command you wrote ...

[foodstamps]

So I can only get oclvanitygen to recognize 2 GPUs at a time on same rig....even if I have 5 connected. Is this normal?

[Jude Austin]

So I can only get oclvanitygen to recognize 2 GPUs at a time on same rig....even if I have 5 connected. Is this normal?

Did you try using -D argument?

oclvanitygen64 -D 0:0 -D 0:1 -D 0:2 -D 0:3 -D 0:4 12manyGPUs

[bitcreditscc]

Been wondering how to go about creating a vanity multi-sig address anyone ever attempted ? Fail/Succeed?

[TheRealSteve]

Been wondering how to go about creating a vanity multi-sig address anyone ever attempted ? Fail/Succeed?

See this discussion for some pointers:
https://www.reddit.com/r/Bitcoin/comments/202ka5/is_it_possible_to_make_a_vanity_multisig_address/

I'm pretty sure I've seen a multisig vanity out there used either by a pool or an exchange, but don't recall any details.

[bitcreditscc]

Been wondering how to go about creating a vanity multi-sig address anyone ever attempted ? Fail/Succeed?

See this discussion for some pointers:
https://www.reddit.com/r/Bitcoin/comments/202ka5/is_it_possible_to_make_a_vanity_multisig_address/

I'm pretty sure I've seen a multisig vanity out there used either by a pool or an exchange, but don't recall any details.

great thanks!!!

[tspacepilot]

I guess I finally noticed this paragraph on the wiki page for vanitygen:

As vanitygen performs a lot of large integer arithmetic, running it in 64-bit mode makes a huge difference in key search rate, easily a 50% improvement over 32-bit mode. If you are using a 64-bit edition of Windows, and not using a GPU, be sure to use vanitygen64.exe.

So that made me double-check and it turned out that my binary of vanitygen was:

Code:

tspacepilot@computer:~/src/vanitygen$ file vanitygen
vanitygen: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=36407df1ab36b5bef2906e418394ec750806c884, not stripped

Whoops!

So I rebuilt it and now Ihave a 64-bit executable and things are faster.  Okay, so I continue reading on the same page:

In custom builds, CPU performance will be less than expected if the OpenSSL library is an older version (<1.0.0d) or is not built with the appropriate optimizations enabled.

Well, I had built by just saying "make", so this makes me wonder what are the appropriate optimizations (are they Makefile options I should be passing?).  That's the point of this question then, should I just say "make" or should I be passing some kind of optimization parameters?

[hexafraction]

I guess I finally noticed this paragraph on the wiki page for vanitygen:

As vanitygen performs a lot of large integer arithmetic, running it in 64-bit mode makes a huge difference in key search rate, easily a 50% improvement over 32-bit mode. If you are using a 64-bit edition of Windows, and not using a GPU, be sure to use vanitygen64.exe.

So that made me double-check and it turned out that my binary of vanitygen was:

Code:

tspacepilot@computer:~/src/vanitygen$ file vanitygen
vanitygen: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=36407df1ab36b5bef2906e418394ec750806c884, not stripped

Whoops!

So I rebuilt it and now Ihave a 64-bit executable and things are faster.  Okay, so I continue reading on the same page:

In custom builds, CPU performance will be less than expected if the OpenSSL library is an older version (<1.0.0d) or is not built with the appropriate optimizations enabled.

Well, I had built by just saying "make", so this makes me wonder what are the appropriate optimizations (are they Makefile options I should be passing?).  That's the point of this question then, should I just say "make" or should I be passing some kind of optimization parameters?

You might need to set CFLAGS and/or CXXFLAGS to include -O3 when running configure if you don't see -O3 in the command lines shown when running make. However, -O3 might be already set most likely. I'd need to double check.

[tspacepilot]

I guess I finally noticed this paragraph on the wiki page for vanitygen:

As vanitygen performs a lot of large integer arithmetic, running it in 64-bit mode makes a huge difference in key search rate, easily a 50% improvement over 32-bit mode. If you are using a 64-bit edition of Windows, and not using a GPU, be sure to use vanitygen64.exe.

So that made me double-check and it turned out that my binary of vanitygen was:

Code:

tspacepilot@computer:~/src/vanitygen$ file vanitygen
vanitygen: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=36407df1ab36b5bef2906e418394ec750806c884, not stripped

Whoops!

So I rebuilt it and now Ihave a 64-bit executable and things are faster.  Okay, so I continue reading on the same page:

In custom builds, CPU performance will be less than expected if the OpenSSL library is an older version (<1.0.0d) or is not built with the appropriate optimizations enabled.

Well, I had built by just saying "make", so this makes me wonder what are the appropriate optimizations (are they Makefile options I should be passing?).  That's the point of this question then, should I just say "make" or should I be passing some kind of optimization parameters?

You might need to set CFLAGS and/or CXXFLAGS to include -O3 when running configure if you don't see -O3 in the command lines shown when running make. However, -O3 might be already set most likely. I'd need to double check.

I might be completely wrong here, but isn't the -O3 just going to build the program in parallel?  I guess I thought the wiki wasn't referring to optimizing the build process itself, but to optimizing the built binary for working on some harware or another.  Please correct me if I'm wrong!

[hexafraction]

I might be completely wrong here, but isn't the -O3 just going to build the program in parallel?  I guess I thought the wiki wasn't referring to optimizing the build process itself, but to optimizing the built binary for working on some harware or another.  Please correct me if I'm wrong!

No, that's -j2 (or some other number) passed to make. -O3 means optimization level 3 (highest performance). When you add it to CFLAGS or CXXFLAGS and then run ./configure, the makefile will contain -O3 for all compiler steps. Thus the compiler will be called with -O3 and thus every compilation unit/source file will be compiled with maximum optimizations.

[tspacepilot]

I might be completely wrong here, but isn't the -O3 just going to build the program in parallel?  I guess I thought the wiki wasn't referring to optimizing the build process itself, but to optimizing the built binary for working on some harware or another.  Please correct me if I'm wrong!

No, that's -j2 (or some other number) passed to make. -O3 means optimization level 3 (highest performance). When you add it to CFLAGS or CXXFLAGS and then run ./configure, the makefile will contain -O3 for all compiler steps. Thus the compiler will be called with -O3 and thus every compilation unit/source file will be compiled with maximum optimizations.

Thanks, I'll look at the Makefile that I downloaded from github and see what's going on in there with respect to CFLAGS/CXXFLAGS.

EDIT:

This is the top of the default Makefile, looks like I'm okay if that's the only optimizations they're referring to in the wiki:

Code:

LIBS=-lpcre -lcrypto -lm -lpthread
CFLAGS=-ggdb -O3 -Wall

[hexafraction]

I might be completely wrong here, but isn't the -O3 just going to build the program in parallel?  I guess I thought the wiki wasn't referring to optimizing the build process itself, but to optimizing the built binary for working on some harware or another.  Please correct me if I'm wrong!

No, that's -j2 (or some other number) passed to make. -O3 means optimization level 3 (highest performance). When you add it to CFLAGS or CXXFLAGS and then run ./configure, the makefile will contain -O3 for all compiler steps. Thus the compiler will be called with -O3 and thus every compilation unit/source file will be compiled with maximum optimizations.

Thanks, I'll look at the Makefile that I downloaded from github and see what's going on in there with respect to CFLAGS/CXXFLAGS.

EDIT:

This is the top of the default Makefile, looks like I'm okay if that's the only optimizations they're referring to in the wiki:

Code:

LIBS=-lpcre -lcrypto -lm -lpthread
CFLAGS=-ggdb -O3 -Wall

Yep, it looks like it's being fully optimized. I'm not sure why -ggdb is included; debug builds usually have poorer performance. -ggdb should be removed and the final executable tested.

[tspacepilot]

I might be completely wrong here, but isn't the -O3 just going to build the program in parallel?  I guess I thought the wiki wasn't referring to optimizing the build process itself, but to optimizing the built binary for working on some harware or another.  Please correct me if I'm wrong!

No, that's -j2 (or some other number) passed to make. -O3 means optimization level 3 (highest performance). When you add it to CFLAGS or CXXFLAGS and then run ./configure, the makefile will contain -O3 for all compiler steps. Thus the compiler will be called with -O3 and thus every compilation unit/source file will be compiled with maximum optimizations.

Thanks, I'll look at the Makefile that I downloaded from github and see what's going on in there with respect to CFLAGS/CXXFLAGS.

EDIT:

This is the top of the default Makefile, looks like I'm okay if that's the only optimizations they're referring to in the wiki:

Code:

LIBS=-lpcre -lcrypto -lm -lpthread
CFLAGS=-ggdb -O3 -Wall

Yep, it looks like it's being fully optimized. I'm not sure why -ggdb is included; debug builds usually have poorer performance. -ggdb should be removed and the final executable tested.

Thanks for the tip, I'll remove the debugger flag and rebuild.  Cheers!

EDIT: that actually does appear to have made a small difference, but to be honest I think it's in the margin of error (10Kkeys/s or so) since I'm doing other things on this computer at the same time.

[hexafraction]

I might be completely wrong here, but isn't the -O3 just going to build the program in parallel?  I guess I thought the wiki wasn't referring to optimizing the build process itself, but to optimizing the built binary for working on some harware or another.  Please correct me if I'm wrong!

No, that's -j2 (or some other number) passed to make. -O3 means optimization level 3 (highest performance). When you add it to CFLAGS or CXXFLAGS and then run ./configure, the makefile will contain -O3 for all compiler steps. Thus the compiler will be called with -O3 and thus every compilation unit/source file will be compiled with maximum optimizations.

Thanks, I'll look at the Makefile that I downloaded from github and see what's going on in there with respect to CFLAGS/CXXFLAGS.

EDIT:

This is the top of the default Makefile, looks like I'm okay if that's the only optimizations they're referring to in the wiki:

Code:

LIBS=-lpcre -lcrypto -lm -lpthread
CFLAGS=-ggdb -O3 -Wall

Yep, it looks like it's being fully optimized. I'm not sure why -ggdb is included; debug builds usually have poorer performance. -ggdb should be removed and the final executable tested.

Thanks for the tip, I'll remove the debugger flag and rebuild.  Cheers!

EDIT: that actually does appear to have made a small difference, but to be honest I think it's in the margin of error (10Kkeys/s or so) since I'm doing other things on this computer at the same time.

No problem, I'll do some testing myself. I don't have working OpenCL drivers so I'm forced to go CPU, so I'm always on the lookout for compile-time optimizations beyond the defaults for some CPU-intensive executables I use.

[ChetnotAtkins]

Could anybody post the necessary code changes to allow oclvanitygen to generate compressed and uncompressed keys simultaneously? I suspect the speed increase must be substantial

Thanks!

[deepceleron]

Could anybody post the necessary code changes to allow oclvanitygen to generate compressed and uncompressed keys simultaneously? I suspect the speed increase must be substantial

Thanks!

Your "suspicion" is misplaced. The only calculation in common that would be saved is the calculation of the x coordinate of the public key, which is just a few multiplications. Everything else, from creating the compressed public key parity, creating an address from a compressed public key and checking for the vanity match would be a completely different process.

[Monopoly]

I have 5 prefix letters , what is the command line for find at least a BTC address for it ?