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

[bigbeninlondon]

Alright, so I'm trying to figure this shit out.

Here's the parameters I'm using:

oclvanitygen -k -t 256 -d 0 -f c:\temp\pattern.txt -o c:\temp\match.txt -s c:\temp\random.txt

-k: keep searching
-t 256: 256 threads; seems to net me the most MKeys/Sec
-d 0: my GPU
-f c:\temp\pattern.txt: A list of 7 patterns I'd like
-o c:\temp\match.txt: output any matches here
-s c:\temp\random.txt: seed with text from random.org

I've been running for days; patterns are prefixes between 4-10 characters long and I've been unable to find anything.  Here's an output of it running now:



From what I've read 30Mkeys/Sec is pretty good, but how come I haven't found anything for like 4 or 5 days?  I've got 6 patterns that are 1XXXX and  one that is 1XXXXXXXX.  

One additional question, which letters/numbers are prohibited?  I heard somewhere 1's and l's and I's are not allowed?  

[1714152268]

1714152268

[1714152268]

1714152268

[Ente]

Those "CPU Hash / GPU Hash" combinations mean you found an adress, but the calculation was corrupt. This is pretty common at the moment. Some people got a working system on linux with a distinct version of catalyst. Others speculate it's actual hardware problems with the GPU. Noone is really sure what's going on, I believe.

Prohibited in base58 for Bitcoin: and 1l - thats the only two pairs.  o and L are allowed though.

Ente

[bigbeninlondon]

Those "CPU Hash / GPU Hash" combinations mean you found an adress, but the calculation was corrupt. This is pretty common at the moment. Some people got a working system on linux with a distinct version of catalyst. Others speculate it's actual hardware problems with the GPU. Noone is really sure what's going on, I believe.

Prohibited in base58 for Bitcoin: and 1l - thats the only two pairs.  o and L are allowed though.

Ente

Ok.  Here's my AMD driver package, if this helps:



I can mine btc on it just fine.

Is there a known working version of catalyst I can roll back to?

[Ente]

I am as lost here as you are, I didn't get it to work on the Windows machine I have a remote login on.
Maybe someone else can chime in here?

Ente

[els]

Those "CPU Hash / GPU Hash" combinations mean you found an adress, but the calculation was corrupt. This is pretty common at the moment. Some people got a working system on linux with a distinct version of catalyst. Others speculate it's actual hardware problems with the GPU. Noone is really sure what's going on, I believe.
...
Ente

----
this is the condition that required me to use the source code modification that i mentioned recently.  (which i found much earlier in this discussion group somewhere).  i swapped hardware and tried many drivers to rule things out, but the code was the issue.

if using -S works (it'll be slow) then the below may resolve the issue.

commenting the following 2 lines out of oclengine.c and rebuilding removes problematic optimizations which cause the corruption w/o slowing things down (i am getting 26mh/s on 7970):

                      if (dvn && strstr(dvn, "cl_amd_media_ops"))
                              quirks |= VG_OCL_AMD_BFI_INT;

haven't tried this with newer drivers (i have no need for).  using linux.

--els

[ratty]

I get that EXACT problem, and it is because the program won't work with modern video cards, we're just waiting for someone to fix it. If it worked, it also prints the private and public key to the console. It doesn't matter what video driver you're using, I tried Catalyst 12 but it won't work with my card. I think other people said it did for them, you can just read earlier in the thread for that info.

[Ente]

if using -S works (it'll be slow) then the below may resolve the issue.

There's at least one combination where -S does not resolve this..
So I won't even start recompiling this for windows.
*sigh*

Ente

[els]

if using -S works (it'll be slow) then the below may resolve the issue.

There's at least one combination where -S does not resolve this..
So I won't even start recompiling this for windows.
*sigh*

Ente

i wasn't paying close attention as i was researching trying to solve for linux, but i seem to recall that that case was with the post-12.10 drivers...i'll hazard a guess that with 12.10, -S works and the code fix might too.  i'll also guess that if -S doesn't work, the issues are bigger.  but you probably know more about this than i.

[aamarket]

confirmed to work here :

https://github.com/samr7/vanitygen/issues/19#issuecomment-22475393

[Eternity]

Thats truly marvelous

[ratty]

Just so its clearly linked in this thread, this guy made a fork of it and made it faster, and more compatible with modern AMD cards:
https://bitcointalk.org/index.php?topic=301068.0
Thanks to a lot of help from the developer, I got it working by using OpenCL from Catalyst 12.10, and I can still use 13.9 for everything else. It even does compressed keys.

[FanDjangoBTC]

I can confirm 13.10beta and 13.9 works for my HD7950 (using the lifeboat fork mentioned above) by doing the following:

Install the 13.9 driver normally, use express install if you like.

Download the 12.4 driver. Start the install and let the install extract the files to your AMD\Support folder. Don't let the install continue after that, but leave the installer window open. Later, you can just cancel the install process. But for now, you need the extracted files.

Delete amdocl*.*, OpenCL.dll and the other files from Windows\system32 as described in the README of the new vanitygen program. Before deleting them, take a note of their file dates, so that after the next step you can be confident to have gotten an EARLIER SDK from 12.4. This effectively removes the base files of the SDK.

Then go into the AMD\Support\...12.4...\packages\apps folder and run the opencl.msi installer ONLY. This effectively installs the SDK again, but this time it will be the OLDER one from 12.4. After this, you can cancel the open install window of 12.4

Confirm the earlier file dates of the files that should now be there. I just checked the amdocl... and Opencl.dll stuff.

Reboot.

Delete the oclvanitygen oclbin files. This is needed or else a previous compile will be used unless you are on a fresh install of vanitygen.

Run oclvanitygen and take note of the output (I use -v): Version: OpenCL 1.2 AMD-APP (923.1)

This version would be much higher in the vanilla 13.9 driver.

Try it!

Worked nicely for me and was quicker than doing all the downgrading, booting and upgrading etc. Also really no need for driver-sweeper on the downgrade path.

[george51]

Sorry if this has been answered... but the thread is long and after searching I can't find the answer

When trying to run oclvanityminer on windows 8 I get:


Get work request failed: Problem with the SSL CA cert (path? access rights?)


Using: oclvanityminer.exe -u https://vanitypool.appspot.com -a 1NkxtjPeWHvjfk7joTAXhJFEBn8kevM661


Also doesn't work for vanitypooltest.appspot.com

Any help would be appreciated

[Eternity]

Great to hear about this

[deepceleron]

Prohibited in base58 for Bitcoin: and 1l - thats the only two pairs.  o and L are allowed though.

O + 0 is now

[george51]

Sorry if this has been answered... but the thread is long and after searching I can't find the answer

When trying to run oclvanityminer on windows 8 I get:


Get work request failed: Problem with the SSL CA cert (path? access rights?)


Using: oclvanityminer.exe -u https://vanitypool.appspot.com -a 1NkxtjPeWHvjfk7joTAXhJFEBn8kevM661


Also doesn't work for vanitypooltest.appspot.com

Any help would be appreciated

Further to this I have the calc_addrs.cl in the same folder as oclvanityminer and it still says it can't find kernel. No file/directory.

Any suggestions for this either?

[Dabs]

Can someone tell me their video cards and their speeds for those cards? There isn't an updated list.

[bernard75]

Can someone tell me their video cards and their speeds for those cards? There isn't an updated list.

Toms Hardware has pretty updated GPGPU benchmarks:
http://www.tomshardware.com/reviews/bitcoin-mining-make-money,3514-4.html

[aamarket]

... hmmm ... new meaning for 'updated'  - couple years old cards and stuff

I found my july2013 notes for BTC mining:
7850 around 330 Mhash/sec
7950 around 627 Mhash/sec
long time average

regarding oclvanitygen - no notes found, but I would say around 25 M keys per sec
with 7950

[Dabs]

I'm looking for bitcoin address generation, not mining. No point doing any GPU mining when you can get a ASIC powered USB miner. (I have a group buy, see sig.)