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

[phantastisch]

Does anyone got an idea how a premine - secure key exchange could work? As if someone premines an adress with an public key, gets the private key part , then gives the secret to somebody who decrypts the public key obtains the other private key part and combines both parts for the private key.
Yeah , i know that in this scenario the miner has everything to create the private key for himself , but thats the tricky part.

[1713508326]

1713508326

[1713508326]

1713508326

[1713508326]

1713508326

[1713508326]

1713508326

[The00Dustin]

Does anyone got an idea how a premine - secure key exchange could work? As if someone premines an adress with an public key, gets the private key part , then gives the secret to somebody who decrypts the public key obtains the other private key part and combines both parts for the private key.
Yeah , i know that in this scenario the miner has everything to create the private key for himself , but thats the tricky part.

https://bitcointalk.org/index.php?topic=84569.0

[phantastisch]

Does anyone got an idea how a premine - secure key exchange could work? As if someone premines an adress with an public key, gets the private key part , then gives the secret to somebody who decrypts the public key obtains the other private key part and combines both parts for the private key.
Yeah , i know that in this scenario the miner has everything to create the private key for himself , but thats the tricky part.

https://bitcointalk.org/index.php?topic=84569.0

If i understand this correct, then i have to obtain the public key before i mine , but i want to mine first then exchange any keys.

[The00Dustin]

If i understand this correct, then i have to obtain the public key before i mine , but i want to mine first then exchange any keys.

IOW, you want to vanity-address squat, or more specifically, firstbits squat (because another vanity address with the same effect could be generated vs buying yours).  Unfortunately, the last sentence in your original question speaks volumes.  Perhaps there is someway to overcome this and have some sort of proof that the key hasn't been created, but that seems unlikely.  On the other hand, I am operating under the assumption that human trust is the only thing keeping the glod bars / coins with private keys on a sealed QR code fom being emptied by the creator.  In the case that I am wrong about that, your answer may well exist in their process.

[deepceleron]

Does anyone got an idea how a premine - secure key exchange could work? As if someone premines an adress with an public key, gets the private key part , then gives the secret to somebody who decrypts the public key obtains the other private key part and combines both parts for the private key.
Yeah , i know that in this scenario the miner has everything to create the private key for himself , but thats the tricky part.

https://bitcointalk.org/index.php?topic=84569.0

If i understand this correct, then i have to obtain the public key before i mine , but i want to mine first then exchange any keys.

The public key is essentially the Bitcoin address.
The private key is the un-seen complement to the address that allows spending coins.

Vanitygen generates a random public-private pair, and then sees if it has the vanity phrase in it. If not, it discards the result and tries again. About a million times a second.

It is impossible to find the private key for a Bitcoin address if you don't have it. That would allow spending that address's funds.

For details specific to vanity key pooling, please see the linked thread. Also https://vanitypool.appspot.com/faq

[samr7]

Just realized I'm actually able to post I been waiting to leave my Newbie status on here for awhile (this is my real first post).  I been going crazy here I can't figure this out I been waiting to post this question for a month.  I have the same problem as this post quoted.  I get outputs like this when I use opencl.

Difficulty: 1353
Match idx: 0
CPU hash: a4900f3de57df3ea62654b295b1a92048ddc994d
GPU hash: 3d0f90a4eaf37de5294b656204921a5b4d99dc8d
Found delta: 1919 Start delta: 1
[151.19 Kkey/s][total 2048][Prob 78.0%][80% in 0.0s]

I think its the real output because the first time I tried it I got a output like that after 5 hours.  I didn't think to test it before hand it took 5 hours just to get CPU hash - GPU hash output like this.  If I pick a easier address I get outputs like this scrolling down.  If I use a CPU generator I get a private key output the correct way it is only happening with opencl.

I tried oclvanitygen today, and discovered that it produces output like the following, instead of private keys.

Code:

Match idx: 0
CPU hash: 93b30d0ad99f8133a0bc3c4793a27dbad5a0961f
GPU hash: 0a0db39333819fd9473cbca0ba7da2931f96a0d5
Found delta: 1919 Start delta: 1

Am I doing it wrong?

What hardware/OS/drivers are you guys using?

When oclvanitygen does this, it means:

• The OpenCL code reported having found a matching address
• The address was re-calculated using the CPU
• The address calculated by the CPU did not match what was calculated by the GPU, or any patterns in the pattern list

Unfortunately, I have a small variety of hardware to test with, and don't have a platform that can reproduce this type of problem with current code.

Some folks in the past have reported this type of problem using AMD hardware with Catalyst drivers.  Some of them had reported that the problem went away after upgrading to Catalyst 11.11.  Certain older versions of NVIDIA drivers will cause failures too, but tend to cause oclvanitygen to crash, rather than hash mismatches like we're seeing here.

One way to detect this type of problem quickly is to use OpenCL verification mode (-V).  This causes oclvanitygen to run the normal address generation procedure, but to verify results at every step of the way.  It runs much slower, but if there is misbehavior on the OpenCL side, it will find it quickly, and will isolate the kernel that is producing incorrect results.

I think I had that same issue trying to gpu-mine with self-compiled code on linux.  I just gave up and use Windows.

Interesting, was this with AMD hardware?  Do you remember which driver you were using on Linux?

[The00Dustin]

I think I had that same issue trying to gpu-mine with self-compiled code on linux.  I just gave up and use Windows.

Interesting, was this with AMD hardware?  Do you remember which driver you were using on Linux?

Radeon 5830
Fedora 15
xorg-x11-drv-ati-6.14.1-2.20110525gitfe5c42f51.fc15.x86_64

[samr7]

