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

[digicoinuser]

Yep I did that check before and It has been successful in 10 seconds.

How can I be sure it will continue the work on restart? Does it save some hash/stuff somewhere? I will try another 50%. I'll let you know

EDIT: Ok i'm a naaab. I did the check with CPU and it was ok. Then with OCL I have a lot of CPU/GPU hash mismatch and I didn't know it's an issue. with -S option it seems running well but with half of Mkey/s.

Ok. I will dig deeper over amd driver problems after my vacation. I've found some threads from 2013, is there some solution for current AMD drivers (Windows 10)?

Definitely could be an issue with the driver. As for "continuing" the work - it doesn't resume as you're thinking, my understanding is five identical machines running to 20% would be the same as one machine running to 100%.

[LoyceV]

Definitely could be an issue with the driver. As for "continuing" the work - it doesn't resume as you're thinking, my understanding is five identical machines running to 20% would be the same as one machine running to 100%.

It will never reach 100%.

Think of it as throwing a dice trying to hit a 6 four times in a row. You can stop and continue at any moment, previous misses don't need to be saved, you just start at random again.

[xhomerx10]

I'd say you're going to get it soon.  

I've seen mine get to 99.8% but I haven't watched it enough to see it pass that.

Ok it's enough. I give up. After 99.9% the Prob section disappeared and it's 12 more hours since then without results

 Can we ask what prefix you were looking for?

1Sapiens

Interesting, have you confirmed it can find an easy address like "1Sap"?  

If you ran up to 99.9% and didn't find it, technically you should find it within 50% of the next try.  It's additive over time and doesn't restart searching through the same addresses it did last time.

Yep I did that check before and It has been successful in 10 seconds.

How can I be sure it will continue the work on restart? Does it save some hash/stuff somewhere? I will try another 50%. I'll let you know

EDIT: Ok i'm a naaab. I did the check with CPU and it was ok. Then with OCL I have a lot of CPU/GPU hash mismatch and I didn't know it's an issue. with -S option it seems running well but with half of Mkey/s.

Ok. I will dig deeper over amd driver problems after my vacation. I've found some threads from 2013, is there some solution for current AMD drivers (Windows 10)?

 Past a few lines of output so we can see if there is a problem.

Code:

c:\oclvanitygen>oclvanitygen -d 0:0 -k 1Sapiens
Difficulty: 51529903411245
[25.70 Mkey/s][total 629145600][Prob 0.0%][50% in 16.1d]

The difficulty of 1Sapiens is very high for an 8 letter prefix because the capital S after the 1 has a lower probability of a match than other possibilities.  Based on one of my machines running @ 25Mkeys/s the difficulty for 1Sapiens (case sensitive) is 51529903411245 and I'm looking at ~16 days for 50% probability.  For an 8 letter prefix, you've picked a doozey.

[RentGPU]

I want to ask a question can someone with this vanitygen random generated addresses or any other generator while trying to reach the address he want end landing on someone else adderess and private key , so i enter my wallet to find someone had shared it with me and for sure spent my coins ??!!

[aarons6]

I want to ask a question can someone with this vanitygen random generated addresses or any other generator while trying to reach the address he want end landing on someone else adderess and private key , so i enter my wallet to find someone had shared it with me and for sure spent my coins ??!!

i think i understand your question.. if you made a bitcoin address say 1btc or something, and used it, how possible is it to try to make that same wallet again?

the simple answer is very not likely.

while you can make other addresses start with 1btc.. you will never find exactly the same one twice.

[RentGPU]

I want to ask a question can someone with this vanitygen random generated addresses or any other generator while trying to reach the address he want end landing on someone else adderess and private key , so i enter my wallet to find someone had shared it with me and for sure spent my coins ??!!

i think i understand your question.. if you made a bitcoin address say 1btc or something, and used it, how possible is it to try to make that same wallet again?

the simple answer is very not likely.

while you can make other addresses start with 1btc.. you will never find exactly the same one twice.

So it's mathematically can but not very likely , i think it's just like we want to find each other in the ocean ...it can be done but needs 10000000% luck, is that right

[MICRO]

Does this still work? Haven't used it in a while.

[aarons6]

I want to ask a question can someone with this vanitygen random generated addresses or any other generator while trying to reach the address he want end landing on someone else adderess and private key , so i enter my wallet to find someone had shared it with me and for sure spent my coins ??!!

i think i understand your question.. if you made a bitcoin address say 1btc or something, and used it, how possible is it to try to make that same wallet again?

the simple answer is very not likely.

while you can make other addresses start with 1btc.. you will never find exactly the same one twice.

So it's mathematically can but not very likely , i think it's just like we want to find each other in the ocean ...it can be done but needs 10000000% luck, is that right

its more like finding the same atom out of all the atoms in the entire world.

[TryNinja]

I want to ask a question can someone with this vanitygen random generated addresses or any other generator while trying to reach the address he want end landing on someone else adderess and private key , so i enter my wallet to find someone had shared it with me and for sure spent my coins ??!!

i think i understand your question.. if you made a bitcoin address say 1btc or something, and used it, how possible is it to try to make that same wallet again?

the simple answer is very not likely.

while you can make other addresses start with 1btc.. you will never find exactly the same one twice.

I would say for sure that it's almost impossible. Otherwise, Bitcoin wouldn't be that safe anymore right?

"To obtain the same address, the result of RIPEMD-160 hashing would need to be the same. Probability of that happening is 1 in 2^160.

In simple terms, if you were testing against 500k patterns at 25/Mkey a second, it'd take about 25 quadrillion years to get a few collisions. Factoring out the randomness of course, as the nature of randomness entails that it could take 2 seconds or 2 sextillion years.

Even if you put all the calculating power of the entire bitcoin network on it, it would still take 10^12+ years."
https://bitcoin.stackexchange.com/questions/7676/what-are-the-chances-of-vanitygen-address-private-key-pair-collision

Does this still work? Haven't used it in a while.

Yes it does.

Just used yesterday actually.

[hirish]

I'd say you're going to get it soon.  

I've seen mine get to 99.8% but I haven't watched it enough to see it pass that.

Ok it's enough. I give up. After 99.9% the Prob section disappeared and it's 12 more hours since then without results

 Can we ask what prefix you were looking for?

1Sapiens

Interesting, have you confirmed it can find an easy address like "1Sap"?  

If you ran up to 99.9% and didn't find it, technically you should find it within 50% of the next try.  It's additive over time and doesn't restart searching through the same addresses it did last time.

Yep I did that check before and It has been successful in 10 seconds.

How can I be sure it will continue the work on restart? Does it save some hash/stuff somewhere? I will try another 50%. I'll let you know

EDIT: Ok i'm a naaab. I did the check with CPU and it was ok. Then with OCL I have a lot of CPU/GPU hash mismatch and I didn't know it's an issue. with -S option it seems running well but with half of Mkey/s.

Ok. I will dig deeper over amd driver problems after my vacation. I've found some threads from 2013, is there some solution for current AMD drivers (Windows 10)?

 Past a few lines of output so we can see if there is a problem.

Code:

c:\oclvanitygen>oclvanitygen -d 0:0 -k 1Sapiens
Difficulty: 51529903411245
[25.70 Mkey/s][total 629145600][Prob 0.0%][50% in 16.1d]

The difficulty of 1Sapiens is very high for an 8 letter prefix because the capital S after the 1 has a lower probability of a match than other possibilities.  Based on one of my machines running @ 25Mkeys/s the difficulty for 1Sapiens (case sensitive) is 51529903411245 and I'm looking at ~16 days for 50% probability.  For an 8 letter prefix, you've picked a doozey.

I was using -i, It's not a must the S capital letter.

Code:

$ ./oclvanitygen -d 0:0 -i 1Sapiens
Difficulty: 805154740800
[26.12 Mkey/s][total 184549376][Prob 0.0%][50% in 5.9h]

