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

++ very cool

Tnx i needed that one to . U are the man.

No you don't need to.
This subject has been discussed in this topic. U have to use option "X" with the code of the coin.

Something like this: vanitygen -X 48 -o addys.txt LTCmis
The same for OCLVanitygen...... Be aware to state as first and second letter according with coin specs

For LTC: 48
FTC: 14
NVC: 8
ANC: 23
PTC: 47
CNC: 28
DGC:30
NMC: 52
PPC:55
YAC: 77
BQC: 85
IXC: 138
DOGE: 30

oh one other Q, is it possible to use the generator for altcoin addresses? I assume yes, but in that case I assume one has to modify the source code?

same problem - how do i fix this?

Does anyone have any good tips or suggestions on how to tweak the oclvanitygen settings so that my computer will remain responsive while running the program?  I'd like to dial it in to where I can get good speeds while still being able to do other activities while it is running. Thanks.

Edit: Played around and did some tweaking.

No tweaks, Default-
Grid size: 3584x2048
Modular inverse: 7168 threads, 1024 ops each
Keyrate: 22.00 Mkey/s
Observations:  Very laggy, lots of input delay, and slow responsiveness

1st Tweak, More Speed-
Grid size: 2048x2048
Modular inverse: 4096 threads, 1024 ops each
Keyrate: 22.50 Mkey/s
Observations:  Slight lag, small input delay, and best of all higher keyrate, yay!

2nd Tweak More Responsiveness-
Grid size: 1024x1024
Modular inverse: 4096 threads, 256 ops each
Keyrate: 21.20 Mkey/s
Observations: Very little lag/input delays (almost none), and only a small decrease in keyrate, success!

Note: I did try a grid size of 2048x1024 as well as 1024x2048.  They were both about 22 Mkey/s and both had about the same responsiveness which was between that of the 1st and 2nd tweak as you could have guessed.  So it doesn't seem to matter if you use square grids, it is only the size that matters in my experience.

System info for anyone wondering:
I5-3570k at 4.4 GHz
GTX 660TI by Asus
Windows 8.0 64 bit
4x4GB of 1600 DDR3 ram

Anyhow I think these tweaks were quite successful and I'm very happy with them.  If anyone still has any tips or suggestions maybe I can improve them some more.  Thanks.

I just checked that would take me forever . U would need to pay for it at least 0.1 btc. Did u tried some pool ? 

I used a work PC @ 25 Mkey/s for over 3 months to try and find 1tri11ium with case sensitivity off and no luck.

Heheh... My username is just perfect. I even got 1Micro... addy in just few hours
I also sold some addyes but urs username is to long even for me

Damn you and your tiny-length username.

This is great i used it to make addy from my sig .

Hi guys, I think I need some advice to compile and build the vanitygen against openssl 1.0+ on osx Mavericks 10.9.1

I 'make' it after upgrade openssl but it says:


if I then check the openssl version i got:


so i symlinked the new openssl to the include and retried the 'make'
this is the output:


I think i have to modify the Makefile to adapt it to 10.9.1 but i'm not so skilled to do it by myself,

can anyone help?

Thanks

jaap

Compressed keys has been discussed before, but I wonder if anyone considered it for potential speedup? So every time a new EC point is calculated, you produce SHA256+RIPEMD for both the uncompressed coordinates (04 "x" "y") and the compressed ones (with leading byte 02 or 03), this basically doubles the chances to match the required prefix without adding too much overhead (just an extra hash).

To take this further, one might as well also hash the inverse point on the curve (x, -y). As long as one can hash faster than EC_POINT_add I think it is worth it?

Pretty much, yeah.

So, I use importprivkey to get the private key into bitcoind. Will it then automatically detect payments to my vanity address? No need to get bitcoind to recognize the vanity address?

I've updated https://github.com/WyseNynja/vanitygen with 2 bug fixes reported on GitHub.

If you already have vanitygen installed from my OSX homebrew tap:


If you don't:

Hi, I carefully studied a regex to search for, but it seems vanitygen can't accept the character ^ in the regex in order to force the following group of characters to be the beginning of the address.

vanitygen simply ignore the character ^, while it correctly take as input the character $ to force the group to be at the end of the line. each address it returns, it writes the pattern searched without the ^ character.

basically I'd want to search for an address with a custom prefix and suffix. any help is appreciated.

edit: ok found the solution, had to enclose the searched pattern between ""

No.

I have an NVIDIA GeForce GTX 560. With 336 CUDA Cores and 1780 MHz Shader (890 MHz Core, 1000 MHz Memory), I get ~14.1 Mkey/s. This suggests a ratio of 23.6 for this card. That is, Key/s = (CUDA Cores) x (Shader MHz) x 23.6

Because the C drive system crashes, lost the wallet address, asking for help, how can I get back to the lost wallet?I'm a Chinese and my English is poor.