Vanitygen: Vanity bitcoin address generator/miner [v0.22]

[LoyceMobile]

So, in about 100000000000000 years you may find one, only to realize you're still a few digits short.

[1714126955]

1714126955

[1714126955]

1714126955

[1714126955]

1714126955

[PietCoin97]

for now i will find nothing becuase the tool wont work for me at the moment

but i say you one collega found with this method 7 Addresses

restart every 30 min It's all just possibility and probability

[xhomerx10]

for now i will find nothing becuase the tool wont work for me at the moment

but i say you one collega found with this method 7 Addresses

restart every 30 min It's all just possibility and probability

Dude.  Seriously. There are

Code:

115792089237316195423570985008687907852837564279074904382605163141518161494336

possible Bitcoin addresses and you you are looking randomly for 6 million?  Have you done the math?

Code:

115792089237316195423570985008687907852837564279074904382605163141518161494336 divided by 6 million=
19,298,681,539,552,699,237,261,830,834,781,317,975,472,927,379,845,817,397,100,860,523,586,360.249056 

Stop.  You look silly.  I wager one colleague is a liar.

[aarons6]

for now i will find nothing becuase the tool wont work for me at the moment

but i say you one collega found with this method 7 Addresses

restart every 30 min It's all just possibility and probability

there is zero chance your friend brute forced an entire btc address..


you are just wasting your time.

[PietCoin97]

yeah i know that i dont use it anymore.

[KingZee]

yeah i know that i dont use it anymore.

In case you try to do this in the future again, dont use half patterns.. The difference between 10^-80 and 10^-60 is almost inexistent, youre better off searching for full patterns rather than maybe landing on a close relative to your address.

[88nE6w2xfri6izL1Xx239ELXb]

If someone interested in deep conversation about vanitygen and math,
welcome to subreddit I created recently.

https://www.reddit.com/r/vanitygen/

[gembitz]

for now i will find nothing becuase the tool wont work for me at the moment

but i say you one collega found with this method 7 Addresses

restart every 30 min It's all just possibility and probability

there is zero chance your friend brute forced an entire btc address..


you are just wasting your time.

chuck norris comes to mind    hehe

[elda34b]

Have anybody try to run vanitygen on Google's TPU cloud machine or any HPC service? What's the best keysearch rates has it archive so far?

Why would you run it online? It is risky to do that because your data could be intercepted.
You should run vanitygen offline on a secure computer. Using OpenCL is fast enough for me.

[ABCbits]

Have anybody try to run vanitygen on Google's TPU cloud machine or any HPC service? What's the best keysearch rates has it archive so far?

Why would you run it online? It is risky to do that because your data could be intercepted.
You should run vanitygen offline on a secure computer. Using OpenCL is fast enough for me.

I think his point is Google's TPU or HPU can generate vanity address at faster rate. While it's true that the information could be intercepted, using encrypted connection could solve the problem.

But Google's TPU is optimized for AI stuff (deep learning, neural network, machine learning, etc.).

[elda34b]

Just want to find out how fast vanitygen can go, hashcat release benchmark & performance of lastest GPU card all the time, i usually use vanitygen to test my GPU card max performance when my family's internet cafe buy a new PC. I always wonder with these days strongest hardware, have we archive the speed of 1bil or even 1 trillion keys/s?

I see. I'm not so sure about the speed but I really doubt we reach that point. 1 billion keys/sec is crazy.
At this moment I can't find the result on the internet either, so your best choice would be to try it out yourself.

[LoyceV]

Have anybody try to run vanitygen on Google's TPU cloud machine or any HPC service? What's the best keysearch rates has it archive so far?

Why would you run it online? It is risky to do that because your data could be intercepted.
You should run vanitygen offline on a secure computer. Using OpenCL is fast enough for me.

I think his point is Google's TPU or HPU can generate vanity address at faster rate. While it's true that the information could be intercepted, using encrypted connection could solve the problem.

Using split key is a much better solution, so that Google itself can't know your private key either. They can still know you generated the address through.

[ABCbits]

Have anybody try to run vanitygen on Google's TPU cloud machine or any HPC service? What's the best keysearch rates has it archive so far?

Why would you run it online? It is risky to do that because your data could be intercepted.
You should run vanitygen offline on a secure computer. Using OpenCL is fast enough for me.

I think his point is Google's TPU or HPU can generate vanity address at faster rate. While it's true that the information could be intercepted, using encrypted connection could solve the problem.

Using split key is a much better solution, so that Google itself can't know your private key either. They can still know you generated the address through.

I totally forget about split key. But google knowing user generate vanity address doesn't matter unless you could know bitcoin address just from partial private key, brute force to get private from an address with partial private key or have serious privacy concern.

[manhquang2206]

Does anybody know how to modify this?
I found a post on bitcoin stackexchange show how to create a bitcoin address from given hex private key

In vanitygen.c

