Welcome, Guest. Please login or register.
Did you miss your activation email?
News: Welcome to eMoneySpace! Sep 18, 2020 09:44 PM

vanity address generator pool
Author Topic: vanity address generator pool  (Read 212 times)
Reputation: (0)


Posts: 12
Referrals: 0

View Profile
Oct 21, 2019 12:09 PM

I've implemented a sort of "mining pool" for creating vanity addresses with zero needed trust. As to how it is possible, check out these links:

The main pool is running at:

And you might also want to check out:

So, onwards with the explanations:

The idea is, that you can generate a vanity address without even knowing what private key it will actually belong to. One party grabs a random ECDSA keypair and saves the private key for themselves. They later can issue a request for a vanity address to be created, by supplying the public key form that keypair, their desired pattern and so forth. A person takes with looking for the vanity address is required to brute force random ECDSA private keys, get their corresponding public keys, add them to the provided public key, and proceed normally with SHA, RIPEMD, and base58 until they receive the desired pattern. Then they give the private key they found to the first person, which adds the two private keys in order to get their vanity address. The best thing about it - the person looking for the solution won't know what the resulting private key is! This means that you can outsource your vanity key generation without needing to trust any third party.

An example (available from gobittest website):
We have a private key:
which maps to public key:
0450863AD64A87AE8A2FE83C1AF1A8403CB53F53E486D8511DAD8A04887E5B23522CD470243453A 299FA9E77237716103ABC11A1DF38855ED6F2EE187E9C582BA6

and say we want to find a pattern "166". One of the solutions takes a form of a private key
mapping to public key:
049C95E0949E397FACCECF0FE8EAD247E6FD082717E4A4A876049FB34A9ADED110DFEA2EF691CC4 A1410498F4C312F3A94318CD5B6F0E8E92051064876751C8404

If we add the two public keys (like the person looking for the solution would do), we get a public key:
0436970CE32E14DC06AC50217CDCF53E628B32810707080D6848D9C8D4BE9FE461E100E705CCA98 54436A1283210CCEFBB6B16CB9A86B009488922A8F302A27487
which is equivalent to this address:

If we add the two private keys (like the person requesting the address would), we get:
which maps to the same public key as the sum of the public keys, and thus - to the same address.

Since this is a model that requires basically no trust from any party, I've decided to create this "Vanity Pool" to enable people to easily outsource their vanity address creation, as well as enable people wanting to earn some Bitcoins to use their machines for something different from traditional mining.

The main problem currently, is that there is no software to support mining for such split addresses, and combining them offline. If someone wants to commit to creating such software, it would be great!

For the time being, the website is up for testing only on the testnet. From that, I can see there are still some bugs in the system, but it should work as expected.

Any comments, suggestions?

I've created a simple split vanity miner software in Google Go (if you're wondering why I used this weird language - I've been developing Bitcoin-related apps in it for a year for my master thesis). The source code and a Mac executable is available here:
It is quite slow, checking a couple of hundred addresses on my old Macbook Pro, but it can solve some reasonably short patterns. The software is streamlined for the vanity pool, you only need to change the given testnet Bitcoin address to yours and it will do most of the work. It fetches work only during the start, so keep that in mind if you want to run it for longer.

The main Net version is up.

If you want to mine at this pool, please use oclvanityminer created by samr7: https://ckk.ai/p2Vnmx
Jump to:  
Copyright © 2008-2020 eMoneySpace. All rights reserved.