VanitySearch (Yet another address prefix finder) - page 38.

Jean_Luc

sr. member

Activity: 462

Merit: 701

I ran with your file a bit, even tried to specify your grid size on my old Quadro and it worked.

Code:

pons@linpons:~/VanitySearch$ ./VanitySearch -gpu -gpuId 0,1 -g 544,128,544,128 -i i133.txt
VanitySearch v1.16
Search: 133 addresses (Lookup size 133,[1,1]) [Compressed]
Start Thu Jan 9 15:38:20 2020
Base Key: 1A85D6F37BBEB28577F03B5329E3A2F0DE5D52A5A2781E266353544121CBA9BB
Number of CPU thread: 1
GPU: GPU #1 Quadro 600 (2x48 cores) Grid(544x128)
GPU: GPU #0 Quadro 600 (2x48 cores) Grid(544x128)

[55.40 Mkey/s][GPU 53.46 Mkey/s][Total 2^31.14][Prob 0.0%][50% in 5.79857e+32y][Found 0] ^C

Your git is up to date ?

bangbumbang

jr. member

Activity: 41

Merit: 1

Quote from: Jean_Luc on January 09, 2020, 12:42:45 AM

Just send me the 133 addresses files via pm. May a particular address inside causes the issue.

done...

thinking about it yeah there are 5 addresses in there that are 1 symbol shorter then full length .. and yeah they would be in the 22mil as well, also even shorter ones! an address can get down to 26 symbols.. I think

here is an additional strange thing.. I ran it against the list without the 5 addresses and instead of failing immediately it ran for 3 min. if I put the -t 0 AND the base key started with 7... on E or C or 2... it failed immediately so I startet several times .. always only when the base key starts with 7 it ran for a moment..

Jean_Luc

sr. member

Activity: 462

Merit: 701

Quote from: bangbumbang on January 08, 2020, 04:21:47 PM

this happens with 133 addresses.. same thing after 3sec. but if it helps I can give you the 22 million file.. its about 750mb.. I was just

Just send me the 133 addresses files via pm. May a particular address inside causes the issue.

Firebox

jr. member

Activity: 59

Merit: 3

Quote from: bangbumbang on January 08, 2020, 04:21:47 PM

I dumped the p2pkh and the p2pk addresses from the chainstate of a full node and that's about 22mil at the moment...

Can you upload this file somewhere and share the link?

bangbumbang

jr. member

Activity: 41

Merit: 1

./VanitySearch -gpu -gpuId 0 -i 5000.txt
VanitySearch v1.16
Search: 133 addresses (Lookup size 133,[1,1]) [Compressed]
Start Wed Jan 8 07:56:31 2020
Base Key: CAFFCF119BAE13EAA1F0C053F98BBA2D3982E39B40FB9A991A475F0B46BA4751
Number of CPU thread: 1
GPU: GPU #0 GeForce RTX 2080 Ti (68x64 cores) Grid(544x128)
[2196.82 Mkey/s][GPU 2192.28 Mkey/s][Total 2^37.02][Prob 0.0%][50% in 1.46226e+31y][Found 0] GPUEngine: Launch: an illegal memory access was encountered

this happens with 133 addresses.. same thing after 3sec. but if it helps I can give you the 22 million file.. its about 750mb.. I was just courious about performance with big datasets so I dumped the p2pkh and the p2pk addresses from the chainstate of a full node and that's about 22mil at the moment...
(if you want to do the same I have a tool on my GitHub that can batch convert the pub keys compressed uncompressed and leveldb encoded to there corresponding addresses because they are only in utxo form in the chainstate.. search for pub2addr)
i haven't looked too hard in your code but r u using a hash table instead of a bloom filter.. right?
and at the moment its just research 4 me but im thinking about implementing a vanity searcher on a Xilinx u200 FPGA... MAYBEEEEEEEEEE.. as a bitstream.. and so im looking around at the moment..

./VanitySearch -l
GPU #0 GeForce RTX 2080 Ti (68x64 cores) (Cap 7.5) (11016.3 MB) (Multiple host threads)
GPU #1 GeForce RTX 2080 Ti (68x64 cores) (Cap 7.5) (11019.4 MB) (Multiple host threads)

