I see great minds think alike. Using similar calculations I determined that it currently isn't worth mining vanity addresses based on the current bounties and difficulties. Straight BTC mining is still more profitable.
For instance, 1JohnGALT with its 0.38 BTC bounty only earns about 1/2 what I can make mining BTC directly.
To be competitive, 1JohnGALT would have to offer 0.8 BTC to get anyone's attention.
Topic: Vanity Pool - vanity address generator pool - page 22. (Read 148044 times)
For practical mining values I find http://fizzisist.com/mining-value/ to be more useful.
Since there seems to be some confusion about how these calculations are done, I just added a thorough explanation to the page. To be clear, this is also how oclvanityminer works, only searching for patterns that belong to the single highest valued public key.
For practical mining values I find http://fizzisist.com/mining-value/ to be more useful. At this point it isn't worth pushing any mining power at the vanity pool. I have miners checking for work but not actually doing any hashing unless it is worth more than other mining and I would guess there is a decent number of others doing the same given how quickly work gets solved when it is worth working on. Right now even if the pool started accepting compressed solutions it would just barely have an income equivalent to bitcoin mining, without higher valued names requested you're better off elsewhere.
Lets see, from the FAQ (https://vanitypool.appspot.com/faq):
L = 2^32 * (b/c)
MR = L * (d/r) * (k/m) = 2^32 * (b/c) * (d/r) * (k/m)
k/m was taken as 0.06 from the hardware page (https://en.bitcoin.it/wiki/Vanity_mining_hardware_comparison). Difficulty is currently about 3300000, reward is 25. Total lavishness is 0.00029 . We can calculate that:
MR = 0.00029 * 3300000 / 25 * 0.06 = 2.2968
With your setup the k/m is 25.29 Mkey/s / 660Mh/s ~~ 0.038 . This gives a mining ratio of 1.45 . A bit less, but still more profitable than block mining. On the flip side, there is a higher variance mining for keys, as the website does not work like a pool with shares.
L = 2^32 * (b/c)
MR = L * (d/r) * (k/m) = 2^32 * (b/c) * (d/r) * (k/m)
k/m was taken as 0.06 from the hardware page (https://en.bitcoin.it/wiki/Vanity_mining_hardware_comparison). Difficulty is currently about 3300000, reward is 25. Total lavishness is 0.00029 . We can calculate that:
MR = 0.00029 * 3300000 / 25 * 0.06 = 2.2968
With your setup the k/m is 25.29 Mkey/s / 660Mh/s ~~ 0.038 . This gives a mining ratio of 1.45 . A bit less, but still more profitable than block mining. On the flip side, there is a higher variance mining for keys, as the website does not work like a pool with shares.
..which means if all submitted work was signed by the same key, i.e. same person, and I would work on all work "parallel", I would have a mining ratio of 1.45?
With just one single task at a time, as it seems I am working on, I have the much lower ratio I saw?
Ente
Lets see, from the FAQ (https://vanitypool.appspot.com/faq):
L = 2^32 * (b/c)
MR = L * (d/r) * (k/m) = 2^32 * (b/c) * (d/r) * (k/m)
k/m was taken as 0.06 from the hardware page (https://en.bitcoin.it/wiki/Vanity_mining_hardware_comparison). Difficulty is currently about 3300000, reward is 25. Total lavishness is 0.00029 . We can calculate that:
MR = 0.00029 * 3300000 / 25 * 0.06 = 2.2968
With your setup the k/m is 25.29 Mkey/s / 660Mh/s ~~ 0.038 . This gives a mining ratio of 1.45 . A bit less, but still more profitable than block mining. On the flip side, there is a higher variance mining for keys, as the website does not work like a pool with shares.
L = 2^32 * (b/c)
MR = L * (d/r) * (k/m) = 2^32 * (b/c) * (d/r) * (k/m)
k/m was taken as 0.06 from the hardware page (https://en.bitcoin.it/wiki/Vanity_mining_hardware_comparison). Difficulty is currently about 3300000, reward is 25. Total lavishness is 0.00029 . We can calculate that:
MR = 0.00029 * 3300000 / 25 * 0.06 = 2.2968
With your setup the k/m is 25.29 Mkey/s / 660Mh/s ~~ 0.038 . This gives a mining ratio of 1.45 . A bit less, but still more profitable than block mining. On the flip side, there is a higher variance mining for keys, as the website does not work like a pool with shares.
That value is using a default of .06 for the (k/m) value from the FAQ equation for mining ratio. I believe it is also using either the additive lavishness for all bounties. Now per bounty it may be lower.
And from what I calculated for that particular one and your card your mining ratio is only ~.07. For the whole set of bounties your ratio is like 1.5 using additive lavishness, and .81 using multiplicative lavishness
And from what I calculated for that particular one and your card your mining ratio is only ~.07. For the whole set of bounties your ratio is like 1.5 using additive lavishness, and .81 using multiplicative lavishness
Okay, so I am testing vanitymining..
I use a Sapphire 7950 OC at 1200 Mhz
https://en.bitcoin.it/wiki/Vanitygen:
It does:
"Lavishness: 1.3e-05"
It mines away with 660Mh/s, http://www.alloscomp.com/bitcoin/calculator says 0.1 BTC per day.
https://vanitypool.appspot.com/availableWork says "Mining ratio - 2.32"
To me, vanity mining seems a magnitute less lucrative than blockmining. I can't see an obvious discrepancy on my side. So, where does the "2.32 times more lucrative than mining" come from?
Thank you,
Ente
I use a Sapphire 7950 OC at 1200 Mhz
https://en.bitcoin.it/wiki/Vanitygen:
Quote
AMD Radeon 58XX, 68XX GPUs: up to 23.5 Mkey/s.
AMD Radeon 69XX GPUs: up to 19.5 Mkey/s.
AMD Radeon 69XX GPUs: up to 19.5 Mkey/s.
It does:
Quote
Searching for pattern: "1JohnGALT" Reward: 0.384000 Value: 0.000027 BTC/MkeyHr
Difficulty: 50656515217834
[25.29 Mkey/s][total 461373440][Prob 0.0%][50% in 16.1d]
..which seems about right, according to bitcoinwiki.Difficulty: 50656515217834
[25.29 Mkey/s][total 461373440][Prob 0.0%][50% in 16.1d]
"Lavishness: 1.3e-05"
It mines away with 660Mh/s, http://www.alloscomp.com/bitcoin/calculator says 0.1 BTC per day.
https://vanitypool.appspot.com/availableWork says "Mining ratio - 2.32"
To me, vanity mining seems a magnitute less lucrative than blockmining. I can't see an obvious discrepancy on my side. So, where does the "2.32 times more lucrative than mining" come from?
Thank you,
Ente
Hmm, that is strange, does this mean my certificate would expire? This would be kind of hard, since my website is hosted through Google and their certificate.
I'm afraid I can't really help you there, I don't know much about the problem you are experiencing.
I'm afraid I can't really help you there, I don't know much about the problem you are experiencing.
Yes, indeed strange. The .appspot.com cert isn't expired of course.. heh
And what would I need a local cert.pem for anyway?
F*********CK!
AHHHHHHHHHHHH!!
Windows system clock: 15.12.2013!
*bangs head on keyboard*
LOL!
Ente
I've been running that exact Windows version for a while and never had a problem. It connects to the pool and starts mining with no problems.
Hmm, that is strange, does this mean my certificate would expire? This would be kind of hard, since my website is hosted through Google and their certificate.
I'm afraid I can't really help you there, I don't know much about the problem you are experiencing.
I'm afraid I can't really help you there, I don't know much about the problem you are experiencing.
I try to connect via samr7's oclvanityminer on windows. I use
https://github.com/downloads/samr7/vanitygen/vanitygen-0.22-win.zip for this.
I get this verbose error:
Any help?
Seems like I am the only one trying to run on (my friend's) windows. Could any of you upload his [linux] cacert.pem for me?
Thank you!
Ente
https://github.com/downloads/samr7/vanitygen/vanitygen-0.22-win.zip for this.
I get this verbose error:
Quote
* About to connect() to vanitypool.appspot.com port 443 (#0)
* Trying 74.125.132.141...
* connected
* Connected to vanitypool.appspot.com (74.125.132.141) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: cacert.pem
CApath: none
* SSL certificate problem: certificate has expired
* Closing connection #0
* Peer certificate cannot be authenticated with given CA certificates
Get work request failed: Peer certificate cannot be authenticated with given CA certificates
* Trying 74.125.132.141...
* connected
* Connected to vanitypool.appspot.com (74.125.132.141) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: cacert.pem
CApath: none
* SSL certificate problem: certificate has expired
* Closing connection #0
* Peer certificate cannot be authenticated with given CA certificates
Get work request failed: Peer certificate cannot be authenticated with given CA certificates
Any help?
Seems like I am the only one trying to run on (my friend's) windows. Could any of you upload his [linux] cacert.pem for me?
Thank you!
Ente
Okay, the server appears to be back to the usual load for now.
Hmm, my Amazon EC2 micro instance appears to be blasting at a 100% load. Gave it a restart, updated Bitcoin, and hopefully that will help. So far I don't see much of an improvement. I suppose it's that time of year when everyone needs their server time and so forth. I will try looking into what I can do about the situation over the next couple weeks and so forth. I hope either the 0.8 version will decrease the CPU load, I will be able to host my wallet someplace else, or the Amazon load will go back to normal.
... as well as replace Lavishness with Value.
Wait, my crazy ramblings about units convinced you? Awesome! I hope other people agree with me, too. I did spend a lot of time thinking about that when I set up the stuff on fizzisist.com. Might not be the best way of looking at it, of course. But, we should at least be having the debate now before the number of people interested in this stuff goes up by a factor of 10 or 100, when the difficulty spikes after ASICs appear.
I'm completely open to criticism about my proposed conventions, if anyone has other ideas.
I guess something is wrong with my bitcoind server, I will need to check its status when I will be home. Thanks for the info.
Thanks. Now I'm getting:
Quote
An error has occurred...
Error communicating with Bitcoin, please try again later
when trying to request a new vanity address. Error communicating with Bitcoin, please try again later
So, I want to request a vanity address to be solved for me, but I don't know how to generate a private key/public key in the proper format for my side? I tried looking at the FAQ, but it only tells me to go here: https://gobittest.appspot.com/Vanity which seems completely unrelated.
I did find this: https://gobittest.appspot.com/PrivateKey which seems to generate private keys, but doesn't seem to generate the public key I would also need to submit to the vanity mining site?
I did find this: https://gobittest.appspot.com/PrivateKey which seems to generate private keys, but doesn't seem to generate the public key I would also need to submit to the vanity mining site?
Okay, the unsolvable work has been deleted from the system and the reward will be returned to the person that requested it. The system should clear out any traces of the work soon and everything will be normal again.
I still have to create some safeguard against submitting unsolvable work, as well as replace Lavishness with Value. For now I'm busy with other projects, so I'm not planning on doing those fixes this week.
Thank you all for bringing the unsolvable work issue to my attention and explaining why it is unsolvable.
I still have to create some safeguard against submitting unsolvable work, as well as replace Lavishness with Value. For now I'm busy with other projects, so I'm not planning on doing those fixes this week.
Thank you all for bringing the unsolvable work issue to my attention and explaining why it is unsolvable.
Hmm, I guess I will have to look into fixing the pool for that. I would probably need to develop some more general algorithm though, instead of handling things just for Bitcoin and Namecoin.
Jump to: