Topic: VanitySearch (Yet another address prefix finder) - page 8. (Read 32966 times)
Sorry if this seems like a dumb question. But wouldn't it be more effective and much more performant to use an ASIC miner for the computational tasks of VanitySearch instead of a modern GPU? My GPU does 1,750 MKeys/sec and in comparison to that a GekkoScience Compac F USBminer does about 300 GHashes per second. Is there possibly a VanitySearch version that uses such a Compac F for the calculation and thus works much faster, any clues ?
Workaround:
Instead of using g++-11 compiler you should install and use g++-9 and re-compile from scratch. There's obviously going something wrong when using version 11. But Version9 works!!!
Instead of using g++-11 compiler you should install and use g++-9 and re-compile from scratch. There's obviously going something wrong when using version 11. But Version9 works!!!
I'm pretty sure version 11 or perhaps 10 introduced some default optimization flag which breaks the checksum computation algorithm for the GPU code. Might want to look into compiling with -g or -O0.
have you python version of group addition ? i tryed to understund how VanitySearch group addition works but c+ is hard to me
Workaround:
Instead of using g++-11 compiler you should install and use g++-9 and re-compile from scratch. There's obviously going something wrong when using version 11. But Version9 works!!!
Instead of using g++-11 compiler you should install and use g++-9 and re-compile from scratch. There's obviously going something wrong when using version 11. But Version9 works!!!
I'm pretty sure version 11 or perhaps 10 introduced some default optimization flag which breaks the checksum computation algorithm for the GPU code. Might want to look into compiling with -g or -O0.
Workaround:
Instead of using g++-11 compiler you should install and use g++-9 and re-compile from scratch. There's obviously going something wrong when using version 11. But Version9 works!!!
and the calculated pub addresses are correct now. I'm happy so far
Instead of using g++-11 compiler you should install and use g++-9 and re-compile from scratch. There's obviously going something wrong when using version 11. But Version9 works!!!
Code:
$ ./VanitySearch -check
Quote
$ ./VanitySearch -check
GetBase10() Results OK
Add() Results OK : 400.000 MegaAdd/sec
Mult() Results OK : 48.077 MegaMult/sec
Div() Results OK : 15.152 MegaDiv/sec
R1=1000003D1
R2=1000007A2000E90A1
Field characteristic size: 256bits
ModInv()/ModExp() Results OK
ModInv() Edge cases Results OK
.Avg = 6.13
ModInv() Results OK : 929.515 KiloInv/sec
ModInv() cycles : 2685.26
ModSqrt() Results OK !
IntGroup.ModInv() Results OK : 12.757 MegaInv/sec
ModMulK1() Results OK : 47.549 MegaMult/sec
ModSquareK1() Results OK : 53.285 MegaSqr/sec
ModInv() Cost : 114.7 S
ModMulK1order() Results OK : 8.427 MegaMult/sec
Check Generator :OK
Check Double :OK
Check Add :OK
Check GenKey :OK
Adress : 15t3Nt1zyMETkHbjJTTshxLnqPzQvAtdCe OK!
Adress : 1BoatSLRHtKNngkdXEeobR76b53LETtpyT OK!
Adress : 1Test6BNjSJC5qwYXsjwKVLvz7DpfLehy OK!
Adress : 16S5PAsGZ8VFM1CRGGLqm37XHrp46f6CTn OK!
Adress : 1Tst2RwMxZn9cYY5mQhCdJic3JJrK7Fq7 OK!
Adress : 3CyQYcByvcWK8BkYJabBS82yDLNWt6rWSx OK!
Adress : 31to1KQe67YjoDfYnwFJThsGeQcFhVDM5Q OK!
Adress : bc1q6tqytpg06uhmtnhn9s4f35gkt8yya5a24dptmn OK!
Check Calc PubKey (full) 1ViViGLEawN27xRzGrEhhYPQrZiTKvKLo :OK
Check Calc PubKey (even) 385cR5DM96n1HvBDMzLHPYcw89fZAXULJP:OK
Check Calc PubKey (odd) 18aPiLmTow7Xgu96msrDYvSSWweCvB9oBA:OK
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x128 cores) Grid(320x128)
Seed: 1663082517
1.553 GigaKey/sec
ComputeKeys() found 7711 items , CPU check...
^C
GetBase10() Results OK
Add() Results OK : 400.000 MegaAdd/sec
Mult() Results OK : 48.077 MegaMult/sec
Div() Results OK : 15.152 MegaDiv/sec
R1=1000003D1
R2=1000007A2000E90A1
Field characteristic size: 256bits
ModInv()/ModExp() Results OK
ModInv() Edge cases Results OK
.Avg = 6.13
ModInv() Results OK : 929.515 KiloInv/sec
ModInv() cycles : 2685.26
ModSqrt() Results OK !
IntGroup.ModInv() Results OK : 12.757 MegaInv/sec
ModMulK1() Results OK : 47.549 MegaMult/sec
ModSquareK1() Results OK : 53.285 MegaSqr/sec
ModInv() Cost : 114.7 S
ModMulK1order() Results OK : 8.427 MegaMult/sec
Check Generator :OK
Check Double :OK
Check Add :OK
Check GenKey :OK
Adress : 15t3Nt1zyMETkHbjJTTshxLnqPzQvAtdCe OK!
Adress : 1BoatSLRHtKNngkdXEeobR76b53LETtpyT OK!
Adress : 1Test6BNjSJC5qwYXsjwKVLvz7DpfLehy OK!
Adress : 16S5PAsGZ8VFM1CRGGLqm37XHrp46f6CTn OK!
Adress : 1Tst2RwMxZn9cYY5mQhCdJic3JJrK7Fq7 OK!
Adress : 3CyQYcByvcWK8BkYJabBS82yDLNWt6rWSx OK!
Adress : 31to1KQe67YjoDfYnwFJThsGeQcFhVDM5Q OK!
Adress : bc1q6tqytpg06uhmtnhn9s4f35gkt8yya5a24dptmn OK!
Check Calc PubKey (full) 1ViViGLEawN27xRzGrEhhYPQrZiTKvKLo :OK
Check Calc PubKey (even) 385cR5DM96n1HvBDMzLHPYcw89fZAXULJP:OK
Check Calc PubKey (odd) 18aPiLmTow7Xgu96msrDYvSSWweCvB9oBA:OK
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x128 cores) Grid(320x128)
Seed: 1663082517
1.553 GigaKey/sec
ComputeKeys() found 7711 items , CPU check...
^C
and the calculated pub addresses are correct now. I'm happy so far
No, the second computer I used is something completely different. But I want to emphasize that I compiled with a simple
and thus no GPU support. The test I run after the successful compile is just
again, no GPU is in use here.
Code:
make
Code:
./VanitySearch -check
Well, I did some more checks and troubleshooting and have found maybe some valuable information that may leed finding the culprit.
What I simply did: downloading a specific release version, unzip and then just run "make" so it won't get compiled with gpu support. Then I execute "./VanitySearch -check" to see if it works or fails.
I started from latest release 1.19 and went down step by step. Release version 1.13 is the one that works without errors. Everything later than 1.13 will throw an error on my computer.
I continued playing around with 1.13, mean I first reverted everything back
then modified the Makefile and replaced lines 33-36 to fit to my system
and the compiled again with GPU support. Please note that you need to specify the ccap variable name in lower-case, else it won't work. This was corrected in later version in future.
Then I ran a real test and the results were all correct. Works!
Summary so far: Whatever change were made after 1.13 obviously leads to the mentioned error.. Anyone is welcome to test and try to reproduce. Maybe Jean_Luc can test and proof and fix this ?
EDIT: On a different computer I download the latest master 1.19 version, unzipped, executed "make && ./VanitySearch -check" and it worked like a charm. That means on another computer there's no issue. I am not sure what the error is related to. Any hints? Jean_Luc, do you happen to be there and give us some hints?
What I simply did: downloading a specific release version, unzip and then just run "make" so it won't get compiled with gpu support. Then I execute "./VanitySearch -check" to see if it works or fails.
I started from latest release 1.19 and went down step by step. Release version 1.13 is the one that works without errors. Everything later than 1.13 will throw an error on my computer.
I continued playing around with 1.13, mean I first reverted everything back
Code:
make clean
then modified the Makefile and replaced lines 33-36 to fit to my system
Quote
CXX = g++
CUDA = /usr/local/cuda-11.7
CXXCUDA = /usr/bin/g++-11
NVCC = $(CUDA)/bin/nvcc
CUDA = /usr/local/cuda-11.7
CXXCUDA = /usr/bin/g++-11
NVCC = $(CUDA)/bin/nvcc
and the compiled again with GPU support. Please note that you need to specify the ccap variable name in lower-case, else it won't work. This was corrected in later version in future.
Code:
make gpu=1 ccap=86 all
Code:
./VanitySearch -check
Quote
GetBase10() Results OK
Add() Results OK : 1.250 GigaAdd/sec
Mult() Results OK : 60.606 MegaMult/sec
Div() Results OK : 8.000 MegaDiv/sec
ModInv()/ModExp() Results OK
ModInv() Results OK : 430.389 KiloInv/sec
IntGroup.ModInv() Results OK : 14.674 MegaInv/sec
ModMulK1() Results OK : 21.432 MegaMult/sec
ModSquareK1() Results OK : 20.982 MegaMult/sec
ModMulK1order() Results OK : 9.701 MegaMult/sec
ModSqrt() Results OK !
Check Generator :OK
Check Double :OK
Check Add :OK
Check GenKey :OK
Adress : 15t3Nt1zyMETkHbjJTTshxLnqPzQvAtdCe OK!
Adress : 1BoatSLRHtKNngkdXEeobR76b53LETtpyT OK!
Adress : 1Test6BNjSJC5qwYXsjwKVLvz7DpfLehy OK!
Adress : 16S5PAsGZ8VFM1CRGGLqm37XHrp46f6CTn OK!
Adress : 1Tst2RwMxZn9cYY5mQhCdJic3JJrK7Fq7 OK!
Adress : 3CyQYcByvcWK8BkYJabBS82yDLNWt6rWSx OK!
Adress : 31to1KQe67YjoDfYnwFJThsGeQcFhVDM5Q OK!
Adress : bc1q6tqytpg06uhmtnhn9s4f35gkt8yya5a24dptmn OK!
Check Calc PubKey (full) 1ViViGLEawN27xRzGrEhhYPQrZiTKvKLo :OK
Check Calc PubKey (even) 1Gp7rQ4GdooysEAEJAS2o4Ktjvf1tZCihp:OK
Check Calc PubKey (odd) 18aPiLmTow7Xgu96msrDYvSSWweCvB9oBA:OK
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x0 cores) Grid(320x128)
Seed: 63852
1.488 GigaKey/sec
ComputeKeys() found 7712 items , CPU check...
^C
Add() Results OK : 1.250 GigaAdd/sec
Mult() Results OK : 60.606 MegaMult/sec
Div() Results OK : 8.000 MegaDiv/sec
ModInv()/ModExp() Results OK
ModInv() Results OK : 430.389 KiloInv/sec
IntGroup.ModInv() Results OK : 14.674 MegaInv/sec
ModMulK1() Results OK : 21.432 MegaMult/sec
ModSquareK1() Results OK : 20.982 MegaMult/sec
ModMulK1order() Results OK : 9.701 MegaMult/sec
ModSqrt() Results OK !
Check Generator :OK
Check Double :OK
Check Add :OK
Check GenKey :OK
Adress : 15t3Nt1zyMETkHbjJTTshxLnqPzQvAtdCe OK!
Adress : 1BoatSLRHtKNngkdXEeobR76b53LETtpyT OK!
Adress : 1Test6BNjSJC5qwYXsjwKVLvz7DpfLehy OK!
Adress : 16S5PAsGZ8VFM1CRGGLqm37XHrp46f6CTn OK!
Adress : 1Tst2RwMxZn9cYY5mQhCdJic3JJrK7Fq7 OK!
Adress : 3CyQYcByvcWK8BkYJabBS82yDLNWt6rWSx OK!
Adress : 31to1KQe67YjoDfYnwFJThsGeQcFhVDM5Q OK!
Adress : bc1q6tqytpg06uhmtnhn9s4f35gkt8yya5a24dptmn OK!
Check Calc PubKey (full) 1ViViGLEawN27xRzGrEhhYPQrZiTKvKLo :OK
Check Calc PubKey (even) 1Gp7rQ4GdooysEAEJAS2o4Ktjvf1tZCihp:OK
Check Calc PubKey (odd) 18aPiLmTow7Xgu96msrDYvSSWweCvB9oBA:OK
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x0 cores) Grid(320x128)
Seed: 63852
1.488 GigaKey/sec
ComputeKeys() found 7712 items , CPU check...
^C
Then I ran a real test and the results were all correct. Works!
Summary so far: Whatever change were made after 1.13 obviously leads to the mentioned error.. Anyone is welcome to test and try to reproduce. Maybe Jean_Luc can test and proof and fix this ?
EDIT: On a different computer I download the latest master 1.19 version, unzipped, executed "make && ./VanitySearch -check" and it worked like a charm. That means on another computer there's no issue. I am not sure what the error is related to. Any hints? Jean_Luc, do you happen to be there and give us some hints?
without providing the argument to compile with GPU capabilities. -snip-
it still throws errors. Tried the release and master branch. IMHO the bug is not in the GPU/Cuda part but somewhere else ?
I think you should start with the compiler or other requirement, see if you satisfied the required versions, specially gcc sinceit still throws errors. Tried the release and master branch. IMHO the bug is not in the GPU/Cuda part but somewhere else ?
you already tried the release which should work without an issue, also compiled without CUDA.
Other that that, I have no other comment since I can't reproduce it.
No luck here. I did
without providing the argument to compile with GPU capabilities. But when I run
it still throws errors. Tried the release and master branch. IMHO the bug is not in the GPU/Cuda part but somewhere else ?
Code:
make clean && make all
without providing the argument to compile with GPU capabilities. But when I run
Code:
./VanitySearch -check
it still throws errors. Tried the release and master branch. IMHO the bug is not in the GPU/Cuda part but somewhere else ?
Just tried this. No luck! I also tried using all the available codes for my GPU which I got with
-snip-
You also tried it without a -gpu parameter and it still produced an invalid WIF PrvKey and address...-snip-
Anyways, have you tried to compile the source code from vanitysearch's releases instead of the master branch?
I think the best course of action is to support the existing issue in GitHub by adding more info.
The developer may need it to fix the issue.
Just like the result in your vanitySearch -check command, the checksum here is also invalid.
The first four Bytes of SHA256[SHA256(80F30DBBB1FFF76EBF9741202CCE4676B6258ACCAF648C040844D9796F239AD99801)] should be: 0xA3B0A194
while the invalid WIF private key has: 0x6B4E251C, so it didn't pass the checksum.
Same with the address, 1citboYAWtgbJCySZe8C7U7y36cxGfZUZ has an invalid checksum of 0xB071873E
The first four Bytes of SHA256[SHA256(0006C186C1421FF64024B3FC356AF312061DE52688)] should be: 0x054A4884
Someone has reported a similar issue (also using a GPU): https://github.com/JeanLucPons/VanitySearch/issues/124
BTW, I'm not experiencing this when only using CPU.
The first four Bytes of SHA256[SHA256(80F30DBBB1FFF76EBF9741202CCE4676B6258ACCAF648C040844D9796F239AD99801)] should be: 0xA3B0A194
while the invalid WIF private key has: 0x6B4E251C, so it didn't pass the checksum.
Same with the address, 1citboYAWtgbJCySZe8C7U7y36cxGfZUZ has an invalid checksum of 0xB071873E
The first four Bytes of SHA256[SHA256(0006C186C1421FF64024B3FC356AF312061DE52688)] should be: 0x054A4884
Someone has reported a similar issue (also using a GPU): https://github.com/JeanLucPons/VanitySearch/issues/124
BTW, I'm not experiencing this when only using CPU.
That means the CUDA code for generating address checksums is wrong, which is not surprising to me since VanityGen was retrofitted using Kangaroo source code (which does not have this subsystem), so probably wasn't tested thoroughly enough.
Just tried this. No luck! I also tried using all the available codes for my GPU which I got with
VanitySearch -check always returning errors.
Which Nvidia drivers and CUDA version do you use, can you post some more details ?[/code]
Code:
/usr/local/cuda-11.7/bin/nvcc --list-gpu-code[/quote]
I compiled and tried all these available GPU codes:
[code]
$ /usr/local/cuda-11.7/bin/nvcc --list-gpu-code
sm_35
sm_37
sm_50
sm_52
sm_53
sm_60
sm_61
sm_62
sm_70
sm_72
sm_75
sm_80
sm_86
sm_87
Which Nvidia drivers and CUDA version do you use, can you post some more details ?[/code]
According to the output on the second search while omitting the GPU flag it shows only "Number of CPU thread used" = 1 and no hint about GPU. But the error is still there, the calculation is wrong.
Hmm, that's weird since I'm not experiencing that using Vanitysearch v1.19 (release).Here's the result of ./vanitysearch -check command:
Code:
GetBase10() Results OK
Add() Results OK : 666.667 MegaAdd/sec
Mult() Results OK : 44.209 MegaMult/sec
Div() Results OK : 5.368 MegaDiv/sec
ModInv()/ModExp() Results OK
ModInv() Results OK : 531.457 KiloInv/sec
IntGroup.ModInv() Results OK : 9.421 MegaInv/sec
ModMulK1() Results OK : 39.186 MegaMult/sec
ModSquareK1() Results OK : 47.253 MegaSqr/sec
ModInv() Cost : 88.9 S
ModMulK1order() Results OK : 6.737 MegaMult/sec
ModSqrt() Results OK !
Check Generator :OK
Check Double :OK
Check Add :OK
Check GenKey :OK
Adress : 15t3Nt1zyMETkHbjJTTshxLnqPzQvAtdCe OK!
Adress : 1BoatSLRHtKNngkdXEeobR76b53LETtpyT OK!
Adress : 1Test6BNjSJC5qwYXsjwKVLvz7DpfLehy OK!
Adress : 16S5PAsGZ8VFM1CRGGLqm37XHrp46f6CTn OK!
Adress : 1Tst2RwMxZn9cYY5mQhCdJic3JJrK7Fq7 OK!
Adress : 3CyQYcByvcWK8BkYJabBS82yDLNWt6rWSx OK!
Adress : 31to1KQe67YjoDfYnwFJThsGeQcFhVDM5Q OK!
Adress : bc1q6tqytpg06uhmtnhn9s4f35gkt8yya5a24dptmn OK!
Check Calc PubKey (full) 1ViViGLEawN27xRzGrEhhYPQrZiTKvKLo :OK
Check Calc PubKey (even) 385cR5DM96n1HvBDMzLHPYcw89fZAXULJP:OK
Check Calc PubKey (odd) 18aPiLmTow7Xgu96msrDYvSSWweCvB9oBA:OK
GPUEngine: CudaGetDeviceCount CUDA driver version is insufficient for CUDA runtime version 35
A quick test using your command: ./vanitySearch -stop 1cit:
Code:
PubAddress: 1citZrQ1cZ5Hhx62v4uzv5rVHvv84hCUc
Priv (WIF): p2pkh:L2yxjxkwLKAoanYJ7f5SE2z82UVoPmGQdksjyWdsBGDn3dwLHasP
Priv (HEX): 0xABF38C98E8F446012CA1C5F40D8E96761DE1E2F10A1B06A8A642316F20EB04B6
Have you compiled directly from the master branch?
If so, try to build from the 'releases tags' instead, specifically v1.19 (link).
The issue may have been introduced by the last few commits after Aug 10, 2020.
Quote
$ ./VanitySearch -gpu -stop 1cit
Code:
VanitySearch v1.19
Difficulty: 4553521
Search: 1cit [Compressed]
Start Sun Aug 28 12:02:43 2022
Base Key: FF4374C8A994CB92A73E269619F6019E79F940A6617B9B0AF8E79179A38BE6B9
Number of CPU thread: 1
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x128 cores) Grid(320x128)
PubAddress: 1citMwSBYgWGTNtgmRsrb89nKbt3jDzPK
Priv (WIF): p2pkh:KwF9Dkr1yn25tZS9RoD5pDZiZMKcZNqCUz6qAUbfv414DguNxe6z
Priv (HEX): 0xBC8B37566B346D58C1D969E609FE6040B59C404DCD0530C6EACD132CA2C723
Quote
$ ./VanitySearch -stop 1cit
Code:
VanitySearch v1.19
Difficulty: 4553521
Search: 1cit [Compressed]
Start Sun Aug 28 12:02:23 2022
Base Key: 9EA70CAD422B49B5BC29E1112C41FE14EEAAB16E971E1DCE172B8322984C3775
Number of CPU thread: 1
PubAddress: 1citmgfDZuA4GYMjRTcRVStBL4nirQpuN
Priv (WIF): p2pkh:L2Y7NazcDkpU9HFSCXGv34CK7Bjc2Wj8XVWFhJMmhDwr61s7R8rr
Priv (HEX): 0x9EA70CAD422B49B5BC29E1112C41FE14EEAAB16E971E1DCE172B8322984F580F
According to the output on the second search while omitting the GPU flag it shows only "Number of CPU thread used" = 1 and no hint about GPU. But the error is still there, the calculation is wrong.
-snip-
One more example with legacy address ...
What's wrong here? Any clues?
Anyway. I hope this post can help other like-minded Linux users to get VanitySearch run on latest GNU/Linux version with CUDA support. If you have failed like I did, you can try this little tutorial shown here which in my case is related to Ubuntu 22.04 Jammy Jellyfish with Nvidia CUDA running. I wish you success and keep my fingers crossed. Thanks and good luck!!!
Just like the result in your vanitySearch -check command, the checksum here is also invalid.One more example with legacy address ...
Code:
$ sudo ./VanitySearch -stop -t 4 -gpu 1citbo
Quote
VanitySearch v1.19
Difficulty: 15318045009
Search: 1citbo [Compressed]
Start Fri Aug 26 02:33:37 2022
Base Key: 2E1FCD8E1F65964ACDC032650D63817355259952D4CBD2C8CD2A5C577B49E882
Number of CPU thread: 4
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x128 cores) Grid(320x128)
[1661.79 Mkey/s][GPU 1635.34 Mkey/s][Total 2^33.63][Prob 58.0%][60% in 00:00:00][Found 0]
PubAddress: 1citboYAWtgbJCySZe8C7U7y36cxGfZUZ
Priv (WIF): p2pkh:L5NB8KdCFkL7q8ZTAKAuHHeJhsP41XoJijqtuiZrXJffMEfzwaZy
Priv (HEX): 0xF30DBBB1FFF76EBF9741202CCE4676B6258ACCAF648C040844D9796F239AD998 <--- is correct
Difficulty: 15318045009
Search: 1citbo [Compressed]
Start Fri Aug 26 02:33:37 2022
Base Key: 2E1FCD8E1F65964ACDC032650D63817355259952D4CBD2C8CD2A5C577B49E882
Number of CPU thread: 4
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x128 cores) Grid(320x128)
[1661.79 Mkey/s][GPU 1635.34 Mkey/s][Total 2^33.63][Prob 58.0%][60% in 00:00:00][Found 0]
PubAddress: 1citboYAWtgbJCySZe8C7U7y36cxGfZUZ
Priv (WIF): p2pkh:L5NB8KdCFkL7q8ZTAKAuHHeJhsP41XoJijqtuiZrXJffMEfzwaZy
Priv (HEX): 0xF30DBBB1FFF76EBF9741202CCE4676B6258ACCAF648C040844D9796F239AD998 <--- is correct
What's wrong here? Any clues?
Anyway. I hope this post can help other like-minded Linux users to get VanitySearch run on latest GNU/Linux version with CUDA support. If you have failed like I did, you can try this little tutorial shown here which in my case is related to Ubuntu 22.04 Jammy Jellyfish with Nvidia CUDA running. I wish you success and keep my fingers crossed. Thanks and good luck!!!
The first four Bytes of SHA256[SHA256(80F30DBBB1FFF76EBF9741202CCE4676B6258ACCAF648C040844D9796F239AD99801)] should be: 0xA3B0A194
while the invalid WIF private key has: 0x6B4E251C, so it didn't pass the checksum.
Same with the address, 1citboYAWtgbJCySZe8C7U7y36cxGfZUZ has an invalid checksum of 0xB071873E
The first four Bytes of SHA256[SHA256(0006C186C1421FF64024B3FC356AF312061DE52688)] should be: 0x054A4884
Someone has reported a similar issue (also using a GPU): https://github.com/JeanLucPons/VanitySearch/issues/124
BTW, I'm not experiencing this when only using CPU.
Hey there. First of all BIG THANKS to Jean_Luc for that tool which I downloaded and compiled on Linux. I am running Ubuntu 22.04 (Jammy Jellyfish) and have the GPU NVIDIA GeForce RTX 3070 in use with all drivers up-to-date. I can access it without issues with various applications. However I cannot make use of it with the VanitySearch tool.
I tried to build with
I installed Nvidia Toolkit as shown HERE and it went well. Now there are folders /usr/local/cuda* on my disk. I retried running the build command of VanitySearch with GPU support, but it fails:
I do not have a /usr/local/cuda-8.0 folder on my system, but there is a /usr/local/cuda-11.7 folder which contains the nvcc file. So i had to modify the line 34 inside Makefile of VanitySearch and put the corresponding version which is installed on my system:
then I retried the build process which again failed:
Seems it doesn't understand the required compute capability 2.0. Uhmm?? Let's dig further ...
I understand that this has something to do with compute capability but honestly said I have no clue what exactly these numbers represent. (EDIT: SOLVED! see bottom of this post!) I guess and hope the higher the value the better
So I tried editing VanitySearch' Makefile once more and manually assign the value 87 to the particular variable (note: this is wrong, I had to use 86, check the solution on the bottom of my post)
It failed again with error stating not founding g++-4.8 on my system. Indeed, I don't have this executable but instead I have /usr/bin/g++-11 and g++, latter is just a symlink to it. Now modifying again the Makefile ...
because I already hard-fixed it in Makefile. So far SO GOOD but ...
I cannot run VanitySearch with GPU support, see here:
when I omit the -gpuId 0,1 parameter as shown in developers example I get this error
Simply said, I dont have two GPUs, only one. Being said I need to either use -gpuId 0 or ommit the switch so default setting (0) take effect.
EDIT: ==> SOLVED !!! YEAH !!! I just had to continue reading on Jean_Luc's GIT repository at the section "Docker". There is a link to Wikipedia explaining CUDA computing capabilities and the various GPUs, alternatively check also this link. In my case (Nvidia RTX 3070Ti) it is computing capability 8.6 but I used 8.7 in my initial try. After replacing with 8.6 and rebuilding the tool it runs perfectly (... I thought
)
this took <5 seconds
I'm curious what rates other can achieve with their GPU. Anyone out there willing to share his GPU model and the achieved calc rate with VanitySearch, please? I get 1,680 MKey/s with my Nvidia 3070 Ti.
Now the bad news are --> All addresses with prefix 1 or 3 that were found are unknown/invalid on the blockexplorer. Only adresses with prefix bc1q that I found are valid but their private keys are invalid, too. When I run VanitySearch with the -check switch it outputs warnings, see here:
That confirms that only the calculated bc1q addresses are valid. Going one step further I tried to import one of the found bc1q addresses into a fresh new Electrum wallet. But the private key seems to be invalid, too. I cannot import it in Electrum. See following example of a valid bcq1 that was found by VanitySearch:
In Electrum I click [File] --> New/Restore --> "Import Bitcoin addresses or private keys" --> and the description says:
As I experienced VanitySearch partially outputs invalid bitcoin addresses, now it seems that this is true also for the calculated private keys. I did further tests today just to realize that all private keys VanitySearch is outputting are invalid. Did anyone else experience this and can confirm? Is this a known bug or did I miss anything? Any help appreciated.
EDIT: Here some examples ...
VanitySearch' resulting "Priv (HEX)" is correct, but the Priv (WIF) is invalid. When I convert on my own from Priv (HEX) --to--> Address I get this result
1TryMeBmkZbYQRh24QZUSCjZfMuzJsK32 # manually calculated
1TryMeBmkZbYQRh24QZUSCjZfMuzgbqd6 # calculated and shown in VanitySearch
One more example with legacy address ...
VanitySearch calculated and shown Priv (WIF):
L5NB8KdCFkL7q8ZTAKAuHHeJhsP41XoJijqtuiZrXJffMEfzwaZy
But the correct corresponding compressed Priv (WIF) for the above Priv (HEX) should be correctly:
L5NB8KdCFkL7q8ZTAKAuHHeJhsP41XoJijqtuiZrXJffMEhSXy1u
That results in VanitySearch showing the wrong address:
1citboYAWtgbJCySZe8C7U7y36cxGfZUZ
Whereas correctly should be:
1citboYAWtgbJCySZe8C7U7y36cstvVjR
What's wrong here? Any clues?
Anyway. I hope this post can help other like-minded Linux users to get VanitySearch run on latest GNU/Linux version with CUDA support. If you have failed like I did, you can try this little tutorial shown here which in my case is related to Ubuntu 22.04 Jammy Jellyfish with Nvidia CUDA running. I wish you success and keep my fingers crossed. Thanks and good luck!!!
citb0in
Code:
nvidia-smi
Quote
NVIDIA-SMI 510.85.02 Driver Version: 510.85.02 CUDA Version: 11.6
I tried to build with
Code:
make gpu=1 CCAP=2.0 all
but I have no folder /usr/local/cuda* on my disk so the compilation fails. I could only compile it without GPU support. Do I need to install additional CUDA stuff on my machine, do I need CUDA SDK ? I've done some research and the answer obviously is YES, I do.I installed Nvidia Toolkit as shown HERE and it went well. Now there are folders /usr/local/cuda* on my disk. I retried running the build command of VanitySearch with GPU support, but it fails:
Code:
make clean && make gpu=1 CCAP=2.0 all
Quote
[...]
g++ -DWITHGPU -m64 -mssse3 -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/hash/ripemd160_sse.o -c hash/ripemd160_sse.cpp
g++ -DWITHGPU -m64 -mssse3 -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/hash/sha256_sse.o -c hash/sha256_sse.cpp
/usr/local/cuda-8.0/bin/nvcc -maxrregcount=0 --ptxas-options=-v --compile --compiler-options -fPIC -ccbin /usr/bin/g++-4.8 -m64 -O2 -I/usr/local/cuda-8.0/include -gencode=arch=compute_20,code=sm_20 -o obj/GPU/GPUEngine.o -c GPU/GPUEngine.cu
make: /usr/local/cuda-8.0/bin/nvcc: file or directory not found
make: *** [Makefile:65: obj/GPU/GPUEngine.o] error 127
g++ -DWITHGPU -m64 -mssse3 -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/hash/ripemd160_sse.o -c hash/ripemd160_sse.cpp
g++ -DWITHGPU -m64 -mssse3 -Wno-write-strings -O2 -I. -I/usr/local/cuda-8.0/include -o obj/hash/sha256_sse.o -c hash/sha256_sse.cpp
/usr/local/cuda-8.0/bin/nvcc -maxrregcount=0 --ptxas-options=-v --compile --compiler-options -fPIC -ccbin /usr/bin/g++-4.8 -m64 -O2 -I/usr/local/cuda-8.0/include -gencode=arch=compute_20,code=sm_20 -o obj/GPU/GPUEngine.o -c GPU/GPUEngine.cu
make: /usr/local/cuda-8.0/bin/nvcc: file or directory not found
make: *** [Makefile:65: obj/GPU/GPUEngine.o] error 127
I do not have a /usr/local/cuda-8.0 folder on my system, but there is a /usr/local/cuda-11.7 folder which contains the nvcc file. So i had to modify the line 34 inside Makefile of VanitySearch and put the corresponding version which is installed on my system:
Code:
CUDA = /usr/local/cuda-11.7
then I retried the build process which again failed:
Code:
make clean && make gpu=1 CCAP=2.0 all
Quote
[...]
g++ -DWITHGPU -m64 -mssse3 -Wno-write-strings -O2 -I. -I/usr/local/cuda-11.7/include -o obj/hash/sha256_sse.o -c hash/sha256_sse.cpp
/usr/local/cuda-11.7/bin/nvcc -maxrregcount=0 --ptxas-options=-v --compile --compiler-options -fPIC -ccbin /usr/bin/g++-4.8 -m64 -O2 -I/usr/local/cuda-11.7/include -gencode=arch=compute_20,code=sm_20 -o obj/GPU/GPUEngine.o -c GPU/GPUEngine.cu
nvcc fatal : Unsupported gpu architecture 'compute_20'
make: *** [Makefile:65: obj/GPU/GPUEngine.o] error 1
g++ -DWITHGPU -m64 -mssse3 -Wno-write-strings -O2 -I. -I/usr/local/cuda-11.7/include -o obj/hash/sha256_sse.o -c hash/sha256_sse.cpp
/usr/local/cuda-11.7/bin/nvcc -maxrregcount=0 --ptxas-options=-v --compile --compiler-options -fPIC -ccbin /usr/bin/g++-4.8 -m64 -O2 -I/usr/local/cuda-11.7/include -gencode=arch=compute_20,code=sm_20 -o obj/GPU/GPUEngine.o -c GPU/GPUEngine.cu
nvcc fatal : Unsupported gpu architecture 'compute_20'
make: *** [Makefile:65: obj/GPU/GPUEngine.o] error 1
Seems it doesn't understand the required compute capability 2.0. Uhmm?? Let's dig further ...
Code:
$ /usr/local/cuda-11.7/bin/nvcc --list-gpu-code
Quote
sm_35
sm_37
sm_50
sm_52
sm_53
sm_60
sm_61
sm_62
sm_70
sm_72
sm_75
sm_80
sm_86
sm_87
sm_37
sm_50
sm_52
sm_53
sm_60
sm_61
sm_62
sm_70
sm_72
sm_75
sm_80
sm_86
sm_87
Code:
$ /usr/local/cuda-11.7/bin/nvcc --list-gpu-arch
Quote
compute_35
compute_37
compute_50
compute_52
compute_53
compute_60
compute_61
compute_62
compute_70
compute_72
compute_75
compute_80
compute_86
compute_87
compute_37
compute_50
compute_52
compute_53
compute_60
compute_61
compute_62
compute_70
compute_72
compute_75
compute_80
compute_86
compute_87
I understand that this has something to do with compute capability but honestly said I have no clue what exactly these numbers represent. (EDIT: SOLVED! see bottom of this post!) I guess and hope the higher the value the better
So I tried editing VanitySearch' Makefile once more and manually assign the value 87 to the particular variable (note: this is wrong, I had to use 86, check the solution on the bottom of my post)Code:
vi ./Makefile
Quote
#ccap = $(shell echo $(CCAP) | tr -d '.')
ccap = 87
[/quote]ccap = 87
It failed again with error stating not founding g++-4.8 on my system. Indeed, I don't have this executable but instead I have /usr/bin/g++-11 and g++, latter is just a symlink to it. Now modifying again the Makefile ...
Code:
vi ./Makefile
Quote
#CXXCUDA = /usr/bin/g++-4.8
CXXCUDA = /usr/bin/g++-11
CXXCUDA = /usr/bin/g++-11
Code:
make clean && make gpu=1 CCAP=2.0 all
and the build finished without errors. BTW: At this step I realized that I can ommit the CCAP=2.0 in the command line *lol* because I already hard-fixed it in Makefile. So far SO GOOD but ...I cannot run VanitySearch with GPU support, see here:
Code:
export LD_LIBRARY_PATH=/usr/local/cuda-11.7/lib64
./VanitySearch -t 7 -gpu -gpuId 0,1 1TryMe
./VanitySearch -t 7 -gpu -gpuId 0,1 1TryMe
Quote
VanitySearch v1.19
Difficulty: 15318045009
Search: 1TryMe [Compressed]
Start Wed Aug 24 21:14:27 2022
Base Key: 4DFFFFFFFFFF.........
Number of CPU thread: 7
GPUEngine: invalid device ordinal
GPU:
Speicherzugriffsfehler (Speicherabzug geschrieben) # this is german and means something like "memory access violation (memory dumped)"
Difficulty: 15318045009
Search: 1TryMe [Compressed]
Start Wed Aug 24 21:14:27 2022
Base Key: 4DFFFFFFFFFF.........
Number of CPU thread: 7
GPUEngine: invalid device ordinal
GPU:
Speicherzugriffsfehler (Speicherabzug geschrieben) # this is german and means something like "memory access violation (memory dumped)"
when I omit the -gpuId 0,1 parameter as shown in developers example I get this error
Code:
./VanitySearch -t 7 -gpu 1TryMe
Quote
VanitySearch v1.19
Difficulty: 15318045009
Search: 1TryMe [Compressed]
Start Wed Aug 24 21:14:49 2022
Base Key: F9blablabla.....
Number of CPU thread: 7
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x128 cores) Grid(320x128)
GPUEngine: Kernel: no kernel image is available for execution on the device
Difficulty: 15318045009
Search: 1TryMe [Compressed]
Start Wed Aug 24 21:14:49 2022
Base Key: F9blablabla.....
Number of CPU thread: 7
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x128 cores) Grid(320x128)
GPUEngine: Kernel: no kernel image is available for execution on the device
Simply said, I dont have two GPUs, only one. Being said I need to either use -gpuId 0 or ommit the switch so default setting (0) take effect.
EDIT: ==> SOLVED !!! YEAH !!! I just had to continue reading on Jean_Luc's GIT repository at the section "Docker". There is a link to Wikipedia explaining CUDA computing capabilities and the various GPUs, alternatively check also this link. In my case (Nvidia RTX 3070Ti) it is computing capability 8.6 but I used 8.7 in my initial try. After replacing with 8.6 and rebuilding the tool it runs perfectly (... I thought
)Code:
./VanitySearch -gpu bc1quantum
Quote
VanitySearch v1.19
Difficulty: 1073741824
Search: bc1quantum [Compressed]
Start Wed Aug 24 21:48:26 2022
Base Key: CF63B6CE85C8ABDF6957BC51F6FDF7021B79ED3D418A74CE778BFE6AF20C1325
Number of CPU thread: 1
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x128 cores) Grid(320x128)
PubAddress: bc1quantum5kfktr2jf5x4rth3pyrkrya3ur0d36wl
Priv (WIF): p2wpkh:
Priv (HEX):
PubAddress: bc1quantumk06cchhxyvl6m5uav3xu43q8xar4ztk8
Priv (WIF): p2wpkh:
Priv (HEX):
PubAddress: bc1quantumjvvfen3ps35gezay5pd6psrzw4sfte0c
Priv (WIF): p2wpkh:
Priv (HEX):
PubAddress: bc1quantumvuxaz3tf84hk7l4ywxq863xhjk6vyx85
Priv (WIF): p2wpkh:
Priv (HEX):
^C
Difficulty: 1073741824
Search: bc1quantum [Compressed]
Start Wed Aug 24 21:48:26 2022
Base Key: CF63B6CE85C8ABDF6957BC51F6FDF7021B79ED3D418A74CE778BFE6AF20C1325
Number of CPU thread: 1
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x128 cores) Grid(320x128)
PubAddress: bc1quantum5kfktr2jf5x4rth3pyrkrya3ur0d36wl
Priv (WIF): p2wpkh:
Priv (HEX):
PubAddress: bc1quantumk06cchhxyvl6m5uav3xu43q8xar4ztk8
Priv (WIF): p2wpkh:
Priv (HEX):
PubAddress: bc1quantumjvvfen3ps35gezay5pd6psrzw4sfte0c
Priv (WIF): p2wpkh:
Priv (HEX):
PubAddress: bc1quantumvuxaz3tf84hk7l4ywxq863xhjk6vyx85
Priv (WIF): p2wpkh:
Priv (HEX):
^C
this took <5 seconds
I'm curious what rates other can achieve with their GPU. Anyone out there willing to share his GPU model and the achieved calc rate with VanitySearch, please? I get 1,680 MKey/s with my Nvidia 3070 Ti.Quote
[1689.55 Mkey/s][GPU 1635.58 Mkey/s][Total 2^32.65][Prob 99.8%][99% in 00:00:00][Found 9]
Now the bad news are --> All addresses with prefix 1 or 3 that were found are unknown/invalid on the blockexplorer. Only adresses with prefix bc1q that I found are valid but their private keys are invalid, too. When I run VanitySearch with the -check switch it outputs warnings, see here:
Code:
$ ./VanitySearch -check
Quote
GetBase10() Results OK
Add() Results OK : 1.429 GigaAdd/sec
Mult() Results OK : 63.291 MegaMult/sec
Div() Results OK : 13.333 MegaDiv/sec
R1=1000003D1
R2=1000007A2000E90A1
Field characteristic size: 256bits
ModInv()/ModExp() Results OK
ModInv() Edge cases Results OK
.Avg = 6.13
ModInv() Results OK : 934.307 KiloInv/sec
ModInv() cycles : 2671.49
ModSqrt() Results OK !
IntGroup.ModInv() Results OK : 15.772 MegaInv/sec
ModMulK1() Results OK : 84.104 MegaMult/sec
ModSquareK1() Results OK : 94.724 MegaSqr/sec
ModInv() Cost : 202.8 S
ModMulK1order() Results OK : 8.494 MegaMult/sec
Check Generator :OK
Check Double :OK
Check Add :OK
Check GenKey :OK
Warning, Invalid private key checksum !
Adress : 15t3Nt1zyMETkHbjJTTshxLnqPzQvAtdCe Failed !
15t3Nt1zyMETkHbjJTTshxLnqPzQu1bXfv
Warning, Invalid private key checksum !
Adress : 1BoatSLRHtKNngkdXEeobR76b53LETtpyT Failed !
1BoatSLRHtKNngkdXEeobR76b53LKMWP3w
Warning, Invalid private key checksum !
Adress : 1Test6BNjSJC5qwYXsjwKVLvz7DpfLehy Failed !
1Test6BNjSJC5qwYXsjwKVLvz7DpjtjnQ
Warning, Invalid private key checksum !
Adress : 16S5PAsGZ8VFM1CRGGLqm37XHrp46f6CTn Failed !
16S5PAsGZ8VFM1CRGGLqm37XHrp47fqtNF
Warning, Invalid private key checksum !
Adress : 1Tst2RwMxZn9cYY5mQhCdJic3JJrK7Fq7 Failed !
1Tst2RwMxZn9cYY5mQhCdJic3JJmbS2Bg
Warning, Invalid private key checksum !
Adress : 3CyQYcByvcWK8BkYJabBS82yDLNWt6rWSx Failed !
3CyQYcByvcWK8BkYJabBS82yDLNWuH5qBa
Warning, Invalid private key checksum !
Adress : 31to1KQe67YjoDfYnwFJThsGeQcFhVDM5Q Failed !
31to1KQe67YjoDfYnwFJThsGeQcFkVZ6Es
Warning, Invalid private key checksum !
Adress : bc1q6tqytpg06uhmtnhn9s4f35gkt8yya5a24dptmn OK!
Check Calc PubKey (full) 1ViViGLEawN27xRzGrEhhYPQrZiSCLm3G :OK
Check Calc PubKey (even) 385cR5DM96n1HvBDMzLHPYcw89fZ9G2Vm5:OK
Check Calc PubKey (odd) 18aPiLmTow7Xgu96msrDYvSSWweCwm6WL3:OK
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x128 cores) Grid(320x128)
Seed: 1661373526
1.638 GigaKey/sec
ComputeKeys() found 7590 items , CPU check...
^C
Add() Results OK : 1.429 GigaAdd/sec
Mult() Results OK : 63.291 MegaMult/sec
Div() Results OK : 13.333 MegaDiv/sec
R1=1000003D1
R2=1000007A2000E90A1
Field characteristic size: 256bits
ModInv()/ModExp() Results OK
ModInv() Edge cases Results OK
.Avg = 6.13
ModInv() Results OK : 934.307 KiloInv/sec
ModInv() cycles : 2671.49
ModSqrt() Results OK !
IntGroup.ModInv() Results OK : 15.772 MegaInv/sec
ModMulK1() Results OK : 84.104 MegaMult/sec
ModSquareK1() Results OK : 94.724 MegaSqr/sec
ModInv() Cost : 202.8 S
ModMulK1order() Results OK : 8.494 MegaMult/sec
Check Generator :OK
Check Double :OK
Check Add :OK
Check GenKey :OK
Warning, Invalid private key checksum !
Adress : 15t3Nt1zyMETkHbjJTTshxLnqPzQvAtdCe Failed !
15t3Nt1zyMETkHbjJTTshxLnqPzQu1bXfv
Warning, Invalid private key checksum !
Adress : 1BoatSLRHtKNngkdXEeobR76b53LETtpyT Failed !
1BoatSLRHtKNngkdXEeobR76b53LKMWP3w
Warning, Invalid private key checksum !
Adress : 1Test6BNjSJC5qwYXsjwKVLvz7DpfLehy Failed !
1Test6BNjSJC5qwYXsjwKVLvz7DpjtjnQ
Warning, Invalid private key checksum !
Adress : 16S5PAsGZ8VFM1CRGGLqm37XHrp46f6CTn Failed !
16S5PAsGZ8VFM1CRGGLqm37XHrp47fqtNF
Warning, Invalid private key checksum !
Adress : 1Tst2RwMxZn9cYY5mQhCdJic3JJrK7Fq7 Failed !
1Tst2RwMxZn9cYY5mQhCdJic3JJmbS2Bg
Warning, Invalid private key checksum !
Adress : 3CyQYcByvcWK8BkYJabBS82yDLNWt6rWSx Failed !
3CyQYcByvcWK8BkYJabBS82yDLNWuH5qBa
Warning, Invalid private key checksum !
Adress : 31to1KQe67YjoDfYnwFJThsGeQcFhVDM5Q Failed !
31to1KQe67YjoDfYnwFJThsGeQcFkVZ6Es
Warning, Invalid private key checksum !
Adress : bc1q6tqytpg06uhmtnhn9s4f35gkt8yya5a24dptmn OK!
Check Calc PubKey (full) 1ViViGLEawN27xRzGrEhhYPQrZiSCLm3G :OK
Check Calc PubKey (even) 385cR5DM96n1HvBDMzLHPYcw89fZ9G2Vm5:OK
Check Calc PubKey (odd) 18aPiLmTow7Xgu96msrDYvSSWweCwm6WL3:OK
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x128 cores) Grid(320x128)
Seed: 1661373526
1.638 GigaKey/sec
ComputeKeys() found 7590 items , CPU check...
^C
That confirms that only the calculated bc1q addresses are valid. Going one step further I tried to import one of the found bc1q addresses into a fresh new Electrum wallet. But the private key seems to be invalid, too. I cannot import it in Electrum. See following example of a valid bcq1 that was found by VanitySearch:
Quote
PubAddress: bc1qxxxxxxxxkdmn6srmenzwx9vemzckwl9nrtrffr
Priv (WIF): p2wpkh:KwTYmSw4***********************************************aWXAz3m
Priv (HEX): 0x71E5C****************************************************646DDF
[1767.69 Mkey/s][GPU 1745.63 Mkey/s][Total 2^41.56][Prob 94.8%][99% in 00:17:06]
Priv (WIF): p2wpkh:KwTYmSw4***********************************************aWXAz3m
Priv (HEX): 0x71E5C****************************************************646DDF
[1767.69 Mkey/s][GPU 1745.63 Mkey/s][Total 2^41.56][Prob 94.8%][99% in 00:17:06]
In Electrum I click [File] --> New/Restore --> "Import Bitcoin addresses or private keys" --> and the description says:
Quote
Enter a list of Bitcoin addresses (this will create a watching-only wallet), or a list of private keys. WIF keys are typed in Electrum, based on script type.
A few examples:
p2pkh:KxZcY47uGp9a... -> 1DckmggQM...
p2wpkh-p2sh:KxZcY47uGp9a... -> 3NhNeZQXF...
p2wpkh:KxZcY47uGp9a... -> bc1q3fjfk...
I tried entering the Priv (WIF) that was output by VanitySearchA few examples:
p2pkh:KxZcY47uGp9a... -> 1DckmggQM...
p2wpkh-p2sh:KxZcY47uGp9a... -> 3NhNeZQXF...
p2wpkh:KxZcY47uGp9a... -> bc1q3fjfk...
Quote
p2wpkh:KwTYmSw4***********************************************aWXAz3m
but I cannot click next. Even when I omit the p2wpkh: string and just entering the key solely. It doesn't work either, Electrum does not accept it. I tried some private keys which I can ensure they are valid and Electrum accepts them so I can be sure Electrum has no bug As I experienced VanitySearch partially outputs invalid bitcoin addresses, now it seems that this is true also for the calculated private keys. I did further tests today just to realize that all private keys VanitySearch is outputting are invalid. Did anyone else experience this and can confirm? Is this a known bug or did I miss anything? Any help appreciated.EDIT: Here some examples ...
Quote
$ sudo ./VanitySearch -stop -gpu 1TryMe
Quote
VanitySearch v1.19
Difficulty: 15318045009
Search: 1TryMe [Compressed]
Start Fri Aug 26 02:07:35 2022
Base Key: EA39E4FEA1F9A57B3D1153C51436F3DC5F346FDA89AB90B2E0BEBC4B3B616D76
Number of CPU thread: 1
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x128 cores) Grid(320x128)
[1956.69 Mkey/s][GPU 1949.94 Mkey/s][Total 2^32.87][Prob 40.0%][50% in 00:00:01][Found 0]
PubAddress: 1TryMeBmkZbYQRh24QZUSCjZfMuzgbqd6 <---- this BTC adress is invalid
Priv (WIF): p2pkh:KzVPRaUaiDiRniEr6YSKUHazHvo8CAvffFdRawzQQYg7pP84fycW <---- this Priv/WIF key is invalid
Priv (HEX): 0x6193A9465DDEA2E9E0BFBB43960A5288817B7AC5BE9ACA09BFC46DEDC8E9FF14 <--- is correct
Difficulty: 15318045009
Search: 1TryMe [Compressed]
Start Fri Aug 26 02:07:35 2022
Base Key: EA39E4FEA1F9A57B3D1153C51436F3DC5F346FDA89AB90B2E0BEBC4B3B616D76
Number of CPU thread: 1
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x128 cores) Grid(320x128)
[1956.69 Mkey/s][GPU 1949.94 Mkey/s][Total 2^32.87][Prob 40.0%][50% in 00:00:01][Found 0]
PubAddress: 1TryMeBmkZbYQRh24QZUSCjZfMuzgbqd6 <---- this BTC adress is invalid
Priv (WIF): p2pkh:KzVPRaUaiDiRniEr6YSKUHazHvo8CAvffFdRawzQQYg7pP84fycW <---- this Priv/WIF key is invalid
Priv (HEX): 0x6193A9465DDEA2E9E0BFBB43960A5288817B7AC5BE9ACA09BFC46DEDC8E9FF14 <--- is correct
VanitySearch' resulting "Priv (HEX)" is correct, but the Priv (WIF) is invalid. When I convert on my own from Priv (HEX) --to--> Address I get this result
1TryMeBmkZbYQRh24QZUSCjZfMuzJsK32 # manually calculated
1TryMeBmkZbYQRh24QZUSCjZfMuzgbqd6 # calculated and shown in VanitySearch
Quote
$ sudo ./VanitySearch -stop -gpu 3TryMe
Quote
VanitySearch v1.19
Ignoring prefix "3TryMe" (Unreachable, 31h1 to 3R2c only)
VanitySearch: nothing to search !
Ignoring prefix "3TryMe" (Unreachable, 31h1 to 3R2c only)
VanitySearch: nothing to search !
Quote
$ sudo ./VanitySearch -stop -gpu bc1qtryme
Quote
VanitySearch v1.19
Difficulty: 33554432
Search: bc1qtryme [Compressed]
Start Fri Aug 26 02:12:53 2022
Base Key: 905139A9CDCF33BC677ED4F0BA7CB07254BFF2B7C2D0E8BD34D6EFB7FD1B610
Number of CPU thread: 1
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x128 cores) Grid(320x128)
PubAddress: bc1qtryme20s0rqssxdk36qkfu7lcquhy6mqf584k4 <---- this BTC adress is valid
Priv (WIF): p2wpkh:L5VopZHRZ3AhXfRt7uCZwkeJ3zYNXJY87snY33KGmjGaSWHKTDco <---- this Priv/WIF key is invalid
Priv (HEX): 0xF6FAEC6563230CC4398812B0F45834F794E2DDBB21D191AFEC84EF9150648957 <--- is correct
Difficulty: 33554432
Search: bc1qtryme [Compressed]
Start Fri Aug 26 02:12:53 2022
Base Key: 905139A9CDCF33BC677ED4F0BA7CB07254BFF2B7C2D0E8BD34D6EFB7FD1B610
Number of CPU thread: 1
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x128 cores) Grid(320x128)
PubAddress: bc1qtryme20s0rqssxdk36qkfu7lcquhy6mqf584k4 <---- this BTC adress is valid
Priv (WIF): p2wpkh:L5VopZHRZ3AhXfRt7uCZwkeJ3zYNXJY87snY33KGmjGaSWHKTDco <---- this Priv/WIF key is invalid
Priv (HEX): 0xF6FAEC6563230CC4398812B0F45834F794E2DDBB21D191AFEC84EF9150648957 <--- is correct
One more example with legacy address ...
Code:
$ sudo ./VanitySearch -stop -t 4 -gpu 1citbo
Quote
VanitySearch v1.19
Difficulty: 15318045009
Search: 1citbo [Compressed]
Start Fri Aug 26 02:33:37 2022
Base Key: 2E1FCD8E1F65964ACDC032650D63817355259952D4CBD2C8CD2A5C577B49E882
Number of CPU thread: 4
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x128 cores) Grid(320x128)
[1661.79 Mkey/s][GPU 1635.34 Mkey/s][Total 2^33.63][Prob 58.0%][60% in 00:00:00][Found 0]
PubAddress: 1citboYAWtgbJCySZe8C7U7y36cxGfZUZ
Priv (WIF): p2pkh:L5NB8KdCFkL7q8ZTAKAuHHeJhsP41XoJijqtuiZrXJffMEfzwaZy
Priv (HEX): 0xF30DBBB1FFF76EBF9741202CCE4676B6258ACCAF648C040844D9796F239AD998 <--- is correct
Difficulty: 15318045009
Search: 1citbo [Compressed]
Start Fri Aug 26 02:33:37 2022
Base Key: 2E1FCD8E1F65964ACDC032650D63817355259952D4CBD2C8CD2A5C577B49E882
Number of CPU thread: 4
GPU: GPU #0 NVIDIA GeForce RTX 3070 Laptop GPU (40x128 cores) Grid(320x128)
[1661.79 Mkey/s][GPU 1635.34 Mkey/s][Total 2^33.63][Prob 58.0%][60% in 00:00:00][Found 0]
PubAddress: 1citboYAWtgbJCySZe8C7U7y36cxGfZUZ
Priv (WIF): p2pkh:L5NB8KdCFkL7q8ZTAKAuHHeJhsP41XoJijqtuiZrXJffMEfzwaZy
Priv (HEX): 0xF30DBBB1FFF76EBF9741202CCE4676B6258ACCAF648C040844D9796F239AD998 <--- is correct
VanitySearch calculated and shown Priv (WIF):
L5NB8KdCFkL7q8ZTAKAuHHeJhsP41XoJijqtuiZrXJffMEfzwaZy
But the correct corresponding compressed Priv (WIF) for the above Priv (HEX) should be correctly:
L5NB8KdCFkL7q8ZTAKAuHHeJhsP41XoJijqtuiZrXJffMEhSXy1u
That results in VanitySearch showing the wrong address:
1citboYAWtgbJCySZe8C7U7y36cxGfZUZ
Whereas correctly should be:
1citboYAWtgbJCySZe8C7U7y36cstvVjR
What's wrong here? Any clues?
Anyway. I hope this post can help other like-minded Linux users to get VanitySearch run on latest GNU/Linux version with CUDA support. If you have failed like I did, you can try this little tutorial shown here which in my case is related to Ubuntu 22.04 Jammy Jellyfish with Nvidia CUDA running. I wish you success and keep my fingers crossed. Thanks and good luck!!!
citb0in
With VanitySearch engine
Can anyone help to modify BTCCollider to can custom rank search?
https://github.com/JeanLucPons/BTCCollider
if possible I would like to custom start seed from random 256 bit start to any seed want
I would like to start seed from 63bit and 119 bit for both puzzle64 and puzzle120
Somebody told me Vanity/BTCcollider could be used on Intel processors only. Is this true?
No, I've seen some replies who tested this with their Ryzen CPUs like this one (link)He might have misunderstood the info that it doesn't work with AMD GPUs (Video Cards).
Somebody told me Vanity/BTCcollider could be used on Intel processors only. Is this true?
Can it be AMD as well?
Can it be AMD as well?
We are currently messing with pricing matrices. some of you keep submitting things that have a heavier byte count therefore introducing a pivot going off length alone isnt ideal. (we've lowered the free difficulty for the time being)
It saves time if your running a single 1080 vs whats under our hood but if you have a farm with a script you can can easily do this (the average retail investor that would want this doesnt have gpu farms)
but i think your referring to a simple .bat such as
starting off with a lowercase d vs a D is a difference in a starting power of 23 vs 1354
so DKBiT9 can be found almost in about 1 min but dkbit9 would take like 30 mins.
we just want people to quit using junk like this http://vanitygen.net/ we can make it easy ,trusting and a little educational in the process.
even that guy charges for more then 3 digits , and then he sweeps your coin after you load it.
People have been getting scammed by services like these since samr7 released the first vanity search software.
if we can provide a consistent service maybe people wont fall pray to that kind of behavior anymore.
It saves time if your running a single 1080 vs whats under our hood but if you have a farm with a script you can can easily do this (the average retail investor that would want this doesnt have gpu farms)
but i think your referring to a simple .bat such as
Code:
C:\Users\PC\Desktop\VanitySearch.exe -gpu -gpuId 0,1,2,3,4,5,6 -gpu -gpuId 0,1,2,3,4,5,6 -o C:\Users\PC\Desktop\output.txt -c 1easybat
save that as a .bat and right click and edit your prefix before running.starting off with a lowercase d vs a D is a difference in a starting power of 23 vs 1354
so DKBiT9 can be found almost in about 1 min but dkbit9 would take like 30 mins.
we just want people to quit using junk like this http://vanitygen.net/ we can make it easy ,trusting and a little educational in the process.
even that guy charges for more then 3 digits , and then he sweeps your coin after you load it.
People have been getting scammed by services like these since samr7 released the first vanity search software.
if we can provide a consistent service maybe people wont fall pray to that kind of behavior anymore.
I don't think the account was ever terminated. I think Lauda left voluntarily. All one has to do is change the password to xxxxxxxxxx-some-random-long-password, and no one else will be able to log into it. (obviously, from a secure device.)
I will request that theymos ban the "Lauda" account (u=101872)
Asking owner of forum to ban/kill your account it's very definition of suicide and I think his words posted above will be enough, so please let's not continue going off-road with this.
I only mentioned him here because I created few vanity addresses with his name, that's all.
Now let's get back on topic.
Jump to: