Pages:
Author

Topic: VanitySearch (Yet another address prefix finder) (Read 33086 times)

legendary
Activity: 3808
Merit: 7912
I got curious and tested this on my new setup aswell.
I use "vanitysearch.exe -stop -gpu bc1q....." and I'm getting 2200 Mkey/s on my 4060TI paired with an i7 14700k (undervolted).
However my CPU is at 100% usage and my GPU shows 1-2% in task manager. Is this normal or is my gpu not putting out enough work here?

 I just tested that with mine and task manager shows ~100% for both CPU and GPU.  I haven't changed the voltage settings on my CPU though - the only thing I've done is to flash the mobo to the latest bios before I started playing with it.
 
legendary
Activity: 1092
Merit: 1125
I got curious and tested this on my new setup aswell.
I use "vanitysearch.exe -stop -gpu bc1q....." and I'm getting 2200 Mkey/s on my 4060TI paired with an i7 14700k (undervolted).
However my CPU is at 100% usage and my GPU shows 1-2% in task manager. Is this normal or is my gpu not putting out enough work here?
legendary
Activity: 3808
Merit: 7912
Just fired up my new computer with an RTX4070 Super and I'm getting ~3700 Mkeys/s on single prefix searches.  Wow.
As an added bonus, I didn't have to fool around installing the CUDA SDK which was a nice surprise.
full member
Activity: 1232
Merit: 242
Shooters Shoot...
Have you tried to rent GPU from vast.ai?
Nope.

Quote
but the problem is that I don't know how to do that. If you know how to do that and find this experiment funny like I do, then I'll pay the rent price of a few hours (you can use it to solve your problem).
I know my way around a VPS, but I'd have no idea how to get a GPU on a server working for this.



Two days ago, xhomerx10 got me 13soLUTioNvEDH5E4mxRDVo2q5JZHg3xwT. It triggers my OCD to not have a digit after "solution", but considering it's difficulty, and the low chance of having this word in a seed phrase, 1 out of 2048 being imperfect will have to do Smiley
I just sent you a "1solution" that meets your OCD criteria Smiley
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
Have you tried to rent GPU from vast.ai?
Nope.

Quote
but the problem is that I don't know how to do that. If you know how to do that and find this experiment funny like I do, then I'll pay the rent price of a few hours (you can use it to solve your problem).
I know my way around a VPS, but I'd have no idea how to get a GPU on a server working for this.



Two days ago, xhomerx10 got me 13soLUTioNvEDH5E4mxRDVo2q5JZHg3xwT. It triggers my OCD to not have a digit after "solution", but considering it's difficulty, and the low chance of having this word in a seed phrase, 1 out of 2048 being imperfect will have to do Smiley
hero member
Activity: 882
Merit: 792
Watch Bitcoin Documentary - https://t.ly/v0Nim
Did we have overview what for a Speed we get with a NVIDIA 4080 or 4090 card?
Or any other better cards, that we know for highspeed with vanitysearch.

I would like put my 3 NVIDIA 3070 out and buy the latest top model if i have the information, how the speed is.

Best regards,
Willi
I think that the best way for an individual to test the hashrate of any top GPU in VanitySearch is to rent a GPU online and run VanitySearch. It costs a few cents per hour to rent as powerful GPU as RTX 4090 is.

I don't need it for anything secure*
~
* This is for another time, when I'm done Smiley
Would someone with VanitySearch with high hash rates on GPU be willing to help me out? I'm trying to build a "vanity address version" of the BIP39 word list (2048 words). I've processed most words already, and used all lower or all upper case when possible, but now I'm stuck on the long words, and my poor old laptop is having a hard time crunching the last 10% of the longest words. If anyone's willing to help me create uncompressed addresses (case insensitive), I can complete my list. I don't mind if you know the private keys. I have a list of missing prefixes, all ending on [1-9] to distinguish the words from the rest of the address.
I know that WanderingPhilospher already helped you but I have a question. Have you tried to rent GPU from vast.ai? It's very cheap and I think it will be nice and funny to rent lots of 4090 GPU or any other GPU that will have the best hashrate to cost ratio and try to generate a vanity address but the problem is that I don't know how to do that. If you know how to do that and find this experiment funny like I do, then I'll pay the rent price of a few hours (you can use it to solve your problem).
jr. member
Activity: 37
Merit: 68
I'll create a new topic for my BIP38<>BIP39 project later.

Does this mean your upcoming project is for the Vanity Address generation but via mnemonics?
Will be interesting.
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
Would someone with VanitySearch with high hash rates on GPU be willing to help me out? I'm trying to build a "vanity address version" of the BIP39 word list (2048 words). I've processed most words already, and used all lower or all upper case when possible, but now I'm stuck on the long words, and my poor old laptop is having a hard time crunching the last 10% of the longest words. If anyone's willing to help me create uncompressed addresses (case insensitive), I can complete my list. I don't mind if you know the private keys. I have a list of missing prefixes, all ending on [1-9] to distinguish the words from the rest of the address.
WanderingPhilospher already helped me out a lot, and I now have 2028 out of 2048 the required addresses. See: loyce.club/other/keys.txt if you're interested. I'll create a new topic for my BIP38<>BIP39 project later.
I'm missing those:
Code:
DONE!

If anyone is willing to throw some hashrate at this, I've made it "easier" by creating 90 potential prefixes for each word:
Code:
GONE!
I'm looking for 1 uncompressed legacy address for each prefix to complete my set. Considering the difficulty, case-insensitive is totally fine.

Update: the "missing" list keeps getting shorter is gone Smiley
full member
Activity: 1232
Merit: 242
Shooters Shoot...
I don't need it for anything secure*
~
* This is for another time, when I'm done Smiley
Would someone with VanitySearch with high hash rates on GPU be willing to help me out? I'm trying to build a "vanity address version" of the BIP39 word list (2048 words). I've processed most words already, and used all lower or all upper case when possible, but now I'm stuck on the long words, and my poor old laptop is having a hard time crunching the last 10% of the longest words. If anyone's willing to help me create uncompressed addresses (case insensitive), I can complete my list. I don't mind if you know the private keys. I have a list of missing prefixes, all ending on [1-9] to distinguish the words from the rest of the address.
Send me the list of missing prefixes, let me take a look at how many and the difficulty. I could run some hash at it.
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
what happens if you run

Code:
./VanitySearch 1try
Code:
./VanitySearch -i input.txt
Code:
./VanitySearch 1try -o output.txt
I still get the errors. It's just that writing output to a file instead of console makes it more obvious, because not every key leads to the error.

I can't tell if compiling g++-9 will solve it, even after installing it, make can't find g++-9. Either way:
I'll just stick to the wine solution with the Windows executable.
It's not that important (for now). If I'll ever get my GPU working for this, I'll give it another try.



I don't need it for anything secure*
~
* This is for another time, when I'm done Smiley
Would someone with VanitySearch with high hash rates on GPU be willing to help me out? I'm trying to build a "vanity address version" of the BIP39 word list (2048 words). I've processed most words already, and used all lower or all upper case when possible, but now I'm stuck on the long words, and my poor old laptop is having a hard time crunching the last 10% of the longest words. If anyone's willing to help me create uncompressed addresses (case insensitive), I can complete my list. I don't mind if you know the private keys. I have a list of missing prefixes, all ending on [1-9] to distinguish the words from the rest of the address.

Mod note: Consecutive posts merged
hero member
Activity: 630
Merit: 731
Bitcoin g33k
Yes, that's indeed related. I forgot to mention that.

@LoyceV: try following additional step...

edit the file "Makefile" and search for the line

Quote
CXX        = g++

then replace it by

Quote
CXX        = g++-9

and execute
Code:
make clean
Code:
make

finally try again your run and see if this solved your issue. Wish you good luck bro
legendary
Activity: 1612
Merit: 1608
精神分析的爸
This helped me:

https://github.com/JeanLucPons/VanitySearch/issues/81#issuecomment-2284606604

And the tip I posted in your other thread fixed that too.
hero member
Activity: 630
Merit: 731
Bitcoin g33k
what does your command look like, I'm curious.

I cannot reproduce this on my side.
I used:
Code:
./VanitySearch -i input.txt -o output.txt
I get the Warning many times per second. It still addes keys to output.txt too, and I guess those are correct. But to avoid all this hassle, I just use the wine version.

