Topic: Vanity Pool - vanity address generator pool - page 28. (Read 148044 times)

I am sorry to hear that. Did you double check that the solution is correct? There have been cases of the miner coming up with incorrect answers. You can check your answer here: gobittest.appspot.com .

I will look into the issue.

Except that total BTC per GKey for miners will be lower, because miners need to keep hashing to get whole reward; although that user don't care about next results. But it was just an idea and I understand it may be a bit tricky to implement.

Feature request:

Possibility to request more prefixes for one public key and do not offer one price for every prefix, but one price for any solution (which comes first). For example I want some nice personal address and it can be 1slush or 1marek, but I don't need both of them. When pool is able to stop searching for other prefix when one has been already found, user can offer higher reward per GKey...

Afaik this can be done pretty easily; miner search for more prefixes with the same pubkey already. So it's "only" change of the pool, to hide other works when first one has been solved, plus use shared reward per pubkey, not per prefix.

Please correct me if it won't work for some reason...

According to the bounty calculator almost all off the current work is under priced by a lot, does this mean that it's not actually worth "mining" for keys at the moment?
//DeaDTerra

Please test it out and let me know how it works for you!

Looks promising!


0.1BTC, and please keep in mind that the Pool keeps 20% of the bounties, so the final reward will be 80% of the initial reward.

I wrote a "bounty calculator" to help users decide what bounty to set on a new piece of work. The idea is that the value of your new work should be just higher than the current highest valued work, but not higher than it needs to be, in order to put it at the front of the line. I explained it on the page:

A question for ThePiachu, what is the lowest bounty you can set for new work?

VanityPool still lists 1Private but refuses to accept solutions (one of my rig found the solution and all of the ones I pointed at VanityPool tried to submit new ones several times).

When submitting work to vanitypool.appspot.com, it can be difficult to decide what bounty to set. To get your work done fast, the bounty should be high enough that the "value" of doing your work is higher than the value of doing other work. This will ensure that oclvanityminer will select your work over the others, and it will be the only work done by miners until it is solved or a more valuable piece of work is submitted. On the other hand, you should set the bounty as low as possible so as to not overpay.

This calculator will calculate the difficulty of a given pattern, check the current highest value work at vanitypool, then suggest a bounty for your work that would move your work to the front of the line, since it has the highest value. The suggested bounty will be 0.00001 BTC higher than the equivalent bounty for the current highest valued work. You are encouraged to set the bounty even higher so that your work remains at the front of the line in case some new work is submitted in this time.

Note: if you have outstanding work at vanitypool already, a worker can simultaneously search for all patterns belonging to a single public key. This means you may be able to reduce the bounty for a newly added pattern since the value of searching for all work belonging to a single public key is equal to the sum of the values of each pattern. If you have outstanding work at vanitypool, enter the public key belonging to the work in the form, and it will take this into the calculation to decide an applicable bounty.

Also any suggestions or tips on how to increase my MKey/s rate?

I noticed that if I run 2 instances of the miner on the same card, I get a higher total mkey/s.  I tried playing around with --threads to get the same effect, but that must not be what I thought.

Right now I have 3 instances of oclvanityminer running across 5 gpus and I get ~125 mkey/s instead of ~111.

Added those three cards in.

Probably at the moment we would need some software optimisation for the miner. Block mining has been polished a lot, while vanity mining is still a new thing. Asides from that, the standard - overclocking, getting better hardware etc...

I wonder when someone will start vanity mining with FPGA boards...

Also any suggestions or tips on how to increase my MKey/s rate?

Cool. I added mine to the table. If anyone has data for their hardware and doesn't feel like editing the wiki, please at least post here!

I just tried fizzisist's patch:


actually current jobs don't look like worth of electricity ;-). However I don't know if it is just a bug in calculation or current work is really so hard/underpaid.

Total value for current work: 0.000000 BTC/Mkey