VanitySearch (Yet another address prefix finder)

[citb0in]

Thank you.

[minime99999]

why do i occasionally get this error after running the program for few hours?


Start Sun Jan  1 00:21:00 2023
Base Key: C6AB3FFC716A4DF46849D6887E7327EE78DE482B370BB5AF58DD815F5A449504
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce GTX 1050 Ti (6x128 cores) Grid(48x128)
[106.21 Mkey/s][GPU 106.21 Mkey/s][Total 2^40.40][Prob 0.0%][50% in 3.02455e+32y][Found 0]  GPUEngine: Launch: unknown error

[WhyFhy]

why do i occasionally get this error after running the program for few hours?


Start Sun Jan  1 00:21:00 2023
Base Key: C6AB3FFC716A4DF46849D6887E7327EE78DE482B370BB5AF58DD815F5A449504
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce GTX 1050 Ti (6x128 cores) Grid(48x128)
[106.21 Mkey/s][GPU 106.21 Mkey/s][Total 2^40.40][Prob 0.0%][50% in 3.02455e+32y][Found 0]  GPUEngine: Launch: unknown error

What version are of VS you running?
What version of cuda?
It's a Cuda error.

[nc50lc]

why do i occasionally get this error after running the program for few hours?

Since it run for hours, look for hardware or software issues specially the GPU and its driver.
You're basically straining the GPU's processes for hours so hardware issues that's not occurring at idle may show symptoms.
If it's Vanitysearch, you should get errors right off the bat.

Is there any additional command line options that you've added?

[hodld0r]

bech32m support incoming? 🤔

[minime99999]

hi
im getting memory error.
when I loaded 6219 prefixes (no error), but when i loaded 82 full address i get "illegal memory access error", when i reduce the full address to 15 addresses, it worked.
I ran GPU memory test and it says no error.

any idea what is the problem?



[Building lookup32 100.0%]
Search: 6219 prefixes (Lookup size 2) [Compressed]
Start Tue Jan  3 21:29:45 2023
Base Key: BD6291C1DE2447068E663194E0DDFBE0C72CD78A8177B51CAE080716AD7496F3
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce RTX 2060 SUPER (34x64 cores) Grid(272x128)
[404.78 Mkey/s][GPU 404.78 Mkey/s][Total 2^32.43][Prob 31.4%][50% in 00:00:11][Found 33]  ^C
C:\Users\abc\Desktop>


C:\Users\abc\Desktop>VanitySearch.exe -stop -i addresses.txt -o found.txt -t 0 -gpu
VanitySearch v1.19
Search: 82 addresses (Lookup size 82,[1,1]) [Compressed]
Start Tue Jan  3 21:32:26 2023
Base Key: 5323DAB06CE0DAC8D3C8E5191F1D6DA70ABFC8F6D9188B89C186845E543C2674
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce RTX 2060 SUPER (34x64 cores) Grid(272x128)
GPUEngine: Launch: an illegal memory access was encountered


C:\Users\abc\Desktop>VanitySearch.exe -stop -i addresses.txt -o found.txt -t 0 -gpu
VanitySearch v1.19
Search: 15 addresses (Lookup size 15,[1,1]) [Compressed]
Start Tue Jan  3 21:32:34 2023
Base Key: A6D841113DFC9539F68F8FF5345D7AECC1A62A4A3651FD86ECF6D3696C3A9644
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce RTX 2060 SUPER (34x64 cores) Grid(272x128)
[1295.00 Mkey/s][GPU 1295.00 Mkey/s][Total 2^32.88][Prob 0.0%][50% in 2.48055e+31y][Found 0]

[WhyFhy]

hi
im getting memory error.
when I loaded 6219 prefixes (no error), but when i loaded 82 full address i get "illegal memory access error", when i reduce the full address to 15 addresses, it worked.
I ran GPU memory test and it says no error.

any idea what is the problem?



[Building lookup32 100.0%]
Search: 6219 prefixes (Lookup size 2) [Compressed]
Start Tue Jan  3 21:29:45 2023
Base Key: BD6291C1DE2447068E663194E0DDFBE0C72CD78A8177B51CAE080716AD7496F3
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce RTX 2060 SUPER (34x64 cores) Grid(272x128)
[404.78 Mkey/s][GPU 404.78 Mkey/s][Total 2^32.43][Prob 31.4%][50% in 00:00:11][Found 33]  ^C
C:\Users\abc\Desktop>


C:\Users\abc\Desktop>VanitySearch.exe -stop -i addresses.txt -o found.txt -t 0 -gpu
VanitySearch v1.19
Search: 82 addresses (Lookup size 82,[1,1]) [Compressed]
Start Tue Jan  3 21:32:26 2023
Base Key: 5323DAB06CE0DAC8D3C8E5191F1D6DA70ABFC8F6D9188B89C186845E543C2674
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce RTX 2060 SUPER (34x64 cores) Grid(272x128)
GPUEngine: Launch: an illegal memory access was encountered


C:\Users\abc\Desktop>VanitySearch.exe -stop -i addresses.txt -o found.txt -t 0 -gpu
VanitySearch v1.19
Search: 15 addresses (Lookup size 15,[1,1]) [Compressed]
Start Tue Jan  3 21:32:34 2023
Base Key: A6D841113DFC9539F68F8FF5345D7AECC1A62A4A3651FD86ECF6D3696C3A9644
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce RTX 2060 SUPER (34x64 cores) Grid(272x128)
[1295.00 Mkey/s][GPU 1295.00 Mkey/s][Total 2^32.88][Prob 0.0%][50% in 2.48055e+31y][Found 0]

Again.
What version are of VS you running?
What version of cuda?
It's a probably a Cuda error combined with a poor VM setup.
We need more information.
And initial feedback to previous suggestions would help us troubleshoot. 

[minime99999]

hi
im getting memory error.
when I loaded 6219 prefixes (no error), but when i loaded 82 full address i get "illegal memory access error", when i reduce the full address to 15 addresses, it worked.
I ran GPU memory test and it says no error.

any idea what is the problem?



[Building lookup32 100.0%]
Search: 6219 prefixes (Lookup size 2) [Compressed]
Start Tue Jan  3 21:29:45 2023
Base Key: BD6291C1DE2447068E663194E0DDFBE0C72CD78A8177B51CAE080716AD7496F3
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce RTX 2060 SUPER (34x64 cores) Grid(272x128)
[404.78 Mkey/s][GPU 404.78 Mkey/s][Total 2^32.43][Prob 31.4%][50% in 00:00:11][Found 33]  ^C
C:\Users\abc\Desktop>


C:\Users\abc\Desktop>VanitySearch.exe -stop -i addresses.txt -o found.txt -t 0 -gpu
VanitySearch v1.19
Search: 82 addresses (Lookup size 82,[1,1]) [Compressed]
Start Tue Jan  3 21:32:26 2023
Base Key: 5323DAB06CE0DAC8D3C8E5191F1D6DA70ABFC8F6D9188B89C186845E543C2674
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce RTX 2060 SUPER (34x64 cores) Grid(272x128)
GPUEngine: Launch: an illegal memory access was encountered


C:\Users\abc\Desktop>VanitySearch.exe -stop -i addresses.txt -o found.txt -t 0 -gpu
VanitySearch v1.19
Search: 15 addresses (Lookup size 15,[1,1]) [Compressed]
Start Tue Jan  3 21:32:34 2023
Base Key: A6D841113DFC9539F68F8FF5345D7AECC1A62A4A3651FD86ECF6D3696C3A9644
Number of CPU thread: 0
GPU: GPU #0 NVIDIA GeForce RTX 2060 SUPER (34x64 cores) Grid(272x128)
[1295.00 Mkey/s][GPU 1295.00 Mkey/s][Total 2^32.88][Prob 0.0%][50% in 2.48055e+31y][Found 0]

Again.
What version are of VS you running?
What version of cuda?
It's a probably a Cuda error combined with a poor VM setup.
We need more information.
And initial feedback to previous suggestions would help us troubleshoot. 

thx for the reply.
nvm i just return the card, could be faulty.

[nc50lc]

im getting memory error.
when I loaded 6219 prefixes (no error), but when i loaded 82 full address i get "illegal memory access error", when i reduce the full address to 15 addresses, it worked.

Now, this is an entirely different issue from your first post, I presume?
Because the command line doesn't show that it stopped after running for hours.

For that error, it's could be the issue when searching for multiple full addresses with Nvidia GPU, try to downgrade to v1.17.
Reference (issue #81): https://github.com/JeanLucPons/VanitySearch/issues/81#issuecomment-745085166

[minime99999]

how to ask vanitysearch to search for classic bitcoin address and segwit too?

[NotATether]

PSA: If you're getting:

Code:

/usr/bin/ld: obj/main.o: in function `std::vector<int, std::allocator<int> >::vector(std::vector<int, std::allocator<int> > const&)':
main.cpp:(.text._ZNSt6vectorIiSaIiEEC2ERKS1_[_ZNSt6vectorIiSaIiEEC5ERKS1_]+0x96): undefined reference to `std::__throw_bad_array_new_length()'
collect2: error: ld returned 1 exit status

while compiling VanitySearch, you need to clear the object files and rebuild the project with:

Code:

make clean
make

It's a GCC bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71757 (despite being closed as WONTFIX, it still pops around apparently) so it should not affect Windows and Visual Studio doesn't need any fix.


Anyone knows how I can add a 3rd party lib to a Visual Studio project?

how to ask vanitysearch to search for classic bitcoin address and segwit too?

It will detect the "1" or "3" or "bc1" at the beginning and automatically choose the correct address type.

[citb0in]

how to ask vanitysearch to search for classic bitcoin address and segwit too?

(P2PKH, P2SH or BECH32 allowed at once)

you cannot mix them up. You have to run and search for a bc1q... address and later on you could run a search for a 1... address

[NotATether]

A strange error happens when I run my custom build of VanitySearch in non-debug mode - I get:

"Warning wrong private key generated!"

Keep in mind that I did not modify any key generation code, my mods were limited to adding regex support for the prefixes.

In the debug mode, it gets the address right every single time. So what gives?

[citb0in]

what's the output of

Code:

./VanitySearch -check

read HERE and HERE

try to compile with gcc 9 instead of the latest gcc 11

in Linux try to set optimization flag -O2 to -O1 in Makefile
In Windows / cygwin64 the same

try IntMod.cpp change

Code:

static Int _P; // Field characteristic in IntMod.cpp

to

Code:

static Int Field_P;

and all other occurences in file

[NotATether]

what's the output of

Code:

./VanitySearch -check

read HERE and HERE

try to compile with gcc 9 instead of the latest gcc 11

in Linux try to set optimization flag -O2 to -O1 in Makefile
In Windows / cygwin64 the same

try IntMod.cpp change

Code:

static Int _P; // Field characteristic in IntMod.cpp

to

Code:

static Int Field_P;

and all other occurences in file

VanitySearch -check unit test is failing because of "Invalid private key checksum", and indeed, all parts of the address are equal except for the checksum part. So I will investigate this.

I'll be surprised if this bug is in JLP's VanitySearch build as well.

[citb0in]

I'll be surprised if this bug is in JLP's VanitySearch build as well.

original VanitySearch of JLP works fine, no issues. We certainly would heard about existing bugs

[NotATether]

Anyone want to lend me their GPU for a few days so I can fix my broken VanitySearch build (and maybe Kangaroo as well as people are starting to complain about the hash table not working and stuff)?

I have $10 in Vast.ai from a while ago but the card used to find it has since expired and I have no way to fund it now.

[WanderingPhilospher]

Anyone want to lend me their GPU for a few days so I can fix my broken VanitySearch build (and maybe Kangaroo as well as people are starting to complain about the hash table not working and stuff)?

I have $10 in Vast.ai from a while ago but the card used to find it has since expired and I have no way to fund it now.

You want me to ship you one?

[NotATether]

Anyone want to lend me their GPU for a few days so I can fix my broken VanitySearch build (and maybe Kangaroo as well as people are starting to complain about the hash table not working and stuff)?

I have $10 in Vast.ai from a while ago but the card used to find it has since expired and I have no way to fund it now.

You want me to ship you one?

Well that won't really make any sense to me, as I only got (quite old) laptops handy at the moment, and the power utility is a b*tch.

I think just put it in a DIY box and slap some temporary SSH access on it for me to get in and debug VanitySearch should do the trick.

[citb0in]

Anyone want to lend me their GPU for a few days so I can fix my broken VanitySearch build (and maybe Kangaroo as well as people are starting to complain about the hash table not working and stuff)?

I have $10 in Vast.ai from a while ago but the card used to find it has since expired and I have no way to fund it now.

@NotATether
I've prepared a machine for you. Check your mailbox (DM)