VanitySearch (Yet another address prefix finder)

[Nika_e621]

WOW you are really true code master man, how long do you think will this take you to have a working GPU build?

Well, I wouldn't call myself that.  

citb0in actually asked me that question already, and we both thought it would take max. a week or two. This was in the beginning of January. But unfortunately (among other things) I discovered that adding the GPU support wasn't as simple as changing a few lines of code (and I refunded him his money last night).

So as it stands, there's only a working CPU build - just now I pushed the code that will enable you to run queries like "./VanitySearch ^1abc" to search for 1abc prefix at the beginning, and also you could already do ./VanitySearch 1abc$ to search for 1abc at the end of the address, and some other things I will list below.

Wildcard searches with *, +, and {m,n} work but they are not very useful as current hardware can only reasonably search for 6-7 characters at a time:

(difficulty estimation is currently wrong for {m,n} and will report much longer time than actual)


Character classes and quantifier example:

./VanitySearch -t 8 '^1[fF][iI].{2,4}[sS][hH]'

Code:

 time ./VanitySearch -t 8 '^1[fF][iI].{2,4}[sS][hH]'
VanitySearch v1.19
Benchmarking regex matching speed of prefix "^1[fF][iI].{2,4}[sS][hH]" (case sensitive) for 1 second, please wait... done
Difficulty: 9225725494
Search: ^1[fF][iI].{2,4}[sS][hH] [Compressed]
Start Tue Feb  7 12:12:39 2023
Base Key: CA21EDE5142917948E79FEFD98EBBB2E485ECA54E1C814B482C39A2C8B8D5B37
Number of CPU thread: 8

PubAddress: 1FiF7Sh6Ei8ezjMASNdED1ixyTZ9HY4DbP
Priv (WIF): p2pkh:Kxsq34CD5UBCqhRMZi4WNH1oQjnr3FHjzQqS2kEDb6CN3EpZYauo
Priv (HEX): 0x317261FB480D6C92F777B4F3B18176433CAED4D61E8A3E507A0414E3A6BCCAD4

PubAddress: 1FiZ9bmpedPk1ksHRtUtZEDZ2n7fNz68LP
Priv (WIF): p2pkh:L3zdVyH3kWaRtzJ4eLEc6FwcbrzBRpVgoPZjCC3Gq1d2ZCEENuM6
Priv (HEX): 0xCA21EDE5142917948E79FEFD98EBBB31485ECA54E1C814B782C39A2C8B8D6ACE
[0.20 Mkey/s][GPU 0.00 Mkey/s][Total 2^18.63][Prob 0.0%][50% in 08:45:41][Found 2]
PubAddress: 1FidbgsHsR9B2iEu5KkfYxRE7SPjadWSiS
Priv (WIF): p2pkh:L12uW3KSdEkLQzPutC9E6cpGJe6w9R9udHi4tLCrVEJKkCeikoJJ
Priv (HEX): 0x71CA8897DFCA52F8649A489E5C34216517D724D6E9710FE937FEE419F019AA9F
[0.19 Mkey/s][GPU 0.00 Mkey/s][Total 2^19.55][Prob 0.0%][50% in 09:15:06][Found 3]  ^C

real    0m8.447s
user    0m51.466s
sys     0m0.075s

Note: Make sure you put the regex in single quotes '' otherwise bash might mess them up!

Anyway, I'm going to try to optimize the CPU build first before working on the GPU (regex mode is currently 2x slower than non-regex mode), maybe put some SSE or AVX in there somehow.

When I try to run "c:\Users\Main\VanitySearch.exe -t 8 '^1[fF][iI].{2,4}[sS][hH]'" in Windows, it says "Ignoring prefix " -t 8 '^1[fF][iI].{2,4}[sS][hH]'" (must start with 1 or 3 or bc1q)", does anyone know what I'm doing wrong?

[citb0in]

Simply said, the version you're referring to is broken and not working correctly. This is an unofficial version where NotATether tried to implement regex funcationality but it does not work as expected, there are lots of bugs. I do not recommend to use and rely on it. Your mileage may vary. Good luck though

citb0in

[Nika_e621]

Simply said, the version you're referring to is broken and not working correctly. This is an unofficial version where NotATether tried to implement regex funcationality but it does not work as expected, there are lots of bugs. I do not recommend to use and rely on it. Your mileage may vary. Good luck though

citb0in

It's from "https://github.com/JeanLucPons/VanitySearch/releases", I thought that this is the official version but if it's not, where can I get the official version?

[NotATether]

Simply said, the version you're referring to is broken and not working correctly. This is an unofficial version where NotATether tried to implement regex funcationality but it does not work as expected, there are lots of bugs. I do not recommend to use and rely on it. Your mileage may vary. Good luck though

citb0in

Don't use that version, it's been unmaintained for a couple of years 

[citb0in]

Simply said, the version you're referring to is broken and not working correctly. This is an unofficial version where NotATether tried to implement regex funcationality but it does not work as expected, there are lots of bugs. I do not recommend to use and rely on it. Your mileage may vary. Good luck though

citb0in

It's from "https://github.com/JeanLucPons/VanitySearch/releases", I thought that this is the official version but if it's not, where can I get the official version?

You obviously confusing two different programs. The original one is from JLP and this version does not support RegEx. This genuine applications works fine ! but it does not support RegEx

The other version was a fork from NotATether where he tried to implement RegEx funcationality. It does not work correctly and you should avoid using it. Just my coins

[nc50lc]

It's from "https://github.com/JeanLucPons/VanitySearch/releases", I thought that this is the official version but if it's not, where can I get the official version?

That link is the official version.
The command provided by NotATether will only work in his experimental build.

When I try to run "c:\Users\Main\VanitySearch.exe -t 8 '^1[fF][iI].{2,4}[sS][hH]'" in Windows, it says "Ignoring prefix " -t 8 '^1[fF][iI].{2,4}[sS][hH]'" (must start with 1 or 3 or bc1q)", does anyone know what I'm doing wrong?

For the official version, just start it with your preferred args followed by your address prefix.
e.g.: VanitySearch.exe -stop bc1qsegwt
use: VanitySearch.exe -h to see all the available options.

[Nika_e621]

ok, now it makes sense, thank you guys for clarifying that for me, appreciate it 👍

[NotFuzzyWarm]

Interesting: Just ran some tests to generate my new non-legacy donation address seen in my sig.
EDIT: Having issues importing the new Bech32 address into Blockchain.com so reverted back to original Legacy tips address

Tested times using Legacy (1), Segwit (3) and Bech32 (btc1q) prefixes and was astounded at the reported times to generate it. For all of them the same 9 characters (FuzzyWarm) were added to the prefix.

Hardware is my ThinkPad P15 workstation laptop using Vanity Search1.19
CPU is Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz, reports 57% usage
16GB ram
GPU is nVidia Quadro T1000 (14x64 cores), reports 80% usage
All runs are using GPU and 6 of the 12 core threads.

Speeds:
   Legacy speed:  [541.45 Mkey/s][GPU 516.45 Mkey/s][Total 2^34.46][Prob 0.0%][50% in 44.5d][Found 0]
   Segwit speed:  [288.25 Mkey/s][GPU 271.25 Mkey/s][Total 2^31.43][Prob 0.0%][50% in 83.6d][Found 0]
   Bech32 speed: [545.76 Mkey/s][GPU 515.95 Mkey/s][Total 2^32.36][Prob 0.0%][50% in 12:24:35][Found 0]

Summary of initial reported times:
    Legacy 44.5 DAYS
    Segwit 83.6 DAYS
    Bech32 12.5 hrs

Bech32 is the clear winner for speed and was the only one allowed to run to completion & generate my new address, run time was 17hrs 42min.

Question for OP: Why are Legacy and Segwit search times so astonishingly long vs Bech32 search time?

[LoyceV]

Why are Legacy and Segwit search times so astonishingly long vs Bech32 search time?

Bech32 addresses aren't case sensitive. Or better: they're only lower-case, so there are less possibilities per position.

[alexeyneu]

The other version was a fork from NotATether where he tried to implement RegEx funcationality. It does not work correctly and you should avoid using it. Just my coins

idk who is author but there's vanitygen which supports regex and is included say to archlinux via aur .