Pages:
Author

Topic: Vanity Pool - vanity address generator pool - page 25. (Read 147800 times)

donator
Activity: 3108
Merit: 1166
feedback:

I put a generation request (MoLeCuLaR) with a much too low bounty.
...

I'm sure you know that you can send additional bounty to the same bounty address if you wish to make it more attractive/realistic.
legendary
Activity: 1386
Merit: 1097
I think maybe both these problems could be taken care of by informing the user about the results of some educated guess as to how high the bounty should be on the page where people enter the requests? Maybe a little table based on the given "difficulty" like this:

That would be great. Unfortunately it requires pool to know pool hashrate, which is not possible yet. And it might fluctuate a lot, depends on the highest bounty in the pool.

However another "educated quest" may be provided for users. Pool can calculate "recommended bounty", which will make mining for this solution a bit more profitable than bitcoin mining. AFAIK there's some simple approximation between (vanity's) GKey and (bitcoin's) MHash, at least for some kind of hardware as ATI HD xxxx. Fizzists's calculator is useful, although it don't take bitcoin profitability in account.

I believe that providing bounties a bit higher than equivalent in bitcoin mining will attach much more attention to all this stuff...
hero member
Activity: 896
Merit: 1000
You're right that this feature does nothing when you have a more sophisticated system like yours.
Just realized that I didn't elaborate on my trigger idea. To make it easier to integrate with other things, simply passing a script for both start/stop event which would be called with a fork/exec would help.
Still, it can provide a very simple mechanism when the user is only interested in mining address or doing nothing. If they set the minimum value to roughly their cost of power, it will only switch on whenever they can make any profit. Since it only adds an additional command line option, it doesn't really do any harm to add it, so I feel like it would be a worthwhile addition (although of limited use).

Glad to hear that you got a system working for you, and that I could help! That is exactly what I had envisioned when I started out my little project. Are you interested in sharing your script?
It's raw, needs external scripts to work and I think I have a bug when your API isn't reachable that makes it exit in error (probably trivial to fix).
http://pastebin.com/Ci2azd7h
donator
Activity: 2772
Merit: 1019
feedback:

I mined for a bit in the pool but determined it was not profitable at the moment BTC (I guess there are some low-hanging fruit popping up from time to time but they are of course snatched quickly, right?).

I put a generation request (MoLeCuLaR) with a much too low bounty.

I think maybe both these problems could be taken care of by informing the user about the results of some educated guess as to how high the bounty should be on the page where people enter the requests? Maybe a little table based on the given "difficulty" like this:


you pay | expected time to delivery
----------------------
BTC 0.1 | 2 years
BTC 1.0 | 3 months
BTC 5.0 | 2 weeks


possible? makes sense?
hero member
Activity: 720
Merit: 525
I just calculated expected daily profitability for my card (HD 5870):
27 MKey/s * 3600 * 24 = 2332 GKey/day
Total value for current work: 0.000018 BTC/Gkey

So 2332*0.000018 = 0.04199 BTC / day in average. Is it really less worth than bitcoin mining or I have any mistake in my calc?

Your calculation is correct, you can check

http://fizzisist.com/mining-value/

to get quick info if it is worth to turn vanity miner on

Yep, vanity address mining on the pool is seriously under valued right now. Now would be a good time to submit a very difficult pattern with a low bounty, as long as the bounty is high enough.

Also, I just added the ability to look at older data in the graphs by clicking on any of them.
hero member
Activity: 720
Merit: 525
[...]
I'm hoping to be watching near the moment the work switches over to "available" because I'm testing out a new feature for oclvanityminer that allows you to set a minimum value to mine for, otherwise put oclvanityminer in a sleeping state. This could make it possible to automatically switch to mining vanity addresses whenever it is more valuable than bitcoin mining (right now it isn't)...

If anyone wants to try it out, feel free to try my fork: https://github.com/fizzisist/vanitygen
I'm on your fork. Works great.

Switching from vanity to bitcoin mining and back is a good idea. I'm actually already doing it with a custom Ruby script which is monitoring your API and the Bitcoin difficulty. It's not reusable (it builds upon my own existing setup with a central monitoring server which already knows how to reconfigure each of my rigs which all use cgminer).

I don't see exactly how oclvanityminer simply sleeping when rewards are not high enough will allow dynamic switching. There needs to be a trigger when oclvanityminer detects a switch from Bitcoin to Vanity or vice versa is adequate that handles all the work needed to properly switch. Here are the things my script does on all rigs when it detects a change from Bitcoin to Vanity is appropriate:
  • stop the GPU in cgminer and change the memory speed (vanity mining sweet spot is around 650MHz for my 5870 and 5970 GPUs) through its API and leave it running to manage the fan speeds
  • launch oclvanityminer
in the other case (Vanity -> Bitcoin) oclvanityminer is killed and cgminer restarted to reapply optimized settings for Bitcoin mining.

You're right that this feature does nothing when you have a more sophisticated system like yours. Still, it can provide a very simple mechanism when the user is only interested in mining address or doing nothing. If they set the minimum value to roughly their cost of power, it will only switch on whenever they can make any profit. Since it only adds an additional command line option, it doesn't really do any harm to add it, so I feel like it would be a worthwhile addition (although of limited use).

Glad to hear that you got a system working for you, and that I could help! That is exactly what I had envisioned when I started out my little project. Are you interested in sharing your script?
hero member
Activity: 759
Merit: 502
I just calculated expected daily profitability for my card (HD 5870):
27 MKey/s * 3600 * 24 = 2332 GKey/day
Total value for current work: 0.000018 BTC/Gkey

So 2332*0.000018 = 0.04199 BTC / day in average. Is it really less worth than bitcoin mining or I have any mistake in my calc?

Your calculation is correct, you can check

http://fizzisist.com/mining-value/

to get quick info if it is worth to turn vanity miner on
legendary
Activity: 1386
Merit: 1097
I just calculated expected daily profitability for my card (HD 5870):
27 MKey/s * 3600 * 24 = 2332 GKey/day
Total value for current work: 0.000018 BTC/Gkey

So 2332*0.000018 = 0.04199 BTC / day in average. Is it really less worth than bitcoin mining or I have any mistake in my calc?
sr. member
Activity: 444
Merit: 313
The fix is live and it appears to be working. It also addresses a part of the issue with the lower case characters being used for public key making it harder to submit work. Now new works' public keys will be converted to upper case, as it is the same case used by oclvanityminer.
legendary
Activity: 952
Merit: 1000
Then I realized that with ASICs and the reward drop around the corner, my GPUs will likely only be good for vanity mining soon enough.
+1
hero member
Activity: 742
Merit: 500
[...]
I'm hoping to be watching near the moment the work switches over to "available" because I'm testing out a new feature for oclvanityminer that allows you to set a minimum value to mine for, otherwise put oclvanityminer in a sleeping state. This could make it possible to automatically switch to mining vanity addresses whenever it is more valuable than bitcoin mining (right now it isn't)...

If anyone wants to try it out, feel free to try my fork: https://github.com/fizzisist/vanitygen
I'm on your fork. Works great.

Switching from vanity to bitcoin mining and back is a good idea. I'm actually already doing it with a custom Ruby script which is monitoring your API and the Bitcoin difficulty. It's not reusable (it builds upon my own existing setup with a central monitoring server which already knows how to reconfigure each of my rigs which all use cgminer).

I don't see exactly how oclvanityminer simply sleeping when rewards are not high enough will allow dynamic switching. There needs to be a trigger when oclvanityminer detects a switch from Bitcoin to Vanity or vice versa is adequate that handles all the work needed to properly switch. Here are the things my script does on all rigs when it detects a change from Bitcoin to Vanity is appropriate:
  • stop the GPU in cgminer and change the memory speed (vanity mining sweet spot is around 650MHz for my 5870 and 5970 GPUs) through its API and leave it running to manage the fan speeds
  • launch oclvanityminer
in the other case (Vanity -> Bitcoin) oclvanityminer is killed and cgminer restarted to reapply optimized settings for Bitcoin mining.
I've started writing a python script to do something very similar.  Then I realized that with ASICs and the reward drop around the corner, my GPUs will likely only be good for vanity mining soon enough.

I didn't think about changing memory values to improve speeds.  I'll try it out with my 5970s.
hero member
Activity: 896
Merit: 1000
[...]
I'm hoping to be watching near the moment the work switches over to "available" because I'm testing out a new feature for oclvanityminer that allows you to set a minimum value to mine for, otherwise put oclvanityminer in a sleeping state. This could make it possible to automatically switch to mining vanity addresses whenever it is more valuable than bitcoin mining (right now it isn't)...

If anyone wants to try it out, feel free to try my fork: https://github.com/fizzisist/vanitygen
I'm on your fork. Works great.

Switching from vanity to bitcoin mining and back is a good idea. I'm actually already doing it with a custom Ruby script which is monitoring your API and the Bitcoin difficulty. It's not reusable (it builds upon my own existing setup with a central monitoring server which already knows how to reconfigure each of my rigs which all use cgminer).

I don't see exactly how oclvanityminer simply sleeping when rewards are not high enough will allow dynamic switching. There needs to be a trigger when oclvanityminer detects a switch from Bitcoin to Vanity or vice versa is adequate that handles all the work needed to properly switch. Here are the things my script does on all rigs when it detects a change from Bitcoin to Vanity is appropriate:
  • stop the GPU in cgminer and change the memory speed (vanity mining sweet spot is around 650MHz for my 5870 and 5970 GPUs) through its API and leave it running to manage the fan speeds
  • launch oclvanityminer
in the other case (Vanity -> Bitcoin) oclvanityminer is killed and cgminer restarted to reapply optimized settings for Bitcoin mining.
sr. member
Activity: 444
Merit: 313
How many confirmations do you require before a new pattern is available? I submitted this one and the bounty payment has 8 confirmations, but the work is still "awaiting payment."

Hmm, I think I might've put in a strict inequality (<) in the work updating tool, while I should've used a non-strict inequality (<=). So for the time being paying exactly 0.1 can cause the work not to update.

I will change that today.

[...]I'm testing out a new feature for oclvanityminer that allows you to set a minimum value to mine for, otherwise put oclvanityminer in a sleeping state. This could make it possible to automatically switch to mining vanity addresses whenever it is more valuable than bitcoin mining (right now it isn't)...

This probably would be a welcome feature for a lot of miners.
hero member
Activity: 720
Merit: 525
Please tell us when it's fixed. I've disabled vanitypool in my configurations: in the current state I lose money on it (0.16BTC for ~6GH/s worth of rigs in 24h...).

The fix is live. I hope it will work as intended.

How many confirmations do you require before a new pattern is available? I submitted this one and the bounty payment has 8 confirmations, but the work is still "awaiting payment."

I'm hoping to be watching near the moment the work switches over to "available" because I'm testing out a new feature for oclvanityminer that allows you to set a minimum value to mine for, otherwise put oclvanityminer in a sleeping state. This could make it possible to automatically switch to mining vanity addresses whenever it is more valuable than bitcoin mining (right now it isn't)...

If anyone wants to try it out, feel free to try my fork: https://github.com/fizzisist/vanitygen

13 confirmations now... Looks like something went wrong with that fix.

Definitely something wrong, the work still isn't available.
hero member
Activity: 896
Merit: 1000
Sorry, I updated the url to just api/vanitypool-value after samr7's explanation yesterday. I forgot to set up a redirect for that one, and the old url just points to the old data (which is no longer being updated). Sorry about that!
Works with the new URL, thanks.
hero member
Activity: 720
Merit: 525
fizzizsst: I use your API (http://fizzisist.com/mining-value/api/vanitypool-value-mult) to trigger vanity mining but it seems it doesn't work anymore (returns the same value oclvanityminer used to give me yesterday).

Sorry, I updated the url to just api/vanitypool-value after samr7's explanation yesterday. I forgot to set up a redirect for that one, and the old url just points to the old data (which is no longer being updated). Sorry about that!
hero member
Activity: 896
Merit: 1000
fizzizsst: I use your API (http://fizzisist.com/mining-value/api/vanitypool-value-mult) to trigger vanity mining but it seems it doesn't work anymore (returns the same value oclvanityminer used to give me yesterday).
hero member
Activity: 720
Merit: 525
Please tell us when it's fixed. I've disabled vanitypool in my configurations: in the current state I lose money on it (0.16BTC for ~6GH/s worth of rigs in 24h...).

The fix is live. I hope it will work as intended.

How many confirmations do you require before a new pattern is available? I submitted this one and the bounty payment has 8 confirmations, but the work is still "awaiting payment."

I'm hoping to be watching near the moment the work switches over to "available" because I'm testing out a new feature for oclvanityminer that allows you to set a minimum value to mine for, otherwise put oclvanityminer in a sleeping state. This could make it possible to automatically switch to mining vanity addresses whenever it is more valuable than bitcoin mining (right now it isn't)...

If anyone wants to try it out, feel free to try my fork: https://github.com/fizzisist/vanitygen

13 confirmations now... Looks like something went wrong with that fix.
hero member
Activity: 720
Merit: 525
Please tell us when it's fixed. I've disabled vanitypool in my configurations: in the current state I lose money on it (0.16BTC for ~6GH/s worth of rigs in 24h...).

The fix is live. I hope it will work as intended.

How many confirmations do you require before a new pattern is available? I submitted this one and the bounty payment has 8 confirmations, but the work is still "awaiting payment."

I'm hoping to be watching near the moment the work switches over to "available" because I'm testing out a new feature for oclvanityminer that allows you to set a minimum value to mine for, otherwise put oclvanityminer in a sleeping state. This could make it possible to automatically switch to mining vanity addresses whenever it is more valuable than bitcoin mining (right now it isn't)...

If anyone wants to try it out, feel free to try my fork: https://github.com/fizzisist/vanitygen
sr. member
Activity: 444
Merit: 313
Please tell us when it's fixed. I've disabled vanitypool in my configurations: in the current state I lose money on it (0.16BTC for ~6GH/s worth of rigs in 24h...).

The fix is live. I hope it will work as intended.
Pages:
Jump to: