Topic: Vanity Pool - vanity address generator pool - page 9. (Read 147183 times)

If you're up for that, sure. Just keep in mind I don't have much of a budget for this, so I wouldn't want you to spend too much work on it .

If you allow me I could design a rough template for a new site and share it with you. As already mentioned, this project has great potential and all it really needs to grow is more available work, which can be solved by using different language and terminology on the landing page. I can do that for you.

Prices are calculated based on the current Bitcoin difficulty. The front page prices are a bit outdated.

So are the prices on the website still current? Are they in BTC?

In other words, do I understand correctly that if I would want to request a search for a pattern with eight characters (1Abcdefg) that that would cost BTC 8.3 or USD 5222?

Thanks for the suggestion. The website is long overdue for a frontend overhaul, but I'm not really that good at frontend design. I also am rather busy with my other projects at the moment, so I don't have the time to improve this one. At the moment it's functioning quite well by itself.

This project has so much potential!

I don't understand why ever aspect of this project is made out to be so complicated. 

You don't see the engine from the drivers seat when driving a car.  Why does the common user need to know 98% of the stuff described on the https://vanitypool.appspot.com page?  It's noise that turns potential miners and buyers off.  Tech people love it.  Great!  Hide it in a section that tech people can find but that takes it away from others.

Both the ordering page and the mining page could really be improved.

Why does it need to be so complicated? 

Sorry if it sounds like I am whining.  I am.  I haven't had much sleep.  Just upsets me that so much work has been done but that this project has been left to the joys of an engineer instead of a marketing person. lol.  Please clean up the pages so that a 7 year old could order!

There is hardly any work to be done because this page is written in a way that it requires a bitcoin software programmer to use it!
https://vanitypool.appspot.com/newWork

Just take the 80/20 rule... make this page so AN AVERAGE BITCOIN USER can order their own vanity address!

Geez... this whole thing could big as big as web address registrars become... please improve it and DUMB IT DOWN. 

(Sorry if I should have written this when I had more sleep.)

Thanks for the info

That depends on the available work.  The work currently available (as I'm writing this), is too high in difficulty - meaning you would be better off just mining Bitcoin directly.

If you check this list: https://vanitypool.appspot.com/availableWork
Look for the last column, 'Lavishness'.  If that is above 1.0, it makes sense to try generating that vanity address.

Such work pops up from time to time, but you're basically best off setting up a system that checks for such work and only tries mining it when it pops up, instead of 'wasting' processing time on the hard ones that you could otherwise be using for something else.
( I believe there's a fork that semi-automatically does this, but I can't think of it off the top of my head. )

And therein lies a bit of a rub: the Lavishness is only with respect to mining Bitcoin.  It's entirely possible that you can get better returns by mining an Altcoin, even if a relatively lucrave Bitcoin vanity address pops up.

is it profitable to "mine" this?

Best ask on the vanitygen's topic.

I downloaded the latest version and compiled it for OSX but I can't seem to specify a public address when I use ./oclvanitygen instead of ./vanitygen however the topic start mentions it's both possible. What am I missing? -P doesn't seem to be an option for oclvanitygen.

Correct.  There have been suggestions to make it more pool-like, but really there would first have to be more interest in vanity addresses again to begin with.  They have gone somewhat out of vogue

but it still pure luck - as you are not paid by shares or work contributed - first who found takes all prize?

If it not possible to generate it without public key being used. Otherwise you are compromising the security of the private key by knowing it. As far as I remember, you can use vanityminer and specify the public key in it even if you are generating offline. Best look at samr7's vanitygen thread for instructions.


A lot of the time Vanity Pool doesn't have very profitable work. However, new work comes in a few times a week that has better payout. If you automate your vanity miner to fetch work from the pool automatically you should be on that work quickly.

Given the usual vanities being requested - the current one being selected being 1AntjeDahm - yeah, probably not entirely unexpected.  My test machine would take a decade and then some, on average

Trying vanityminer on pool:
Is it normal to have 1.2y 50% prob on 50mkey/sec?

oh ok.
missed split-key somehow...
is there opportunity to use list of prefixes with list of Public Keys with oclvanityminer?

also is there opportunity to generate priv key without pubkey and than combine somehow?

Or it is only possible with oclvanitygen to generate 1 address at a time with split-key requirements?

thank you!

Addresses are case sensitive. Also keep in mind to use split-key vanity address generators in case you haven't been.

hi got the solution for

Pattern: 1BitSnitch
Address: 1BiTSniTCH....
Privkey: Kx19...........



when submitting - getting error:
Solution does not match the pattern

using bitcoin address utility by Casascius to convert key to hex.
Please advise.

It's a bit technical, but let's distill it down to the basics...

ECDSA keys are comprised of X and Y coordinate information.  A compressed key is simply a shorter representation of the public key by discarding the Y coordinate and instead adding a small bit of information about the coordinates that allows a bit of code to work out the Y coordinate based on the X coordinate.
This is desirable because it keeps the size of the blockchain down a fair bit at the expense of a teensy bit more computation for any piece of software that has to actually deal with these calculations.
However, because Bitcoin addresses are based on the public key representation - rather than the public key information - such a compressed key yields a different address than a non-compressed key.
( For those wondering - yes, that means that for every address out there, there's another matching address.  That's why private keys represented in a WIF format will have a bit of information for clients on whether the public key is uncompressed (WIF starts with a '5') or compressed (WIF starts with 'K' or 'L'), while for raw or incorrect imports you'll have to help the client along a bit by specifying it specifically. )

The additive and multiplicative bits are even more technical, you really would have to read up on the finer details, but suffice it to say that both yield the same results due to the way elliptic curve cryptography work with the exception that when using additive you can combine two public keys and get the desired address, while with multiplicative you can't.  This doesn't really affect the end-result other than having to choose which combination to use to actually get the correct address - i.e. if it is multiplicative and you choose additive instead, you still get a valid Bitcoin address.. just not the one with the vanity.

Can't help you with the other one other than that I believe the steps are exactly as you mention with the modification that the base point is added as that still yields valid results and is faster than re-generating a new key for each test.