May i ask if VanitySearch work by generate massive sha256 random hex priv key? If there isn't, i'd like to modify it

Hello. Can i specify in command line keyspace when i would like to scan for find key to selected prefix?

1. If the -g value is set manually - it goes high enough that VanitySearch will start operation, but it will precede the search with the message:

======
Warning, 639 items lost
Hint: Search with less prefixes, less threads (-g) or increase maxFound (-m)

How to understand this message? Do I understand correctly that the quantity given has been "skipped"? Is this amount a one-time amount, or is it somehow more negatively affecting the results?

2. When starting work - the application provides the value of "difficulty" of the selected prefix ...

How was this calculated? Can it be understood that once in X (where X is the value of difficulty) such a prefix must be found. Assuming then, let's assume a keyspace pool with the size of X - is it certain that this prefix is there?

Thank you in advance for dispelling my doubts!

A message appeared in the forum about a problem that appeared when searching for short prefixes beginning with "3". Here is the original content of the applicant:

Hi. C:\VanitySearch\VanitySearch.exe -o A:\result.txt -nosse -c 3P
3P112wcuMsGWJ1jLAouxu5tDwTzKUJGjyN
3P114dg7NYteQctAmS8cgGt3c3cJxeMJJ6
3P11gVc4n7wVizvku88ic1yydNwa5GY5ae
and etc
Why are addresses not randomly generated?
...next try:
C:\VanitySearch\VanitySearch.exe -o A:\result.txt -nosse 3E
3E11oBnqGw3cwkk6U4ekid3xm6LjA8F3mm
3E11UemvQxkVTY6KMuqmwfb2utfi3i2rFB
3E11PHRhUXNiqcyuMzEo8kTNFJNNDbrmBn
3E11nkf3TXRKMeHPRMS61yKECaYREFB2uD
random goes after 4 characters

To sum up: the user wanting to find two-character prefixes - receives the results consisting of these two characters and additionally two ones (only). No other prefixes are caught (e.g. 3PP).

The problem is small, but if it occurs it can invisibly affect the results in larger searches somewhere - hence please check this problem in the code.

any help?

GPUEngine: Kernel: invalid device function

root@my-pc:/home/van# ./vs -gpu 1ffff
Difficulty: 264104224
Search: 1ffff [Compressed]
Start Sat Aug 24 00:00:19 2019
Base Key:CFAA17E3291B6B89DEBD839F00BAB73587E85F29ED7CFECD04E72328A51A6C30
Number of CPU thread: 1
GPU: GPU #0 GeForce RTX 2060 SUPER (34x64 cores) Grid(272x128)
GPUEngine: Kernel: invalid device function

root@my-pc:/home/van# ./vs -l
GPU #0 GeForce RTX 2060 SUPER (34x64 cores) (Cap 7.5) (7952.3 MB) (Multiple host threads)

root@my-pc:/home/van# ldd ./vs
linux-vdso.so.1 => (0x00007ffcca289000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f988568b000)
libcudart.so.8.0 => /usr/local/cuda-8.0/targets/x86_64-linux/lib/libcudart.so.8.0 (0x00007f9885425000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f98850a3000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f9884d9a000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f9884b84000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f98847ba000)
/lib64/ld-linux-x86-64.so.2 (0x00007f9885b2b000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f98845b6000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f98843ae000)

root@my-pc:/home/van# gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 5.4.0-6ubuntu1-16.04.11' --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-5 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1 16.04.11)

I have problems with the drivers help please solve it

Jean-Luc is the 1.14 update only for CL...I don't see a Cuda version...

This looks great Jean Luc, keep up the good work!

GPU/GPUEngine.h

// Number of thread per block
#define NB_TRHEAD_PER_GROUP 128

try increase it to 256 or 512..

>VanitySearch-1.1.5_th128gr -t 0 -gpu  12345689
GPU: GPU #0 GeForce GTX 1070 (15x128 cores) Grid(120x128)
549.958 MK/s (GPU 549.958 MK/s) (2^33.98) [P 1.88%][50.00% in 00:18:09][0]

>VanitySearch-1.1.5_th256gr -t 0 -gpu  12345689
GPU: GPU #0 GeForce GTX 1070 (15x128 cores) Grid(120x256)
664.534 MK/s (GPU 664.534 MK/s) (2^34.08) [P 2.02%][50.00% in 00:14:59][0]

