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

[ExploitAgency]

Try my samr7(lifeboat_) fork
I added support for over 50 altcoins too
https://github.com/exploitagency/vanitygen-plus

[1714769122]

1714769122

[1714769122]

1714769122

[Timelord2067]

Try my samr7(lifeboat_) fork
I added support for over 50 altcoins too
https://github.com/exploitagency/vanitygen-plus

Is that the OgNasty LifeBoat version I've been using for over a year, or is this a different lifeboat version?


any relation?

Code:

Name: 	samr7 u=20336 http://archive.is/PUQQy
Posts: 	163
Activity: 	140
Position: 	Full Member
Date Registered: 	09 June 2011, 08:59:48
Last Active: 	25 October 2012, 01:59:55

[Jude Austin]

Has anyone compiled oclvanitygen on Windows?

I can get it to compile but when I try to run it errors out:

Code:

D:\Downloads\vanitygen-master>oclvanitygen 1Jude
Difficulty: 4476342
      0 [main] oclvanitygen 16316 cygwin_exception::open_stackdumpfile: Dumping stack trace to oclvanitygen.exe.stackdump

Stackdump:

Code:

Exception: STATUS_ACCESS_VIOLATION at eip=200428D8
eax=00000000 ebx=200426A8 ecx=20042714 edx=00000000 esi=6107CE80 edi=00000000
ebp=0065CC48 esp=0065C8B8 program=D:\Downloads\vanitygen-master\oclvanitygen.exe, pid 16316, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame     Function  Args
0065CC48  200428D8 (00000002, 0065CC6C, 200280F0, 61007A6A)
0065CD18  61007ACF (00000000, 0065CD74, 61006B00, 00000000)
End of stack trace

I am almost certain it's because of the OpenCL implementation in Cygwin but I am not sure how to use an alternative.

Thanks,
Jude

[ExploitAgency]

Its a different version ( Im not lifeboat nor samr7 just his build was solid and this should be too )
https://github.com/exploitagency/vanitygen-plus
I forked it and made some changes add support for 70+ altcoins and manually merged pull requests defunct repos either added or ignored that i found important

easy ticker symbol flags

./oclvanitygen -C LBRY bTEST
oclvanitygen -C NMC Ntest
vanitygen -C LTC Ltest
etc...

if you do a kali linux build heres compile instructions


https://legacysecuritygroup.com/index.php/projects/recent/12-software/35-oclvanitygen-compiling-and-use

Try my samr7(lifeboat_) fork
I added support for over 50 altcoins too
https://github.com/exploitagency/vanitygen-plus

Is that the OgNasty LifeBoat version I've been using for over a year, or is this a different lifeboat version?


any relation?

Code:

Name: 	samr7 u=20336 http://archive.is/PUQQy
Posts: 	163
Activity: 	140
Position: 	Full Member
Date Registered: 	09 June 2011, 08:59:48
Last Active: 	25 October 2012, 01:59:55

[error08]

I recently transfered 11 inputs from a vanity addy, and it made me realize the transaction gets quite big, which requires higher fees. Using vanity addresses also adds to the already large number of unconfirmed transactions.

I just found out Lifeboat supports compressed keys, which is 15% faster (source: README in this zip) than regular keys! But it's specialized for AMD, and available for Windows only. So I can't use it.
The last version of vanitygen is 4 years old now. It would be very nice to see an update that includes compressed keys. Unfortunately I don't have the skills to chance the source myself. It might be a relatively small change to add compressed keys.

If generate a specific address make the transaction fees goes higher and add more time/user to unconfirmed transaction, then is it worth to do? As we should be fine with our random address right now as long as it works just like others and safely to transact through it. Maybe it will be cool to have your name at the address but consider the side effects of it. Well, I would like to see newest vanitygen than what left for 4 years.

[xhomerx10]

I recently transfered 11 inputs from a vanity addy, and it made me realize the transaction gets quite big, which requires higher fees. Using vanity addresses also adds to the already large number of unconfirmed transactions.

I just found out Lifeboat supports compressed keys, which is 15% faster (source: README in this zip) than regular keys! But it's specialized for AMD, and available for Windows only. So I can't use it.
The last version of vanitygen is 4 years old now. It would be very nice to see an update that includes compressed keys. Unfortunately I don't have the skills to chance the source myself. It might be a relatively small change to add compressed keys.

If generate a specific address make the transaction fees goes higher and add more time/user to unconfirmed transaction, then is it worth to do? As we should be fine with our random address right now as long as it works just like others and safely to transact through it. Maybe it will be cool to have your name at the address but consider the side effects of it. Well, I would like to see newest vanitygen than what left for 4 years.

 Vanity addresses do NOT contribute to higher fees.  In fact, there is absolutely no difference to the network when using a vanity address as it is just the same as any other Bitcoin address.  Don't spread FUD - especially when you don't even understand the concept!

[Chris!]

Could someone direct me to where exactly this lifeboat vanitygen is? Can I download it from github or am I missing something? Also could you link me to where it's explained what is does/if it's different/why it's better? Googling just keeps coming up with reddit post after reddit post but no real information for me... Sorry for the newb questions rofl.

http://lifeboat.com/oclvanitygen

 It will start the download right away.

Thank you very much!

I recently transfered 11 inputs from a vanity addy, and it made me realize the transaction gets quite big, which requires higher fees. Using vanity addresses also adds to the already large number of unconfirmed transactions.

I just found out Lifeboat supports compressed keys, which is 15% faster (source: README in this zip) than regular keys! But it's specialized for AMD, and available for Windows only. So I can't use it.
The last version of vanitygen is 4 years old now. It would be very nice to see an update that includes compressed keys. Unfortunately I don't have the skills to chance the source myself. It might be a relatively small change to add compressed keys.

If generate a specific address make the transaction fees goes higher and add more time/user to unconfirmed transaction, then is it worth to do? As we should be fine with our random address right now as long as it works just like others and safely to transact through it. Maybe it will be cool to have your name at the address but consider the side effects of it. Well, I would like to see newest vanitygen than what left for 4 years.

Thanks for stopping by. Stay longer next time to learn a little bit. Clearly generating vanity addresses has zero affect on transaction fees.

You signature spammers crack me up...

[LoyceV]

Clearly generating vanity addresses has zero affect on transaction fees.

I don't know if my question was unclear, I've changed my post a bit.

Example:
1 vanity input with 2 outputs: 257 bytes.
1 compressed input with 2 outputs: 225 bytes.

Doing the same with 11 inputs and 1 output gives a (relatively) larger difference, as inputs are larger than outputs.

Of course vanity addresses don't create larger transactions than "normal" addresses, that's not the point. The point is: compressed (input) addresses create smaller inputs, and if it would be possible to generate compressed vanity addresses, you could have the best of both worlds.

[Chris!]

Clearly generating vanity addresses has zero affect on transaction fees.

I don't know if my question was unclear, I've changed my post a bit.

1 vanity input with 2 outputs: 257 bytes.
1 compressed input with 2 outputs: 225 bytes.

Doing the same with 11 inputs and 1 output gives a (relatively) larger difference, as inputs are larger than outputs.

Of course vanity addresses don't create larger transactions than "normal" addresses, that's not the point. The point is: compressed (input) addresses create smaller transactions, and if it would be possible to generate compressed vanity addresses, you could have the best of both worlds.

Ahh ok that makes a hell of a lot more sense. It does seem like a very small issue though as that's not even a 1% increase in size. At the risk of sounding like a newb, are there other differences like this in other 'normal' bitcoin addresses? If I generate 2 random addresses and they each have the same number of inputs I always assumed they would both be the same size in bytes.

[LoyceV]

It does seem like a very small issue though as that's not even a 1% increase in size.

Your math is off: from 225 to 257 bytes is over 14% increase. The percentage is even larger with more inputs and less outputs, and (as far as I know) it's the reason compressed addresses were introduced. For this reason, most wallets now use compressed addresses.

are there other differences like this in other 'normal' bitcoin addresses?

I don't think so.

[ExploitAgency]

Hey will you guys test my fork on some altcoins?

I've got 70+ altcoins lists on my vanitygen fork.  Also working up a vm soon to compile some windows binaries

https://github.com/exploitagency/vanitygen-plus

Not trying to spam, it just seemed to go unnoticed earlier.  I suppose because everyone wants windows binaries?

[Timelord2067]

Hey will you guys test my fork on some altcoins?

I've got 70+ altcoins lists on my vanitygen fork.  Also working up a vm soon to compile some windows binaries

https://github.com/exploitagency/vanitygen-plus

Not trying to spam, it just seemed to go unnoticed earlier.  I suppose because everyone wants windows binaries?

Yes please (I did read the FM, but it wanted me to make my own)

[OgNasty]

It's not driver-specific issue, seems to be difference in OpenCL implementations and their behavior on your hardware.

To fix it:
1. Open "calc_addrs.cl" with text editor.
2. Go to line 180 and change __constant bignum bn_zero; to __constant bignum bn_zero = { 0 };
3. Happily use your oclvanitygen

P.S. : forgot to mention, run with -S option enabled, otherwise it will throw out hashing mismatches instead of privkeys.

This works great for AMD Radeon 400 series cards and if you use the Lifeboat version there is no need to enable the -S option.

[Jambo]

Hey, I'm not sure if this is allowed here, but I'll pay $25 if someone can compile me the lifeboat oclvanitygen64 with support for compressed BTC addresses. Only the lifeboat version spits out valid data on my computer (i7-6800k, GTX 1070, Win 7). I'm very busy at the moment and building for Windows always drives me crazy trying to find the correct libraries etc..

I'm paying way too high fees from my uncompressed address 1KEyVEndor3p6c3NL2UiVhscXPZKb3DfY1 and I want to keep a vanity address for my business.

[LoyceV]

I'll pay $25 if someone can compile me the lifeboat oclvanitygen64 with support for compressed BTC addresses.

Compressed is a standard option in lifeboat. From the README from https://lifeboat.com/oclvanitygen/ :

To create compressed keys use the "-F compressed" option as in
oclvanitygen -F compressed -d 0 1Life or
vanitygen -F compressed 1Life

Have you tried this?

[Jambo]

I'll pay $25 if someone can compile me the lifeboat oclvanitygen64 with support for compressed BTC addresses.

Compressed is a standard option in lifeboat. From the README from https://lifeboat.com/oclvanitygen/ :

To create compressed keys use the "-F compressed" option as in
oclvanitygen -F compressed -d 0 1Life or
vanitygen -F compressed 1Life

Have you tried this?

My bad. I looked into the arguments but not carefully enough . Thank you so much it works great

[ExploitAgency]

Vanitygen PLUS!
Now working on windows

Binary release out

This version also supports compressed keys and encrypting and decrypting your private keys so you can set a password and safely save generated keys to a file if you want.  All documentation is in readme.

Generate addresses for 80+ cryptocurrencies!

https://github.com/exploitagency/vanitygen-plus/releases

Still working on finding time to finish fiddling with opencl in my vm to compile oclvanitygen properly currently just cpu vanitygen and updated keyconv on windows
linux fully supported with both

[Timelord2067]

Vanitygen PLUS!

Still working on finding time to finish fiddling with opencl in my vm to compile oclvanitygen properly currently just cpu vanitygen and updated keyconv on windows
linux fully supported with both

VanityGen Plus gives out about 215KKeys/sec on my system, am looking forward to a GPU update when ever it arrives.

[xhomerx10]

Vanitygen PLUS!

Still working on finding time to finish fiddling with opencl in my vm to compile oclvanitygen properly currently just cpu vanitygen and updated keyconv on windows
linux fully supported with both

VanityGen Plus gives out about 215KKeys/sec on my system, am looking forward to a GPU update when ever it arrives.

 You can always use vanitygen and the version code for the coin for which you want to generate an address from the table on this page:

https://en.bitcoin.it/wiki/List_of_address_prefixes

to create addresses at GPU speeds.  I'm on my phone right now so I can't test the command line syntax to tell you exactly what to type but I've been doing this for a while now to generate a variety of coin addresses using oclvanitygen.

[LoyceV]

Vanitygen PLUS!
Now working on windows

Binary release out

This version also supports compressed keys

...

linux fully supported with both

I am very interested in compressed vanity keys for Bitcoin (I don't need any other cryptocurrency to be supported). I am a bit scared though to run software from unknown origin. Would it be too much to ask for just the source-changes to turn (ocl)vanitygen into a version that supports compressed keys? Going through the full source changes now will be too much for my limited programming knowledge, and I'm trying to keep my system trusted.
I'm running Linux and will happily compile it by myself.