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

mrxtraf

member

Activity: 255

Merit: 27

Why down calculattion in used more card.
Use 1 card. Showed 37-40 Mkey/s.
Use 8 cards at same task. Showed 225-242 Mkey/s. But if calculate must be 296-320.
Other big process not runned, only oclvanitygen and systems.
And card not used at 100 percents.

Code:

nvidia-smi
Sun Aug 27 17:44:14 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  Tesla K80           On   | 0000:00:17.0     Off |                    0 |
| N/A   80C    P0   132W / 149W |   1734MiB / 11439MiB |     94%      Default |
+-------------------------------+----------------------+----------------------+
|   1  Tesla K80           On   | 0000:00:18.0     Off |                    0 |
| N/A   64C    P0   151W / 149W |   1734MiB / 11439MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+
|   2  Tesla K80           On   | 0000:00:19.0     Off |                    0 |
| N/A   82C    P0   120W / 149W |   1734MiB / 11439MiB |     82%      Default |
+-------------------------------+----------------------+----------------------+
|   3  Tesla K80           On   | 0000:00:1A.0     Off |                    0 |
| N/A   68C    P0   144W / 149W |   1734MiB / 11439MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+
|   4  Tesla K80           On   | 0000:00:1B.0     Off |                    0 |
| N/A   79C    P0    84W / 149W |   1734MiB / 11439MiB |      9%      Default |
+-------------------------------+----------------------+----------------------+
|   5  Tesla K80           On   | 0000:00:1C.0     Off |                    0 |
| N/A   64C    P0   107W / 149W |   1734MiB / 11439MiB |     36%      Default |
+-------------------------------+----------------------+----------------------+
|   6  Tesla K80           On   | 0000:00:1D.0     Off |                    0 |
| N/A   78C    P0   144W / 149W |   1734MiB / 11439MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+
|   7  Tesla K80           On   | 0000:00:1E.0     Off |                    0 |
| N/A   66C    P0   153W / 149W |   1734MiB / 11439MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0     62887    C   ./oclvanitygen                                1730MiB |
|    1     62887    C   ./oclvanitygen                                1730MiB |
|    2     62887    C   ./oclvanitygen                                1730MiB |
|    3     62887    C   ./oclvanitygen                                1730MiB |
|    4     62887    C   ./oclvanitygen                                1730MiB |
|    5     62887    C   ./oclvanitygen                                1730MiB |
|    6     62887    C   ./oclvanitygen                                1730MiB |
|    7     62887    C   ./oclvanitygen                                1730MiB |
+-----------------------------------------------------------------------------+

after few seconds
nvidia-smi
Sun Aug 27 17:45:23 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  Tesla K80           On   | 0000:00:17.0     Off |                    0 |
| N/A   79C    P0    83W / 149W |   1734MiB / 11439MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  Tesla K80           On   | 0000:00:18.0     Off |                    0 |
| N/A   64C    P0   152W / 149W |   1734MiB / 11439MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+
|   2  Tesla K80           On   | 0000:00:19.0     Off |                    0 |
| N/A   82C    P0   127W / 149W |   1734MiB / 11439MiB |     63%      Default |
+-------------------------------+----------------------+----------------------+
|   3  Tesla K80           On   | 0000:00:1A.0     Off |                    0 |
| N/A   68C    P0   150W / 149W |   1734MiB / 11439MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+
|   4  Tesla K80           On   | 0000:00:1B.0     Off |                    0 |
| N/A   80C    P0   145W / 149W |   1734MiB / 11439MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+
|   5  Tesla K80           On   | 0000:00:1C.0     Off |                    0 |
| N/A   64C    P0   148W / 149W |   1734MiB / 11439MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+
|   6  Tesla K80           On   | 0000:00:1D.0     Off |                    0 |
| N/A   78C    P0   136W / 149W |   1734MiB / 11439MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+
|   7  Tesla K80           On   | 0000:00:1E.0     Off |                    0 |
| N/A   66C    P0   144W / 149W |   1734MiB / 11439MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0     62887    C   ./oclvanitygen                                1730MiB |
|    1     62887    C   ./oclvanitygen                                1730MiB |
|    2     62887    C   ./oclvanitygen                                1730MiB |
|    3     62887    C   ./oclvanitygen                                1730MiB |
|    4     62887    C   ./oclvanitygen                                1730MiB |
|    5     62887    C   ./oclvanitygen                                1730MiB |
|    6     62887    C   ./oclvanitygen                                1730MiB |
|    7     62887    C   ./oclvanitygen                                1730MiB |
+-----------------------------------------------------------------------------+