The solution with AWS instances with NVIDIA GRID GPUs is still a valid solution? For a couple of bucks I could save myself burning alive in my bedroom

[xhomerx10]

I'd say you're going to get it soon.  

I've seen mine get to 99.8% but I haven't watched it enough to see it pass that.

Ok it's enough. I give up. After 99.9% the Prob section disappeared and it's 12 more hours since then without results

 Can we ask what prefix you were looking for?

1Sapiens

Interesting, have you confirmed it can find an easy address like "1Sap"?  

If you ran up to 99.9% and didn't find it, technically you should find it within 50% of the next try.  It's additive over time and doesn't restart searching through the same addresses it did last time.

Yep I did that check before and It has been successful in 10 seconds.

How can I be sure it will continue the work on restart? Does it save some hash/stuff somewhere? I will try another 50%. I'll let you know

EDIT: Ok i'm a naaab. I did the check with CPU and it was ok. Then with OCL I have a lot of CPU/GPU hash mismatch and I didn't know it's an issue. with -S option it seems running well but with half of Mkey/s.

Ok. I will dig deeper over amd driver problems after my vacation. I've found some threads from 2013, is there some solution for current AMD drivers (Windows 10)?

 Past a few lines of output so we can see if there is a problem.

Code:

c:\oclvanitygen>oclvanitygen -d 0:0 -k 1Sapiens
Difficulty: 51529903411245
[25.70 Mkey/s][total 629145600][Prob 0.0%][50% in 16.1d]

The difficulty of 1Sapiens is very high for an 8 letter prefix because the capital S after the 1 has a lower probability of a match than other possibilities.  Based on one of my machines running @ 25Mkeys/s the difficulty for 1Sapiens (case sensitive) is 51529903411245 and I'm looking at ~16 days for 50% probability.  For an 8 letter prefix, you've picked a doozey.

I was using -i, It's not a must the S capital letter.

Code:

$ ./oclvanitygen -d 0:0 -i 1Sapiens
Difficulty: 805154740800
[26.12 Mkey/s][total 184549376][Prob 0.0%][50% in 5.9h]

The solution with AWS instances with NVIDIA GRID GPUs is still a valid solution? For a couple of bucks I could save myself burning alive in my bedroom

 Yeah you could use AWS but use split-key generation to make sure that your key isn't compromised.
If you're going to do that, there are members on here who will generate keys for fees. It might be a little cheaper than AWS costs.
 I think Shorena does it but I'm not certain.

[digicoinuser]

Definitely could be an issue with the driver. As for "continuing" the work - it doesn't resume as you're thinking, my understanding is five identical machines running to 20% would be the same as one machine running to 100%.

It will never reach 100%.

Think of it as throwing a dice trying to hit a 6 four times in a row. You can stop and continue at any moment, previous misses don't need to be saved, you just start at random again.

Understood, does it sit at 99.9% until complete or does the % go away at that point?

[MrPaky]

Alas, I would have a question. Starting from a private key, can you generate another similar address?

Let me give an example:

Suppose I have the private key of the address:
1PasqAbbbbbbbbbbbbbbbbbbbbbcgehnE

I want to generate another similar address:
1PasqRbbbbbbbbbbbbbbbbbbbbbcsaSgf

Can you generate it from the private key of the first address so you do not have to "generate" keys by causality?

Thank you

Sorry for my English

[xhomerx10]

Alas, I would have a question. Starting from a private key, can you generate another similar address?

Let me give an example:

Suppose I have the private key of the address:
1PasqAbbbbbbbbbbbbbbbbbbbbbcgehnE

I want to generate another similar address:
1PasqRbbbbbbbbbbbbbbbbbbbbbcsaSgf

Can you generate it from the private key of the first address so you do not have to "generate" keys by causality?

Thank you

Sorry for my English

 No!  If it worked that way, Bitcoin would be worthless.
