hes inactive since a long time

I think he may return; last time he came back with a new version of vanitygen after 11 months of inactivity.

the CPU is too bad for it

How'd you figure out the functions that were causing it to crash?

Forgive me if this is a stupid post, but is vanitygen safe?

That is to say, are the keys that it generates always 100% working keys that can be imported into a Bitcoin client? Is there a chance of creating a "bad private key" from vanitygen, such that one cannot, for some reason, import said key into a wallet?

Are the keys that are generated with vanitygen random enough, or at least as random as addresses generated with the standard Bitcoin client?

Also, I am assuming that smarter folks than I have made sure that this little program doesn't create keys and then send them all back to the vanitygen creator or something else likewise nefarious, right?

Go here, https://www.bitaddress.org , and select the "wallet details" option. Then put there the private key created by vanitygen (you can download the html-js code and create your own page, if you don't trust) and check it


The second option (AFAIK from my last contact with the program)


The code is open for your revision.

Hello,

I've created workaround for buggy 13.x catalyst driver, needs some testing though (especially the miner and win32).

For the impatient:
linux:

In case you get odd output like:

It means the compiler backend is still outputting broken code (although it compiles). To fix that try:


Windows users can try applying the dll override script in the directory of official vanitygen binaries [edit: link with resulting archive removed due security concerns].

The gory details:

https://github.com/wyuzhe/vanitygen/commit/6f7fd04adc609b19520cdab4cc12d648e364adbe

In short, ATI LLVM-IR backend miscompiles stuff like:


The boolean result of (a < b) is expressed as byte (u8 in crash report), but VLIW architectures know no such thing. Workaround is using artificially complex expressions which cannot be readily expressed as setcc in llvm ir (but will be optimized away during R600 lowering anyway).

Actually, the vanitygen binaries are verbatim from official zip, plus just opencl dlls stitched in the archive. Naturally you should test on untrusted machine, as every binary code posted on forums.

For paranoid users, i'd recommend to use the linux version.

win32 is just downgrade of opencl compiler - no further changes made at this point.

I'll provide script to build resulting archive to avoid further implications.

I'n the meantime, I'd like to offer you 1BTC for factual evidence aforementioned archive is "virused up" - since it was created on a linux workstation, it is higly unlikely but I'd prefer to be on the safe side - I'm certainly no expert in that area. I've removed the link from my post, in case your accusation is proven to be true.