Topic: Vanitygen: Vanity bitcoin address generator/miner [v0.22] - page 108. (Read 1153678 times)

I have a hack of an implementation for cpu only— I don't have any gpus anymore, so doing more than that wasn't interesting to me. https://people.xiph.org/~greg/compressed.keys.patch

Yeah it would make life much more easier. How hard is to implement that ?
I did not saw any devs commenting on this thread in a long time.

Still no compressed keys?  I'm kinda surprised considering how much faster it makes the searching.

If u encrypted it with password u can use that to decrypt , if u generated part keys u will need to put them together here: https://www.bitaddress.org/

That will allow you to add keys to the wallet, but you still need to "decrypt" the encrypted output of vanitygen somehow....

Here is how to do it :

If you have an encrypted wallet (recommended), you need to unlock it temporarily before importing private keys. The RPC command for unlocking an encrypted wallet is walletpassphrase . Typing this directly in a bash terminal will leave your wallet passphrase directly in the bash history but there are a couple of techniques you can use to avoid this. Simply add a space before the command:

(space)bitcoind walletpassphrase yourpassphrase 120
Another alternative is to use a bash variable:

read x
(input your passphrase)
bitcoind walletpassphrase "$x" 120   # Do not set the timeout too long or too short.

Not sure about bitcoind, but i think u need to decrypt it first. Than to import private key.

Correct.  Bitcoind just gave me an error when I tried to do it.  I assumed it would prompt for the passphrase.

How to import it into wallet ?

How do you import an exported, encrypted private key from vanitygen?

It works just fine on my w8.1 . I guess its problem with his graphic driver or his gpu.

I can confirm that output means you have a wrong driver version. If the newer driver versions are all that work on Win 8/8.1 then I guess you'll have to find yourself another OS.

That is rly weird. We need somebody from devs of vanitygen to help u out.

what you mean?
I have tried 12.8 and 12.10 (on "win 8.1 update 1") and could not get any  software to recognize ocl devices.... (cgminer 3.7.2, oclvanitygen) (even these drivers were working good with cgminer 3.7.2 on "win 8")
I have tried 13.12 14.4 14.6beta drivers - ocl devices are recognized under win 8.1 update 1 and working fine with cgminer 3.7.2 for example. But even oclvanitygen recognizes ocl devices - it won`t produce any keys. I`m getting following errors:

[25.60 Mkey/s][total 113246208]                                                Match idx: 0
CPU hash: 62877214296428cff20ae302409afcabd66b05f1
GPU hash: 86c80e8df57566f7401c78c932b0862b13269b7e
Found delta: 6291453 Start delta: 1
Match idx: 0
CPU hash: a7154bbe3446797050205a116adc2a4b0e05Match idx: 0
CPU hash: eaf026c81206d7baf5a8ee137fa62d7b1efa1359
e11b
GPU hash: 2b5e766241541bf70a8ccc2489acMatch idx: 0
CPU hash: d73417646c48df0a688e6eca77b02291e3041f88
GPU hash: 9da6ec6c7c488c63ce5cfea3a1c4ec55f9734956
e87fc51bdf0c
Found delta: 6290172 Start delta: 1


As wiki states:

For AMD Catalyst 13.1+ you need to run the AMD APP SDK Runtime from Catalyst 12.10 in order to get this program to work. (So all your Catalyst drivers would be brand new except for the SDK Runtime.) This is discussed on GitHub. For Linux, use AMD APP SDK 2.7.
(https://en.bitcoin.it/wiki/Vanitygen)

there is incompatability of new drivers and oclvanitygen

So I also tried to install 2.7 and 2.8 amd app sdk on 12.10 13.12 14.4 drivers - with no success.

Basically what I`m asking - is there any solution to use oclvanitygen on win 8.1 update 1, or whatever latest patched and updated windows 8.1 is named.

8.1 update 1 - 12.8 and 12.10 wont work (

I had the same problem than i updated to 8.1 update 1 . And it was working.

can`t get 12.8 and 12.10 drivers to work on win 8.1 at all - no ocl devices detected...
any workaround?
13.1 and 13.6 - devices detected, but won`t work with ocl

Thank you.

This is correct just create a pattern list of all the numbers it's much faster.

If you only want a specific address like 18888888 or smtgh. you shouldn't use -r because it is extremely slow compared to standard prefixes.

Just use 18888888 17777777 ect then.