what happens if you run

Code:
./VanitySearch 1try
Code:
./VanitySearch -i input.txt
Code:
./VanitySearch 1try -o output.txt
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
what does your command look like, I'm curious.

I cannot reproduce this on my side.
I used:
Code:
./VanitySearch -i input.txt -o output.txt
I get the Warning many times per second. It still addes keys to output.txt too, and I guess those are correct. But to avoid all this hassle, I just use the wine version.
hero member
Activity: 630
Merit: 731
Bitcoin g33k
But: when saving to file, I get a continuous stream of Warnings on my console:
Code:
Warning, wrong private key generated !"

what does your command look like, I'm curious.

I cannot reproduce this on my side. It works on my side and I used three different hosts and operating systems with different hardware. All work fine for me. I compiled simply with "make" and I am not using GPU for this test because this is the scenario you explained before.

Code:
$ ./VanitySearch 1try
Quote
VanitySearch v1.19
Difficulty: 4553521
Search: 1try [Compressed]
Start Thu Dec 19 17:05:22 2024
Base Key: EF34BA5BA02CCF41AE36124D91E5B9212E93E8C8AB1B81BDA14B821589A0068F
Number of CPU thread: 1

PubAddress: 1trykc9Ah11NVCNHVVt3orKjhgK8A84pu
Priv (WIF): p2pkh:L2miMJCwxyiH4tFx3gt2RK9q1iGzzz4wdGdkN7eYQ6Q9Qs4skmRy
Priv (HEX): 0xA5A68522A409A4A74E9FF31676531BEA96E38294815FEA218A700F7C368D4D03

PubAddress: 1tryWESn6mzaor1Te5sf3Nrdm181dxfFt
Priv (WIF): p2pkh:L5EhKgiE17Uzs2PPimJKhHX62uPDZ3yeFrbu1WmpGTPpe9wh6LUX
Priv (HEX): 0xEF34BA5BA02CCF41AE36124D91E5B9212E93E8C8AB1B81BDA14B821589AB5F32

PubAddress: 1tryJdNgYShLv9yFuLFhRNNoWRiJR876C
Priv (WIF): p2pkh:L5EhKgiE17Uzs2PPimJKhHX62uPDZ3yeFrbu1WmpGWGjd5fo1qRU
Priv (HEX): 0xEF34BA5BA02CCF41AE36124D91E5B9212E93E8C8AB1B81BDA14B821589BC93C4

PubAddress: 1tryseTSYxF5SqyLW7oKijhnPsgYcgj1n
Priv (WIF): p2pkh:L24p7EMx4SP62UWm6Y1v3TmeZig11KAE2unc5httpzvUexs81SLu
Priv (HEX): 0x909C0D9F227E47E12834C1EF91711C35510A5E0DA5632CA8F0B4E714696D3848
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
alternatively you can download the finished solution with my patch already applied, directly from my repository.

Code:
git clone https://github.com/citb0in/VanitySearch.git
cd VanitySearch
make
This is what I used. I don't need it for anything secure*, so I took the easiest solution.
Thanks!

But: when saving to file, I get a continuous stream of Warnings on my console:
Code:
Warning, wrong private key generated !"

So I'll just stick to the wine solution with the Windows executable. I already have 5 GB of output data to search through.

* This is for another time, when I'm done Smiley
hero member
Activity: 630
Merit: 731
Bitcoin g33k
What kind of compiling issues do you have? Post them here -including the GPU used so we can see if the CCAP matches- and we'll try to assist.
I wasn't even trying to install GPU drivers (yet). This is what I get:
Code:
~/VanitySearch-master$ make
cd obj &&       mkdir -p GPU
cd obj &&       mkdir -p hash
g++ -m64 -mssse3 -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/main.o -c main.cpp
In file included from main.cpp:18:
Timer.h:36:10: error: ‘uint32_t’ does not name a type
   36 |   static uint32_t getSeed32();
      |          ^~~~~~~~
Timer.h:23:1: note: ‘uint32_t’ is defined in header ‘’; did you forget to ‘#include ’?
   22 | #include
  +++ |+#include
   23 | #ifdef WIN64
Timer.h:37:27: error: ‘uint32_t’ has not been declared
   37 |   static void SleepMillis(uint32_t millis);
      |                           ^~~~~~~~
main.cpp: In function ‘int main(int, char**)’:
main.cpp:372:16: error: ‘getSeed32’ is not a member of ‘Timer’
  372 |   rseed(Timer::getSeed32());
      |                ^~~~~~~~~
make: *** [Makefile:70: obj/main.o] Error 1
I opened a new topic yesterday: Question: what is currently the best software for generating vanity addresses?. I'll continue with the suggestions posted there.

Hey Loyce,

since this fits well in this topic and should also help other people looking for help in the future, I will answer you here.

Manual procedure:

1) start from scratch by cloning the git repository in a fresh new folder on your local disk
Code:
git clone https://github.com/JeanLucPons/VanitySearch
Code:
cd VanitySearch

2) open each of the following files

   - Timer.h (capital 'T')
   - hash/sha256.cpp
   - hash/sha512.cpp
   - hash/sha256.h

and search from in the beginning for lines like:
Code:
#include 
   or
Code:
#include 

3) add this new line after the line you found in step 2)
Code:
#include 

... and save the changes you made.

4) compile it now, it should hopefully work
Code:
make

For a wrap-up, finally this is the resulting patch file which you can manually create into your cloned folder on your local disk and apply it.

fix_by_citb0in.patch
Code:
diff --git a/Timer.h b/Timer.h
index b649bf0..0407c79 100644
--- a/Timer.h
+++ b/Timer.h
@@ -20,6 +20,7 @@

 #include
 #include
+#include
 #ifdef WIN64
 #include
 #endif
diff --git a/hash/sha256.cpp b/hash/sha256.cpp
index 30cde56..fa92dc5 100644
--- a/hash/sha256.cpp
+++ b/hash/sha256.cpp
@@ -16,6 +16,7 @@
 */

 #include
+#include
 #include "sha256.h"

 #define BSWAP
diff --git a/hash/sha256.h b/hash/sha256.h
index 7f106b7..a4476d1 100644
--- a/hash/sha256.h
+++ b/hash/sha256.h
@@ -18,6 +18,7 @@
 #ifndef SHA256_H
 #define SHA256_H
 #include
+#include

 void sha256(uint8_t *input,int length, uint8_t *digest);
 void sha256_33(uint8_t *input, uint8_t *digest);
@@ -32,4 +33,4 @@ void sha256sse_checksum(uint32_t *i0, uint32_t *i1, uint32_t *i2, uint32_t *i3,
 std::string sha256_hex(unsigned char *digest);
 void sha256sse_test();

-#endif
\ No newline at end of file
+#endif
diff --git a/hash/sha512.cpp b/hash/sha512.cpp
index 2ab9bae..240e438 100644
--- a/hash/sha512.cpp
+++ b/hash/sha512.cpp
@@ -16,6 +16,7 @@
 */

 #include
+#include
 #include "sha512.h"

 #define BSWAP

I've made the mentioned patch file for the required adjustments to fix the issue and created a pull-request to have it merged into JeanLucPons' repository. However, whether and when he will check and approve this is written in the stars Smiley You can of course view, download and apply the fix at any time as follows.

visit the URL and click on the pull request named "Fix Undefined Type 'uint32_t' by Including "


Simple and quick solution:

alternatively you can download the finished solution with my patch already applied, directly from my repository.

Code:
git clone https://github.com/citb0in/VanitySearch.git
Code:
cd VanitySearch
Code:
make

I hope I have been able to help you and wish you every success. All the best.
citb0in
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
'if this dude could generate this i can too' . then you have his private key very fast
By all means: try it!
member
Activity: 393
Merit: 44
what i don't understand in vanity mania: you have a bot that catches all addresses that have human-readable part. So at this point you already know it's generated with this stuff. 'if this dude could generate this i can too' . then you have his private key very fast . ofc you(dude that first generated it) have random part in address and hope it's unique but i really doubt about this. we already have vanitygen(search)eth-gpu-whatever example where all those wallets was cracked at once.
Pages:
Jump to: