VanitySearch (Yet another address prefix finder)

[Jean_Luc]

So do you think that the standard 18.04 distro will work for GPU? Or would I need to install some specific CUDA software for 18.04?

I think it will work but effectively you may need to install specific CUDA software.

[bangbumbang]

@Jean_Luc , you are right, 1.14 is working fine... do you have an actual changelog somewhere?

[Jean_Luc]

There is only few changes since the 1.14.
Does the 1.15 works also ?
I can imagine that a bug has been introduced with the dynamic grid size in 1.16 but in 1.15 there is only a change that concern P2SH and BECH32 addresses...

You can show changes by looking there:
https://github.com/JeanLucPons/VanitySearch/releases

[bangbumbang]

@Jean_Luc


no, 1.15 and 1.16 both do NOT work.. same error when loading lists..

will try with your exe though.. one moment...

what the hell.. im not getting errors on 5 or 6 when using your exe.. could only test for a minute though.. sometimes it took longer to crash

is my compile env gone haywire? I compiled 5 and a few days later 6 with VS19 and only changed the target to my cuda 10.2 env.. was there some change from 10.0?
(ps: no, no compile errors or anything.. just straight forward..)

... will test tonight...

[bangbumbang]

@Jean_Luc , btw..

yeah I can search all keys in 3 days

this is with 1.16

Vanitysearch.exe -b -t 0 -gpu -gpuId 0,1 -g 1088,512,1088,512 -r 10000000 -o found_0.txt -i in.txt

[4544125350086.37 Mkey/s][GPU 4544125350086.37 Mkey/s][Total 2^64.00][Prob 0.0%][50% in 7.06916e+21y][Found 0]

544,512,544,512 still shows korrekt MKeys

[Jean_Luc]

lol 
What a grid size !

Seems an integer overflow.

If you manage to compile, could you try to change:

Vanity.cpp: 1565
      counters[thId] += 6 * STEP_SIZE * nbThread; // Point +  endo1 + endo2 + symetrics
by
      counters[thId] += 6ULL * STEP_SIZE * nbThread; // Point +  endo1 + endo2 + symetrics

This should be enough.

[bangbumbang]

@Jean_Luc , btw..

yeah I can search all keys in 3 days

this is with 1.16

Vanitysearch.exe -b -t 0 -gpu -gpuId 0,1 -g 1088,512,1088,512 -r 10000000 -o found_0.txt -i in.txt

[4544125350086.37 Mkey/s][GPU 4544125350086.37 Mkey/s][Total 2^64.00][Prob 0.0%][50% in 7.06916e+21y][Found 0]

544,512,544,512 still shows korrekt MKeys

just a bug.. its showing 45000 Trillion Key per second

[Jean_Luc]

Hi there,

A new release is available (1.17):
-Slight performance increase (compressed key only) GPU
-Fixed counting bug for large grid size

Thanks to test it
Have fun

[voitelgluk]

Hi there,

A new release is available (1.17):
-Slight performance increase (compressed key only) GPU
-Fixed counting bug for large grid size

Thanks to test it
Have fun

please tell me how to run on radeon rx 570?

[MrFreeDragon]

-snip-
-Slight performance increase (compressed key only) GPU
-snip-

What was the main reason for performance increase?

[zielar]

Something does not suit me here...
In the original version - four GPU's gave me a score of 6800-7000Mkeys/s.
Current version - keeping the same settings (I only replaced the .exe file) shows 42000-43000Mkeys/s.

This is not possible, especially since the prefix discovery speed has not changed and the GPUs in NVIDIA-SMI themselves show power consumption instead of 240-250W, now 190-200W.

[Jean_Luc]

Hi,

What was the main reason for performance increase?

I optimized a bit the GPU code for compressed key, GPU/GPUHash.h and GPU/GPUCompute.h.
More or less, I factored a bit the HASH calculation of symmetric keys and I added some _synchthreads() in order to try to keep a best synchronization between threads. This gives me a ~5% performance increase on my hardware.

please tell me how to run on radeon rx 570?

VanitySearch supports only CUDA.

Something does not suit me here...
In the original version - four GPU's gave me a score of 6800-7000Mkeys/s.
Current version - keeping the same settings (I only replaced the .exe file) shows 42000-43000Mkeys/s.

This is not possible, especially since the prefix discovery speed has not changed and the GPUs in NVIDIA-SMI themselves show power consumption instead of 240-250W, now 190-200W.

You mean 1.16 gives  6800-7000Mkeys/s and 1.17  42000-43000Mkeys/s ?
Did you wait a bit in order to stabilize the key rate measurement ?
Could you give me your grid size(s) ?

[Timelord2067]

Is there a windows walk through please?

[Jean_Luc]

Is there a windows walk through please?

The only informations available are there:
https://github.com/JeanLucPons/VanitySearch/blob/master/README.md
If you need furthers details, you can ask here.

[Timelord2067]

Is there a windows walk through please?

The only informations available are there:
https://github.com/JeanLucPons/VanitySearch/blob/master/README.md
If you need furthers details, you can ask here.

Alright, where can I find a VanitySearch.sln and where can I get a Visual C++ 2017 ?

[Jean_Luc]

Alright, where can I find a VanitySearch.sln and where can I get a Visual C++ 2017 ?

The sln file is included in the repository.
Start by cloning the repository (you need git to be installed)
git clone https://github.com/JeanLucPons/VanitySearch.git
Visual Studio community edition is freely available from the Microsoft Website (I don't know if 2017 can still be download but it should work also with 2019, if it is not working with 2019 then I'll try to make a path).
Then launch visual studio and open the sln file.

[Timelord2067]

Alright, where can I find a VanitySearch.sln and where can I get a Visual C++ 2017 ?

The sln file is included in the repository.
Start by cloning the repository (you need git to be installed)
git clone https://github.com/JeanLucPons/VanitySearch.git
Visual Studio community edition is freely available from the Microsoft Website (I don't know if 2017 can still be download but it should work also with 2019, if it is not working with 2019 then I'll try to make a path).
Then launch visual studio and open the sln file.

I've updated to version 10.2 of the Nvidia Cuda and tried running the program. It works for a few seconds - hangs - then crashes.  Other parts of NVidia are now asking to be updated, so am just working on them too.

[Jean_Luc]

I've updated to version 10.2 of the Nvidia Cuda and tried running the program. It works for a few seconds - hangs - then crashes.  Other parts of NVidia are now asking to be updated, so am just working on them too.

It seems that there is some problems with recent release of CUDA. I will also try to have a look at this. Thanks for you report.

[bangbumbang]

Hey
@Jean_Luc
and

I've updated to version 10.2 of the Nvidia Cuda and tried running the program. It works for a few seconds - hangs - then crashes.  Other parts of NVidia are now asking to be updated, so am just working on them too.

yep 10.2 is the problem.. when I tried 10.0 it worked I think.. though I didn't have time jet to run it more than a few minutes.. I did not test 10.1

[Timelord2067]

So far I have only installed (upgraded) NVidia Cuda to Ver 10.2

I have this as my command:

Code:

VanitySearch_V1.17>vanitysearch -g 5x,128y -i find.txt -o findout.txt -stop

Not sure what I'm supposed to put at

Code:

-gpu

regardless it starts then crashes.


This is a typical output.

Code:

VanitySearch v1.17
Search: 5 prefixes (Lookup size 5) [Compressed]
Start Wed Feb  5 15:09:14 2020
Base Key: F2957B149DAE0AF5CD7D4ECBC8AC163D552EF4FD8AB9F54AC3DBF93B9EDA91F8
Number of CPU thread: 2

But nothing is written to file.


*edit* Still can't find a VanitySearch.sln file.