VanitySearch (Yet another address prefix finder)

[Angelo1710]

How do you change keyspace in vanitysearch? Let's say I want to run in 160bit+ space.

Tnx

[1713292580]

1713292580

[1713292580]

1713292580

[1713292580]

1713292580

[1713292580]

1713292580

[1713292580]

1713292580

[1713292580]

1713292580

[dextronomous]

hi there angelo1710.

i really can't tell, don't really know a lot about it. wish i did. guess range is not same as seed -s seed: Specify a seed for the base key, default is random,?

>powershell Get-Date && VanitySearch-1.15_bitcrack -stop -t 0 -gpu -gpuId 0 -r 10000 ---keyspace 8000000000000000000000000000000000000000

Starting at PrivKey: 8000000000000000000000000000000000000000  - guess here it starts
care for the beer soon.

[airppc]

Hi,

Here is the results with GeForce RTX 2060 SUPER!

why Uncompressed speed is lower then Compressed with vanitysearch?
oclvanitygen can make both compressions in same speed.
any tricks/help to improve Uncompressed speeds as compressed?
because i need Uncompressed only.

Code:

oclvanitygen:
[compressed]
[164.75 Mkey/s][total 1336934400][Prob 0.0%][50% in 2.5d]
[Uncompressed]
[151.58 Mkey/s][total 1880621056][Prob 0.0%][50% in 2.7d]

Code:

vanitysearch:
[Compressed]
GPU: GPU #0 GeForce RTX 2060 SUPER (34x64 cores) Grid(272x256)
[1361.71 Mkey/s][GPU 1361.71 Mkey/s][Total 24.39 Bkeys][Prob 2.7%][50% in 00:07:14][Found 0]

[Uncompressed]
GPU: GPU #0 GeForce RTX 2060 SUPER (34x64 cores) Grid(272x256)
[827.71 Mkey/s][GPU 827.71 Mkey/s][Total 20.96 Bkeys][Prob 2.3%][50% in 00:11:58][Found 0]

[Compressed or Uncompressed]
GPU: GPU #0 GeForce RTX 2060 SUPER (34x64 cores) Grid(272x256)
[519.94 Mkey/s][GPU 519.94 Mkey/s][Total 13.26 Bkeys][Prob 1.5%][50% in 00:19:18][Found 0]

[WhyFhy]

Hi,

Here is the results with GeForce RTX 2060 SUPER!

why Uncompressed speed is lower then Compressed with vanitysearch?
oclvanitygen can make both compressions in same speed.
any tricks/help to improve Uncompressed speeds as compressed?
because i need Uncompressed only.

oclvanitygen:
[compressed]
[164.75 Mkey/s][total 1336934400][Prob 0.0%][50% in 2.5d]
[Uncompressed]
[151.58 Mkey/s][total 1880621056][Prob 0.0%][50% in 2.7d]

vanitysearch:
[Compressed]
GPU: GPU #0 GeForce RTX 2060 SUPER (34x64 cores) Grid(272x256)
[1361.71 Mkey/s][GPU 1361.71 Mkey/s][Total 24.39 Bkeys][Prob 2.7%][50% in 00:07:14][Found 0]
[Uncompressed]
GPU: GPU #0 GeForce RTX 2060 SUPER (34x64 cores) Grid(272x256)
[827.71 Mkey/s][GPU 827.71 Mkey/s][Total 20.96 Bkeys][Prob 2.3%][50% in 00:11:58][Found 0]
[Compressed or Uncompressed]
GPU: GPU #0 GeForce RTX 2060 SUPER (34x64 cores) Grid(272x256)
[519.94 Mkey/s][GPU 519.94 Mkey/s][Total 13.26 Bkeys][Prob 1.5%][50% in 00:19:18][Found 0]

You must be the one solving the work this week. Noticed the list is diminishing

[WhyFhy]

Im a little flusterd to see someone worked out the bug on solutions and hasnt shared it.

[Angelo1710]

If we use -r flag for re-key and we set it to let's say 1M, does that mean program will use random base key every 1M keys? Would that work with higher speeds? When I try to use -r and I set it up to 1M then I get max speed of 35MK/s (uncompressed). Probably that is maximum that it can calculate when you use very low re-key number for base key.

[MeBender]

Code:

C:\users\default\vanitygen>vanitysearch -gpu -o vs.txt -g 4480 -t 0 1FeexV6b
VanitySearch v1.15
Difficulty: 888446610539
Search: 1FeexV6b [Compressed]
Start Mon Sep 16 05:14:20 2019
Base Key: C85DB0A401AC6C5BA884366178067CBA2F3E43DDAA5AF0634FD004DA96B652D7
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1080 Ti (28x128 cores) Grid(4480x128)
5757943931943.335 MK/s (GPU 5757943931943.335 MK/s) (2^64.00) [P 100.00%][99.00% in 00:00:00][0]

This is an error right? lol

[WhyFhy]

Code:

-snipped  [P 100.00%][99.00% in 00:00:00][0]

This is an error right? lol

No just unlucky. keep trying!


edit just noticed the keypsec count somethings off

[airppc]

Results with GeForce RTX 2080 SUPER!

Code:

oclvanitygen:
[Compressed]
[272.99 Mkey/s][total 1119879168][Prob 0.0%][50% in 1.579412e+008y]
[Uncompressed]
[247.86 Mkey/s][total 1509949440][Prob 0.0%][50% in 1.739557e+008y]

Code:

vanitysearch:
[Compressed]
GPU: GPU #0 GeForce RTX 2080 SUPER (48x64 cores) Grid(384x256)
[2001.52 Mkey/s][GPU 2001.52 Mkey/s][Total 24.76 Bkeys][Prob 0.0%][50% in 12.0d][Found 0]
[Uncompressed]
GPU: GPU #0 GeForce RTX 2080 SUPER (48x64 cores) Grid(384x256)
[1244.88 Mkey/s][GPU 1244.88 Mkey/s][Total 10.27 Bkeys][Prob 0.0%][50% in 19.3d][Found 0]
[Compressed or Uncompressed]
GPU: GPU #0 GeForce RTX 2080 SUPER (48x64 cores) Grid(384x256)
[780.01 Mkey/s][GPU 780.01 Mkey/s][Total 15.10 Bkeys][Prob 0.0%][50% in 30.9d][Found 0]

is there any way to increase Uncompressed speed like Compressed search?

[MeBender]

Code:

-snipped  [P 100.00%][99.00% in 00:00:00][0]

This is an error right? lol

No just unlucky. keep trying!


edit just noticed the keypsec count somethings off

Yeah I set the grid to 4480x128 and it gave me crazy Mkey/s

[solokol]

I have vanitysearch:
[Compressed]
GPU: GPU #0 GeForce RTX 2080 SUPER (48x64 cores) Grid(384x128)
[1886 Mkey/s][GPU 1852 Mkey/s][Total 55 Bkeys][Prob 0.0%][50% in 56.0d][Found 0]

[Chris!]

Does anyone have any basic steps on getting this to run on a debian based Linux OS?

[asche]

Does anyone have any basic steps on getting this to run on a debian based Linux OS?

Actually this is detailed on Jean-Luc's github page. The compilation steps are pretty straight forward.

Linux
Intall CUDA SDK.
Depenging on the CUDA SDK version and on your Linux distribution you may need to install an older g++ (just for the CUDA SDK).
Edit the makefile and set up the good CUDA SDK path and appropriate compiler for nvcc.

CUDA       = /usr/local/cuda-8.0
CXXCUDA    = /usr/bin/g++-4.8
You can enter a list of architectrure (refer to nvcc documentation) if you have several GPU with different architecture. Compute capability 2.0 (Fermi) is deprecated for recent CUDA SDK. VanitySearch need to be compiled and linked with a recent gcc (>=7). The current release has been compiled with gcc 7.3.0.
Go to the VanitySearch directory. ccap is the desired compute capability.

$ g++ -v
gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
$ make all (for build without CUDA support)
or
$ make gpu=1 ccap=20 all

https://github.com/JeanLucPons/VanitySearch#linux

If you need help don't hesitate to mention my name, I will do my best to assist you.

[WhyFhy]

Telariust

what are you currently working?youve been a great help in this endeavor, I'd like to work rastafari this week if your not.

[destansi]

( VanitySearch-1.15.2_bitcrack.exe -gpu -b -t 0 -i balans1.txt -o buldu.txt )
This is how my command performs sequential searches. I've experimented and found the address in 4.5 million addresses. The program is successful. So what do I need to add to my command to run a random scan if it's not sequential?
Will AMD cards work in the future? Do you have any work on this?

[Dabs]

Does anyone know how to use this VanitySearch to find ALL UPPERCASE LETTERS only (with or without numbers)? I'd like to do it with addresses starting with 3. I can do 3DABS ... I can't seem to find the regex thing or if anyone has done it already.

[zielar]

Does anyone know how to use this VanitySearch to find ALL UPPERCASE LETTERS only (with or without numbers)? I'd like to do it with addresses starting with 3. I can do 3DABS ... I can't seem to find the regex thing or if anyone has done it already.

If you set prefix 3DABS - the application will only inform / save found prefixes exactly as you indicated (only with uppercase letters).
You can set the parameter specifying the case-insensitivity by adding "-c" to the startup command (this is case insensitivity).
I don't know if that was the point :-) Anticipating the facts, when you are looking for ONLY the whole addresses consisting of uppercase letters - here you have the version: https://github.com/skipper70/VanitySearch ... unfortunately it is a lot slower because the search method for such results needs more resources.
I hope the information is helpful.

[000xxxfff]

Hi. C:\VanitySearch\VanitySearch.exe -o A:\result.txt -nosse -c 3P
3P112wcuMsGWJ1jLAouxu5tDwTzKUJGjyN
3P114dg7NYteQctAmS8cgGt3c3cJxeMJJ6
3P11gVc4n7wVizvku88ic1yydNwa5GY5ae
and etc
Why are addresses not randomly generated?

[Dabs]

Looks random to me, except if you meant 3P11***. Try a different prefix and see what it shows.

[000xxxfff]

C:\VanitySearch\VanitySearch.exe -o A:\result.txt -nosse 3E
3E11oBnqGw3cwkk6U4ekid3xm6LjA8F3mm
3E11UemvQxkVTY6KMuqmwfb2utfi3i2rFB
3E11PHRhUXNiqcyuMzEo8kTNFJNNDbrmBn
3E11nkf3TXRKMeHPRMS61yKECaYREFB2uD
random goes after 4 characters