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

[DavidCWG]

Is it possible to use (ocl)vanitygen to generate addresses for BitMessage?

[Red Emerald]

samr7 doesn't seem to have touched his repo in a while.  I went ahead and forked his repo and merged in pretty much all the public branches on github.  I've done some quick tests, and there were no merge conflicts, but it's possible I combined some incompatible things.  

https://github.com/samr7/vanitygen/network has lots of pretty colored lines connecting to one branch now.  I also updated my OSX brew tap (`brew tap WyseNynja/bitcoin && brew install WyseNynja/bitcoin/vanitygen`) to include my branch of vanitygen which I tagged version 0.23-red.  It worked for me on Mavericks and it uses brew's openssl.  I added the red suffix just in case someone else has already done this and I just missed it in my cursory searching.

[Red Emerald]

Greetings.
According to oclvanitygen.c :
'"By default, <pattern> is interpreted as an exact prefix.\n"'
But is there any possibility to use the vanitygen on an OpenCL device to find address not only by prefix, but, for example, by suffix or postfix or regex.

For example not like "1Love.*" but like "1.*Love"?

I think it would be possible, but I know regex would be a lot slower.

[devthedev]

samr7 doesn't seem to have touched his repo in a while.  I went ahead and forked his repo and merged in pretty much all the public branches on github.  I've done some quick tests, and there were no merge conflicts, but it's possible I combined some incompatible things.  

https://github.com/samr7/vanitygen/network has lots of pretty colored lines connecting to one branch now.  I also updated my OSX brew tap (`brew tap WyseNynja/bitcoin && brew install WyseNynja/bitcoin/vanitygen`) to include my branch of vanitygen which I tagged version 0.23-red.  It worked for me on Mavericks and it uses brew's openssl.  I added the red suffix just in case someone else has already done this and I just missed it in my cursory searching.

Do you have a precompiled OSX build of Vanitygen?

[they]

I don't ever want to underestimate my own stupidity, much less publicly proclaim it, but here goes:

I'm generating vanity addresses to give out bitcoin for holiday gifts. I'm using oclvanitygen (since some of the prefixes are kinda long...)

So here's my 1st world problem:

I'm doing this on my laptop with an nvidia card (that is otherwise unused). It's running just fine, except sometimes the laptop overheats from the GPU and shuts down.

Is there some flag that I can use to throttle GPU usage with oclvanitygen?

./oclvanitygen -h
oclVanitygen 0.23-red (OpenSSL 1.0.1 14 Mar 2012)
Usage: ./oclvanitygen [-vqrik1NTS] [-d <device>] [-f <filename>|-] [<pattern>...]
Generates a bitcoin receiving address matching <pattern>, and outputs the
address and associated private key.  The private key may be stored in a safe
location or imported into a bitcoin client to spend any balance received on
the address.
By default, <pattern> is interpreted as an exact prefix.
By default, if no device is specified, and the system has exactly one OpenCL
device, it will be selected automatically, otherwise if the system has
multiple OpenCL devices and no device is specified, an error will be
reported.  To use multiple devices simultaneously, specify the -D option for
each device.

Options:
-v            Verbose output
-q            Quiet output
-i            Case-insensitive prefix search
-k            Keep pattern and continue search after finding a match
-1            Stop after first match
-N            Generate namecoin address
-T            Generate bitcoin testnet address
-X <version>  Generate address with the given version
-F <format>   Generate address with the given format (pubkey, compressed)
-e            Encrypt private keys, prompt for password
-E <password> Encrypt private keys with <password> (UNSAFE)
-P <pubkey>   Use split-key method with <pubkey> as base public key
-p <platform> Select OpenCL platform
-d <device>   Select OpenCL device
-D <devstr>   Use OpenCL device, identified by device string
              Form: <platform>:<devicenumber>[,<options>]
              Example: 0:0,grid=1024x1024
-S            Safe mode, disable OpenCL loop unrolling optimizations
-w <worksize> Set work items per thread in a work unit
-t <threads>  Set target thread count per multiprocessor
-g <x>x<y>    Set grid size
-b <invsize>  Set modular inverse ops per thread
-V            Enable kernel/OpenCL/hardware verification (SLOW)
-f <file>     File containing list of patterns, one per line
              (Use "-" as the file name for stdin)
-o <file>     Write pattern matches to <file>
-s <file>     Seed random number generator from <file>

Would the -w, -g or -t switches/options be what I'm looking for? I'm unsure what exactly each means in the context of this program. Would anyone feel like pulling out their hand-puppets to explain them to me? (I'm guessing that -t is only for CPU usage, not GPU... and subsequently assuming that -b is somehow related to that?)

I'm trying to cobble together something that watches psensor and sends a kill -STOP or a kill -CONT to the actual process, but if there's something I'm missing, I'm all ears!

TIA, folks...

[Kontakt]

The best way, imo, would be to write a powershell script that watches the hardware temp and kills/restarts the process when thresholds are crossed.

[deepceleron]

I'm doing this on my laptop with an nvidia card (that is otherwise unused). It's running just fine, except sometimes the laptop overheats from the GPU and shuts down.

A better approach is to use the nvidia control panel to underclock the GPU core speed. Then vacuum the dust out of the fan hole and slots. And get a desktop PC before you solder-crack your GPU chip.

[Kontakt]

I'm doing this on my laptop with an nvidia card (that is otherwise unused). It's running just fine, except sometimes the laptop overheats from the GPU and shuts down.

A better approach is to use the nvidia control panel to underclock the GPU core speed. Then vacuum the dust out of the fan hole and slots. And get a desktop PC before you solder-crack your GPU chip.

Even better than lowering core is lowering memory speed. Memory is hot.

[they]

Thanks for the suggestions and warnings, folks.

I'm running ubuntu, so the powershell doesn't quite cut it.

Now I'm running an additional script that just watches the temperature and pauses the oclvanitygen process when the temperature of the motherboard goes over 84 (and continues the process when the temperature drops under that).

I'm including a copy of the script, in the hope that it can help others that might be looking for a similar solution.

Code:

#!/bin/bash 
OPID=$(pgrep oclvanitygen) 
 
until [ 1 == 0 ]; do  
    TEMP=$(sensors|grep temp1:|tr -cd '0-9:.'|cut -f1 -d.|cut -f2 -d:) 
    SIGNAL='-CONT' 
    [ $TEMP -gt 84 ] && SIGNAL='-STOP' 
    echo $TEMP... $SIGNAL 
    kill $SIGNAL $OPID 
    sleep 5 
done 

[NoL1m1tZ]

I have a problem: when i start oclvanitygen with 1something, unless to generate public and private key, vg generate a useless cpu and gpu hash...

How i can resolve?

Can you give the string you're using, and the output from the window?

Code:

oclvanitygen -p 1 -d 0 1something

And output like this:

Code:

Difficulty: 264104224
[22.86 Mkey/s][total 455081984][Prob 82.1%][90% in 6.7s]                       
Match idx: 0
CPU hash: 71682fec9bcafa7b1291c2cc09954692b716ca3e
GPU hash: 099bccd501a398a56eff31b40b924d8d9b132b72
Found delta: 4131272 Start delta: 1

I've started to experience this as well, I have concluded this problem is related to newer drivers (eg 13.xx). I had this card working great with v 12.8 Radeon drivers, as have many others.

I'm experiencing this as well.

[Sohcahtoa]

Has anyone had problems with the OCL generator/miner crashing your system when you try to close it?

I'm running a GeForce 460 GTX with the latest drivers.  I can run the OCL versions just fine, that is, until I try to close it.  When that happens, one of three things will happen:

1. It closes just fine with no problems.
2. My screen goes black for a second, then comes back, and I get a notice on my system tray that my display driver had crashed, but it recovered.
3. My system hard locks completely.  Doesn't respond to key presses, any audio that was playing at the time does the machine gun effect, etc.  Only solution is a manual power-off.

#2 happens the most often, with #1 actually being somewhat rare.

Has anyone dealt with this and have any idea how to fix it?

[salfter]

samr7 doesn't seem to have touched his repo in a while.  I went ahead and forked his repo and merged in pretty much all the public branches on github.  I've done some quick tests, and there were no merge conflicts, but it's possible I combined some incompatible things.  

https://github.com/samr7/vanitygen/network has lots of pretty colored lines connecting to one branch now.  I also updated my OSX brew tap (`brew tap WyseNynja/bitcoin && brew install WyseNynja/bitcoin/vanitygen`) to include my branch of vanitygen which I tagged version 0.23-red.  It worked for me on Mavericks and it uses brew's openssl.  I added the red suffix just in case someone else has already done this and I just missed it in my cursory searching.

I see you pulled in (among other things) my compressed-key fixes. 

I spend most of my time in Linux, but I had a request come through for a Windows build.  After tinkering with the makefile a bit, I got Visual C++ 2008 to build vanitygen.  The result is here:

https://dl.dropboxusercontent.com/u/57535575/vanitygen-0.23-red-win32.zip

oclvanityminer is not included, as libcurl was built against a different OpenSSL DLL than what was used for building the other tools.  If you need oclvanityminer, set up a Linux box...building from source on Linux is much easier than building from source on Windows.  vanitygen, oclvanitygen, and keyconv have been built. 

[nevrending]

samr7 doesn't seem to have touched his repo in a while.  I went ahead and forked his repo and merged in pretty much all the public branches on github.  I've done some quick tests, and there were no merge conflicts, but it's possible I combined some incompatible things.  

https://github.com/samr7/vanitygen/network has lots of pretty colored lines connecting to one branch now.  I also updated my OSX brew tap (`brew tap WyseNynja/bitcoin && brew install WyseNynja/bitcoin/vanitygen`) to include my branch of vanitygen which I tagged version 0.23-red.  It worked for me on Mavericks and it uses brew's openssl.  I added the red suffix just in case someone else has already done this and I just missed it in my cursory searching.

Hi. I'm getting the following error

Code:

MacBookLive:vanitygen y458m$ oclvanitygen -D 0:1 -k 1111111
Difficulty: 281474976710656
Compiling kernel, can take minutes...vg_ocl_context_callback error: [CL_DEVICE_NOT_AVAILABLE] : OpenCL Error : Error: Build Program driver returned (517)
vg_ocl_context_callback error: OpenCL Warning : clBuildProgram failed: could not build program for 0x1021b00 (ATI Radeon HD 6750M) (err:-2)
vg_ocl_context_callback error: [CL_BUILD_ERROR] : OpenCL Build Error : Compiler build log:
Error returned by cvms_element_build_from_source

failure.
clBuildProgram: CL_BUILD_PROGRAM_FAILURE
Build log:
Error returned by cvms_element_build_from_source
Device: ATI Radeon HD 6750M
Vendor: AMD (1021b00)
Driver: 1.2 (Sep 19 2013 22:22:06)
Profile: FULL_PROFILE
Version: OpenCL 1.2 
Max compute units: 6
Max workgroup size: 256
Global memory: 536870912
Max allocation: 134217728
Could not open device '0:1', ignoring
Available OpenCL platforms:
0: [Apple] Apple
  0: [Intel] Intel(R) Core(TM) i7-2675QM CPU @ 2.20GHz
  1: [AMD] ATI Radeon HD 6750M

How can I resolve this? Thanks

[Red Emerald]

samr7 doesn't seem to have touched his repo in a while.  I went ahead and forked his repo and merged in pretty much all the public branches on github.  I've done some quick tests, and there were no merge conflicts, but it's possible I combined some incompatible things.  

https://github.com/samr7/vanitygen/network has lots of pretty colored lines connecting to one branch now.  I also updated my OSX brew tap (`brew tap WyseNynja/bitcoin && brew install WyseNynja/bitcoin/vanitygen`) to include my branch of vanitygen which I tagged version 0.23-red.  It worked for me on Mavericks and it uses brew's openssl.  I added the red suffix just in case someone else has already done this and I just missed it in my cursory searching.

Hi. I'm getting the following error

Code:

MacBookLive:vanitygen y458m$ oclvanitygen -D 0:1 -k 1111111
Difficulty: 281474976710656
Compiling kernel, can take minutes...vg_ocl_context_callback error: [CL_DEVICE_NOT_AVAILABLE] : OpenCL Error : Error: Build Program driver returned (517)
vg_ocl_context_callback error: OpenCL Warning : clBuildProgram failed: could not build program for 0x1021b00 (ATI Radeon HD 6750M) (err:-2)
vg_ocl_context_callback error: [CL_BUILD_ERROR] : OpenCL Build Error : Compiler build log:
Error returned by cvms_element_build_from_source

failure.
clBuildProgram: CL_BUILD_PROGRAM_FAILURE
Build log:
Error returned by cvms_element_build_from_source
Device: ATI Radeon HD 6750M
Vendor: AMD (1021b00)
Driver: 1.2 (Sep 19 2013 22:22:06)
Profile: FULL_PROFILE
Version: OpenCL 1.2 
Max compute units: 6
Max workgroup size: 256
Global memory: 536870912
Max allocation: 134217728
Could not open device '0:1', ignoring
Available OpenCL platforms:
0: [Apple] Apple
  0: [Intel] Intel(R) Core(TM) i7-2675QM CPU @ 2.20GHz
  1: [AMD] ATI Radeon HD 6750M

How can I resolve this? Thanks

Hmm. I'm not really sure.  I don't have a mac with a graphics card and haven't been able to test the opencl pieces   I made an issue on github, lets continue this conversation there.  https://github.com/WyseNynja/vanitygen/issues/2

samr7 doesn't seem to have touched his repo in a while.  I went ahead and forked his repo and merged in pretty much all the public branches on github.  I've done some quick tests, and there were no merge conflicts, but it's possible I combined some incompatible things. 

https://github.com/samr7/vanitygen/network has lots of pretty colored lines connecting to one branch now.  I also updated my OSX brew tap (`brew tap WyseNynja/bitcoin && brew install WyseNynja/bitcoin/vanitygen`) to include my branch of vanitygen which I tagged version 0.23-red.  It worked for me on Mavericks and it uses brew's openssl.  I added the red suffix just in case someone else has already done this and I just missed it in my cursory searching.

I see you pulled in (among other things) my compressed-key fixes. 

I spend most of my time in Linux, but I had a request come through for a Windows build.  After tinkering with the makefile a bit, I got Visual C++ 2008 to build vanitygen.  The result is here:

https://dl.dropboxusercontent.com/u/57535575/vanitygen-0.23-red-win32.zip

oclvanityminer is not included, as libcurl was built against a different OpenSSL DLL than what was used for building the other tools.  If you need oclvanityminer, set up a Linux box...building from source on Linux is much easier than building from source on Windows.  vanitygen, oclvanitygen, and keyconv have been built. 

Thanks for the fixes   If you submit a patch for the Makefile, I'll probably merge it in, too.

samr7 doesn't seem to have touched his repo in a while.  I went ahead and forked his repo and merged in pretty much all the public branches on github.  I've done some quick tests, and there were no merge conflicts, but it's possible I combined some incompatible things. 

https://github.com/samr7/vanitygen/network has lots of pretty colored lines connecting to one branch now.  I also updated my OSX brew tap (`brew tap WyseNynja/bitcoin && brew install WyseNynja/bitcoin/vanitygen`) to include my branch of vanitygen which I tagged version 0.23-red.  It worked for me on Mavericks and it uses brew's openssl.  I added the red suffix just in case someone else has already done this and I just missed it in my cursory searching.

Do you have a precompiled OSX build of Vanitygen?

I can upload the one that I've built on my laptop.  No guarantees it's portable though.

[smeagol]

kernel file calc_address.cl is erroring when opening, apparently, any solution?
"calc_address.cl"

On windows, using the oclvanitygen executable

[Red Emerald]

kernel file calc_address.cl is erroring when opening, apparently, any solution?
"calc_address.cl"

On windows, using the oclvanitygen executable

I got that on OSX when it tried to build the .oclbin file (which it does on first run if the file does not exist) without being in the same directory as calc_address.cl.

I'm not sure how to resolve this on windows, but in OS X, that file is installed by my brew tap to /usr/local/opt/vanitygen/include/


nevrending I think the -D flag you are using is wrong.  Try this,

Code:

brew reinstall vanitygen
cd /usr/local/opt/vanitygen/include
oclvanitygen -d 1 -k 1111111

[nevrending]

Hi Red Emerald

Thanks for your reply

I previously used samr7's vanitygen with the following command line

Code:

./oclvanitygen -D 0:1 -t 16 -w 256 -k <prefix>

Normally, samr7's won't compile oclvanitygen on OSX, so I modified the Makefile here and there, and It compiled oclvanitygen
It ran gracefully up until OSX 10.8.5

After I upgraded to OSX 10.9
It no longer runs

I'm gonna try out your suggestions here and on GitHub and will report back the results

[skovbitcoin]

Also having the GPU hash/CPU hash error. I'm running Catalyst 13.11 and downgrading is not an option for me. Also AMD APP SDK v2.9, willing to downgrade this if this is the issue.

[smeagol]

Do you have a precompiled OSX build of Vanitygen?

Looking for a precompiled OSX build as well

[mikeschuld]

For those of you experiencing the hashes not matching issue, what solved the problem for me was to delete the OpenCL files for that newer version of Catalyst and to install an old copy of the 2.7 AMD APP SDK.
Here's the list of files I deleted:

C:\Windows\System32\amdocl64.dll
C:\Windows\System32\OpenCL.dll
C:\Windows\System32\OpenVideo64.dll
C:\Windows\System32\OVDecode64.dll
C:\Windows\System32\SlotMaximizerAg.dll
C:\Windows\System32\SlotMaximizerBe.dll

C:\Windows\SysWOW64\amdocl.dll
C:\Windows\SysWOW64\OpenCL.dll
C:\Windows\SysWOW64\OpenVideo.dll
C:\Windows\SysWOW64\OVDecode.dll
C:\Windows\SysWOW64\SlotMaximizerAg.dll
C:\Windows\SysWOW64\SlotMaximizerBe.dll

The 2.7 SDK I installed was the 32 bit version (I'm running 64-bit Windows 8 but my oclvanitygen is 32-bit). I'm guessing you only need to delete the files in the architecture of the vanitygen you are running.