VanitySearch (Yet another address prefix finder)

[nc50lc]

Please write mi in words how many years it is:

1.055e+06y

The simpler method is to just move the decimal point depending on the value of "e+number".

From your example:

	1.055	(e+06 = move by 6 decimal places)
	10.55	=  move by 1 place
	105.5	=  move by 2 places
	1055.	=  move by 3 places
	10550.	=  move by 4 places
	105500.	=  move by 5 places
	1055000.	=  move by 6 places

Other note: You can use your forum signature for off-topic messages.
You can access it in: "Profile->Forum Profile Information".

[inlovewiththedj]

Please write mi in words how many years it is:

1.055e+06y

The simpler method is to just move the decimal point depending on the value of "e+number".

From your example:

	1.055	(e+06 = move by 6 decimal places)
	10.55	=  move by 1 place
	105.5	=  move by 2 places
	1055.	=  move by 3 places
	10550.	=  move by 4 places
	105500.	=  move by 5 places
	1055000.	=  move by 6 places

Other note: You can use your forum signature for off-topic messages.
You can access it in: "Profile->Forum Profile Information".

Thanks!



Am I correct with  6.02311e+07y?

6.02311    (e+07 = move by 7 decimal places)
60.2311      =  move by 1 place
602.311      =  move by 2 places
6023.11      =  move by 3 places
60231.1      =  move by 4 places
602311.      =  move by 5 places
6023110.      =  move by 6 places
60231100.      =  move by 7 places

[brainless]

Please write mi in words how many years it is:

1.055e+06y

The simpler method is to just move the decimal point depending on the value of "e+number".

From your example:

	1.055	(e+06 = move by 6 decimal places)
	10.55	=  move by 1 place
	105.5	=  move by 2 places
	1055.	=  move by 3 places
	10550.	=  move by 4 places
	105500.	=  move by 5 places
	1055000.	=  move by 6 places

Other note: You can use your forum signature for off-topic messages.
You can access it in: "Profile->Forum Profile Information".

Thanks!



Am I correct with  6.02311e+07y?

6.02311    (e+07 = move by 7 decimal places)
60.2311      =  move by 1 place
602.311      =  move by 2 places
6023.11      =  move by 3 places
60231.1      =  move by 4 places
602311.      =  move by 5 places
6023110.      =  move by 6 places
60231100.      =  move by 7 places

use big calc
https://www.calculator.net/big-number-calculator.html

[nullama]

Hello

I try to understand big numbers I mean, thousand of years and so on.

Please write mi in words how many years it is:

1.055e+06y

One million and fifty five thousand years.

By that time some interesting things will happen:

Betelgeuse, one of the top ten brightest stars in our sky, will have exploded in a supernova. It will be so bright that it will be visible on Earth in day time. [1]

A couple of Uranus moons, Desdemona and Cressida, will probably have already collided with each other. [2]

inlovewiththedj will probably have obtained his vanity address. [3]

[1]: https://earthsky.org/brightest-stars/betelgeuse-will-explode-someday
[2]: https://astronomy.com/news/2017/09/uranus-colliding-moons
[3]: https://bitcointalk.org/index.php?topic=5112311.msg59427656#msg59427656

[WhyFhy]

We are building something special, still working on a difficulty calculator like no other so we can offer up to 7 digits free
We could use some help solving this here as we have discovered JL's VS difficulty calculator is inaccurate at some points/pivots/bits.
problem is our difficulty calculator has to be more accurate than even vanitysearch's, so our quotes will be accurate so we dont operate at loss or email you guys saying we cant do it.
We run about 16,000 MK/S with -sp applied (so far)
We run a combination eth mining rigs to achieve this with proprietary software assigning workers, logging speeds and an api callback server relaying said data.
We've essentially created a real vanity searching mining pool(workaround) ,
We plan to use smi or wmic to pull card data and catagorize speeds against collected data such as DaveF's list and auto configure arguments.
and relay to website for time estimates. even a simple 7digit case insensitive can be done in under a few mins, It's like not hitting a mining share for few mins.
Our quotes are still broken, until we solve for a few x's on difficulty calculations via pivots/bits
We have a few other bugs to work out.
emails being marked as spam, or our personal smtp server not sending email in the first place thinking we are sending spam
We do not want to quote on wallet length like all the competition does. Our process if fully automated.
This has been a work in progress for about 16 months. Some of you tried our google form based beta. We took all the feedback with grace and went back to the drawing board.
We are not targeting guys like you that already know how to do it but if you lack power please feel free to use our service when it's officially announced.
We accept BTC and LN ,(implemented and tested working)
Again, the service isn't ready but at this point right now feedback is crucial as we near launch. We strive to be the definitive service in splitkey generation.
I offer you guys a preview at 1splitkey.com

[slumberjack]

Again, the service isn't ready but at this point right now feedback is crucial as we near launch. We strive to be the definitive service in splitkey generation.

I had never heard of vanity addresses until WhyFhy introduced me to them. The process I went through to create the public/private key was a breeze thanks to his instructions. I have zero experience in coding and/or brute forcing, so this was a neat project to be a part of. At no point was I asked for the private key. In my experience, no compromise in security. Now i've got a Vanity Address to show off and share my experience.

[WhyFhy]

Again, the service isn't ready but at this point right now feedback is crucial as we near launch. We strive to be the definitive service in splitkey generation.

I had never heard of vanity addresses until WhyFhy introduced me to them. The process I went through to create the public/private key was a breeze thanks to his instructions. I have zero experience in coding and/or brute forcing, so this was a neat project to be a part of. At no point was I asked for the private key. In my experience, no compromise in security. Now i've got a Vanity Address to show off and share my experience.

Thank you for vectorizing the logo and churching it up , some of the work you asked for was eye opening as well such as the difficulty differences.

[alexeyneu]

reality is that if you're too long on one address it goes to aml blacklist. And then you best option is black exchange rate . So i don't see much sense in all this stuff anymore.

[dkbit98]

Again, the service isn't ready but at this point right now feedback is crucial as we near launch. We strive to be the definitive service in splitkey generation.

I don't think that sending private keys via email is a good option, especially when we know most people are using one email address and it's most likely gmail.
Just for fun I tested the pricing using various characters and I think price is fair (few bucks only) if I pick up to six characters, but it grows much higher adding just one more character.
I have to be honest and say that I honestly don't know why would I use 1splitkey when I can just generate my own vanity address for free with my computer.

Last year I did something similar, just for Luada's funeral:

3LAUDAv3id4CDLC87x6uaR3NjWNRs3NHuP
bc1qlaudahydf4axnjalaf9paz94l2lhh3h4qew0wc

[WhyFhy]

Again, the service isn't ready but at this point right now feedback is crucial as we near launch. We strive to be the definitive service in splitkey generation.

I don't think that sending private keys via email is a good option, especially when we know most people are using one email address and it's most likely gmail.
Just for fun I tested the pricing using various characters and I think price is fair (few bucks only) if I pick up to six characters, but it grows much higher adding just one more character.
I have to be honest and say that I honestly don't know why would I use 1splitkey when I can just generate my own vanity address for free with my computer.

Last year I did something similar, just for Luada's funeral:

3LAUDAv3id4CDLC87x6uaR3NjWNRs3NHuP
bc1qlaudahydf4axnjalaf9paz94l2lhh3h4qew0wc

We are not targeting guys like you that already know how to do it but if you lack power please feel free to use our service when it's officially announced.
We accept BTC and LN ,(implemented and tested working)
Again, the service isn't ready but at this point right now feedback is crucial as we near launch. We strive to be the definitive service in splitkey generation.
I offer you guys a preview at 1splitkey.com

Literally one line above your quote stated we aren't targeting people who know how to do it,
At this current point in time there is only 3 legitimate services relevant to vanity splitkey generation
LoyceV's service,
bitcoin-uni.de's service
and our's.
all the rest are scams or not yet scams as they do not provide split key generation options at all.
We still haven't zero 'ed in on pricing but are getting close.
We do not log base keys (since we use rekey options we don't even see them in cli, we have learned switching up base keys generally yields results quicker, some basekeys simply dont yield results even on low difficulty wallets ),
All we have logged is the following.
Pubkey
Wallet Address
Partial Priv
and email
without a base key, the only flaws we can consider but won't are end users security practices.
even if someone's email where hacked or phished there isnt much that can be done with the partial priv and wallet besides speculating. unless they imported the wallet to some online source and it too was comprimised.
If end user truly kept the partial priv offline and lack of basekey brute forcing is to a moot end.
we tried to create a zero liability system by design.
We should be launching a finished product and announcing it on may 5th-8th'ish as our spamscore will be green light.
In concerns to the pricing  our competitors start charging $2 after 3 digits,  We don't start charging $2 until around the 7th digit or a certain difficulty, so it may feel expensive but its not.
bitcoin-uni.de 1ABCDEFGH=$432         -c $130.41,   1ABCDEFGHi -Cannot even submit this order 11111111 with -c enabled $26.91 and an email/refund apologizing that it cant be done.
 1splitkey.com 1ABCDEFGH=$117.50     -c $58.70,    1ABCDEFGHi -  $6818.10 and will deliver around 1636~ hours later. (66 days) 11111111 without -c enabled (since it cant be done that way) = $166799.90 we will get it done, it might take a year or 2 but we have ways to accomplish this weather it be on vast.ai rentals or A100 instances or an agreement with lambda labs

The difference in our services is we've done the research we had a viable product even before bitcoin-uni.de came out but saw many issues and challenges to overcome in our beta product.
We wanted everyone to be able to use our product not just the technically inclined.
When my child whom is under 10 years old was able to navigate and utilize the service we knew we where onto something. However my wife ,not so much. One's in 3rd grade the other is perusing a MBA.
One thing we are trying to factor in and solve is a proper workflow for assumptive behavior online.  

@dkbit98 I would love it if you tried the service in full fashion and then came back here to report the process, test out 1dkbit, use a burner email we dont care maybe next time you need something like 1Lauda you can know and trust our service and save a lot of time. (not that its time consuming or anything if you know how)
The neat thing about our service its all automated.
Ona side note are you referencing user Lauda I was unaware they passed away. Regardless of whom your referring to I send my condolences.

[LoyceV]

the only flaws we can consider but won't are end users security practices.
~
We wanted everyone to be able to use our product not just the technically inclined.
When my child whom is under 10 years old was able to navigate and utilize the service we knew we where onto something.

For what it's worth: I don't think I've ever had any complaints from users who messed up. But it happened once or twice that someone forgot their part private key after they gave me the public key.

Ona side note are you referencing user Lauda I was unaware they passed away. Regardless of whom your referring to I send my condolences.

Bitcointalk user Lauda is gone, but the person who used to own the account is not known to be dead. See:

After this post, "Lauda" will cease to exist. By that I mean: The faceless virtual persona named "Lauda", who exists only in cypherspace, will become detached from its "soul", and left as an empty shell. "Lauda" has abruptly reached end-of-life.

[dkbit98]

Literally one line above your quote stated we aren't targeting people who know how to do it

I am far from being an expert in generating vanity addresses.
All I did was downloading the Vanitysearch open source software and typing few commands, it was as simple as it gets, and it took me only a few minutes to finish everything.
Someone could easily make one click script that would do this job even quicker, maybe something similar was already created but I am not aware of this.

We wanted everyone to be able to use our product not just the technically inclined.

I appreciate you are trying to make something easier to use, but I am not sure how many kids and grandmas really need vanity addresses.

@dkbit98 I would love it if you tried the service in full fashion and then came back here to report the process, test out 1dkbit, use a burner email we dont care maybe next time you need something like 1Lauda you can know and trust our service and save a lot of time.

I will think about testing your service and report later with my feedback, but like I said before in my case it will not save any time and in reality I would probably need more time for creating new email address.
It could be faster if I want to create address with more characters, but then I would have to pay more for this, and I don't want to do that just for fan.
So far I didn't found a way how to generate address using your website for free.

Ona side note are you referencing user Lauda I was unaware they passed away. Regardless of whom your referring to I send my condolences.

Oh Lauda was the one of the OG's of bitcointalk and he didn't really passed away in real life (at least I don't think he did) but his forum account was terminated by theymos.

we can offer up to 7 digits free

I don't think this was true, during my testing.

[Dabs]

Oh Lauda was the one of the OG's of bitcointalk and he didn't really passed away in real life (at least I don't think he did) but his forum account was terminated by theymos.

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.)

[dkbit98]

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.

[WhyFhy]

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

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.

 

[shlomogold]

Somebody told me Vanity/BTCcollider could be used on Intel processors only. Is this true?
Can it be AMD as well?

[nc50lc]

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).

[fxsniper]

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

[citb0in]

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.

Code:

nvidia-smi

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

[...]
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

[...]
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

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

Code:

$ /usr/local/cuda-11.7/bin/nvcc --list-gpu-arch

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

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

#ccap       = $(shell echo $(CCAP) | tr -d '.')
ccap       = 87

[/quote]
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

#CXXCUDA    = /usr/bin/g++-4.8
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 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)"

when I omit the -gpuId 0,1 parameter as shown in developers example I get this error

Code:

./VanitySearch -t 7 -gpu 1TryMe

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

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

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:<notshownhere>
Priv (HEX): <notshownhere>

PubAddress: bc1quantumk06cchhxyvl6m5uav3xu43q8xar4ztk8
Priv (WIF): p2wpkh:<notshownhere>
Priv (HEX): <notshownhere>

PubAddress: bc1quantumjvvfen3ps35gezay5pd6psrzw4sfte0c
Priv (WIF): p2wpkh:<notshownhere>
Priv (HEX): <notshownhere>

PubAddress: bc1quantumvuxaz3tf84hk7l4ywxq863xhjk6vyx85
Priv (WIF): p2wpkh:<notshownhere>
Priv (HEX): <notshownhere>
^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.

[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

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

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:

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]

In Electrum I click [File] --> New/Restore --> "Import Bitcoin addresses or private keys" --> and the description says:

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 VanitySearch

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 ...

$ sudo ./VanitySearch -stop -gpu 1TryMe

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

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

$ sudo ./VanitySearch -stop -gpu 3TryMe

VanitySearch v1.19
Ignoring prefix "3TryMe" (Unreachable, 31h1 to 3R2c only)
VanitySearch: nothing to search !

$ sudo ./VanitySearch -stop -gpu bc1qtryme

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

One more example with legacy address ...

Code:

$ sudo ./VanitySearch -stop -t 4 -gpu 1citbo

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

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

[nc50lc]

-snip-
One more example with legacy address ...

Code:

$ sudo ./VanitySearch -stop -t 4 -gpu 1citbo

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

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.

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.