This is incredibly cool! I can’t wait to try it.
I assume it won’t run on an intel Mac, though, so I will have to run it on my raspberry pie alongside my full node....? Poor little guy... Is that even possible since it’s not intel?
Might have to create a virtual Linux box just for this, it’s that cool!
Topic: VanitySearch (Yet another address prefix finder) - page 14. (Read 32966 times)
Thanks. I don't think it's as easy as simply removing those. If I do, I get a whole bunch of new compiler errors.
Oh well, at least vanitygen still works fine!
Oh well, at least vanitygen still works fine!
It is likely because VanitySearch uses a bunch of opcodes specific to Intel, specifically inside the Int class that does all the arithmetic. A portable program like Vanitygen won't use assembly instructions like these, and one that's specifically designed for ARM64 would use their assembly instructions instead, walled around an #ifdef block so that you could just pass a switch like -DARM64 or -DINTEL for example to toggle between x86_64 and ARM64 compilation.
I'd like to run VanitySearch through Docker on my Mac.
It worked without issues on my Intel-based Mac, but not on the new Arm-based M1 Macs.
Docker for Arm Macs was just released, so I tried to to build the image, but I'm getting error
Surely, it's something to do with the different architecture.
Anybody know if it's possible / easy to fix?
It worked without issues on my Intel-based Mac, but not on the new Arm-based M1 Macs.
Docker for Arm Macs was just released, so I tried to to build the image, but I'm getting error
Code:
#11 0.153 g++: error: unrecognized command-line option '-m64'
#11 0.153 g++: error: unrecognized command-line option '-mssse3'
#11 0.153 make: *** [Makefile:70: obj/Base58.o] Error 1
Surely, it's something to do with the different architecture.
Anybody know if it's possible / easy to fix?
VanitySearch is being built for the x86_64 platform which is why it's failing on your ARM mac, so if you want it to compile on those you must edit the Makefile by hand and remove the references to "-m64" and "-mssse3" (an Intel instruction set).
Thanks. I don't think it's as easy as simply removing those. If I do, I get a whole bunch of new compiler errors.
Oh well, at least vanitygen still works fine!
I'd like to run VanitySearch through Docker on my Mac.
It worked without issues on my Intel-based Mac, but not on the new Arm-based M1 Macs.
Docker for Arm Macs was just released, so I tried to to build the image, but I'm getting error
Surely, it's something to do with the different architecture.
Anybody know if it's possible / easy to fix?
It worked without issues on my Intel-based Mac, but not on the new Arm-based M1 Macs.
Docker for Arm Macs was just released, so I tried to to build the image, but I'm getting error
Code:
#11 0.153 g++: error: unrecognized command-line option '-m64'
#11 0.153 g++: error: unrecognized command-line option '-mssse3'
#11 0.153 make: *** [Makefile:70: obj/Base58.o] Error 1
Surely, it's something to do with the different architecture.
Anybody know if it's possible / easy to fix?
VanitySearch is being built for the x86_64 platform which is why it's failing on your ARM mac, so if you want it to compile on those you must edit the Makefile by hand and remove the references to "-m64" and "-mssse3" (an Intel instruction set).
I can compile VanitySearch on windows subsystem for linux but it can use only 1 cpu
How can I compile VanitySearch to .exe for run on windows 10 ?
Thank
Now I got error from CUDA version
How can I change from CUDA 11.1 to use CUDA 11.2
I test change from VanitySearch.vcxproj by use notepad edit 11.1 to 11.2 but not success
may be I do wrong how to change on Visual Studio 2019
I can compile VanitySearch on windows subsystem for linux but it can use only 1 cpu
How can I compile VanitySearch to .exe for run on windows 10 ?
Thank
Now I got error from CUDA version
How can I change from CUDA 11.1 to use CUDA 11.2
I test change from VanitySearch.vcxproj by use notepad edit 11.1 to 11.2 but not success
may be I do wrong how to change on Visual Studio 2019
I can compile VanitySearch on windows subsystem for linux but it can use only 1 cpu
How can I compile VanitySearch to .exe for run on windows 10 ?
I'd like to run VanitySearch through Docker on my Mac.
It worked without issues on my Intel-based Mac, but not on the new Arm-based M1 Macs.
Docker for Arm Macs was just released, so I tried to to build the image, but I'm getting error
Surely, it's something to do with the different architecture.
Anybody know if it's possible / easy to fix?
It worked without issues on my Intel-based Mac, but not on the new Arm-based M1 Macs.
Docker for Arm Macs was just released, so I tried to to build the image, but I'm getting error
Code:
#11 0.153 g++: error: unrecognized command-line option '-m64'
#11 0.153 g++: error: unrecognized command-line option '-mssse3'
#11 0.153 make: *** [Makefile:70: obj/Base58.o] Error 1
Surely, it's something to do with the different architecture.
Anybody know if it's possible / easy to fix?
I can compile VanitySearch on windows subsystem for linux but it can use only 1 cpu
How can I compile VanitySearch to .exe for run on windows 10 ?
I just modify Vanity.cpp
to output look like csv format
however it effect with print out on display too
when use option -o ourput.csv
you will got output file look like csv, good to export to use as you want
to output look like csv format
however it effect with print out on display too
when use option -o ourput.csv
you will got output file look like csv, good to export to use as you want
I think it would be a great idea if there was a separate option --csv just for outputting CSV format files, so that we can have a text representation of the addresses and private keys in one file, while programmatically dumping the CSV to another file at the same time.
A CSV format would be convenient for some people but it's hard to read and so I wouldn't delete the human readable output all together.
agree with option CSV
it is convenient to export to use other project or any want
I just modify Vanity.cpp
to output look like csv format
however it effect with print out on display too
when use option -o ourput.csv
you will got output file look like csv, good to export to use as you want
to output look like csv format
however it effect with print out on display too
when use option -o ourput.csv
you will got output file look like csv, good to export to use as you want
I think it would be a great idea if there was a separate option --csv just for outputting CSV format files, so that we can have a text representation of the addresses and private keys in one file, while programmatically dumping the CSV to another file at the same time.
A CSV format would be convenient for some people but it's hard to read and so I wouldn't delete the human readable output all together.
I just modify Vanity.cpp
to output look like csv format
however it effect with print out on display too
when use option -o ourput.csv
you will got output file look like csv, good to export to use as you want
filename = Vanity.cpp
code line = 694 - 718
Code:
if(!needToClose)
printf("\n");
//fprintf(f, "PubAddress: %s\n", addr.c_str());
fprintf(f, "%s,", addr.c_str());
if (startPubKeySpecified) {
fprintf(f, "PartialPriv: %s\n", pAddr.c_str());
} else {
switch (searchType) {
case P2PKH:
//fprintf(f, "Priv (WIF): p2pkh:%s\n", pAddr.c_str());
fprintf(f, "%s,", pAddr.c_str());
break;
case P2SH:
//fprintf(f, "Priv (WIF): p2wpkh-p2sh:%s\n", pAddr.c_str());
fprintf(f, "%s,", pAddr.c_str());
break;
case BECH32:
//fprintf(f, "Priv (WIF): p2wpkh:%s\n", pAddr.c_str());
fprintf(f, "%s,", pAddr.c_str());
break;
}
//fprintf(f, "Priv (HEX): 0x%s\n", pAddrHex.c_str());
fprintf(f, "%s\n", pAddrHex.c_str());
}
if(needToClose)
fclose(f);
fprintf(f, "\n====
thanks guys
fprintf(f, "\n====
wSecond had changed .... not my source code....
Quote
can you show 10 lines from PubList.txt .......
like my search result ....all 9 word match "16jY7qLJn********"
like my search result ....all 9 word match "16jY7qLJn********"
What is your question about matching 9 characters? I have 100,000s of them somewhere.
This code is not efficient if your list grows:
9 characters "16jY7qLJn*" ..... 100,000 ?
all in 8000000000000000:FFFFFFFFFFFFFFFF ??
I am searching #64.......
I think if find 1 "9 characters match" or "10 characters match"
real #64 private key has a small Probability of appearing nearby
I will can Big Jump to Scan next range ....
now I still scan EDEC000000000000:EDECFFFFFFFFFFFF (95% had checked, and only found 6 "9 characters" )
Quote
can you show 10 lines from PubList.txt .......
like my search result ....all 9 word match "16jY7qLJn********"
like my search result ....all 9 word match "16jY7qLJn********"
What is your question about matching 9 characters? I have 100,000s of them somewhere.
This code is not efficient if your list grows:
Code:
...
...
searchfile = open ("PubList.txt", "r")
for line in searchfile:
if pub in line:
print ("KEY =" + priv + "- PUB =" + pub + "\ n")
...
...
So are you randomly generating privs, pubs, addrs and checking the addrs against the list? I'm just trying to figure out what you are doing.
fprintf(f, "\n====
thanks guys
can you show 10 lines from PubList.txt .......
like my search result ....all 9 word match "16jY7qLJn********"
like my search result ....all 9 word match "16jY7qLJn********"
Code:
~snip
This looks like a generated file, what did you use to make it? (AFAIK VanitySearch cannot export CSV files)
Anyway, I doubt that seeing them would be useful. It's not private key output like yours, it's just a bunch of MisterCooper's public keys on each line. He was trying to make VanitySearch search for whole pubkeys instead of prefixes.
I just edit VanitySearch-1.15.4_bitcrack
void VanitySearch::output(........)
download it https://gz.blockchair.com/bitcoin/addresses/
write a simple python code ..... read every public key to output 5 BTC address
to check address BTC balance ~~ if he know all public key <=> private key range...
if address has BTC balance , then use "Kangaroo" to find private key ......if sure private key range is small than 2^70
Code:
Public Key: 0414bdd507894bcda6a0e4b715c50d440498927880e65e4cd389c9db3e44b4b29a49962e139b85ea7da073a32193ac5712c89f1d5d0ed55443249fd3048bd4be43
Public Key compressed: 0314bdd507894bcda6a0e4b715c50d440498927880e65e4cd389c9db3e44b4b29a
Public Address 1: 1C7jNLSUjiZ54xibeP9KmViH5TzwtAKLLu
Public Address 1 compressed: 16jY7qLJnx2ixrxCnTLSraerkgyB3YYAiT
Public Address 3: 3C9VPeUcNeiVMcJuFMzAf7UphvB9SBsrW6
Public Address bc1 P2WPKH: bc1q8mjpx0verazc0cwsg2pnvj2gt35fn9cmdredms
Public Address bc1 P2WSH: bc1qrq28078qctyfr9y8hc4zawlrrmkx4ud9qh69v69lpa30qk0p08fs4fen0t
can you show 10 lines from PubList.txt .......
like my search result ....all 9 word match "16jY7qLJn********"
like my search result ....all 9 word match "16jY7qLJn********"
Code:
~snip
This looks like a generated file, what did you use to make it? (AFAIK VanitySearch cannot export CSV files)
Anyway, I doubt that seeing them would be useful. It's not private key output like yours, it's just a bunch of MisterCooper's public keys on each line. He was trying to make VanitySearch search for whole pubkeys instead of prefixes.
Code:
...
...
searchfile = open ("PubList.txt", "r")
for line in searchfile:
if pub in line:
print ("KEY =" + priv + "- PUB =" + pub + "\ n")
...
...
can you show 10 lines from PubList.txt .......
like my search result ....all 9 word match "16jY7qLJn********"
Code:
000000000000000000000000000000000000000000000000EDEC070CF855EBA0,16jY7qLJnS3hrHQPC9An9K5ZNaZMd98bV4,2021-04-04 23:26:51,,,,,,,,,,
000000000000000000000000000000000000000000000000EDEC26E9C9E3F377,16jY7qLJnSwho77XBFFwY4rpN891YYWh3b,2021-04-06 04:44:36,,,,,,,,,,
000000000000000000000000000000000000000000000000EDEC34CFC668E668,16jY7qLJntTJt2NwVvCj5Y2eB8jY2G9TBx,2021-04-06 17:01:10,,,,,,,,,,
000000000000000000000000000000000000000000000000EDEC6CFD492F0A35,16jY7qLJnSgLpk82Ay6MQuVkxEFitwR3gK,2021-04-12 13:03:56,,,,,,,,,,
000000000000000000000000000000000000000000000000EDECAB37CBF22648,16jY7qLJnbq7VxfZpgXxCVHpBVZh8852tA,2021-04-13 18:36:51,,,,,,,,,,
000000000000000000000000000000000000000000000000EDECB750D404B88A,16jY7qLJnH2Yw5c8H97NERpKDBfmp2SE6q,2021-04-09 17:17:50,,,,,,,,,,
000000000000000000000000000000000000000000000000EDECF90D30C69B90,16jY7qLJn4y8JFFhZ2usCPFzUj4rbqU7Xy,2021-04-11 06:00:07,,,,,,,,,,
in range
000000000000000000000000000000000000000000000000EDEC000000000000
000000000000000000000000000000000000000000000000EDECFFFFFFFFFFFF
What meaning -m option
yes, my input file have a lot of prefix search
yes, my input file have a lot of prefix search
It's only used in GPU search.
It dictates the size of the array that stores the prefixes on GPU memory. It is not possible to search for more prefixes than this simultaneously, because you cannot write past the end of allocated memory or you will get a Segmentation Fault! Instead of hard failing like that, VanitySearch drops some prefixes to stay within the size limit.
Kangaroo also has this kind of concept, only with DPsize.
Thank you
I will try decrease input file with not have much prefix search may be help to faster and better n small GPU
Jump to: