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

[tspacepilot]

Make sure the expression is valid for a bitcoin address. You can search for [O0l] without ever finding a result.

That would actually be a good improvement for vanitygen, to do a validation step to ensure that what's being looked for actually could match a bitcoin address.  I haven't thought about the completeness of the problem but at the very least you could (as you point out) rule out any expressions which explicitly look for [O0I].  I don't think I have the code checked out at the moment or I'd consider submitting a pull request myself.

[Timelord2067]

Make sure the expression is valid for a bitcoin address. You can search for [O0l] without ever finding a result.

That would actually be a good improvement for vanitygen, to do a validation step to ensure that what's being looked for actually could match a bitcoin address.  I haven't thought about the completeness of the problem but at the very least you could (as you point out) rule out any expressions which explicitly look for [O0I].  I don't think I have the code checked out at the moment or I'd consider submitting a pull request myself.

It does:

Invalid Character 'I' in prefix '1BIG'

[K1773R]

not skipping was correct. You'r binary is compiled and ready to go. Now we need to fix the last issue:

Thanks

is the package nvidia-modprobe installed? if not, install it.

Seems like it:

Code:

# lsmod | grep -i nvidia
nvidia               8646656  33
drm                   344064  7 i915,drm_kms_helper,nvidia

Code:

# find / | grep modprobe | grep -i nvidia
/etc/modprobe.d/nvidia-graphics-drivers.conf
/etc/modprobe.d/nvidia-352_hybrid.conf
/lib/nvidia-352/modprobe.conf

The contents of these files:

Code:

Laptop / # cat /etc/modprobe.d/nvidia-graphics-drivers.conf
# This file was installed by nvidia-352
# Do not edit this file manually

blacklist nouveau
blacklist lbm-nouveau
blacklist nvidia-current
blacklist nvidia-173
blacklist nvidia-96
blacklist nvidia-current-updates
blacklist nvidia-173-updates
blacklist nvidia-96-updates
blacklist nvidia-352-updates
alias nvidia nvidia_352
alias nvidia-uvm nvidia_352-uvm
alias nouveau off
alias lbm-nouveau off

Laptop / # cat /etc/modprobe.d/nvidia-352_hybrid.conf
# This file was installed by nvidia-352
# Do not edit this file manually

blacklist nouveau
blacklist lbm-nouveau
alias nouveau off
alias lbm-nouveau off

Laptop / # cat /lib/nvidia-352/modprobe.conf
# This file was installed by nvidia-352
# Do not edit this file manually

blacklist nouveau
blacklist lbm-nouveau
blacklist nvidia-current
blacklist nvidia-173
blacklist nvidia-96
blacklist nvidia-current-updates
blacklist nvidia-173-updates
blacklist nvidia-96-updates
blacklist nvidia-352-updates
alias nvidia nvidia_352
alias nvidia-uvm nvidia_352-uvm
alias nouveau off
alias lbm-nouveau off

I don't know iff the blacklists are relevant.


I am running the Nvidia-driver:


Judging by this I would say my X-server knows the card:


And this is what I have installed:

check if this file exists:

Code:

$ ls -al /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.1

does this exist too?

Code:

$ ls -al /etc/OpenCL/vendors/nvidia.icd

if not:

Code:

$ sudo mkdir -p /etc/OpenCL/vendors
$ sudo tee /etc/OpenCL/vendors/nvidia.icd <<< 'libnvidia-opencl.so.1'

I think this is all okay:

Code:

Laptop ~ # ls -al /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.1
lrwxrwxrwx 1 root root 26 Nov 16 20:51 /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.1 -> libnvidia-opencl.so.352.63
Laptop ~ # ls -alL /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.1
-rw-r--r-- 1 root root 15901968 Nov  8 06:08 /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.1
Laptop ~ # ls -al /etc/OpenCL/vendors/nvidia.icd
-rw-r--r-- 1 root root 22 Nov  8 05:08 /etc/OpenCL/vendors/nvidia.icd
Laptop ~ # cat /etc/OpenCL/vendors/nvidia.icd
libnvidia-opencl.so.1

Anything else I can do/try? It's probably something really simple once you know it

install the nvidia-modprobe package.

try to run the miner with sudo, as with a incorrect OpenCL setup, you'll need root to load the nvidia_uvm kernel module. Once loaded you dont need sudo again. Your missing that module, hence the failure.

[shorena]

Make sure the expression is valid for a bitcoin address. You can search for [O0l] without ever finding a result.

That would actually be a good improvement for vanitygen, to do a validation step to ensure that what's being looked for actually could match a bitcoin address.  I haven't thought about the completeness of the problem but at the very least you could (as you point out) rule out any expressions which explicitly look for [O0I].  I don't think I have the code checked out at the moment or I'd consider submitting a pull request myself.

It does:

Invalid Character 'I' in prefix '1BIG'

I guess it depends on what you actually entered as neiter "small ell" not "big eye" are filtered for me. Are you using -r?

Code:

$ ./vanitygen -r '1BlG'
[154.22 Kkey/s][total 4432640]                              

./vanitygen -r 1BIG
[159.72 Kkey/s][total 2447104]                                                                    

./vanitygen -r 1BiG
Pattern: 1BiG                                                                 
Address: 1BiGFYAr4xegoTRbLfnTKHC9tAdfFgddYA
Privkey: 5J4BeUWY3qjVzMzQc49JGMQrpLDUmyKjeA6eHDMcvuY2anKFxYY

[LoyceV]

try to run the miner with sudo, as with a incorrect OpenCL setup, you'll need root to load the nvidia_uvm kernel module. Once loaded you dont need sudo again. Your missing that module, hence the failure.

This fixed it! Running once as root, compiling kernel, and now it runs as user too.
From 200-400 kkeys/s (depending on system load) to up to over 7.5 Mkeys/s! Thank you so much, that's 25 times faster on average!

Code:

Difficulty: 264104224
Compiling kernel, can take minutes...done!
Pattern: 1test                                                                
Address: 1testvSQ7NjT2bjG3Ywv8GkCNCCQmUxcz
Privkey: 5HrhdHG7LzJG1k1teTKbGRhNqZzU9LxMsYTUxoNoTmUb7frNmDB

Now the search continues It's running at 79 degrees C now, and slowly going up, After cleaning it a bit it runs at 62 degrees C now.

Edit: on performance: the GeForce 840M reaches just over 9 Mkeys/s if I close my browsers to reduce CPU (or video?) load.

[K1773R]

try to run the miner with sudo, as with a incorrect OpenCL setup, you'll need root to load the nvidia_uvm kernel module. Once loaded you dont need sudo again. Your missing that module, hence the failure.

This fixed it! Running once as root, compiling kernel, and now it runs as user too.
From 200-400 kkeys/s (depending on system load) to up to over 7.5 Mkeys/s! Thank you so much!

Code:

Difficulty: 264104224
Compiling kernel, can take minutes...done!
Pattern: 1test                                                                
Address: 1testvSQ7NjT2bjG3Ywv8GkCNCCQmUxcz
Privkey: 5HrhdHG7LzJG1k1teTKbGRhNqZzU9LxMsYTUxoNoTmUb7frNmDB

Now the search continues It's running at 79 degrees C now, and slowly going up, After cleaning it a bit it runs at 62 degrees C now.

Edit: on performance: the GeForce 840M reaches just over 9 Mkeys/s if I close my browsers to reduce CPU (or video?) load.

you needed root to load the nvidia_uvm kernel module. with the nvidia-modprobe package installed, you can load the kernel module as user too or rather, it gets auto loaded.

If you use the GUI, obviously there will be less computing power for the OpenCL stuff. Some browsers use hardware accelerating which hinders oclvanitygen even more.

Have fun with vanitygen

[LoyceV]

you needed root to load the nvidia_uvm kernel module. with the nvidia-modprobe package installed, you can load the kernel module as user too or rather, it gets auto loaded.

I skipped this part of your previous comment since I got it working, but it sounds like an improvement.
When I google it, it simply says to `apt-get install nvidia-modprobe`, but it doesn't exist on my system. I now know it's something I should still fix, but for now I'm happy I can use it

[tspacepilot]

I wonder if you guys are just using different versions of the software.  Perhaps the filtering was added recently?

Make sure the expression is valid for a bitcoin address. You can search for [O0l] without ever finding a result.

That would actually be a good improvement for vanitygen, to do a validation step to ensure that what's being looked for actually could match a bitcoin address.  I haven't thought about the completeness of the problem but at the very least you could (as you point out) rule out any expressions which explicitly look for [O0I].  I don't think I have the code checked out at the moment or I'd consider submitting a pull request myself.

It does:

Invalid Character 'I' in prefix '1BIG'

I guess it depends on what you actually entered as neiter "small ell" not "big eye" are filtered for me. Are you using -r?

Code:

$ ./vanitygen -r '1BlG'
[154.22 Kkey/s][total 4432640]                              

./vanitygen -r 1BIG
[159.72 Kkey/s][total 2447104]                                                                    

./vanitygen -r 1BiG
Pattern: 1BiG                                                                 
Address: 1BiGFYAr4xegoTRbLfnTKHC9tAdfFgddYA
Privkey: 5J4BeUWY3qjVzMzQc49JGMQrpLDUmyKjeA6eHDMcvuY2anKFxYY

[Timelord2067]

I wonder if you guys are just using different versions of the software.  Perhaps the filtering was added recently?

I'm using oclvanitygen64 and there doesn't appear to be a

Code:

-r

switch.

[shorena]

I wonder if you guys are just using different versions of the software.  Perhaps the filtering was added recently?

I'm using oclvanitygen64 and there doesn't appear to be a

Code:

-r

switch.

Yep, the GPU version cant do regex. Not sure why. Try

Code:

vanitygen64 -r test

[K1773R]

you needed root to load the nvidia_uvm kernel module. with the nvidia-modprobe package installed, you can load the kernel module as user too or rather, it gets auto loaded.

I skipped this part of your previous comment since I got it working, but it sounds like an improvement.
When I google it, it simply says to `apt-get install nvidia-modprobe`, but it doesn't exist on my system. I now know it's something I should still fix, but for now I'm happy I can use it

well, then you can either load the module yourself with modprobe, or run any OpenCL application with root and quit it again to load the module.

Code:

$ sudo modprobe nvidia_uvm

if you get any ohter issues, just drop a post or send me a private message.

[actmyname]

Haha, I managed to get lucky on this.

Generated 1ActBTCi5XUMjqnyFxVWgSfE5xWicj8g3o when I was trying to find a non-case-sensitive prefix of "actbtc". It was my first try of that result, in under 10 minutes. Thanks greatly for making this.

If I had more time or much faster computational power I'd go ahead and help other people or generate a full "1actmyname" prefix. (But even the non-case-sensitive of that takes 100+ days at my current speed)

[LoyceV]

If I had more time or much faster computational power I'd go ahead and help other people or generate a full "1actmyname" prefix. (But even the non-case-sensitive of that takes 100+ days at my current speed)

I need 11 days for 50% chance for "1actmyname -i". Are you running on a fast CPU, or on a very slow GPU? If you use a fast CPU now, it may be possible to switch to your video card and get much more speed out of it (for me it added approximately 1 character in the same time).

Out of curiousity: what if the vanity pool finds the required address, but adds something bad behind it? Just bad luck for the person who bought the address? My search for 1faucets" ended up with an additional "uck" behind it. If someone pays good money for an address, they won't like it.

[Timelord2067]

I wonder if you guys are just using different versions of the software.  Perhaps the filtering was added recently?

I'm using oclvanitygen64 and there doesn't appear to be a

Code:

-r

switch.

Yep, the GPU version cant do regex. Not sure why. Try

Code:

vanitygen64 -r test

I just reread the last couple of pages - I didn't know about this feature - I'd use it for middle or especially end of addresses, but the GPU cards can kept doing the front prefix.

If I have the "1" eg "1name" will the -r look just at the front?

[shorena]

I wonder if you guys are just using different versions of the software.  Perhaps the filtering was added recently?

I'm using oclvanitygen64 and there doesn't appear to be a

Code:

-r

switch.

Yep, the GPU version cant do regex. Not sure why. Try

Code:

vanitygen64 -r test

I just reread the last couple of pages - I didn't know about this feature - I'd use it for middle or especially end of addresses, but the GPU cards can kept doing the front prefix.

If I have the "1" eg "1name" will the -r look just at the front?

Nope.

Code:

>vanitygen64.exe -r -k 1name
Pattern: 1name
Address: 1CKNZnaZa2p42woa11name5Deo8WSMnUXa
Privkey: 5K7hoViAWPeqcupUFM4PyyNvxQQKaiLfNcTcqxt63wWFe69ai3M

[LoyceV]

If I have the "1" eg "1name" will the -r look just at the front?

With -r there is no reason for adding the 1, unless you want to. The -r option reduced the speed to less than 100kkeys/s here, about two thirds off.

I have considered searching for somethhing short (say 1Hi), and after this doing a second search through the output-file. Unfortunately, oclvanitygen says I can better use CPU for short strings. I did indeed notice it takes about 1 second for an ocl-search to start, so I can't just output a lot of keys this way. On CPU it finds about 200 per second, if that would be 25 times more on GPU, I could do a regex-search on only the keys starting with 1Hi at 5kkeys/s. But it doesn't work that way, I'm just curious why.

[Timelord2067]

If I had more time or much faster computational power I'd go ahead and help other people or generate a full "1actmyname" prefix. (But even the non-case-sensitive of that takes 100+ days at my current speed)

I need 11 days for 50% chance for "1actmyname -i". Are you running on a fast CPU, or on a very slow GPU? If you use a fast CPU now, it may be possible to switch to your video card and get much more speed out of it (for me it added approximately 1 character in the same time).

Out of curiousity: what if the vanity pool finds the required address, but adds something bad behind it? Just bad luck for the person who bought the address? My search for 1faucets" ended up with an additional "uck" behind it. If someone pays good money for an address, they won't like it.

Code:

1actmyname -i

would take me about ~ 2 days to reach 50% with a part public key

Code:

-i Difficulty: 11,285,585,616,889
Case Sensitive Difficulty: 173,346,595,075,428,786

ON Shorena's Bitcoin Vanity Addresses! https://bitcointalk.org/index.php?topic=1257817.0 page

|   -example-   |   1Qdefghij   |   Y   |   1,506,418,547,304   |   0.0167 BTC   |   
|   lihuajkl   |   1lihuajkl   |   Y   |   1,583,016,100,557   |   0.0165 BTC   |
|   -example-   |   1Tdefghij   |   Y   |   23,349,487,483,220   |   0.2337 BTC   |
|   -example-   |   1abcdefg   |   N   |   51,529,903,411,245   |   0.495 BTC

So, somewhere over the rainbow this'd cost ~ BTC 0.12 (or there abouts) for a case insensitive.

[JWU42]

Did a quick scan for optimized setting for oclvanitygen (worksize).  New box with a 980 and getting 62M Key/s now and didn't know how much better I could go...

TIA!

[Timelord2067]

Did a quick scan for optimized setting for oclvanitygen (worksize).  New box with a 980 and getting 62M Key/s now and didn't know how much better I could go...

TIA!

I've never looked into the worksize side of things, have just started it up and let it run.  I don't think I can get much more out of my cards.  62MKyes/s is impressive though.

[JWU42]

Did a quick scan for optimized setting for oclvanitygen (worksize).  New box with a 980 and getting 62M Key/s now and didn't know how much better I could go...

TIA!

I've never looked into the worksize side of things, have just started it up and let it run.  I don't think I can get much more out of my cards.  62MKyes/s is impressive though.

On my desktop it lags badly.  Reminds me of GPU mining days but there were switches to pass on the command line to decrease the intensity...