VanitySearch (Yet another address prefix finder)

[Atariko]

The Cuda version is the most recent and the graphics card drivers are the same. The bug is present on versions VanitySearch1.18 and VanitySearch1.19. What to do help. Videocard 2070super. Sorry for google translate

Hello,

Could you try to run cuda-memcheck.exe. I didn't manage to reproduce this issue. It may end with "Error: process didn't terminate successfully" but this does not prevent the program to run, this error happens in the exit function...

Code:

C:\C++\VanitySearch>"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe" --tool memcheck x64\Release\VanitySearch.exe -t 0 -gpu -stop 1Tst
========= CUDA-MEMCHECK
VanitySearch v1.19
Difficulty: 4553521
Search: 1Tst [Compressed]
Start Wed Aug 26 10:26:21 2020
Base Key: 83F4E602C7131AFCED71A0BD26861B5EED0402F945D3BE944D7E4148FCCA31CB
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x128)
[0.00 Mkey/s][GPU 0.00 Mkey/s][Total 2^-inf][Prob 0.0%][50% in infy][Found 0]
PubAddress: 1TstZdrmCC2HqcacyiteMUxkHTFsoLGxq
Priv (WIF): p2pkh:L3n1tjjp5VBMncFo3PUWBV8fgYPov7JDeQe5SXNXWqrfH17E1ksu
Priv (HEX): 0xC3A4B99A401854FCDF9E276F831E807DDB92031B47843371E503FD1447F0784D
========= Error: process didn't terminate successfully
========= No CUDA-MEMCHECK results found

Found something, the error appears if there are more than 50 addresses in the file (-i inputfile). My settings- VanitySearch119.exe -gpu -r 1000000 -t 0 -g 320,256 -o found.txt -i 50.txt -stop . Version VanitySearch 1.17 works with any number of addresses in the file (-i inputfile)     https://ibb.co/17p2X58

[Atariko]

The Cuda version is the most recent and the graphics card drivers are the same. The bug is present on versions VanitySearch1.18 and VanitySearch1.19. What to do help. Videocard 2070super. Sorry for google translate

Hello,

Could you try to run cuda-memcheck.exe. I didn't manage to reproduce this issue. It may end with "Error: process didn't terminate successfully" but this does not prevent the program to run, this error happens in the exit function...

Code:

C:\C++\VanitySearch>"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe" --tool memcheck x64\Release\VanitySearch.exe -t 0 -gpu -stop 1Tst
========= CUDA-MEMCHECK
VanitySearch v1.19
Difficulty: 4553521
Search: 1Tst [Compressed]
Start Wed Aug 26 10:26:21 2020
Base Key: 83F4E602C7131AFCED71A0BD26861B5EED0402F945D3BE944D7E4148FCCA31CB
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x128)
[0.00 Mkey/s][GPU 0.00 Mkey/s][Total 2^-inf][Prob 0.0%][50% in infy][Found 0]
PubAddress: 1TstZdrmCC2HqcacyiteMUxkHTFsoLGxq
Priv (WIF): p2pkh:L3n1tjjp5VBMncFo3PUWBV8fgYPov7JDeQe5SXNXWqrfH17E1ksu
Priv (HEX): 0xC3A4B99A401854FCDF9E276F831E807DDB92031B47843371E503FD1447F0784D
========= Error: process didn't terminate successfully
========= No CUDA-MEMCHECK results found

It just happened like this:
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe --tool memcheck VanitySearch119.exe -t 0 -gpu -stop 1Tst
========= CUDA-MEMCHECK
VanitySearch v1.19
Difficulty: 4553521
Search: 1Tst [Compressed]
Start Wed Aug 26 12:59:31 2020
Base Key: 55178A21BDB7163ED5182EAA9D89D164A7D8D5ED1270E5627EF8EEAAAA8366C0
Number of CPU thread: 0
GPU: GPU #0 GeForce RTX 2070 SUPER (40x64 cores) Grid(320x128)
[0.00 Mkey/s][GPU 0.00 Mkey/s][Total 2^-inf][Prob 0.0%][50% in infy][Found 0]
PubAddress: 1TstGtwj3gcEnGWoU5qf9RrkYy3HcHht4
Priv (WIF): p2pkh:L2ww7Y8jJg1K47pY5hReciMTwWaKj8kvx8A9crG2qGTY8Wcp9T7a
Priv (HEX): 0xAAE875DE4248E9C12AE7D15562762E9A125606F96CEFBAD940D96FE225B2D873

[Jean_Luc]

Could you try to run cuda-memcheck with your input address file ?

Code:

"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe" VanitySearch119.exe -gpu -r 1000000 -t 0 -g 320,256 -o found.txt -i 50.txt -stop

[Atariko]

Could you try to run cuda-memcheck with your input address file ?

Code:

"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe" VanitySearch119.exe -gpu -r 1000000 -t 0 -g 320,256 -o found.txt -i 50.txt -stop

After about 3 minutes, there is an error, this is with 100 addresses (-i inputfile). There was no error with 50 addresses. With 500 addresses, an error occurs after a few seconds. We are talking about full bitcoin addresses (example: 152hx7Sp822qqWSPHRbK7b8cKdAaPzALqd)
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin>cuda-memcheck.exe VanitySearch119.exe -gpu -r 1000000 -t 0 -g 320,256 -o found.txt -i 100.txt -stop
========= CUDA-MEMCHECK
VanitySearch v1.19
Search: 101 addresses (Lookup size 101,[1,1]) [Compressed]
Start Wed Aug 26 21:57:03 2020
Base Key: Randomly changed every 1000000 Mkeys
Number of CPU thread: 0
GPU: GPU #0 GeForce RTX 2070 SUPER (40x64 cores) Grid(320x256)
[0.00 Mkey/s][GPU 0.00 Mkey/s][Total 2^28.91][Prob 0.0%][50% in infy][Found 0]  GPUEngine: Launch: unspecified launch failure
========= Invalid __local__ read of size 2
=========     at 0x000158a0 in comp_keys_comp(unsigned short*, unsigned int*, __int64*, unsigned int, unsigned int*)
=========     by thread (57,0,0) in block (210,0,0)
=========     Address 0xb1c420bd is misaligned
=========     Device Frame:comp_keys_comp(unsigned short*, unsigned int*, __int64*, unsigned int, unsigned int*) ($_Z14comp_keys_compPtPjPyjS0_$_Z10CheckPointPjiiiPtS_jS_i : 0xb0)
=========     Saved host backtrace up to driver entry point at kernel launch time
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x81ded]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x82187]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86889]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x1777b9]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0xe9822) [0x307de2]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x361dd]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x36601]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x368e4]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuLaunchKernel + 0x234) [0x20e394]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x3096]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x2164]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4f337]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4f09b]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4a98a]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4643f]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= Program hit cudaErrorLaunchFailure (error 719) due to "unspecified launch failure" on CUDA API call to cudaEventQuery.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x9050e) [0x2aeace]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x92eb3) [0x2b1473]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86f17]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x12cd32) [0x34b2f2]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x15e3]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4deaa]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4a98a]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4643f]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= Program hit cudaErrorLaunchFailure (error 719) due to "unspecified launch failure" on CUDA API call to cudaEventDestroy.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x9050e) [0x2aeace]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x92eb3) [0x2b1473]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86f17]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x12cd32) [0x34b2f2]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x14b3]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4debb]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4a98a]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4643f]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= Program hit cudaErrorLaunchFailure (error 719) due to "unspecified launch failure" on CUDA API call to cudaGetLastError.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x9050e) [0x2aeace]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x92eb3) [0x2b1473]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86f17]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x12cd32) [0x34b2f2]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x1e31]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4dec0]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4a98a]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4643f]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= Program hit cudaErrorLaunchFailure (error 719) due to "unspecified launch failure" on CUDA API call to cudaFree.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x9050e) [0x2aeace]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x92eb3) [0x2b1473]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86f17]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x12cd32) [0x34b2f2]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x186c]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4ce72]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4aba8]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4643f]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= Program hit cudaErrorLaunchFailure (error 719) due to "unspecified launch failure" on CUDA API call to cudaFree.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x9050e) [0x2aeace]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x92eb3) [0x2b1473]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86f17]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x12cd32) [0x34b2f2]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x186c]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4ce7b]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4aba8]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4643f]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= Program hit cudaErrorLaunchFailure (error 719) due to "unspecified launch failure" on CUDA API call to cudaFree.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x9050e) [0x2aeace]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x92eb3) [0x2b1473]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86f17]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x12cd32) [0x34b2f2]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x186c]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4ce89]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4aba8]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4643f]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= Program hit cudaErrorLaunchFailure (error 719) due to "unspecified launch failure" on CUDA API call to cudaFreeHost.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x9050e) [0x2aeace]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x92eb3) [0x2b1473]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86f17]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x12cd32) [0x34b2f2]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x198c]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4ce92]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4aba8]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4643f]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= Program hit cudaErrorLaunchFailure (error 719) due to "unspecified launch failure" on CUDA API call to cudaFree.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x9050e) [0x2aeace]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x92eb3) [0x2b1473]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86f17]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x12cd32) [0x34b2f2]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x186c]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4ce9b]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4aba8]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x4643f]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= Program hit CUDA_ERROR_LAUNCH_FAILED (error 719) due to "unspecified launch failure" on CUDA API call to cuModuleUnload.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x9050e) [0x2aeace]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x92eb3) [0x2b1473]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x84cd7]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll [0x86e13]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuProfilerStop + 0x11479a) [0x332d5a]
=========     Host Frame:C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvcuda64.dll (cuModuleUnload + 0x1d6) [0x1d6766]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0xb775]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0xbd76]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0xc3a8]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x3c1d]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x9206]
=========     Host Frame:C:\WINDOWS\System32\ucrtbase.dll (execute_onexit_table + 0x156) [0x13c86]
=========     Host Frame:C:\WINDOWS\System32\ucrtbase.dll (execute_onexit_table + 0x7b) [0x13bab]
=========     Host Frame:C:\WINDOWS\System32\ucrtbase.dll (execute_onexit_table + 0x34) [0x13b64]
=========     Host Frame:C:\WINDOWS\System32\ucrtbase.dll (exit + 0x142) [0x1ff42]
=========     Host Frame:C:\WINDOWS\System32\ucrtbase.dll (exit + 0xcb) [0x1fecb]
=========     Host Frame:C:\WINDOWS\System32\ucrtbase.dll (exit + 0x6e) [0x1fe6e]
=========     Host Frame:C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\VanitySearch119.exe [0x50153]
=========     Host Frame:C:\WINDOWS\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x16fd4]
=========     Host Frame:C:\WINDOWS\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x4cec1]
=========
========= ERROR SUMMARY: 10 errors