The hashing algorithms used are one-way functions - you would never be able to find
1PasqAbbbbbbbbbbbbbbbbbbbbbcgehnE base58 decoded is 0004456E03A3A379310A0DAB1718A3463EDD73E0436DC23977
1PasqRbbbbbbbbbbbbbbbbbbbbbcsaSgf  base58 decoded is 0004456E07D8524025C216494E6313E49A11D579A0CD20FA28

 Now you can take off the last 4 bytes (checksum) and the first byte (network id)
1PasqAbbbbbbbbbbbbbbbbbbbbbcgehnE; 04456E03A3A379310A0DAB1718A3463EDD73E043
1PasqRbbbbbbbbbbbbbbbbbbbbbcsaSgf;  04456E07D8524025C216494E6313E49A11D579A0

to get the public keys, you have to undo the RIPMD160 hash and then undo the SHA256 hash on each of those results however, there is no known reverse function for either of those.
Even if you could get the public key this way, the public key doesn't map to the private key as this mapping is also a one way function.

 

[MrPaky]

Alas, I would have a question. Starting from a private key, can you generate another similar address?

Let me give an example:

Suppose I have the private key of the address:
1PasqAbbbbbbbbbbbbbbbbbbbbbcgehnE

I want to generate another similar address:
1PasqRbbbbbbbbbbbbbbbbbbbbbcsaSgf

Can you generate it from the private key of the first address so you do not have to "generate" keys by causality?

Thank you

Sorry for my English

 No!  If it worked that way, Bitcoin would be worthless.
The hashing algorithms used are one-way functions - you would never be able to find
1PasqAbbbbbbbbbbbbbbbbbbbbbcgehnE base58 decoded is 0004456E03A3A379310A0DAB1718A3463EDD73E0436DC23977
1PasqRbbbbbbbbbbbbbbbbbbbbbcsaSgf  base58 decoded is 0004456E07D8524025C216494E6313E49A11D579A0CD20FA28

 Now you can take off the last 4 bytes (checksum) and the first byte (network id)
1PasqAbbbbbbbbbbbbbbbbbbbbbcgehnE; 04456E03A3A379310A0DAB1718A3463EDD73E043
1PasqRbbbbbbbbbbbbbbbbbbbbbcsaSgf;  04456E07D8524025C216494E6313E49A11D579A0

to get the public keys, you have to undo the RIPMD160 hash and then undo the SHA256 hash on each of those results however, there is no known reverse function for either of those.
Even if you could get the public key this way, the public key doesn't map to the private key as this mapping is also a one way function.

 

So let's see if I understand having the private key of: 0004456E03A3A379310A0DAB1718A3463EDD73E0436DC23977

I can not generate another similar public address. By assuming the private key of: 0004456E03A3A379310A0DAB1718A3463EDD73E0436DC23977

To do this I should cancel RIPMD160 and SHA256 on the private key, right?

Thank You

[xhomerx10]

Alas, I would have a question. Starting from a private key, can you generate another similar address?

Let me give an example:

Suppose I have the private key of the address:
1PasqAbbbbbbbbbbbbbbbbbbbbbcgehnE

I want to generate another similar address:
1PasqRbbbbbbbbbbbbbbbbbbbbbcsaSgf

Can you generate it from the private key of the first address so you do not have to "generate" keys by causality?

Thank you

Sorry for my English

 No!  If it worked that way, Bitcoin would be worthless.
The hashing algorithms used are one-way functions - you would never be able to find
1PasqAbbbbbbbbbbbbbbbbbbbbbcgehnE base58 decoded is 0004456E03A3A379310A0DAB1718A3463EDD73E0436DC23977
1PasqRbbbbbbbbbbbbbbbbbbbbbcsaSgf  base58 decoded is 0004456E07D8524025C216494E6313E49A11D579A0CD20FA28

 Now you can take off the last 4 bytes (checksum) and the first byte (network id)
1PasqAbbbbbbbbbbbbbbbbbbbbbcgehnE; 04456E03A3A379310A0DAB1718A3463EDD73E043
1PasqRbbbbbbbbbbbbbbbbbbbbbcsaSgf;  04456E07D8524025C216494E6313E49A11D579A0

to get the public keys, you have to undo the RIPMD160 hash and then undo the SHA256 hash on each of those results however, there is no known reverse function for either of those.
Even if you could get the public key this way, the public key doesn't map to the private key as this mapping is also a one way function.

 

So let's see if I understand having the private key of: 0004456E03A3A379310A0DAB1718A3463EDD73E0436DC23977

I can not generate another similar public address. By assuming the private key of: 0004456E03A3A379310A0DAB1718A3463EDD73E0436DC23977

To do this I should cancel RIPMD160 and SHA256 on the private key, right?

Thank You

 Well, you need the private key to derive the public key (this cannot be reversed) and you need the public key to derive your public address (this cannot be reversed)
 This number: 0004456E03A3A379310A0DAB1718A3463EDD73E0436DC23977
is simply the hexadecimal version of this base58 encoded public address:
1PasqAbbbbbbbbbbbbbbbbbbbbbcgehnE

 It's not possible to undo the RIPEMD160 or SHA256 hash functions so you can never go backwards and if you start with similar private keys, they map to entirely different points on the ECDSA curve (so the public keys will be very different) and even if those turned out to be similar, the hash functions will produce very different results on similar numbers.
example:
private key: 0A0000000001 yields public key:
04BADACBF295A97C139B70150AE361E864187A6152A149335568C2B7F3B35482E1D6B0D12818EEF 9A9C2DBDE947B542C220A97F54329BDA2CE2995E12195FB6A41

private key: 0A0000000002 yields public key:
0471AFF13951BDE978F0AA1F1D5AD9FFB38C900CD33127A651826A308F734B54ACD734A0D1052EF 95F921DC23FA962C0E0FCE72F7DF564B56F9710A7248F1E1639

 You can play with the hashing yourself here

[btctousd81]

this is the fastest bitcoin address generator.,
i mean 1mil+ per second.

is it possible to modify the code to create address pair from string ? i mean
passphrase -> private key
and
private key -> bitcoin address

thanks

i know there are tools out there , but nothing matches speed of vanitygen.

[els]

is anybody aware of a newer listing of expected keysearch rates than this (at least as old as 2015):

   https://en.bitcoin.it/wiki/Vanitygen#Expected_keysearch_rate

notable, inclusive of newer GPUs?

thanks

--els

[mrxtraf]

Goes (cycling) on one of the video cards. Nvidia tesla M2050, M2075, M2090, GRID K520.

system kubuntu desctop 16.04. other computer ubuntu server 16.04
run
vanitygen$ ./oclvanitygen -D 0:0 -D 0:1 -o ../files/founds/vanity_3.txt -k -f ../files/vanity.txt
Next match difficulty: 108786463956186 (40 prefixes)
No protocol specified
[32.98 Mkey/s][total 97272201216][Prob 0.1%][50% in 26.4d]

After several hours of work. Maybe an hour, maybe a day. The output of the current state stops.
[32.98 Mkey/s][total 97272201216][Prob 0.1%][50% in 26.4d]

But in the processes the task continues to be executed. It takes up part of the CPU time. And the calculation continues only on one of the cards. I tried to wait about a day, but nothing has changed.
After "^ C" it will stop after 20-30 seconds.

Run on other computer
$ ./oclvanitygen -D 0:0 -D 0:1 -D 0:2 -D 0:3 -o ../../files/vanity/found_vanity.txt -k -f ../../files/vanity/vanity.txt
./oclvanitygen: /usr/local/cuda-8.0/targets/x86_64-linux/lib/libOpenCL.so.1: no version information available (required by ./oclvanitygen)
Next match difficulty: 108786463956186 (40 prefixes)
[77.83 Mkey/s][total 225586446336][Prob 0.2%][50% in 11.2d] {MYENTER}
[77.28 Mkey/s][total 305563435008][Prob 0.3%][50% in 11.2d] {MYENTER}
[77.69 Mkey/s][total 411108900864][Prob 0.4%][50% in 11.2d] {MYENTER}
[74.88 Mkey/s][total 728701599744][Prob 0.7%][50% in 11.5d] {MYENTER}
[76.96 Mkey/s][total 780316704768][Prob 0.7%][50% in 11.2d] {MYENTER}
[79.60 Mkey/s][total 785828020224][Prob 0.7%][50% in 10.9d] {MYENTER}
{MYENTER}
{MYENTER}
{MYENTER}^C

