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

Yes, this can happen and is expected behavior.

If you do not use the rekey function then the program spaces out the threads, CPU or GPU, and then with each thread, searches sequentially.

You are using a fairly simple vanity/not a huge difficulty level,
Difficulty: 33554432
Search: bc1q22ace [Compressed]

So you will find many of those if you let the program continue to run.

I am surprised LloyceV would say it should not happen because I know he knows about vanity addresses/search. If one is searching for 1Bxyz, in a given range, you will find many, and obviously if you are searching in a given range, many keys will be "close".

Even if you use the rekey function, but are searching for an easy vanity, you could get keys in which their private keys are close in nature. If you use the rekey, it generates random starting points for each thread and then searches sequentially until the rekey number is met; then it rinses and repeats.

I'm just using the official build, unaltered.    (OS: Windows 10 with the latest security updates)

Just found another 2 even more similar private keys:

0x90AD2D51198584C695F79D27512B147C865C7093E10065F4B4363881C882C87D
0x90AD2D51198584C695F79D27512B147C865C7093E10065F2B4363881C87CF970


PubAddress: bc1q22ace8n7qwe3xtazp05x6vl8fy7mkf5cwznnp5
Priv (WIF): p2wpkh:L24wedqSrZsKNmmF33fxZj75Xz4P4K562VzHKJCE4Q2p6TrBoJha
Priv (HEX): 0x90AD2D51198584C695F79D27512B147C865C7093E10065F2B4363881C87CF970
PubAddress: bc1q22acevaq6x6r4867ay2n73qfgjlcj95pzrxx9x
Priv (WIF): p2wpkh:L24wedqSrZsKNmmF33fxZj75Xz4P4K562WivkuVB3vnYXXDimUkL
Priv (HEX): 0x90AD2D51198584C695F79D27512B147C865C7093E10065F4B4363881C882C87D


At this point I'm guessing this is due to performance optimizations made by the developer?

Can anyone try to reproduce this?
I'm using the following search pattern:  bc1q22ace

Yes! This should not happen. Unless you altered the source to search from a specific starting point.

I've never used VanitySearch (because I hardly trust any new software), and I don't know how it works internally, but I would expect it to generate a new random private key after finding a match. I think it's okay to add "+1" from a random number to search the next one (which I expect to be much faster than generating new private keys all the time), but two similar private keys shouldn't happen.

Just noticed this today. I got 2 extremely similar private keys.  Does anyone know if this could be a sign of a security issue with the PRNG?
Probably not, but just asking to be sure.


C:\Users\demo\desktop>VanitySearch.exe bc1q22ace
VanitySearch v1.19
Difficulty: 33554432
Search: bc1q22ace [Compressed]
Start Sun Mar 10 10:21:35 2024
Base Key: CF08C5ECA140F4CF8A32B0673E3B88A2B5647661F4EFC0241E8F8E83709C04B5
Number of CPU thread: 4
[7.13 Mkey/s][GPU 0.00 Mkey/s][Total 2^27.02][Prob 98.3%][99% in 00:00:02][Found 0]
PubAddress: bc1q22acereqtjkhs0xx0a8u5gkdxn5xpvhltnwkcs
Priv (WIF): p2wpkh:L4AA9GpBX7GoRJy3wEgAhzg3zkL8diGmam8wcdCFjArkQKzBRgMu
Priv (HEX): 0xCF08C5ECA140F4CF8A32B0673E3B88A2B5647661F4EFC0251E8F8E8370FA8472
[7.13 Mkey/s][GPU 0.00 Mkey/s][Total 2^27.42][Prob 99.5%][99% in 00:00:00][Found 3]
PubAddress: bc1q22aceas0aw22n3rqnm8ws9gpynd8yzlx0alevd
Priv (WIF): p2wpkh:L4AA9GpBX7GoRJy3wEgAhzg3zkL8diGmamsb4EVCikuAiR3jqbG1
Priv (HEX): 0xCF08C5ECA140F4CF8A32B0673E3B88A2B5647661F4EFC0271E8F8E837113FB6D
[7.12 Mkey/s][GPU 0.00 Mkey/s][Total 2^27.64][Prob 99.8%][99% in 00:00:00][Found 4]  

Hello.. I'm an AMD GPU user, and to use vanitysearch, I can only use CPU. Some search results using ninjastic mention that vanitysearch doesn't support AMD GPU users.

Then I saw oclvanitygen, which I immediately interpreted as the abbreviation for OpenCL VanityGen (please correct me if I'm wrong about this abbreviation). Is it true that Windows 11 + AMD GPU users can maximize their machine using oclvanitygen in searching for BTC addy according to the specified custom prefix?

Use a fork of VanitySearch that has been modded to search in a specific range, such as, VanSearch Bitcrack mod, Keyhunt-Cuda, etc.

what is the best programm to use currently?

It absolutely is not the program to use.

The speed you see, takes on an x amount of speed-up for:


It's not a true 6 x speed up, but if you were searching, just in a given range, the speed you see now, would drop.

Also, 5 out of the 6 are not looking in a given range. And with the original VanitySearch, you cannot search in the 66 bit range. You will have to do modifications, or use a fork that has already been modified or use Keyhunt-Cuda.

But yes, the RTX 4090 is the big bad bawse on all GPU programs. I've ran them against A and H100s, 4090 wins. And the crazy thing is, I do not think all of the cards' features are being unlocked/used. Most codes were written when the RTX 20xx series were out.

Thank you. Still way too slow for Puzzle 66. I know this is probably not the best program to solve the puzzle, but I was trying different programs to find the fastest ones.

I remember the days of running oclvanitygen on my GeForce 840M with 9 Mkey/s. You're 1000 times faster.

Tip: search for more than one prefix at a time. It large increases the chance of finding one of them.

That's actually a pretty good speed it is 6 times faster than GTX 2070.

If you are looking for a list of benchmark speeds for other GPUs and CPUs there is an old post posted by Dave you can check this link below.

- https://bitcointalksearch.org/topic/m.50823897

For CPU check this https://en.bitcoin.it/wiki/Vanitygen

I tried running it on 4090 and below is my speed. Is it a good speed?


.\VanitySearch.exe -stop -gpu 1Testx232f
VanitySearch v1.19
Difficulty: 173346595075428800
Search: 1Testx232f [Compressed]
Start Sat Feb 17 17:40:57 2024
Base Key: DA5A15FF6EE38ABBC1D0F21D881998D19D0009F88479FBF0D83000D59697C316
Number of CPU thread: 31
GPU: GPU #0 NVIDIA GeForce RTX 4090 (128x0 cores) Grid(1024x128)
[8645.60 Mkey/s][GPU 8554.04 Mkey/s][Total 2^37.74][Prob 0.0%][50% in 160.9d][Found 0]

I have a few GPU mining rigs and have used them to generate vanity addresses for my Minted Seats coins that I engrave and sell to supporters.  At one point I think I was running 5 GPUs for a period of several years.  The longest vanity address I ever generated was probably one of the 1NastyFans addresses I've made or maybe one of the addresses for my Mythical Creatures coin set.  More impressive though is that I used vanity addresses to generate sequential addresses for my coins.  Hundreds of different addresses in order starting with for example: 1Nasty__.  It took quite a bit of time to get a 9 digit (10 if you count the 1) vanity address, and even the 8 digit vanities, but 7 digits are pretty easy to get.

Naw, it doesn't need what I had it on. It was just cool looking and low wattage.
I own the physical unit.
It didn't need the GPU but you could run the worker on the server in case no workers where active.
We didn't have a worker payment system set up yet. It was a closed ecosphere .some things like workers retained too much information for an endpoint user in our opinion( partials and browser cookies) it psychically checked keys on bitaddress
These things where going to get worked on.
I'll consult , I scrumed/commissioned it. I learned what c# I know on this project.
Workers are .py
Ideally you should be proficient fullstack dev to take this project on.

Interesting.

For the server, doesn’t seem like it needs much juice, it basically lets the workers know when it’s time to work and what to work on, and then sends email, if correct work was found.

So you leased the server? Does it need to be paired with a GPU?

For the workers, it sounds like MRR, where your GPUs can work on whatever, until it’s rented. I like that.

How did you do worker payments, or were you go that point yet, where workers were paid for hashing or only paid for finding the requested address?

I’m interested…no doubt.

Are you willing to stay on, or are you wanting to be done with it completely?

I ran it on a Dell R710 Google GSA server running server 2019 paired with a Tesla T4
The end points where mining rigs. (The endpoints can be anything running windows)
Payments where processed with opennode.
but it enabled a simpler payment system. (It requires server owner to kyc) That's what it was about, simplicity for the endpoint user.
It's a compartmentalized system with argument breaks wrote in mostly c#.
It's a trustless design as far as Bitcoin security goes.
Software wise it's like mining software. Servers the pool, endpoints are workers. It's just clever workarounds to look like a pool
We where going to pull device IDs and cross reference mks for live key count estimations
Endpoint workers are teslaagents that report to server.
 (They are pretty invasive we recommend keeping them on mining rigs and treating it like so)
Endpoint workers check work and only submit correct work.
Correct work got sent via email (jellyfish)
The endpoints run whatever software you want, but when a request comes in it closes that software and prioritizes the workers task untill finished.
You'd need a domain , email,  opennode account

I'd request a few things if I just hand this over.

 , if its repurposed for cracking it retains intended features as well to the public.
If you release SC , you have a checksum of some sort to verify it's the real deal.
Point the tip jar to the 1SPLiTKEY wallet.
Credit the 1SPLiTKEY Team.  I had a partner in this but they wished to remain anon, I'll respect their wishes but still inadvertently credit them this way.

In your experience/opinion, what all would it take?

If only someone had made a system like nicehash for vanity wallet generation. I'd give the source code to anyone capable and willing to maintain and redeploy the service. (I'd prefer it be someone I know or know of)
 

It's not about mining, it's all related to Bitcoin Vanity address generation

All answers have been tailored to his questions and that's why I also pointed out to the fact that Nicehash cannot provide a solution to his needs (because of the mentioned other algorithms involved but also to the fact that he cannot rent a free-for-use GPU arch on NH).

I would agree if @Synchronice ask about mining. But address generation not only use SHA-256, but also RIPEMD-160, ECDSA and other operation depending on which address type you want to generate.