>VanitySearch-1.1.5_th512gr -t 0 -gpu  12345689
GPU: GPU #0 GeForce GTX 1070 (15x128 cores) Grid(120x512)
710.364 MK/s (GPU 710.364 MK/s) (2^34.35) [P 2.43%][50.00% in 00:13:56][0]

hashrate diff:
664/549 = x1,20
710/549 = x1,29

how about -g argv?
120x512=61440
480x128=64440
but it not equal:

>VanitySearch-1.1.5_th128gr  -t 0 -gpu  -g 480  12345689
GPU: GPU #0 GeForce GTX 1070 (15x128 cores) Grid(480x128)
566.206 MK/s (GPU 566.206 MK/s) (2^32.40) [P 0.64%][50.00% in 00:17:57][0]

-g is useless for it, recompilation is necessary

VanitySearch-1.1.5_th128gr(orig).zip
VanitySearch-1.1.5_th256gr.zip
VanitySearch-1.1.5_th512gr.zip
recompiled, non-official build from me (while Jean_Luc thinks what to do)

Hello,

Is support for litecoin or other altcoins are possible?

Thanks.

Hello Jean-Luc,

It would be a nice feature for also looking for ETH addresses.

Is this possible to add??

Like to learn from you!

Greetings Satoshis

I do not know how the use of non-random Basekey works. I set up, let's assume 999999999999999, and he's still taking BASEKEY CEC35CA3247CEC35CA3247CEC35CA3247CEC35CA3247CEC35CA3247. How do I actually set the Basekey to the one I want to set myself?

..

Hi,

Does anybody know the speed of vanitysearch with NVIDIA GTX 1050 4GB or Radeon RX 560 4GB?

Thanks!

GPU code not compiled, use -DWITHGPU when compiling...how to solve this error?

Hi there!
First of all, thanks for your awesome work!!!
Already asked it at the bitcrack repo.
But would it be possible to use the hex-privatey as Input , treat it as bytes, take one round of sha256, and take the sha-string for the privatekey generations?
Keep incrementing the Byte string, and before the treads generate the addresse take one round of sha256 for every worker of the batch?

Thanks in advance

hello

I can not compile on ubuntu source code gives an error gcc
can lay out a binary for ubuntu? that binar that the branch below does not work for me ... and another question in what format should the prefixes in the file be? with "1" or no unit?

List of works to eliminate code issues of VanitySearch:

Filename | Line | Type | Description |

• Int.h | 29 | style | Class 'Int' has a constructor with 1 argument that is not explicit.
• Int.h | 30 | style | Class 'Int' has a constructor with 1 argument that is not explicit.
• hash\ripemd160.cpp | 232 | warning | Member variable 'CRIPEMD160::buf' is not initialized in the constructor.
• hash\ripemd160.cpp | 278 | style | Local variable 'pad' shadows outer variable
• hash\sha256.cpp | 422 | warning | Member variable 'CSHA256::buf' is not initialized in the constructor.
• hash\sha512.cpp | 158 | warning | Member variable 'CSHA512::buf' is not initialized in the constructor.
• hash\sha512.cpp | 78 | style | The scope of the variable 't' can be reduced.
• hash\sha512.cpp | 328 | style | The scope of the variable 'need' can be reduced.
• IntGroup.h | 12 | style | Class 'IntGroup' has a constructor with 1 argument that is not explicit.
• Int.cpp | 1478 | style | Variable 'ok' is reassigned a value before the old one has been used.
• Int.cpp | 1301 | style | Local variable 'i' shadows outer variable
• Int.cpp | 1304 | style | Local variable 'e' shadows outer variable
• Int.cpp | 1385 | style | Variable 'ok' is assigned a value that is never used.
• Int.cpp | 1483 | style | Variable 'ok' is assigned a value that is never used.
• IntGroup.cpp | 5 | warning | Member variable 'IntGroup::ints' is not initialized in the constructor.
• IntGroup.cpp | 8 | style | C-style pointer casting
• IntMod.cpp | 465 | style | The scope of the variable 'bitCount' can be reduced.
• IntMod.cpp | 466 | style | The scope of the variable 'uu' can be reduced.
• IntMod.cpp | 466 | style | The scope of the variable 'uv' can be reduced.
• IntMod.cpp | 466 | style | The scope of the variable 'vu' can be reduced.
• IntMod.cpp | 466 | style | The scope of the variable 'vv' can be reduced.
• IntMod.cpp | 467 | style | The scope of the variable 'v0' can be reduced.
• IntMod.cpp | 467 | style | The scope of the variable 'u0' can be reduced.
• IntMod.cpp | 597 | style | Local variable 'i' shadows outer variable
• IntMod.cpp | 597 | style | Variable 'i' is assigned a value that is never used.
• IntMod.cpp | 694 | style | Variable 'nbBit' is assigned a value that is never used.
• main.cpp | 958 | style | Condition '!found' is always true
• main.cpp | 262 | warning | %X in format string (no. 1) requires 'unsigned int *' but the argument type is 'unsigned char *'.
• main.cpp | 291 | warning | %X in format string (no. 1) requires 'unsigned int *' but the argument type is 'unsigned char *'.
• main.cpp | 321 | warning | %X in format string (no. 1) requires 'unsigned int *' but the argument type is 'unsigned char *'.
• main.cpp | 157 | style | The scope of the variable 'start' can be reduced.
• main.cpp | 157 | style | The scope of the variable 'end' can be reduced.
• main.cpp | 161 | style | The scope of the variable 'item' can be reduced.
• main.cpp | 210 | style | The scope of the variable 'start' can be reduced.
• main.cpp | 210 | style | The scope of the variable 'end' can be reduced.
• main.cpp | 402 | style | The scope of the variable 'start' can be reduced.
• main.cpp | 402 | style | The scope of the variable 'end' can be reduced.
• main.cpp | 811 | style | The scope of the variable 'addrType' can be reduced.
• main.cpp | 804 | performance | Function parameter 'fileName' should be passed by const reference.
• main.cpp | 804 | performance | Function parameter 'outputFile' should be passed by const reference.
• main.cpp | 404 | style | Unused variable: item
• main.cpp | 485 | style | Variable 'f_end' is assigned a value that is never used.
• main.cpp | 956 | style | Unused variable: cAddr
• SECP256K1.cpp | 506 | warning | %X in format string (no. 1) requires 'unsigned int *' but the argument type is 'signed int *'.
• SECP256K1.cpp | 906 | performance | Function parameter 'address' should be passed by const reference.
• SECP256K1.cpp | 120 | style | Variable 'ok' is assigned a value that is never used.
• Vanity.cpp | 3369 | warning | Return value of function CreateThread() is not used.
• Vanity.cpp | 3400 | warning | Return value of function CreateThread() is not used.
• Vanity.cpp | 28 | warning | Member variable 'VanitySearch::counters' is not initialized in the constructor.
• Vanity.cpp | 28 | warning | Member variable 'VanitySearch::task_counters' is not initialized in the constructor.
• Vanity.cpp | 28 | warning | Member variable 'VanitySearch::startTime' is not initialized in the constructor.
• Vanity.cpp | 28 | warning | Member variable 'VanitySearch::endOfSearch' is not initialized in the constructor.
• Vanity.cpp | 28 | warning | Member variable 'VanitySearch::nbCPUThread' is not initialized in the constructor.
• Vanity.cpp | 28 | warning | Member variable 'VanitySearch::nbFoundKey' is not initialized in the constructor.
• Vanity.cpp | 28 | warning | Member variable 'VanitySearch::ghMutex' is not initialized in the constructor.
• Vanity.cpp | 28 | warning | Member variable 'VanitySearch::ghMutex_IncrStartKey' is not initialized in the constructor.
• Vanity.cpp | 316 | warning | Identical inner 'if' condition is always true.
• Vanity.cpp | 376 | warning | %d in format string (no. 3) requires 'int' but the argument type is 'unsigned int'.
• Vanity.cpp | 398 | warning | %d in format string (no. 1) requires 'int' but the argument type is 'unsigned int'.
• Vanity.cpp | 398 | warning | %d in format string (no. 2) requires 'int' but the argument type is 'unsigned int'.
• Vanity.cpp | 398 | warning | %d in format string (no. 3) requires 'int' but the argument type is 'unsigned int'.
• Vanity.cpp | 398 | warning | %d in format string (no. 4) requires 'int' but the argument type is 'unsigned int'.
• Vanity.cpp | 406 | warning | %d in format string (no. 1) requires 'int' but the argument type is 'unsigned int'.
• Vanity.cpp | 406 | warning | %d in format string (no. 2) requires 'int' but the argument type is 'unsigned int'.
• Vanity.cpp | 583 | warning | %X in format string (no. 1) requires 'unsigned int *' but the argument type is 'unsigned char *'.
• Vanity.cpp | 3369 | error | Return value of allocation function 'CreateThread' is not stored.
• Vanity.cpp | 3400 | error | Return value of allocation function 'CreateThread' is not stored.
• Vanity.cpp | 670 | style | The scope of the variable 'nbDigit' can be reduced.
• Vanity.cpp | 672 | style | The scope of the variable 'wrong' can be reduced.
• Vanity.cpp | 2230 | style | The scope of the variable 'pr0' can be reduced.
• Vanity.cpp | 2232 | style | The scope of the variable 'pr1' can be reduced.
• Vanity.cpp | 2234 | style | The scope of the variable 'pr2' can be reduced.
• Vanity.cpp | 2236 | style | The scope of the variable 'pr3' can be reduced.
• Vanity.cpp | 3315 | style | The scope of the variable 't1' can be reduced.
• Vanity.cpp | 3422 | style | The scope of the variable 'gpuCount' can be reduced.
• Vanity.cpp | 3442 | style | The scope of the variable 'keyRate' can be reduced.
• Vanity.cpp | 3444 | style | The scope of the variable 'gpuKeyRate' can be reduced.
• Vanity.cpp | 1770 | style | Local variable 'chkAddr' shadows outer variable
• Vanity.cpp | 2608 | style | Local variable 'i' shadows outer variable
• Vanity.cpp | 32 | performance | Function parameter 'outputFile' should be passed by const reference.
• Vanity.cpp | 2987 | style | Variable 'ok' is assigned a value that is never used.
• Vanity.cpp | 3184 | style | Variable 'hasStarted' is assigned a value that is never used.
• Vanity.cpp | 3422 | style | Variable 'gpuCount' is assigned a value that is never used.
• Vanity.cpp | 3442 | style | Variable 'keyRate' is assigned a value that is never used.
• Vanity.cpp | 3444 | style | Variable 'gpuKeyRate' is assigned a value that is never used.
• Vanity.cpp | 3068 | style | Variable 'ok' is reassigned a value before the old one has been used.

Hi!
I try this: g++ -c IntGroup.cpp
which gives this:
In file included from IntGroup.h:21,
from IntGroup.cpp:18:
Int.h: In function 'void imm_mul(uint64_t*, uint64_t, uint64_t*)':
Int.h:220:32: error: '__builtin_ia32_addcarryx_u64' was not declared in this scope
#define _addcarry_u64(a,b,c,d) __builtin_ia32_addcarryx_u64(a,b,c,(long long unsigned int*)d);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
Int.h:231:7: note: in expansion of macro '_addcarry_u64'
c = _addcarry_u64(c, _umul128(x[1], y, &h), carry, dst + 1); carry = h;
^~~~~~~~~~~~~
Int.h:220:32: note: suggested alternative: '__builtin_ia32_addcarryx_u32'
#define _addcarry_u64(a,b,c,d) __builtin_ia32_addcarryx_u64(a,b,c,(long long unsigned int*)d);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
Int.h:231:7: note: in expansion of macro '_addcarry_u64'
c = _addcarry_u64(c, _umul128(x[1], y, &h), carry, dst + 1); carry = h;
^~~~~~~~~~~~~
Int.h: In function 'void imm_umul(uint64_t*, uint64_t, uint64_t*)':
Int.h:220:32: error: '__builtin_ia32_addcarryx_u64' was not declared in this scope
#define _addcarry_u64(a,b,c,d) __builtin_ia32_addcarryx_u64(a,b,c,(long long unsigned int*)d);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
Int.h:250:7: note: in expansion of macro '_addcarry_u64'
c = _addcarry_u64(c, _umul128(x[1], y, &h), carry, dst + 1); carry = h;
^~~~~~~~~~~~~
Int.h:220:32: note: suggested alternative: '__builtin_ia32_addcarryx_u32'
#define _addcarry_u64(a,b,c,d) __builtin_ia32_addcarryx_u64(a,b,c,(long long unsigned int*)d);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
Int.h:250:7: note: in expansion of macro '_addcarry_u64'
c = _addcarry_u64(c, _umul128(x[1], y, &h), carry, dst + 1); carry = h;

I know this program searches for 256 bit keys. I took a look at the code and I suppose it searches 255,254.. bit too. Is it true? Any comments, please.

Hello Mon'Ami from beautiful France...;-)

I was curious what the ETA of your new and promissing project Pollard Rho will be...

Like to learn from you.

Sincères salutations

Hi dear JeanLucPons, please add Ethereum address generation support, or make another VanitySearch for ETH, thanks a lot.

If keyspace can be used in vanitysearch like if we want to search a address between 2^63-2^64 what we should do

1.9 Seems to be slower and loses a lot of data
Notice the Warning highlighted in bold.

VanitySearch1.9.exe -i FullBTC.txt -stop -o resultbtc.txt -t 0 -gpu -gpuId 0
[Loading input file 100.0%]
[Building lookup16 100.0%]
[Building lookup32 100.0%]
Search: 9111116 addresses (Lookup size 65536,[93,2882]) [Compressed]
Start Sat Mar 23 19:01:55 2019
Base Key:AE22A85EF9188EDAB8382FD1B5B6E45E0114C814A995DF32B722CF2B6636DB13
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1070 (15x128 cores) Grid(120x128)

Warning, 133640 items lost
Hint: Search with less prefixes, less threads (-g) or increase maxFound (-m)
^C.672 MK/s (GPU 70.672 MK/s) (2^31.98) [P 0.00%][50.00% in 4.54541e+32y][0]

VanitySearch1.8.exe -i FullBTC.txt -stop -o resultbtc.txt -t 0 -gpu -gpuId 0
Start Sat Mar 23 19:04:18 2019
Search: 9111116 prefixes (Lookup size 64660)
Base Key:7421184F7FB6F2C8D99484B1BCBACACEC4CC0658A0B112BED2A718B585E0BF73
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1070 (15x128 cores) Grid(120x128)

Warning, 179762 items lost (try to search with less prefixes)
81.551 MK/s (GPU 81.551 MK/s) (2^34.93) [P 0.00%][50.00% in 3.93903e+32y][0]

@JeanLucPons Can you give us an example of applying the -rp and/or -sp flag succesfully...

Thnx in advance

hey there,

is this possible to use multiple GPUs to generate a btc address ?

i tried ,
VanitySearch.exe -stop -gpu gpuId1 3Mpayment
VanitySearch.exe -stop -gpu gpuId1 -gpu gpuId2 3Mpayment.

in both i received "Unexpected gpuId1 argument"

i have multiple GPUs , how can i use them all to generate a an address ?

thanks

Jean-Luc can you give us a example of applying -ps flag...

AFAIK only CUDA (Nvidia) is currently supported.

It is possible to use several gpu to search at all in one process

My PrivKey 0000000000000000000000000000000000000000000000000000000000000002
sp 04c6047f9441ed7d6d3045406e95c07cd85c778e4b8cef3ca7abac09b95c709ee51ae168fea63dc339a3c58419466ceaeef7f632653266d0e1236431a950cfe52a

Example1 found
PubAddress: 111112w3uud3zUeFU8T6LbGsEgdbShYpX
PartialPriv: 5KEQmbPVAPGdezceFGZkHrns4v2Du7BnD8cdtBCaKYqaUvpVvf3
PartialPrivkeyHex: BA78F1AE88F5E27E56BEFEA7A4442F531A11801B4CD549862361746BD7E82B67

Reconstructed key 13B19715083D80BD0C72C6A2941F669EF5B53A470BD27C94655C4773A1A0B083 is wrong key, but if Reconstructed key - PrivKey again = Correct Priv key
13B19715083D80BD0C72C6A2941F669EF5B53A470BD27C94655C4773A1A0B081

Example2 found
PubAddress: 111112pbAVRZ8LjM1xosiN3GeMM4EMGJW
PartialPriv: 5JQU2B6t7D8qZYk3cjmoUC8EFAJYtfYfbD27SpCdqidfrXi1G66
PartialPrivkeyHex: 4D9C1F60C0C715CD3769CE090E869718A8CF745327EEDD445C8C14ACC375AE90

Reconstructed key
F46379FA417F778E81B6060E1EAB5FCCCD2BBA2768F1AA361A9141A4F9BD2976
is wrong key, but if Reconstructed key - PrivKey again = Correct Priv key
F46379FA417F778E81B6060E1EAB5FCCCD2BBA2768F1AA361A9141A4F9BD2974

This error in endomorphism Reconstruction final private key only.

Hi,

sorry for the stupid question:

How to connect it to the gpu?

Dear Jean-Luc, Is it possible to make Pollard Rho in language OpenQASM?
https://developer.ibm.com/code/2017/05/17/developers-guide-to-quantum-qiskit-sdk/

Hello,

I would like to mine vanity address for altcoins

How to change the address prefix on miner?

Thanks.

make gpu=1 all
mkdir -p obj
cd obj && mkdir -p GPU
cd obj && mkdir -p hash
g++ -DWITHGPU -m64 -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/Base58.o -c Base58.cpp
Base58.cpp: In function ‘bool DecodeBase58(const char*, std::vector&)’:
Base58.cpp:45:19: error: ‘nullptr’ was not declared in this scope
if (ch == nullptr)
^
Base58.cpp: In function ‘std::__cxx11::string EncodeBase58(const unsigned char*, const unsigned char*)’:
Base58.cpp:90:5: error: ‘uint32_t’ was not declared in this scope
uint32_t carry = pbegin[i];
^
Base58.cpp:92:7: error: ‘carry’ was not declared in this scope
carry += (uint32_t)(digits[j]) << 8;
^
Base58.cpp:96:11: error: ‘carry’ was not declared in this scope
while(carry > 0) {
^
Makefile:56: recipe for target 'obj/Base58.o' failed
make: *** [obj/Base58.o] Error 1
chawla@i3-6100:~/van/VanitySearch$ make all
cd obj && mkdir -p GPU
g++ -m64 -msse -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/Base58.o -c Base58.cpp
Base58.cpp: In function ‘bool DecodeBase58(const char*, std::vector&)’:
Base58.cpp:45:19: error: ‘nullptr’ was not declared in this scope
if (ch == nullptr)
^
Base58.cpp: In function ‘std::__cxx11::string EncodeBase58(const unsigned char*, const unsigned char*)’:
Base58.cpp:90:5: error: ‘uint32_t’ was not declared in this scope
uint32_t carry = pbegin[i];
^
Base58.cpp:92:7: error: ‘carry’ was not declared in this scope
carry += (uint32_t)(digits[j]) << 8;
^
Base58.cpp:96:11: error: ‘carry’ was not declared in this scope
while(carry > 0) {
^
Makefile:56: recipe for target 'obj/Base58.o' failed
make: *** [obj/Base58.o] Error 1

Hi

About to test the program, found it on bitcointalk.
Is there an option to search from a text file list?
Didnt seem to see it

Thanks again

History : 2019.11.28
Last block : 605732

TOTAL BALANCE : 16.314.489,39540567‬
TOTAL ADDRESS : 27.967.620

Type : P2KH
Total BTC : 10,201,701.07457053
Total ADDR : 21,738,870
Top 10
1 183hmJGRuTEi2YDCWy5iozY8rZtFwVgahM 85947.34899576
2 1FeexV6bAHb8ybZjqQMjJrcCrHGW9sb6uF 79957.20104663
3 1HQ3Go3ggs8pFnXuHVHRytPCq5fGG8Hbhx 69370.13094817
4 1LdRcdxfbSnmCYYNdeYpUnztiYzVfBEQeC 53880.05925968
5 1AC4fMwgY8j9onSbXEWeH6Zan8QGMSdmtA 51830.35711656
6 1LruNZjwamWJXThX2Y8C2d47QqhAkkc5os 44000.07774719
7 17hf5H8D6Yc4B7zHEg3orAtKn7Jhme7Adx 36000.00213111
8 1P5ZEDWTKTFGxQjZphgWPQUpe554WKDfHQ 33442.66299870
9 13JQwoSLLR3ffXwswe2HCTK9oq4i8MWK3q 31010.01150570
10 12ib7dApVFvg82TXKycWBNpN8kFyiAN1dr 31000.06893125

Type : P2SH
Total BTC : 5,758,792.56573372
Total ADDR : 5,606,265
Top 10

1 35hK24tcLEWcgNA4JxpvbkNkoAcDGqQPsP 241102.14098481
2 3CgKHXR17eh2xCj2RGnHJHTDjPpqaNDgyT 111858.24590967
3 37XuVSEpWW4trkfmvWzegTHQt7BdktSKUs 94505.76878827
4 34xp4vRoCGJym3xR7yCVPFHoCNxv4Twseo 90573.70783309
5 3M6UcBNGZAW1HRjiFDMRcY5aXFrQ4F9E1y 89684.30585518
6 3D2oetdNuZUqQHPJmcMDDHYoqkyNVsFk9r 76893.10189206
7 3JZq4atUahhuA9rLhXLMhhTo133J9rF97j 75361.64512652
8 385cR5DM96n1HvBDMzLHPYcw89fZAXULJP 66633.90591295
9 3E35SFZkfLMGo4qX5aVs1bBDSnAuGgBH33 65077.08195065
10 38UmuUqPCrFmQo4khkomQwZ4VbY2nZMJ67 54549.36908663

Type : P2WKH
Total BTC : 325,242.34111757
Total ADDR : 549,370
Top 10
1 bc1q5shngj24323nsrmxv99st02na6srekfctt30ch 40000.32720447
2 bc1q2raxkmk55p000ggfa8euzs9fzq7p4cx4twycx7 10000.01040732
3 bc1q0vrlwmz4z48tuyhmggz74p297j8qln8t084rm7 5355.94523386
4 bc1quchdh8qk9wx40agh5ywnkrwsdqstlcp80aw6ey 4499.99994293
5 bc1qezn9rjetad3k9mcd9zzhmv56ypjz7qv0tssn07 4499.99991056
6 bc1qsnd6zut5n59cfha2vynepgxh7ppq4rcfsu09za 4499.99989412
7 bc1quffts3c992h6jjur98pwn3ga7jerj4ljee26ss 4499.99989001
8 bc1qyf240gfzmgmwemxhrwnep5fe4z3a067vy3mr36 4499.99988677
9 bc1qhvfd4368afv89qdncra8l9r0g35y7jwflwe056 4499.99988179
10 bc1q4xq9m2fd30nxd6n6rkhstd3qxd3a33573afy6y 4499.99986535

Type : P2WSH
Total BTC : 28,753.41398385
Total ADDR : 73,115
Top 10

1 bc1qrvxczdplr3txzmwcp2tn0usaksc2axvdfptxsyw9rtv7dmtu7l7st2g3s9 4047.09858854
2 bc1qf3zxkhkhu6kfscqzp2lqm0tm445yx7k9d5xarknxs6yrve2qjujsaj34ap 2084.86696932
3 bc1qyy30guv6m5ez7ntj0ayr08u23w3k5s8vg3elmxdzlh8a3xskupyqn2lp5w 1427.10169872
4 bc1q7n7e9s9krl95g8xdkgfwh3jn6689r22y0mjhqz4g357tvja8fxzq9ufd2u 583.53419047
5 bc1q2p55hccg33g6v645nspwnayzpcl99jaf3gyfpx2g8lzydc4saslq3emz6k 521.83107441
6 bc1qe696rct77awna2063q79e0m3vercalz970va5x6tv6cr9jp743tsyu9zvg 494.32087653
7 bc1qp3u85682jam6sfv2ps2q0ze7var2lpsddq4665da7lhna7tkntxq9kek56 454.58571306
8 bc1qnhfjgnu3httxwntu450zs4z5zf7j69y68pyv2v0f2j54sz8s77jssm6apd 418.69430487
9 bc1qy57jzss9n56fg4n906eu0hp3fu73n8ecrfytqhva8789dz5lfqaq342ad4 358.44952250
10 bc1q9909xggg842c58v3cncp9l35vv65gxx8mu3483x3w8xvk8a8ng0stfyrd9 256.23056034

Tell me when amd's support will be keen to get involved too.

Hi
Will OPENCL support come?

Hey Jean-Luc,

How are you??

I hope you are well!

Maybe you heard also about the Pollard Kangaroo...to my understanding dev Picachu has made a version, but at this moment this is not avaible to the community.

Do you think it's a good idea to make such a version also...

See link below for an impression...but ofcourse optimized for GPU on Cuda and OCL

https://gist.github.com/natmchugh/7dbd7e4f7c55d915db1e

Like to learn from you my French Friend High End Top Notch Coder...;-)

Kind regards,

Satoshi

Specify the range of keys to search. For example, if you want to search in a specific range of private keys you can specify it in hex or decimal in the format START:END with a specified stride/increment size.

E:>VanitySearch.exe 1feeee
VanitySearch v1.15
Difficulty: 15318045009
Search: 1feeee [Compressed]
Start Mon Jul 15 14:29:41 2019
Base Key: 7DA80A71A970BA79FF8DBE5E6CF2EA7A8331A75532988FAE680292CDB204DE5B
Number of CPU thread: 4
^C834 MK/s (GPU 0.000 MK/s) (2^24.24) [P 0.13%][50.00% in 00:36:32][0]
E:>VanitySearch.exe 1feeee
VanitySearch v1.15
Difficulty: 15318045009
Search: 1feeee [Compressed]
Start Mon Jul 15 14:29:56 2019
Base Key: 75E4F6B159484164BA8AE9CF1A79AB1E0F29C99A5354FB85F5E4B079AA2F5B39
Number of CPU thread: 4
4.553 MK/s (GPU 0.000 MK/s) (2^25.74) [P 0.36%][50.00% in 00:38:39][0]

i think its better to change blinking pointer/cursor position to end of found.
it backing like ^C834 text see above image.
and make the found '[0]' visable after one match found.

Great app...frequent updates...pays attention to idea's of the community!!

JeanLucPons the new kid on the block...;-)

Is it possible to make a version VanitySearch, for AMD cards?

@JeanLucPons
Is your software suitable for trying to find (generate an address) with a balance from the list?
-i inputfile: Get a list of prefixes full address with ballance
and -r (rekey) (20 000 for example) options, or will BitCrack software be better in this regard? For example, the generation of initial random points as implemented in the fork version pikachunakapika (github.com/pikachunakapika/BitCrack)?
Tell me how best to try and with what parameters. Thanks

Hello Jean-Luc,

Welcome back from Holiday, I hope you had a good one, I had a good one...;-)

I'm sure you did some inspiration and good new energy for working on your future and worlds best BTC cracking tool Pollard Rho!

Cheers,

Satoshi

make please Random + Seq for bruteforce
random each point + seq +1

how can i define base key ?

someone can add csv output format to print in outputfile

ie 1: C:\C++\VanitySearch\x64\Release>VanitySearch.exe -stop -gpu -csv 1TryMe

VanitySearch v1.17
Difficulty: 15318045009
Search: 1TryMe [Compressed]
Start Fri Jan 31 08:12:19 2020
Base Key: DA12E013325F12D6B68520E327847218128B788E6A9F2247BC104A0EE2818F44
Number of CPU thread: 7
GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x128)
[251.82 Mkey/s][GPU 235.91 Mkey/s][Total 2^32.82][Prob 39.1%][50% in 00:00:12][Found 0]
BTC,1TryMe,1TryMeJT7cfs4M6csEyhWVQJPAPmJ4NGw,Kxs4iWcqYHGBfzVpH4K94STNMHHz72DjaCuNdZeM5VMiP9zxMg15,310DBFD6AAB6A63FC71CAB1150A0305ECABBE46819641D2594155CD41D081AF1