Replace

Code:

 EC_KEY_generate_key(pkey);

with

Code:

            BIGNUM *res;
            BN_init(&start);
            res = &start;
            BN_hex2bn(&res, "3B1BCC5A67F38853810972B1DA8A67148FAD78C6CD6F22B2C823D141BE59C81C"); //Set up hex private key
            vg_set_privkey(res, pkey);

& remove case

Code:

if (++npoints >= rekey_at)

I intend to replace the input hex private key with function like hashcat to recover lost pivate key like this

Code:

"?1?1?1?1?1?1?1"+"A67F38853810972B1DA8A67148FAD78C6CD6F22B2C823D141BE59C81C"

When i test it on a single hex private key,by default the function keep multiply the key for new address instead of keep try new key completely, if i change it to my given function, it maybe took awhile for the application to generate new key again & the code doesn't even use 100% cpu power, there're no further instruction in the post. Is anybody know to how to adjust the code to check address from mutiple generated key without multiply it. If possible, the performance will stay around like original code or at least decline to 1-20 times, i wouldn't mind that. Thank You

[nc50lc]

So i bump into Bitcoin Collider https://www.reddit.com/r/Bitcoin/comments/655j0r/large_bitcoin_collider_tried_over_3000_trillion/ on reddit & discover its members consider using FPGA for better performance, this is the first time i heard of this device. If we run their program or vanitygen on it, how many keys/s can it archived?

Some examples of FPGAs are FPGA mining cards which is mainly used for mining and as far as I know LBC was optimized (if not the old versions, the latest) to use it efficiently.
On the other hand, Vanitygen is optimized for Processors while Oclvanitygen is optimized for GPUs, I don't know if it will run with FPGA either.

So the answer would be obvious.
But there are forks that have different tweaks supporting different type of devices (even FPGAs)

[elda34b]

If we run their program or vanitygen on it, how many keys/s can it archived?

The best answer would be to try it by yourself. Theoretically, it should be faster than CPU/GPU though. Personally I think OCL is fast enough to create an address/key pair. On top of that, we can use split key too. Loyce has a nice tutorial about this.

[ABCbits]

The best answer would be to try it by yourself. Theoretically, it should be faster than CPU/GPU though. Personally I think OCL is fast enough to create an address/key pair. On top of that, we can use split key too. Loyce has a nice tutorial about this.

Why does it has to be split key? I see many ppl rent AWS to run vanitygen for normal key pair but never seen any private key get leak, are there really any incident that VM service stalk on ppl activity to steal key?

AFAIK no, but most VPS services log some of users activity which raises some privacy concern.

It's just a security practice and IMO better safe than sorry. Additionally by split key, even if your VPS got hacked, your full private key won't be leaked.

[KingZee]

The best answer would be to try it by yourself. Theoretically, it should be faster than CPU/GPU though. Personally I think OCL is fast enough to create an address/key pair. On top of that, we can use split key too. Loyce has a nice tutorial about this.

Why does it has to be split key? I see many ppl rent AWS to run vanitygen for normal key pair but never seen any private key get leak, are there really any incident that VM service stalk on ppl activity to steal key?

If you generate your own private key it makes no difference as long as you're sure no one else has access to it.

Split key generation is used when someone has the processing power, and wants to generate a vanity address for someone else. None of them know the private key unless they have both split solutions to it.

[Chris!]

The best answer would be to try it by yourself. Theoretically, it should be faster than CPU/GPU though. Personally I think OCL is fast enough to create an address/key pair. On top of that, we can use split key too. Loyce has a nice tutorial about this.

Why does it has to be split key? I see many ppl rent AWS to run vanitygen for normal key pair but never seen any private key get leak, are there really any incident that VM service stalk on ppl activity to steal key?

If you generate your own private key it makes no difference as long as you're sure no one else has access to it.

Split key generation is used when someone has the processing power, and wants to generate a vanity address for someone else. None of them know the private key unless they have both split solutions to it.

There's a more simple explanation. Say you generate a key and the private key in base6 looks like

Code:

111112222233333444445555500000111112222233333444445555500000111112222233333444440000011111222223333

That's your half private key (it would be in WIF format most likely). Now someone goes and generates a private key with your partial public key. The private key returned is

Code:

123451234512345123451234512345123451234512345123451234512345123451234512345123451234512345123451234

You add their private key with your private key and boom. You'll see your vanity address that they generated for you. I'm just on a mobile device at the moment so can't calculate the public key or what these two numbers added together would be, but hopefully that's a half decent explaination.

[cccomputing]

Hello general question:
Are Vanitygen less safe than random Adresses since they were bruteforced?

Im dont have too much knowledge in programming but if Vanitygen would always start a bruteforce from 0000000.. until it finds a match that means that a bruteforce / collider would find those adresses first because they are on the very low end of the private key scale.

Is this assumption correct or are those keys as safe as a totally random one?