C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin>pause
Для пpoдoлжeния нaжмитe любyю клaвишy . . .

[math09183]

Could you try to run cuda-memcheck with your input address file ?

Code:

"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe" VanitySearch119.exe -gpu -r 1000000 -t 0 -g 320,256 -o found.txt -i 50.txt -stop

After about 3 minutes, there is an error, this is with 100 addresses (-i inputfile). There was no error with 50 addresses. With 500 addresses, an error occurs after a few seconds. We are talking about full bitcoin addresses (example: 152hx7Sp822qqWSPHRbK7b8cKdAaPzALqd)

What you do makes no sense at all.

[Atariko]

Could you try to run cuda-memcheck with your input address file ?

Code:

"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe" VanitySearch119.exe -gpu -r 1000000 -t 0 -g 320,256 -o found.txt -i 50.txt -stop

After about 3 minutes, there is an error, this is with 100 addresses (-i inputfile). There was no error with 50 addresses. With 500 addresses, an error occurs after a few seconds. We are talking about full bitcoin addresses (example: 152hx7Sp822qqWSPHRbK7b8cKdAaPzALqd)

What you do makes no sense at all.

The point is for the program to work correctly.

[bangbumbang]

Could you try to run cuda-memcheck with your input address file ?

Code:

"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe" VanitySearch119.exe -gpu -r 1000000 -t 0 -g 320,256 -o found.txt -i 50.txt -stop