One vidoecard is occupied by calculations for 100 percent, the other 0 percent. In this case, the memory is busy on all selected.
`
nvidia-smi
Mon Aug 14 08:50:24 2017
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 375.82 Driver Version: 375.82 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 Tesla M2075 Off | 0000:01:00.0 Off | 0 |
| N/A N/A P0 78W / N/A | 1854MiB / 5301MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 1 Tesla M2090 Off | 0000:02:00.0 Off | 0 |
| N/A N/A P0 83W / N/A | 1080MiB / 5301MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 2 Tesla M2050 Off | 0000:03:00.0 Off | 0 |
| N/A N/A P12 N/A / N/A | 0MiB / 2622MiB | 0% Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 19499 C ./oclvanitygen 1842MiB |
| 1 19499 C ./oclvanitygen 1080MiB |
+-----------------------------------------------------------------------------+

vanitygen$ ldd oclvanitygen
linux-vdso.so.1 => (0x00007ffc5b3e2000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f4be2573000)
libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007f4be212f000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f4be1e26000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f4be1c09000)
libOpenCL.so.1 => /opt/amdgpu-pro/lib/x86_64-linux-gnu/libOpenCL.so.1 (0x00007f4be1a02000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4be1638000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f4be1434000)
/lib64/ld-linux-x86-64.so.2 (0x00007f4be27e3000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f4be122c000)
`

Computer #2
`
nvidia-smi
Mon Aug 14 05:08:26 2017
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 375.66 Driver Version: 375.66 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GRID K520 Off | 0000:00:03.0 Off | N/A |
| N/A 36C P8 18W / 125W | 1067MiB / 4036MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 1 GRID K520 Off | 0000:00:04.0 Off | N/A |
| N/A 36C P8 17W / 125W | 1067MiB / 4036MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 2 GRID K520 Off | 0000:00:05.0 Off | N/A |
| N/A 54C P0 49W / 125W | 1067MiB / 4036MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 3 GRID K520 Off | 0000:00:06.0 Off | N/A |
| N/A 32C P8 17W / 125W | 1067MiB / 4036MiB | 0% Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 2733 C ./oclvanitygen 1065MiB |
| 1 2733 C ./oclvanitygen 1065MiB |
| 2 2733 C ./oclvanitygen 1065MiB |
| 3 2733 C ./oclvanitygen 1065MiB |
+-----------------------------------------------------------------------------+

$ ldd oclvanitygen
./oclvanitygen: /usr/local/cuda-8.0/targets/x86_64-linux/lib/libOpenCL.so.1: no version information available (required by ./oclvanitygen)
linux-vdso.so.1 => (0x00007fffdeb47000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007fcb5fa53000)
libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007fcb5f60f000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fcb5f305000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fcb5f0e8000)
libOpenCL.so.1 => /usr/local/cuda-8.0/targets/x86_64-linux/lib/libOpenCL.so.1 (0x00007fcb5eee2000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fcb5eb17000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fcb5e913000)
/lib64/ld-linux-x86-64.so.2 (0x000055683af0e000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fcb5e70b000)

In vanaitygen-pluse also present this bug.

How get dump on worked programm on ubuntu konsole?

[suppersz]

I have always wanted to do a vanitygen for my cold storage, but I am too paranoid the program would have some sort of built in preset way to make an address the creator also has keys for. How am I supposed to know for sure? I just wish I could trust do it trust-less.