ie 2 : C:\C++\VanitySearch\x64\Release>VanitySearch.exe -stop -gpu -csv -o output.txt 1TryMe
In output file:
BTC,1feeee,1feeeePnFezxxAJX6PgxqzPeQtcZ82Tnf,L5BXD5YQjzgCkuNjb5VD34YLZXmcGForDnQkpztKnLZuNkVyP7Z9,ED92ACC110AB40AF7514251581E39C9CF8E4CA739BE768456822DE9ADC4CE1DC
BTC,1feeee,1feeeezsQhMSkndHDfQFNmxuGZ8NHrSuN,KxAhYoExB2n7CTK7MLR33EbThQRHptFXfVNVeQQRCqzB2HDns8Z1,1C49D79BCB0CB00ABD53978233A96C51F5588F5BCAD0A586E9481CD1E4055265
BTC,1feeee,1feeeemZP8AatnN71XcnTC1gEJyhNs2y2,KxpqLbQjQJLkgPT46DT3xrwtJyhjnvbcZRNxCDZkY4gwRS2KzEca,2FE7FB263611530702F19618A4431AE6DACC6B99D28C95C9E61A02E393ED236C
BTC,1feeee,1feeeeFGf8ym1PSyYxwKAy1imXZ1BXDTk,L2i2JBvugeL6PfuTSj79jF8rym7WNaMuziM7Zri6eaDR5anStZfV,A3C07C35F08AFB709E6943E26E4E5BDEC03582E39D78E36A91073B137B70F7EF
BTC,1feeee,1feeeeyzsXe6YwhZUeKabEhvKwVwDXk5t,KxSEGrvrPwN2wK2iawymGtwtetCco85JtRLjyGSZKygFpZNnJVPC,24470C8EC90CB246A76EE7972F77CC77660C28211211FC327AA117BEDDB81132

It would be easier to manage in csv format.
CoinName,Prefix,PubAdress,PrivateKeyWIF,PrivateKeyHEX