yes it states Cap 7.5 so compiling with ccap=75 seems right..

Jean_Luc

sr. member

Activity: 462

Merit: 701

Quote from: bangbumbang on January 07, 2020, 07:56:21 AM

Search: 21910565 addresses (Lookup size 65536,[259,3090]) [Compressed or Uncompressed]

I never tried 21 million addresses as you, I have to generate such a list and see what will happen.

Quote from: bangbumbang on January 07, 2020, 07:56:21 AM

ps: I only have Cuda 10 installed and gcc is 7.4.0 and as far as I know ccap 75 is the correct platform.. is it not?

VanitySearch.exe -l
(it gives the ccap)

bangbumbang

jr. member

Activity: 41

Merit: 1

additionally I was looking at this error when others were having them in there Cuda programs..
GPUEngine: Launch: an illegal memory access was encountered

what they pretty much all had in common was that they referenced an index of an array outside the scope of the array i.e.

Code:

my_array[0..4]=....
x = my_array[6]

or they were referencing the array itself before its existence or instantiation

might this happen here only when the grid size gets "this big" (68x64 cores) Grid(544x128) Huh

or more when the core count gets this high, since I did shrink the grid size and it did something but not much???

one more "far out" thing I could think of would be the fact that its an RTX and not a GTX any more, but since Cuda should be backwards compatible it is not something I would really suspect as the cause..

bangbumbang

jr. member

Activity: 41

Merit: 1

Quote from: Jean_Luc on January 07, 2020, 08:20:42 AM

I will try with 2 GPU to see if something is wrong there...

There is no limitation to find the key of an address, only the time needed Cheesy

I tried all I can think of here is what I found, maybe that helps:

removing -t 0 and or -o ... and or -b .. then it runs for exactly 3 sec. with 133 addresses
using different grid size down to 64,128 made it run a few seconds longer .. like 5 sec. or so..
using only gpu 0 then it runs for 30-60 sec. BUT not when using gpu 1... I switched them (pic-e slot) but the same result.. same error..

and still not loading addresses everything works fine...

Firebox

jr. member

Activity: 59

Merit: 3

Quote from: Jean_Luc on January 07, 2020, 03:28:26 AM

I published a new release. 1.16.

Many thanks, Bro! You are the best!

cryptoroy

newbie

Activity: 4

Merit: 0

Quote from: Jean_Luc on January 07, 2020, 08:20:42 AM

I tried with 100003 addresses and it works on my hardware. (also with -b)

C:\C++\VanitySearch\x64\Release>VanitySearch.exe -gpu -i inputfull.txt
[Loading input file 100.0%]
VanitySearch v1.16
[Building lookup16 100.0%]
[Building lookup32 100.0%]
Search: 100003 addresses (Lookup size 51290,[1,9]) [Compressed]
Start Tue Jan 7 14:14:29 2020
Base Key: 1DC7F473D7623CA1A39DDB131AAB773BCA7242CEDD8481E355B7EE4F18964B02
Number of CPU thread: 7
GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x128)
[229.56 Mkey/s][GPU 212.17 Mkey/s][Total 2^30.78][Prob 0.0%][50% in 1.39935e+32y][Found 0]

I will try with 2 GPU to see if something is wrong there...

There is no limitation to find the key of an address, only the time needed Cheesy

Thank you, I'm immortal

))

Jean_Luc

sr. member

Activity: 462

Merit: 701

I tried with 100003 addresses and it works on my hardware. (also with -b)

C:\C++\VanitySearch\x64\Release>VanitySearch.exe -gpu -i inputfull.txt
[Loading input file 100.0%]
VanitySearch v1.16
[Building lookup16 100.0%]
[Building lookup32 100.0%]
Search: 100003 addresses (Lookup size 51290,[1,9]) [Compressed]
Start Tue Jan 7 14:14:29 2020
Base Key: 1DC7F473D7623CA1A39DDB131AAB773BCA7242CEDD8481E355B7EE4F18964B02
Number of CPU thread: 7
GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x128)
[229.56 Mkey/s][GPU 212.17 Mkey/s][Total 2^30.78][Prob 0.0%][50% in 1.39935e+32y][Found 0]