After about 3 minutes, there is an error, this is with 100 addresses (-i inputfile). There was no error with 50 addresses. With 500 addresses, an error occurs after a few seconds. We are talking about full bitcoin addresses (example: 152hx7Sp822qqWSPHRbK7b8cKdAaPzALqd)

What you do makes no sense at all.

The point is for the program to work correctly.

just to chime in here since i have the same error since 2 month ago... and yep it also craches from 50--100 addresses and upwards



>"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin\cuda-memcheck.exe" VanitySearch.exe -b -t 0 -gpu -gpuId 0 -g 540,512 -m 1520000 -r 44400 -o found_0.txt -i 20.txt
========= CUDA-MEMCHECK
[Loading input file 100.0%]
VanitySearch v1.19
[Building lookup16  98.9%]
[Building lookup32 100.0%]
Search: 67714 addresses (Lookup size 42081,[1,11]) [Compressed or Uncompressed]
Start Tue Sep  1 11:49:36 2020
Base Key: Randomly changed every 44400 Mkeys
Number of CPU thread: 0
GPU: GPU #0 GeForce RTX 2080 Ti (68x64 cores) Grid(540x512)
GPUEngine: Kernel: too many resources requested for launch
========= Program hit cudaErrorLaunchOutOfResources (error 701) due to "too many resources requested for launch" on CUDA API call to cudaLaunchKernel.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll (cuProfilerStop + 0x8ff3e) [0x2ad53e]
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll (cuProfilerStop + 0x928e3) [0x2afee3]
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll [0x86ebe]
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll (cuProfilerStop + 0x113e8a) [0x33148a]
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll (cuProfilerStop + 0x12c212) [0x349812]
=========     Host Frame:C:\Users\x\Desktop\VS\VanitySearch.exe [0x2199]
=========     Host Frame:C:\Users\x\Desktop\VS\VanitySearch.exe [0x4f214]
=========     Host Frame:C:\Users\x\Desktop\VS\VanitySearch.exe [0x4f0ca]
=========     Host Frame:C:\Users\x\Desktop\VS\VanitySearch.exe [0x4a922]
=========     Host Frame:C:\Users\x\Desktop\VS\VanitySearch.exe [0x4643f]
=========     Host Frame:C:\Windows\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x17bd4]
=========     Host Frame:C:\Windows\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x6ce51]
=========
========= Program hit cudaErrorLaunchOutOfResources (error 701) due to "too many resources requested for launch" on CUDA API call to cudaGetLastError.
=========     Saved host backtrace up to driver entry point at error
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll (cuProfilerStop + 0x8ff3e) [0x2ad53e]
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll (cuProfilerStop + 0x928e3) [0x2afee3]
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll [0x86ebe]
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll (cuProfilerStop + 0x113e8a) [0x33148a]
=========     Host Frame:C:\Windows\system32\DriverStore\FileRepository\nv_dispui.inf_amd64_ae0a6307e8a28cc4\nvcuda64.dll (cuProfilerStop + 0x12c212) [0x349812]
=========     Host Frame:C:\Users\x\Desktop\VS\VanitySearch.exe [0x1e31]
=========     Host Frame:C:\Users\x\Desktop\VS\VanitySearch.exe [0x4f0cf]
=========     Host Frame:C:\Users\x\Desktop\VS\VanitySearch.exe [0x4a922]
=========     Host Frame:C:\Users\x\Desktop\VS\VanitySearch.exe [0x4643f]
=========     Host Frame:C:\Windows\System32\KERNEL32.DLL (BaseThreadInitThunk + 0x14) [0x17bd4]
=========     Host Frame:C:\Windows\SYSTEM32\ntdll.dll (RtlUserThreadStart + 0x21) [0x6ce51]
=========
========= ERROR SUMMARY: 2 errors

[gmaxwell]

JeanLuc (and others),

Do you have any references for the work required for the best multi-target discrete log attacks?

For the test vectors for BIP340 it would be extremely useful if there was a test vectors where the signature R or Pubkey's x value had an usually large value in the range the scalar order [0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364141, 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEFFFFFC2F) (between the scalar order and the field order).  Test vectors using points with a value inside this range would test if an implementation isn't erroneously reducing these inputs mod Fn or considering them as too large (e.g. by mistakenly using the Fn overflow test that they use for deserializing the S value in signatures).

To construct tests like this we would need a point with an x in this range where we know the discrete log.

One way to perform this test is to just mock the choice of G in the cryptosystem, if you can pick G you can make any single chosen point have a known DL. ... but having test vectors which require the implementation to use a different G means that the test can't be just applied to an unmodified system, so it's less useful.

Because this range is pretty large-- about 129 bits-- there are ~2^129 acceptable keys...  It sounds to me like it might be feasible for a multi-target discrete log search to find a solution. If so, it would be a record breaking computation that would be practically useful in addition to offering bragging rights.

But it's not clear to me if this actually feasible or what the concrete computational cost would be of the best known multi-target attack.

[I'm posting in this thread because it's obviously most related to vanity search, in particular, it's a vanitysearch for an address prefix "BC1QLLLLLLLLLLLLLLLLLLLLLLLLL"

[j2002ba2]

Do you have any references for the work required for the best multi-target discrete log attacks?

AFAIK there are no multi-target ECDLP algorithms.

Since the private key is not restricted, only the usual Pollard Rho is applicable. Selecting a single public key from the desired range, and doing 2^128 group operations (more or less).

[I'm posting in this thread because it's obviously most related to vanity search, in particular, it's a vanitysearch for an address prefix "BC1QLLLLLLLLLLLLLLLLLLLLLLLLL"

Taproot addresses should start with "BC1P".

[Jean_Luc]

In fact a parallel kangaroo program that look for a single key creates several pubkeys from this key (by simply translating it). So this is a multi key search but this does not decrease the probability to solve this single key. It just allows a simple parallelization.

Usually, for a multi target attack, the first key has no benefit but the following keys can gain from the previous calculation.
If you want to search a pubkey with a x starting with 32 leading F (between n and p), you will have to perform ~2^128 group operations.

[bigvito19]

In fact a parallel kangaroo program that look for a single key creates several pubkeys from this key (by simply translating it). So this is a multi key search but this does not decrease the probability to solve this single key. It just allows a simple parallelization.

Usually, for a multi target attack, the first key has no benefit but the following keys can gain from the previous calculation.
If you want to search a pubkey with a x starting with 32 leading F (between n and p), you will have to perform ~2^128 group operations.

@Jean_Luc

What exactly is the base key and why we can't manually change it?

[Jean_Luc]

@Jean_Luc

What exactly is the base key and why we can't manually change it?

The base key is the key used for starting calculation from. This key is transformed (translation,symmetry and endomorphism) until the target prefix is reached. This base key is generated randomly or from a pass phrase.
There is no way to set it manually to a specific value.

[Atariko]

Why don't VanitySearch1.18 and VanitySearch1.19 versions work for me, reports the error GPUEngine: Launch: an illegal memory access was encountered, and VanitySearch1.17 version works correctly? Help me to understand.

Why is there no answer? Jean Luc ask for an answer on this question. All data I have provided.

[Jean_Luc]

Why is there no answer? Jean Luc ask for an answer on this question. All data I have provided.

I'm sorry but I didn't manage to reproduce the issue.
It is the same if you try to reduce the grid size ?

[Atariko]

Why is there no answer? Jean Luc ask for an answer on this question. All data I have provided.

I'm sorry but I didn't manage to reproduce the issue.
It is the same if you try to reduce the grid size ?

When reducing the grid, the error -GPUEngine: Launch: unspecified launch failure. And when enlarging the grid, the error -GPUEngine: Kernel: too many resources requested for launch. https://fex.net/ru/s/sfypzfa  link to check

[Jean_Luc]

Why is there no answer? Jean Luc ask for an answer on this question. All data I have provided.

I'm sorry but I didn't manage to reproduce the issue.
It is the same if you try to reduce the grid size ?

When reducing the grid, the error -GPUEngine: Launch: unspecified launch failure. And when enlarging the grid, the error -GPUEngine: Kernel: too many resources requested for launch. https://fex.net/ru/s/sfypzfa  link to check

I tried your file and for me it is ok...

Code:

C:\C++\VanitySearch>x64\Release\VanitySearch.exe -t 0 -gpu -g 320,256 -i 500.txt
VanitySearch v1.19
Search: 500 addresses (Lookup size 33,[3,47]) [Compressed]
Start Wed Sep  9 15:57:18 2020
Base Key: E7D91B106BF65AFD901C7E2ED61D78DFD4C2EB2C8CCDFE8C108A40DABFCF8443
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(320x256)
[188.53 Mkey/s][GPU 188.53 Mkey/s][Total 2^33.61][Prob 0.0%][50% in 1.70385e+32y][Found 0]

[Atariko]

Why is there no answer? Jean Luc ask for an answer on this question. All data I have provided.

I'm sorry but I didn't manage to reproduce the issue.
It is the same if you try to reduce the grid size ?

When reducing the grid, the error -GPUEngine: Launch: unspecified launch failure. And when enlarging the grid, the error -GPUEngine: Kernel: too many resources requested for launch. https://fex.net/ru/s/sfypzfa  link to check

I tried your file and for me it is ok...

Code:

C:\C++\VanitySearch>x64\Release\VanitySearch.exe -t 0 -gpu -g 320,256 -i 500.txt
VanitySearch v1.19
Search: 500 addresses (Lookup size 33,[3,47]) [Compressed]
Start Wed Sep  9 15:57:18 2020
Base Key: E7D91B106BF65AFD901C7E2ED61D78DFD4C2EB2C8CCDFE8C108A40DABFCF8443
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(320x256)
[188.53 Mkey/s][GPU 188.53 Mkey/s][Total 2^33.61][Prob 0.0%][50% in 1.70385e+32y][Found 0]

I wonder why it works for you and not for me.
My configuration: windows 10 latest updates , graphics card MSI 2070 super  and cuda last version. What could be the problem? Can someone else on the site run my build and check? Link above.

P.S.  VanitySearch119.exe -r 100000 -t 0 -g 320,256 -o found.txt -i 50.txt   This configuration works without problems.

[bitcoinunide]

Hello Jean Luc  & VanitySearch enthusiasts,

what is the specific calculation for key merging of Bech32 Address Format?

What is the difference by calculating the final private key of legacy & P2SH to Bech32?


I am working on a secure splitkey-only Vanity address service and i need to build a javascript keymergingtool for Bech32 (for using in inkognito browser offline).
I already tried to understand the main.cpp in line 248 'reconstructadd' function, to get the specific mathematical operation, but i dont understood it.



So how do i compute a bech32 address from partialkeys?

 
Thanks for your answers and especially Jean Luc for your awesome Software!

[Jean_Luc]

The final private key reconstruction is explained in the README for the simple case https://github.com/JeanLucPons/VanitySearch#how-it-works
This is what is done at the line 323 of main.cpp. Then you find the 5 other cases for symmetry and endomorphism.
The information of which case (out of the 6) has matched during the search is not in the partial key file, the reconstruction just test the 6 cases until one match.
For the reconstruction of a BECH32 address, you simply compute a BECH32 address from the final private key, this is what is done the CHECK_ADDR() macro at line 238 of main.cpp.

Note: The secret private key passed through the command line for reconstruction is stored in e.

Code:

#define CHECK_ADDR()                                           \
  fullPriv.ModAddK1order(&e, &partialPrivKey);                 \   # Compute the final private key (partialKey + secretKey mod n)
  p = secp->ComputePublicKey(&fullPriv);                       \   # Compute the corresponding public key
  cAddr = secp->GetAddress(addrType, compressed, p);           \   # Compute the corresponding address (for BECH32, addrType=2 defined in SECP256k1.h)
  if (cAddr == addr) {                                         \   # Test if it matches
    found = true;                                              \
    string pAddr = secp->GetPrivAddress(compressed, fullPriv); \
    string pAddrHex = fullPriv.GetBase16();                    \
    outputAdd(outputFile, addrType, addr, pAddr, pAddrHex);    \
  }

[bigvito19]

@Jean_Luc

So you couldn't add where we could search for collisions with a public key? or a prefix at least?

https://github.com/JeanLucPons/BTCCollider