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

[samr7]

First: no apology necessary.
Second: WOOHOO!!!

I am in the Mkeys/s now!  

I'm glad it works for you!

If you put the #define INLINE inline back the way it was, does it still build?
EDIT: be sure to do make clean first, before rebuilding with make all

Also, what GPU do you have, and what key rate are you seeing?

[1714214436]

1714214436

[1714214436]

1714214436

[1714214436]

1714214436

[check_status]

Revalin got me going with Vanitygen and github.

sudo apt-get install libpcre3-dev libssl-dev
git clone https://github.com/samr7/vanitygen.git
cd vanitygen
make
./vanitygen

From: https://bitcointalk.org/index.php?topic=67466.0

Can't wait for the multi GPU build for cluster vanitygening. Will it scale across systems on the same network like cluster knoppix does?

[mcorlett]

Can't wait for the multi GPU build for cluster vanitygening. Will it scale across systems on the same network like cluster knoppix does?

You can already do this — just fire up a new instance for every GPU.

[check_status]

Can't wait for the multi GPU build for cluster vanitygening. Will it scale across systems on the same network like cluster knoppix does?

You can already do this — just fire up a new instance for every GPU.

• How do I get oclvanitygen to use all of my GPUs?
  Support for using multiple GPUs from the same instance will not be very difficult to do, and is planned for a future release.

@samr7 Would this be useful to vanitygen?

Distributed Hash Cracker: ACross-Platform GPU-Accelerated Password Recovery System Andrew Zonenberg Rensselaer Polytechnic Institute.

http://www.cs.rpi.edu/~zonena/papers/cracker.pdf

[mcorlett]

Can't wait for the multi GPU build for cluster vanitygening. Will it scale across systems on the same network like cluster knoppix does?

You can already do this — just fire up a new instance for every GPU.

• How do I get oclvanitygen to use all of my GPUs?
  Support for using multiple GPUs from the same instance will not be very difficult to do, and is planned for a future release.

The way I see it, there is no performance benefit in supporting multiple GPU's from the same instance. It's just aesthetic.

[check_status]

The way I see it, there is no performance benefit in supporting multiple GPU's from the same instance. It's just aesthetic.

Reducing the number of keystrokes to perform a given task is not a performance benefit?
Wouldn't there be fewer processes, therefore a reduced memory footprint?

[samr7]

@samr7 Would this be useful to vanitygen?

Distributed Hash Cracker: ACross-Platform GPU-Accelerated Password Recovery System Andrew Zonenberg Rensselaer Polytechnic Institute.

http://www.cs.rpi.edu/~zonena/papers/cracker.pdf

Interesting paper, you must do a lot of reading on this stuff!

The way these guys did it would be the best way to do it if we wanted to do an exhaustive search of the key space.  However, for bitcoin addresses, each feasible pattern has a ridiculously large number of matching keys.  Even searching for a complete address will have, on average, 2^96 matching keys.  So, there's almost no point in doing an exhaustive search.

The way I see it, there is no performance benefit in supporting multiple GPU's from the same instance. It's just aesthetic.

That is the idea, it is mostly aesthetic.  Instead of having to run oclvanitygen once per GPU, you'll be able to run it once per system, and tell it to use all of your GPUs.

Organized clustering across systems will be more complicated.  One way to do this, in the near future, that follows the model of bitcoin mining, will be:
- Run oclvanityminer on each system in the cluster.
- Run a private bounty server, or the equivalent of a mining proxy, and configure your oclvanityminers to connect to it.

There isn't a private bounty server, at least not yet, but all it would need to do is to support the vanity pool protocol.

[mcorlett]

The way I see it, there is no performance benefit in supporting multiple GPU's from the same instance. It's just aesthetic.

Reducing the number of keystrokes to perform a given task is not a performance benefit?
Wouldn't there be fewer processes, therefore a reduced memory footprint?

I'm not arguing semantics over this. There is no significant performance benefit in supporting multiple GPU's from the same instance.

[ErebusBat]

First: no apology necessary.
Second: WOOHOO!!!

I am in the Mkeys/s now!  

I'm glad it works for you!

If you put the #define INLINE inline back the way it was, does it still build?
EDIT: be sure to do make clean first, before rebuilding with make all

Also, what GPU do you have, and what key rate are you seeing?

It does indeed work without the inline change, must be some code changes since the last time I tried.

Here is my speed output, from my ATI Radeon HD 6750M on my MacBookPro8,3:

Code:

$ ./oclvanitygen -p ADM -d 1 -k 1ErebusBat                                                                                         130 ↵ 
WARNING: Built with OpenSSL 0.9.8r 8 Feb 2011
WARNING: Use OpenSSL 1.0.0d+ for best performance
Difficulty: 2938077882634386
[2.00 Mkey/s][total 69206016][Prob 0.0%][50% in 32.3y]

[samr7]

New version 0.18 released, with all the changes described in the earlier post.

• Split key address generation, ability to use with a bounty pool.
  Support for additive public keys has been implemented, which will be specified via a new command line argument.  Also present is a new miner program that works with ThePiachu's vanity pool.  This feature is available in the current github trunk, and will be in the next release.
  Thanks go to BurtW and others who made concise posts on this topic.
• Ability to generate P2SH (type-3) addresses
  Luke-jr contributed a patch to generate private keys that, when added to a single address multi-signature script, hash to a desired type-3 vanity address.  This is a very convenient way of doing it, because it works with the addmultisigaddress command in the unmodified Satoshi client.  This feature will be in the next release.
  As several folks have pointed out, by placing a nonce of some sort into the script, it is possible to generate type-3 addresses much more efficiently and without any elliptic curve operations.  However, getting a specific bitcoin client to support this is the main obstacle.
• Win32 binaries now hosted on GitHub

It does indeed work without the inline change, must be some code changes since the last time I tried.

Here is my speed output, from my ATI Radeon HD 6750M on my MacBookPro8,3:

Good, the function inlining will not be changed.

Hopefully the speed can be improved, too.  A back of a napkin calculation suggests 3-7 Mkey/s for your GPU.

[flatfly]

That latest version crashes for me (win XP, 32-bit)
right after displaying difficulty. V0.17 still working just fine.

C:\Documents and Settings\v18>vanitygen.exe 1ka
Difficulty: 78508

[stevegee58]

I just dowloaded and ran 0.18 and it ran fine.  Same specs: WinXP 32 bit.

[samr7]

That latest version crashes for me (win XP, 32-bit)
right after displaying difficulty. V0.17 still working just fine.

C:\Documents and Settings\firace\v18>vanitygen.exe 1ka
Difficulty: 78508

Sorry about that.  The vanitygen code changes weren't substantial, but the new binaries were built in a new build environment with newer versions of the dependent libraries, including a new OpenSSL and a new pthreads library, so a lot has changed, but I'm still surprised that it's crashing.

What sort of an error message do you get?  Are you running it on a VM, or bare metal?  What CPU?

My XP 32-bit SP2 and SP3 VMs couldn't reproduce this problem, and I'm currently trying some other environments to find one that is able to reproduce this problem.  If this fails and this is an access violation type of crash, you might be asked to collect a user-mode dump.

[bitcats]

v o.18 crashes
Vista 32, dual core

[samr7]

I figured it out.  Sorry folks.

Version 0.19 is out now.  Hope this one lasts more than nine hours.

[stevegee58]

Wow I wonder why mine worked.

[bitcats]

I figured it out.  Sorry folks.

Version 0.19 is out now.  Hope this one lasts more than nine hours.

where can i download it?

[etsoberano]

https://github.com/downloads/samr7/vanitygen/vanitygen-0.19-win.zip

[samr7]

where can i download it?

There, the front page is fixed.  Binaries are here.

[bitcats]

Thanks, it works now.