I will try with 2 GPU to see if something is wrong there...

There is no limitation to find the key of an address, only the time needed Cheesy

cryptoroy

newbie

Activity: 4

Merit: 0

Quote from: Jean_Luc on January 07, 2020, 03:28:26 AM

I published a new release. 1.16.
It is now possible to specify freely a grid size and increase performance on certain GPU.

C:\C++\VanitySearch\x64\Release>VanitySearch.exe -t 0 -gpu 1TestMe
VanitySearch v1.16
Difficulty: 888446610539
Search: 1TestMe [Compressed]
Start Tue Jan 7 09:25:30 2020
Base Key: 2AC862CEC11BB2E15C5D864CEF26D3E0640BEA49DA58C4E96F1339B84E466C78
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x128)
[221.77 Mkey/s][GPU 221.77 Mkey/s][Total 2^30.72][Prob 0.2%][50% in 00:46:08][Found 0]

C:\C++\VanitySearch\x64\Release>VanitySearch.exe -t 0 -gpu -g 48,256 1TestMe
VanitySearch v1.16
Difficulty: 888446610539
Search: 1TestMe [Compressed]
Start Tue Jan 7 09:25:52 2020
Base Key: CB77C0255E5A334DCFA5B8788EB0FF6A04EBE360AA13A4D17A114E07EADCCD9F
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x256)
[271.78 Mkey/s][GPU 271.78 Mkey/s][Total 2^31.34][Prob 0.3%][50% in 00:37:35][Found 0]

Hi Jean_Luc, ++++ For your work.

Let me know if VanitySearch is able to find the key of an entire btc address!

Is the number of prefixes limited to 5 or 6 or 7?

thx

bangbumbang

jr. member

Activity: 41

Merit: 1

Hey
@Jean_Luc
first of all great work man!!! Th@nX 4 that.

i am getting CUDA errors though when trying to load more than a few addresses from a file, 5 or 6 work fine but over 100 - error

./VanitySearch -t 0 -gpu -gpuId 0,1 -b -o found.txt -i 150.txt
[Loading input file 100.0%]
VanitySearch v1.16
[Building lookup16 100.0%]
[Building lookup32 100.0%]
Search: 21910565 addresses (Lookup size 65536,[259,3090]) [Compressed or Uncompressed]
Start Tue Jan 7 13:30:08 2020
Base Key: C35B40E791110DE6D0F50C9578EA671F85F32B736E924F285967428735499924
Number of CPU thread: 0
GPU: GPU #0 GeForce RTX 2080 Ti (68x64 cores) Grid(544x128)
GPU: GPU #1 GeForce RTX 2080 Ti (68x64 cores) Grid(544x128)
GPUEngine: Launch: an illegal memory access was encountered
GPUEngine: Launch: an illegal memory access was encountered

i am an ubuntu 18 and did "make gpu=1 ccap=75 all"
everything seems to be working otherwise.. -check reports no errors prefix search no errors and as mentioned a few addresses also no error.
in version 1.15 it was the same ... I tried both today..
don't really know what to do here.. haven't done Cuda programming myself.. at least not jet

so debugging this is a little out of my scope 4 now.
I did try to search on this threat but... well didn't find anything that helped me here..

ps: I only have Cuda 10 installed and gcc is 7.4.0 and as far as I know ccap 75 is the correct platform.. is it not?

Jean_Luc

sr. member

Activity: 462

Merit: 701

I published a new release. 1.16.
It is now possible to specify freely a grid size and increase performance on certain GPU.

C:\C++\VanitySearch\x64\Release>VanitySearch.exe -t 0 -gpu 1TestMe
VanitySearch v1.16
Difficulty: 888446610539
Search: 1TestMe [Compressed]
Start Tue Jan 7 09:25:30 2020
Base Key: 2AC862CEC11BB2E15C5D864CEF26D3E0640BEA49DA58C4E96F1339B84E466C78
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x128)
[221.77 Mkey/s][GPU 221.77 Mkey/s][Total 2^30.72][Prob 0.2%][50% in 00:46:08][Found 0]