32 vcpu
480Gb memory.

Code:

top - 17:49:36 up 10 days,  2:51,  3 users,  load average: 10.79, 10.58, 10.40
Tasks: 362 total,   1 running, 361 sleeping,   0 stopped,   0 zombie
%Cpu0  :  20.2/43.6   64[||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||                                    ]
%Cpu1  :  32.1/37.9   70[||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||                              ]
%Cpu2  :  22.2/15.2   37[|||||||||||||||||||||||||||||||||||||                                                               ]
%Cpu3  :  34.4/30.9   65[|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||                                   ]
%Cpu4  :  39.2/38.0   77[|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||                       ]
%Cpu5  :  22.2/19.9   42[||||||||||||||||||||||||||||||||||||||||||                                                          ]
%Cpu6  :  21.9/25.1   47[|||||||||||||||||||||||||||||||||||||||||||||||                                                     ]
%Cpu7  :   4.4/11.2   16[|||||||||||||||                                                                                     ]
%Cpu8  :   3.2/10.6   14[||||||||||||||                                                                                      ]
%Cpu9  :   0.0/0.6     1[|                                                                                                   ]
%Cpu10 :   0.0/1.5     1[|                                                                                                   ]
%Cpu11 :   3.8/6.7    10[|||||||||||                                                                                         ]
%Cpu12 :   0.0/0.6     1[|                                                                                                   ]
%Cpu13 :  19.1/16.2   35[|||||||||||||||||||||||||||||||||||                                                                 ]
%Cpu14 :   0.0/0.0     0[                                                                                                    ]
%Cpu15 :  20.1/51.9   72[||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||                            ]
%Cpu16 :  22.8/18.7   42[||||||||||||||||||||||||||||||||||||||||||                                                          ]
%Cpu17 :   0.0/0.0     0[                                                                                                    ]
%Cpu18 :  43.0/30.1   73[|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||                           ]
%Cpu19 :   0.0/0.3     0[                                                                                                    ]
%Cpu20 :   0.0/0.0     0[                                                                                                    ]
%Cpu21 :   0.0/0.0     0[                                                                                                    ]
%Cpu22 :   0.0/0.0     0[                                                                                                    ]
%Cpu23 :  38.9/34.8   74[||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||                          ]
%Cpu24 :   0.0/0.0     0[                                                                                                    ]
%Cpu25 :  39.7/36.4   76[||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||                        ]
%Cpu26 :  36.3/34.2   70[||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||                              ]
%Cpu27 :  35.2/38.4   74[|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||                           ]
%Cpu28 :  17.9/15.8   34[||||||||||||||||||||||||||||||||||                                                                  ]
%Cpu29 :   0.3/0.6     1[|                                                                                                   ]
%Cpu30 :  18.2/15.0   33[|||||||||||||||||||||||||||||||||                                                                   ]
%Cpu31 :   0.0/0.0     0[                                                                                                    ]
GiB Mem :  0.9/480.280  [                                                                                                    ]
GiB Swap:  0.0/0.000    [                                                                                                    ]

   PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                                                                                                                                                                                   
 62887 ubuntu    20   0  0.572t 738.8m 588.7m S  1005  0.2 786:33.28 oclvanitygen                                                                                                                                                                                              
  1465 root      20   0 1367.2m  35.6m  13.5m S   0.0  0.0   0:44.21 snapd                                                                                                                                                                                                     
   610 root      20   0   50.4m  23.4m  23.1m S   0.0  0.0   0:03.26 systemd-journal

Tomorrowman

member

Activity: 74

Merit: 10

Quote from: digicoinuser on August 25, 2017, 10:52:48 PM

Quote from: Tomorrowman on August 25, 2017, 02:40:46 PM

Guys, I use vanitygen plus with 1080ti and after several hours of work I get an error: CODE

Any ideas? Please help!

What model GeForce GTX 1080 Ti are you using and if you kill/restart vanitygen does it start working again properly?

Asus 1080 ti rog strix oc.
Yes, it does start working again with no problem, but after several hours this error repeats.

digicoinuser

legendary

Activity: 2702

Merit: 1072

Quote from: Tomorrowman on August 25, 2017, 02:40:46 PM

Guys, I use vanitygen plus with 1080ti and after several hours of work I get an error: CODE

Any ideas? Please help!

What model GeForce GTX 1080 Ti are you using and if you kill/restart vanitygen does it start working again properly?

This is what I use to kill a process if something severely locks up:
kill -9 `pidof oclvanitygen`

Is there a clue you can go on such as the temperature of the GPU dropping instantly when the program locks up?

Quote from: salfter on August 25, 2017, 07:37:19 PM

Quote from: els on August 17, 2017, 10:18:53 PM

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?

I'm not, but for a data point that's probably not on there, I'm seeing about 28 Mkeys/s from a Radeon RX460. (Host system is Gentoo Linux with the AMDGPU driver and AMDGPU-Pro OpenCL layer. I had to tweak calc_addrs.cl as described in https://github.com/samr7/vanitygen/issues/38#issuecomment-31248556 to get it to work.)

102 Mkey/s here with a single GTX 1080 Ti 11GB 352-Bit GDDR5X

I agree, the list should be updated and it's way out of date.

salfter

hero member

Activity: 651

Merit: 501

My PGP Key: 92C7689C

Quote from: els on August 17, 2017, 10:18:53 PM

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?

I'm not, but for a data point that's probably not on there, I'm seeing about 28 Mkeys/s from a Radeon RX460. (Host system is Gentoo Linux with the AMDGPU driver and AMDGPU-Pro OpenCL layer. I had to tweak calc_addrs.cl as described in https://github.com/samr7/vanitygen/issues/38#issuecomment-31248556 to get it to work.)

Tomorrowman

member

Activity: 74

Merit: 10

Guys, I use vanitygen plus with 1080ti and after several hours of work I get an error:

Code:

clEnqueueMapBuffer(4): clWaitForEvents(NDRange,e): CL_OUT_OF_RESOURCES
CL_INVALID_COMMAND_QUEUE
vg_ocl_context_callback error: CL_OUT_OF_RESOURCES error waiting for idle on GeForce GTX 1080 Ti (Device 0).

Device: GeForce GTX 1080 Ti
Device: GeForce GTX 1080 Ti
Vendor: NVIDIA Corporation (10de)
Driver: 385.28
Vendor: 385.28 (10de)
Driver: 385.28
Profile: 385.28
Version: OpenCL 1.2 CUDA
Profile: OpenCL 1.2 CUDA
vg_ocl_context_callback error: CL_OUT_OF_RESOURCES error waiting for idle on GeForce GTX 1080 Ti (Device 0).

Max compute units: 28
Version: OpenCL 1.2 CUDA
Max workgroup size: 1024
Max compute units: 28
Global memory: -1073741824
Max workgroup size: 1024
Max allocation: -1342177280
Global memory: -1073741824
ERROR: Could not map row buffer for slot 0
Max allocation: -1342177280
ERROR: allocation failure?
vg_ocl_context_callback error: CL_OUT_OF_RESOURCES error waiting for idle on GeForce GTX 1080 Ti (Device 0).

Any ideas? Please help!

HauntingT-Rex

jr. member

Activity: 40

Merit: 1

Quote from: LoyceV on August 19, 2017, 12:53:26 PM

Quote from: suppersz on August 19, 2017, 12:09:41 PM

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.

If you're totally paranoid: use split-key:

Quote from: LoyceV on March 04, 2017, 03:25:07 PM

Instructions
I can just create an address, and send you the private key. This means you have to trust me, my computer, my cat, both our email clients, and by definition it can no longer be used for cold storage. So let's not. Instead, use split key:
Step 1: Goto https://www.bitaddress.org/ move your mouse/type in the field until it shows 100% and wait a second.
Step 1.5: Optional but highly recommended. Download the page, verify the download and run it locally^*.
Step 2: Click Vanity Wallet click the Generate button next to Generate your "Step1 Key Pair"
Step 3: Reply to this thread with your public key and the prefix for your address. Save the private key somewhere safe. You will need it later when I generated your partial private key. Also, let me know if your preferred prefix is case sensitive, or any case is okay (the latter is much faster)
Step 4: Once you received your partial private key, go back to bitaddress.org and click on Vanity Wallet.
Step 5: Go to step 2 Calculate your vanity wallet. In the first field put the private key you saved and in the second field put the partial private key I gave you. Click Add and Calculate Vanity Wallet
Step 6: Copy the Vanity Private Key (WIF) and import it into your preferred wallet.
Credits to shorena for most of these instructions!
If something doesn't work as expected, have a look at this example.

In Step 3, you run vanitygen by yourself, and use your own publick key.

You can also use split key if you don't trust the computer that you use to run Vanitygen.

What is so special about split-key? Even that might still have some sort of malicious code.

slavikus

newbie

Activity: 6

Merit: 1

Quote from: mrxtraf on August 19, 2017, 06:36:40 PM

If i found pair without "-P ". I have clear private - public key. ?

Yes, but it won't be accepted as a completed work by the vanity pool. You can use it for yourself, though

mrxtraf

member

Activity: 255

Merit: 27

Quote from: slavikus on August 19, 2017, 06:02:57 PM

Quote from: mrxtraf on August 19, 2017, 05:14:04 PM

If I have pair privat-publick key for one of this list https://vanitypool.appspot.com/availableWork may i get rewards?
How split keys?

Yes, if you find the private key for one of the items in that list, you will get the reward listed. Use oclvanityminer for that, or oclvanitygen -P

If i found pair without "-P ". I have clear private - public key. ?

slavikus

newbie

Activity: 6

Merit: 1

Quote from: mrxtraf on August 19, 2017, 05:14:04 PM

If I have pair privat-publick key for one of this list https://vanitypool.appspot.com/availableWork may i get rewards?
How split keys?

Yes, if you find the private key for one of the items in that list, you will get the reward listed. Use oclvanityminer for that, or oclvanitygen -P

mrxtraf

member

Activity: 255

Merit: 27

If I have pair privat-publick key for one of this list https://vanitypool.appspot.com/availableWork may i get rewards?
How split keys?

LoyceV

legendary

Activity: 3290

Merit: 16489

Thick-Skinned Gang Leader and Golden Feather 2021

Quote from: suppersz on August 19, 2017, 12:09:41 PM

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.

If you're totally paranoid: use split-key:

Quote from: LoyceV on March 04, 2017, 03:25:07 PM

Instructions
I can just create an address, and send you the private key. This means you have to trust me, my computer, my cat, both our email clients, and by definition it can no longer be used for cold storage. So let's not. Instead, use split key:
Step 1: Goto https://www.bitaddress.org/ move your mouse/type in the field until it shows 100% and wait a second.
Step 1.5: Optional but highly recommended. Download the page, verify the download and run it locally^*.
Step 2: Click Vanity Wallet click the Generate button next to Generate your "Step1 Key Pair"
Step 3: Reply to this thread with your public key and the prefix for your address. Save the private key somewhere safe. You will need it later when I generated your partial private key. Also, let me know if your preferred prefix is case sensitive, or any case is okay (the latter is much faster)
Step 4: Once you received your partial private key, go back to bitaddress.org and click on Vanity Wallet.
Step 5: Go to step 2 Calculate your vanity wallet. In the first field put the private key you saved and in the second field put the partial private key I gave you. Click Add and Calculate Vanity Wallet
Step 6: Copy the Vanity Private Key (WIF) and import it into your preferred wallet.
Credits to shorena for most of these instructions!
If something doesn't work as expected, have a look at this example.

In Step 3, you run vanitygen by yourself, and use your own publick key.

You can also use split key if you don't trust the computer that you use to run Vanitygen.

suppersz

sr. member

Activity: 336

Merit: 250

There is a day to be born, and another to die

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.

mrxtraf

member

Activity: 255

Merit: 27

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?

els

newbie

Activity: 41

Merit: 0

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

btctousd81

sr. member

Activity: 434

Merit: 270

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.

xhomerx10

legendary

Activity: 3808

Merit: 7912

Quote from: MrPaky on August 16, 2017, 03:53:55 PM

Quote from: xhomerx10 on August 16, 2017, 01:19:58 PM

Quote from: MrPaky on August 16, 2017, 11:56:22 AM

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

MrPaky

jr. member

Activity: 53

Merit: 2

Quote from: xhomerx10 on August 16, 2017, 01:19:58 PM

Quote from: MrPaky on August 16, 2017, 11:56:22 AM

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

legendary

Activity: 3808

Merit: 7912

Quote from: MrPaky on August 16, 2017, 11:56:22 AM

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

jr. member

Activity: 53

Merit: 2

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

digicoinuser

legendary

Activity: 2702

Merit: 1072

Quote from: LoyceV on August 09, 2017, 02:36:49 AM

Quote from: digicoinuser on August 08, 2017, 09:41:06 PM

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?

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