Radeon 5830
Fedora 15
xorg-x11-drv-ati-6.14.1-2.20110525gitfe5c42f51.fc15.x86_64

Is this the open-source driver?  How well does it work with other OpenCL applications?

I've never used it before, and am amazed that it appears to be advanced enough to support OpenCL.

Edit: According to the Gallium3D wiki, OpenCL on R800/Radeon 5xxx is "WIP".  Still amazing though.

[The00Dustin]

Radeon 5830
Fedora 15
xorg-x11-drv-ati-6.14.1-2.20110525gitfe5c42f51.fc15.x86_64

Is this the open-source driver?  How well does it work with other OpenCL applications?

I've never used it before, and am amazed that it appears to be advanced enough to support OpenCL.

Edit: According to the Gallium3D wiki, OpenCL on R800/Radeon 5xxx is "WIP".  Still amazing though.

I honestly don't remember if it is open-source or not, but I installed it via yum as opposed to downloading it from AMD.  I may have had to install non-free repositories to do that.  I am using SDK2.1 downloaded from AMD to use this driver with cgminer and have been for quite some time.  I don't remember if I had to link to SDK to compile oclvanitygen, as it was some time ago, so perhaps I did and the SDK in use / used for compiling is the problem.

[Vanity]

Just tried the Windows version (both 32/64 bits), and they just blew away anything I get under OSX (10.6., so I have few questions:

For the reference, I'm running 2.0 GHz Core 2 Duo in early 2009 macbook.
Just running vanitygen (in OSX - uses one core), I get like ~60 KKeys/s, so even four letter word takes a minute+.
Running oclvanitygen with CPU (runs on both cores) I get 90 KKeys/s - trying to run with GPU freezes the system.

First I was under the impression that these were quite okay results for such old laptop, but then I ran the Windows (7 64bit) versions:
vanitygen32: 160 KKeys/s
vanitygen64: 200 KKeys/s

Only tried oclvanitygen for GPU, but didn't have that much more out of it, 230 KKeys/s maybe.

So why such a great difference?
How do I run vanitygen in OSX in 64 bit mode? I need to recompile it I guess?
Also I get the following error when running:
WARNING: Built with OpenSSL 0.9.8l 5 Nov 2009
WARNING: Use OpenSSL 1.0.0d+ for best performance

But the version of OpenSSL I have is OpenSSL 1.0.1c 10 May 2012. Did I overlook something when compiling it the first time?

[stevegee58]

What GPU devices do you have?  What's your command line?

[Vanity]

I have GF 9400m.

I use just "./vanitygen 1Name" without any bigger parameters (besides the oclvanitygen required -D). Did the same in Windows also.

[stevegee58]

I meant for oclvanitygen.  For instance I use "oclvanitygen -d0 1abcdef" to use my 6770 GPU.  I get around 12 Mkeys/sec this way.

[UNOE]

What hardware/OS/drivers are you guys using?

I have :
Intel i7 3930K
Windows 7 x64 SP1
AMD 7970

I have tried 12.6 12.7 and 12.8 drivers.

Still have the problem.

[Vanity]

I meant for oclvanitygen.  For instance I use "oclvanitygen -d0 1abcdef" to use my 6770 GPU.  I get around 12 Mkeys/sec this way.

Oh, sorry. I use the device parameter to point to GPU in Windows, in OSX 10.6 it either froze the system completely or gave up an error message. I've just installed 10.8 as my previous installation got completely messed up for some reason, so I've yet to try it under this one.

[ErebusBat]

I meant for oclvanitygen.  For instance I use "oclvanitygen -d0 1abcdef" to use my 6770 GPU.  I get around 12 Mkeys/sec this way.

Oh, sorry. I use the device parameter to point to GPU in Windows, in OSX 10.6 it either froze the system completely or gave up an error message. I've just installed 10.8 as my previous installation got completely messed up for some reason, so I've yet to try it under this one.

Just installed Mt. Lion (10. today.... oclvanitygen does indeed run

[Vanity]

Just installed Mt. Lion (10. today.... oclvanitygen does indeed run

Yup, indeed it does - just ran it. Although I do get slightly better results (188KK/s vs. 170KK/s) with just CPU vs. GPU. But it's still bit under what I get in Windows, but that was in the 64 bit vanitykeygen - so I still want to know, how it's possible to run OSX version in 64bit mode?

[ErebusBat]

Just installed Mt. Lion (10. today.... oclvanitygen does indeed run

Yup, indeed it does - just ran it. Although I do get slightly better results (188KK/s vs. 170KK/s) with just CPU vs. GPU. But it's still bit under what I get in Windows, but that was in the 64 bit vanitykeygen - so I still want to know, how it's possible to run OSX version in 64bit mode?

It already does....  In fact I don't think Mt. Lion even comes with a 32bit kernel, but I could be wrong.

What GPU do you have?  I get ~4Mkey/sec with my GPU.

[Vanity]

It already does....  In fact I don't think Mt. Lion even comes with a 32bit kernel, but I could be wrong.

What GPU do you have?  I get ~4Mkey/sec with my GPU.

That's my impression also, but it's still quite a lot behind Windows 7 x64 in terms of performance - although major improvement over 10.6.

I have GeForce 9400m with 256 MB of VRAM, so not exactly a beast of a GPU 

[ErebusBat]

It already does....  In fact I don't think Mt. Lion even comes with a 32bit kernel, but I could be wrong.

What GPU do you have?  I get ~4Mkey/sec with my GPU.

That's my impression also, but it's still quite a lot behind Windows 7 x64 in terms of performance - although major improvement over 10.6.

I have GeForce 9400m with 256 MB of VRAM, so not exactly a beast of a GPU 

Ah ya, nvidia chips are not the best for mining.