C:\C++\VanitySearch\x64\Release>VanitySearch.exe -t 0 -gpu -g 48,256 1TestMe
VanitySearch v1.16
Difficulty: 888446610539
Search: 1TestMe [Compressed]
Start Tue Jan 7 09:25:52 2020
Base Key: CB77C0255E5A334DCFA5B8788EB0FF6A04EBE360AA13A4D17A114E07EADCCD9F
Number of CPU thread: 0
GPU: GPU #0 GeForce GTX 1050 Ti (6x128 cores) Grid(48x256)
[271.78 Mkey/s][GPU 271.78 Mkey/s][Total 2^31.34][Prob 0.3%][50% in 00:37:35][Found 0]

Firebox

jr. member

Activity: 59

Merit: 3

@Jean_Luc
Could you issue new releases with new features more often? See some people have a difficulty to build it.
Let it be beta releases.... why not? ))

Jean_Luc

sr. member

Activity: 462

Merit: 701

I just updated CUDA8 project files for VS2015.
Let me know if it is better...

Jean_Luc

sr. member

Activity: 462

Merit: 701

It seems that you project file (.vcxproj) is not up to date. Wildcard.cpp is missing.
I see that the vcxproj for CUDA8 is not up to date on the git repo. vcxproj for CUDA10 is ok.

zielar

full member

Activity: 282

Merit: 114

Unfortunately, i cannot confirm that on Windows 10 and VS 2015....
This is dump from compilation log:

Code:

1>------ Build started: Project: VanitySearchCUDA8, Configuration: Release x64 ------
1> Compiling CUDA source file GPU\GPUEngine.cu...
1>
1> C:\Users\VAIO\Downloads\appspot\full>"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\bin\nvcc.exe" -gencode=arch=compute_20,code=\"sm_20,compute_20\" --use-local-env --cl-version 2015 -ccbin "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\x86_amd64" -I"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\include" -I"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\include" --keep-dir x64\Release -maxrregcount=0 --ptxas-options=-v --machine 64 --compile -cudart static -D_CRT_SECURE_NO_WARNINGS -DWITHGPU -DWIN32 -DWIN64 -DNDEBUG -D_CONSOLE -D_MBCS -Xcompiler "/EHsc /W3 /nologo /O2 /FS /Zi /MT " -o x64\Release\GPUEngine.cu.obj "C:\Users\VAIO\Downloads\appspot\full\GPU\GPUEngine.cu"
1> ptxas info : 59 bytes gmem, 33456 bytes cmem[2], 8 bytes cmem[14]
1> ptxas info : Compiling entry function '_Z14comp_keys_p2shjPtPjPyjS0_' for 'sm_20'
1> ptxas info : Function properties for _Z14comp_keys_p2shjPtPjPyjS0_
1> 16752 bytes stack frame, 436 bytes spill stores, 868 bytes spill loads
1> ptxas info : Used 63 registers, 80 bytes cmem[0], 28 bytes cmem[16]
1> ptxas info : Function properties for _Z10CheckPointPjiiiPtS_jS_i
1> 72 bytes stack frame, 20 bytes spill stores, 20 bytes spill loads
1> ptxas info : Function properties for _Z11_GetAddressiPjPc
1> 160 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z11_GetHash160PyS_Ph
1> 0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z13CheckP2SHHashjPtPyS0_iPjjS1_
1> 48 bytes stack frame, 44 bytes spill stores, 44 bytes spill loads
1> ptxas info : Function properties for _Z14_ModInvGroupedPA4_y
1> 16592 bytes stack frame, 308 bytes spill stores, 276 bytes spill loads
1> ptxas info : Function properties for _Z15_GetHash160CompPyhPh
1> 0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z17CheckHashP2SHCompPtPyhiPjjS1_
1> 56 bytes stack frame, 32 bytes spill stores, 32 bytes spill loads
1> ptxas info : Function properties for _Z19CheckHashP2SHUncompPtPyS0_iPjjS1_
1> 48 bytes stack frame, 28 bytes spill stores, 28 bytes spill loads
1> ptxas info : Function properties for _Z19_GetHash160P2SHCompPyhPh
1> 24 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z21_GetHash160P2SHUncompPyS_Ph
1> 24 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z6_MatchPKcS0_
1> 0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z7_ModInvPy
1> 96 bytes stack frame, 200 bytes spill stores, 204 bytes spill loads
1> ptxas info : Compiling entry function '_Z17comp_keys_patternjPtPyjPj' for 'sm_20'
1> ptxas info : Function properties for _Z17comp_keys_patternjPtPyjPj
1> 16752 bytes stack frame, 428 bytes spill stores, 852 bytes spill loads
1> ptxas info : Used 63 registers, 72 bytes cmem[0], 28 bytes cmem[16]
1> ptxas info : Function properties for _Z10CheckPointPjiiiPtS_jS_i
1> 72 bytes stack frame, 24 bytes spill stores, 28 bytes spill loads
1> ptxas info : Function properties for _Z11_GetAddressiPjPc
1> 160 bytes stack frame, 4 bytes spill stores, 4 bytes spill loads
1> ptxas info : Function properties for _Z11_GetHash160PyS_Ph
1> 0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z13CheckHashCompPtPyhiPjjS1_
1> 56 bytes stack frame, 32 bytes spill stores, 32 bytes spill loads
1> ptxas info : Function properties for _Z14_ModInvGroupedPA4_y
1> 16592 bytes stack frame, 308 bytes spill stores, 276 bytes spill loads
1> ptxas info : Function properties for _Z15CheckHashUncompPtPyS0_iPjjS1_
1> 56 bytes stack frame, 32 bytes spill stores, 32 bytes spill loads
1> ptxas info : Function properties for _Z15_GetHash160CompPyhPh
1> 0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z6_MatchPKcS0_
1> 0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z7_ModInvPy
1> 96 bytes stack frame, 200 bytes spill stores, 204 bytes spill loads
1> ptxas info : Function properties for _Z9CheckHashjPtPyS0_iPjjS1_
1> 48 bytes stack frame, 44 bytes spill stores, 56 bytes spill loads
1> ptxas info : Compiling entry function '_Z14comp_keys_compPtPjPyjS0_' for 'sm_20'
1> ptxas info : Function properties for _Z14comp_keys_compPtPjPyjS0_
1> 16624 bytes stack frame, 344 bytes spill stores, 668 bytes spill loads
1> ptxas info : Used 63 registers, 72 bytes cmem[0], 28 bytes cmem[16]
1> ptxas info : Function properties for _Z10CheckPointPjiiiPtS_jS_i
1> 80 bytes stack frame, 28 bytes spill stores, 40 bytes spill loads
1> ptxas info : Function properties for _Z11_GetAddressiPjPc
1> 160 bytes stack frame, 4 bytes spill stores, 4 bytes spill loads
1> ptxas info : Function properties for _Z13CheckHashCompPtPyhiPjjS1_
1> 56 bytes stack frame, 36 bytes spill stores, 36 bytes spill loads
1> ptxas info : Function properties for _Z14_ModInvGroupedPA4_y
1> 16592 bytes stack frame, 308 bytes spill stores, 276 bytes spill loads
1> ptxas info : Function properties for _Z15_GetHash160CompPyhPh
1> 0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z6_MatchPKcS0_
1> 0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z7_ModInvPy
1> 96 bytes stack frame, 200 bytes spill stores, 204 bytes spill loads
1> ptxas info : Compiling entry function '_Z22comp_keys_p2sh_patternjPtPyjPj' for 'sm_20'
1> ptxas info : Function properties for _Z22comp_keys_p2sh_patternjPtPyjPj
1> 16752 bytes stack frame, 428 bytes spill stores, 868 bytes spill loads
1> ptxas info : Used 63 registers, 72 bytes cmem[0], 28 bytes cmem[16]
1> ptxas info : Function properties for _Z10CheckPointPjiiiPtS_jS_i
1> 72 bytes stack frame, 20 bytes spill stores, 20 bytes spill loads
1> ptxas info : Function properties for _Z11_GetAddressiPjPc
1> 160 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z11_GetHash160PyS_Ph
1> 0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z13CheckP2SHHashjPtPyS0_iPjjS1_
1> 48 bytes stack frame, 44 bytes spill stores, 44 bytes spill loads
1> ptxas info : Function properties for _Z14_ModInvGroupedPA4_y
1> 16592 bytes stack frame, 308 bytes spill stores, 276 bytes spill loads
1> ptxas info : Function properties for _Z15_GetHash160CompPyhPh
1> 0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z17CheckHashP2SHCompPtPyhiPjjS1_
1> 56 bytes stack frame, 32 bytes spill stores, 32 bytes spill loads
1> ptxas info : Function properties for _Z19CheckHashP2SHUncompPtPyS0_iPjjS1_
1> 48 bytes stack frame, 28 bytes spill stores, 28 bytes spill loads
1> ptxas info : Function properties for _Z19_GetHash160P2SHCompPyhPh
1> 24 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z21_GetHash160P2SHUncompPyS_Ph
1> 24 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z6_MatchPKcS0_
1> 0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z7_ModInvPy
1> 96 bytes stack frame, 200 bytes spill stores, 204 bytes spill loads
1> ptxas info : Compiling entry function '_Z9comp_keysjPtPjPyjS0_' for 'sm_20'
1> ptxas info : Function properties for _Z9comp_keysjPtPjPyjS0_
1> 16752 bytes stack frame, 436 bytes spill stores, 852 bytes spill loads
1> ptxas info : Used 63 registers, 80 bytes cmem[0], 28 bytes cmem[16]
1> ptxas info : Function properties for _Z10CheckPointPjiiiPtS_jS_i
1> 72 bytes stack frame, 24 bytes spill stores, 28 bytes spill loads
1> ptxas info : Function properties for _Z11_GetAddressiPjPc
1> 160 bytes stack frame, 4 bytes spill stores, 4 bytes spill loads
1> ptxas info : Function properties for _Z11_GetHash160PyS_Ph
1> 0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z13CheckHashCompPtPyhiPjjS1_
1> 56 bytes stack frame, 32 bytes spill stores, 32 bytes spill loads
1> ptxas info : Function properties for _Z14_ModInvGroupedPA4_y
1> 16592 bytes stack frame, 308 bytes spill stores, 276 bytes spill loads
1> ptxas info : Function properties for _Z15CheckHashUncompPtPyS0_iPjjS1_
1> 56 bytes stack frame, 32 bytes spill stores, 32 bytes spill loads
1> ptxas info : Function properties for _Z15_GetHash160CompPyhPh
1> 0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z6_MatchPKcS0_
1> 0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
1> ptxas info : Function properties for _Z7_ModInvPy
1> 96 bytes stack frame, 200 bytes spill stores, 204 bytes spill loads
1> ptxas info : Function properties for _Z9CheckHashjPtPyS0_iPjjS1_
1> 48 bytes stack frame, 44 bytes spill stores, 56 bytes spill loads
1>CUDACOMPILE : nvcc warning : The 'compute_20', 'sm_20', and 'sm_21' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning).
1> GPUEngine.cu
1>cl : Command line warning D9002: ignoring unknown option '/arch:SSE2'
1> Base58.cpp
1> Bech32.cpp
1> GPUGenerate.cpp
1> ripemd160.cpp
1> ripemd160_sse.cpp
1> sha256.cpp
1> sha256_sse.cpp
1> sha512.cpp
1> Int.cpp
1> IntGroup.cpp
1> IntMod.cpp
1> main.cpp
1> Point.cpp
1> Random.cpp
1> SECP256K1.cpp
1> Timer.cpp
1> Vanity.cpp
1> Generating Code...
1>Vanity.obj : error LNK2001: unresolved external symbol "public: static bool __cdecl Wildcard::match(char const *,char const *,bool)" (?match@Wildcard@@SA_NPEBD0_N@Z)
1>C:\Users\VAIO\Downloads\appspot\full\x64\Release\VanitySearchCUDA8.exe : fatal error LNK1120: 1 unresolved externals
1>
1>Project Performance Summary:
1> 98084 ms C:\Users\VAIO\Downloads\appspot\full\VanitySearchCUDA8.vcxproj 2 calls
1> 64434 ms Build 1 calls
1> 33650 ms CudaBuildCore 1 calls
1>
1>Target Performance Summary:
1> 0 ms ComputeMIDLGeneratedCompileInputs 1 calls
1> 0 ms PlatformPrepareForBuild 1 calls
1> 0 ms AfterClCompile 1 calls
1> 0 ms BeforeBuildGenerateSources 1 calls
1> 0 ms _ResourceCompile 1 calls
1> 0 ms _PrepareForReferenceResolution 1 calls
1> 0 ms PreLinkEvent 1 calls
1> 0 ms AfterMidl 1 calls
1> 0 ms BeforeResourceCompile 1 calls
1> 0 ms ComputeLinkInputsFromProject 1 calls
1> 0 ms ComputeManifestInputsTargets 1 calls
1> 0 ms ComputeCLInputPDBName 1 calls
1> 0 ms BeforeLink 1 calls
1> 0 ms ComputeManifestGeneratedLinkerInputs 1 calls
1> 0 ms BuildLinkTraverse 1 calls
1> 0 ms ComputeRCOutputs 1 calls
1> 0 ms ModifyUnitTestPlatformVersion 1 calls
1> 0 ms GetReferenceAssemblyPaths 1 calls
1> 0 ms ExpandSDKReferences 1 calls
1> 0 ms _ClCompile 1 calls
1> 0 ms SelectCustomBuild 1 calls
1> 0 ms BuildCompile 1 calls
1> 0 ms _Midl 1 calls
1> 0 ms _PrepareForBuild 1 calls
1> 0 ms BuildCompileTraverse 1 calls
1> 0 ms GetResolvedWinMD 1 calls
1> 0 ms SelectClCompile 1 calls
1> 0 ms CreateCustomManifestResourceNames 1 calls
1> 0 ms _BuildCompileAction 1 calls
1> 0 ms GetInstalledSDKLocations 1 calls
1> 0 ms BuildGenerateSources 1 calls
1> 0 ms AfterResourceCompile 1 calls
1> 0 ms ComputeLegacyManifestEmbedding 1 calls
1> 0 ms ResolveReferences 1 calls
1> 0 ms BuildGenerateSourcesTraverse 1 calls
1> 0 ms _SplitProjectReferencesByFileExistence 1 calls
1> 0 ms ResolveProjectReferences 1 calls
1> 0 ms ComputeCLGeneratedLinkInputs 1 calls
1> 0 ms PrepareForCudaBuild 2 calls
1> 0 ms _Xsd 1 calls
1> 0 ms ResolveSDKReferences 1 calls
1> 0 ms _BuildGenerateSourcesAction 1 calls
1> 0 ms ComputeCustomBuildOutput 1 calls
1> 0 ms ComputeLinkSwitches 1 calls
1> 0 ms AfterBuildGenerateSources 1 calls
1> 0 ms BeforeClCompile 1 calls
1> 0 ms MakeDirsForResourceCompile 1 calls
1> 0 ms PreBuildEvent 1 calls
1> 0 ms ComputeRCGeneratedLinkInputs 1 calls
1> 0 ms AfterBuildCompileEvent 1 calls
1> 0 ms PrepareResourceNames 1 calls
1> 0 ms BeforeResolveReferences 1 calls
1> 0 ms AfterResolveReferences 1 calls
1> 0 ms _SelectedFiles 1 calls
1> 0 ms MakeDirsForMidl 1 calls
1> 0 ms AfterBuildGenerateSourcesEvent 1 calls
1> 1 ms ResolveAssemblyReferences 1 calls
1> 1 ms ValidateCudaCodeGeneration 1 calls
1> 1 ms DoLinkOutputFilesMatch 1 calls
1> 1 ms ComputeReferenceCLInput 1 calls
1> 1 ms MakeDirsForCl 1 calls
1> 1 ms InitializeCudaProjectProperties 1 calls
1> 1 ms ComputeCudaCompileOutput 1 calls
1> 1 ms AssignProjectConfiguration 1 calls
1> 1 ms InitializeCudaHostProperties 1 calls
1> 1 ms Desktop_PlatformPrepareForBuild 1 calls
1> 1 ms SplitResourcesByCulture 1 calls
1> 1 ms FixupCLCompileOptions 1 calls
1> 1 ms MakeDirsForLink 1 calls
1> 1 ms AddCudaLinkMetadata 1 calls
1> 1 ms GetFrameworkPaths 1 calls
1> 1 ms AssignTargetPaths 1 calls
1> 1 ms ValidateCudaBuild 1 calls
1> 2 ms AddCudaCompileMetadata 1 calls
1> 2 ms ComputeCLOutputs 1 calls
1> 3 ms SetBuildDefaultEnvironmentVariables 2 calls
1> 4 ms _CheckForInvalidConfigurationAndPlatform 2 calls
1> 5 ms InitializeBuildStatus 1 calls
1> 6 ms PrepareForBuild 1 calls
1> 8 ms AddCudaCompilePropsDeps 1 calls
1> 10 ms WarnCompileDuplicatedFilename 1 calls
1> 14 ms SetCABuildNativeEnvironmentVariables 1 calls
1> 861 ms Link 1 calls
1> 10804 ms AddCudaCompileDeps 1 calls
1> 18936 ms ClCompile 1 calls
1> 33648 ms CudaBuildCore 1 calls
1> 33757 ms CudaBuild 1 calls
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

I use:
- Windows 10 [newest ver. 1909]
- CUDA 8.0 GA2 (latest version CUDA 8.0)
- Visual Studio 2015 Community
- Windows SDK 10.0.17763.0

Jean_Luc

sr. member

Activity: 462

Merit: 701

Quote from: zielar on January 06, 2020, 06:45:12 AM

1. Are you planning to implement instructions supported by the latest processors? (SSE5, AVX512 etc.)?

I do not have such a processor, just an old core i7-4770. May be few optimizations with AVX2...

Quote from: zielar on January 06, 2020, 06:45:12 AM

2. Will you implement a function that allows you to manually adjust the search scope? (the function is necessary for addresses with a higher degree of difficulty [e.g. 10054102514374868992] where randomness each time the scan is started reduces the potential chance of finding the address faster.

I do not really understand the purpose here. Searching in a specific range (for private keys) does not improve chance of finding a match and you also loose the sym/endo optimizations.

Quote from: zielar on January 06, 2020, 06:45:12 AM

3. I have to compile and test a laptop with GPU on SM_20 architecture [for code testing is enough], but I have a problem with compilation. The highest driver for my [GeForce 410M] card is 391.35, so CUDA 9.2. Compiling on CUDA8 crashes me an error, and CUDA 10 causes an invalid driver error on startup. How do I run VanitySearch without an error on SM_20?

I will try on my linux machine with SM_20 and on an other windows pc set up with cuda 8.

Quote from: zielar on January 06, 2020, 06:45:12 AM

4. What modifications are currently under development and will you publish?

For the moment, the main mods is the possibilitty to set up freely the gridSize (x,y)

Quote from: zielar on January 06, 2020, 06:45:12 AM

You have a typing error in the file GPU/GPUEngine.h (line 59)

Thanks corrected.

zielar

full member

Activity: 282

Merit: 114

I see that you have resumed the project. I enjoy it!
In this connection, I would like to know:
1. Are you planning to implement instructions supported by the latest processors? (SSE5, AVX512 etc.)?
2. Will you implement a function that allows you to manually adjust the search scope? (the function is necessary for addresses with a higher degree of difficulty [e.g. 10054102514374868992] where randomness each time the scan is started reduces the potential chance of finding the address faster.
3. I have to compile and test a laptop with GPU on SM_20 architecture [for code testing is enough], but I have a problem with compilation. The highest driver for my [GeForce 410M] card is 391.35, so CUDA 9.2. Compiling on CUDA8 crashes me an error, and CUDA 10 causes an invalid driver error on startup. How do I run VanitySearch without an error on SM_20?
4. What modifications are currently under development and will you publish?

Regards

[edit]
You have a typing error in the file GPU/GPUEngine.h (line 59)

Code:

GPUEngine(int nbThreadGroup,int nbThreadPerGourp,int gpuId,uint32_t maxFound,bool rekey);

Topic: VanitySearch (Yet another address prefix finder) - page 38. (Read 32072 times)