I'm so dense sometimes. I never noticed the oclvanityminer program (until now).
Interesting how profitable applications are popping up for GPUs now that BTC mining may become unprofitable.
Topic: Vanity Pool - vanity address generator pool - page 30. (Read 148044 times)
Do I read right that this isn't really a "pool" like for BTC where miners directly connect to a mining address? I've used oclvanitygen some already for my own use but I'm not sure how to go about this for the pool...
It's sort of like a traditional pool, only dedicated to mining for vanity addresses, rather than Bitcoin blocks. You need to use oclvanityminer application by samr7 (https://bitcointalksearch.org/topic/vanitygen-vanity-bitcoin-address-generatorminer-v022-25804 - same package, different executable). You just specify my Pool and your reward address, and the program does all the mining:
Quote
$ ./oclvanityminer -u https://vanitypool.appspot.com/ -a 1samr7UZxtC6MEAFHqr1h3Kq453xJJbe4
This is all possible thanks to some properties of the cryptography behind ECDSA - generally you can outsource vanity address creation with zero risk to your coins. Only the person starting the bounty will know the private key.
Do I read right that this isn't really a "pool" like for BTC where miners directly connect to a mining address? I've used oclvanitygen some already for my own use but I'm not sure how to go about this for the pool...
Actually displaying timestamp and prefix difficulty of solved matches on the web would help some estimation. It will be extremely inaccurate, but at least something....
I guess I could look into implementing that.
For now, some more smaller updates to the Pool - making it look less messy, as well as streamlining reward payout (as in, some changes on the server side of things).
vanitypool.appspot.com
Actually displaying timestamp and prefix difficulty of solved matches on the web would help some estimation. It will be extremely inaccurate, but at least something....
Is there any estimation how much workers and what MKey/s power is working for the pool? (btw I joined the pool few hours ago and just found the match, yay!)
Not really. I guess one could try estimating that through number of calls to the url displaying work and how much work gets submitted, but at the moment I don't really have a clue.
I'm glad you are having your first successes with the Pool.
Is there any estimation how much workers and what MKey/s power is working for the pool? (btw I joined the pool few hours ago and just found the match, yay!)
ThePiachu, can you add the pattern difficulty to the work list?
I could, although that feature might not be up for awhile. Currently working on my other projects. Some small sprucing up of the page might be coming soon though.
I understand. I do believe knowing this will be the key to get people to mine addresses using the pool. It is currently quite hard to figure out if mining addresses is more profitable than mining bitcoins. What's worse is that the profitability of each is changing all the time. Having the current value available would help make it easier to decide which to do.
Another effect this will have is to help a work submitter decide how much to pay. If they want their address to be generated first, they need to set a reward that makes the value of that address higher than the current highest value. If they can wait a bit, they can set the reward slightly lower, but higher than some of the other work available. Without this, you need to do a lot to figure out what reward to set. This will hopefully drive up the rewards over time as people compete for the computing power of the pool.
If all of this is done, I really could see vanity address mining a good replacement for bitcoin mining for all those non-ASIC devices that are pushed out when the difficulty rises. Without this, it's just a really cool toy.
Well, I made the site look a bit more presentable. Also I'm testing some updates on the vanitypooltest.appspot.com website - mainly under the hood stuff. The tables should be neater, errors should be more informative and so forth.
For reference:
Update to the main net version of the Pool should be up within a couple days. I just want to ask if you guys prefer the more compact view of the lists, or do you want all the info?
For reference:
Quote
Database error, please try again later
types errors I found out mean that the Pool was not able to fetch the work info from the database. I guess some argument could be missing, as if the search just finds nothing, it displays a different error. I hope that's what it is...Update to the main net version of the Pool should be up within a couple days. I just want to ask if you guys prefer the more compact view of the lists, or do you want all the info?
ThePiachu, can you add the pattern difficulty to the work list?
I could, although that feature might not be up for awhile. Currently working on my other projects. Some small sprucing up of the page might be coming soon though.
ThePiachu, can you add the pattern difficulty to the work list? If you went one step further and showed the best possible total_value (largest sum of values for a single pubkey, where value = reward / difficulty) at the top of the work list or similar would be really cool, but this can be easily calculated based on the work list (if difficulty is available in the API). Thank you!
FYI, I answered my own question in the vanity gen thread, since I realized it is more about the software than this pool:
I finally had a chance to look at the source and apparently the units of the "value" shown are simply BTC/Mkey, but multiplied by 3600, or in code:
This is not BTC/MKeyHr, this is a meaningless number. More correctly, you could say the units are BTC*s/Mkey*hr. I suggest removing the 3600 and just displaying the value as BTC/Mkey. If the number is too small (too many decimals to be easily readable), change it to BTC/Gkey, since most people are calculating at least a Gkey every minute. If you would like to go one step further, you can show BTC/hr as:
Where rate is the calculated Mkey/s for your hardware (so vg_output_timing() will have to been called already).
Code:
wip->value = (reward * 1000000.0 * 3600.0) / difficulty;
This is not BTC/MKeyHr, this is a meaningless number. More correctly, you could say the units are BTC*s/Mkey*hr. I suggest removing the 3600 and just displaying the value as BTC/Mkey. If the number is too small (too many decimals to be easily readable), change it to BTC/Gkey, since most people are calculating at least a Gkey every minute. If you would like to go one step further, you can show BTC/hr as:
Code:
3600 * rate * reward / difficulty
Where rate is the calculated Mkey/s for your hardware (so vg_output_timing() will have to been called already).
On the solved work page can you make it so it displays the date it was solved and the address that solved it?
I guess I could, although you can get that information from the Block Chain if you search for the donation address. Any reason for the inclusion of that information?
On the solved work page can you make it so it displays the date it was solved and the address that solved it?
Uh... I'm not exactly sure what happened here. It seems I found a key, but there was a db error or something.
http://pastebin.com/K4zZvXz6
I checked that private key and it wasn't 1room77. What the hell happened?
http://pastebin.com/K4zZvXz6
I checked that private key and it wasn't 1room77. What the hell happened?
You answered to yourselves - the private key does not map to 1room77 address pattern => error with GPU computing, it happens from time to time. If you dont have big Rejected ratio when you mine bitcoins at a pool, you dont need to worry
Uh... I'm not exactly sure what happened here. It seems I found a key, but there was a db error or something.
http://pastebin.com/K4zZvXz6
I checked that private key and it wasn't 1room77. What the hell happened?
http://pastebin.com/K4zZvXz6
I checked that private key and it wasn't 1room77. What the hell happened?
Hmm, lets see...
Did you enter the private key as base58 string, or hex string? The pool only accepts the latter. The newer version of the vanity miner should be displaying the correct string to copy.
Did you multiply/add the private key to the public key before checking what it maps to? http://gobittest.appspot.com/
It might be an error on my part, although that error didn't appear to trigger any logs, I will have to look into that issue, as someone else has already mentioned something similar. I'm sorry for the inconvenience.
Uh... I'm not exactly sure what happened here. It seems I found a key, but there was a db error or something.
http://pastebin.com/K4zZvXz6
I checked that private key and it wasn't 1room77. What the hell happened?
http://pastebin.com/K4zZvXz6
I checked that private key and it wasn't 1room77. What the hell happened?
Correct me if I'm wrong, but when I'm using the miner with this pool, its technically mining for every vanity address at once correct?
BTC (per) Mkey (per) Hour
So...
Say you generate 60Mkey/s...
If the BTC/MkeyHr was 0.005, then you'd make (theoretically, its based on luck) 0.005BTC * 60 every hour.
Yep, just tried out the client for the first time and I see "Value: 0.000022 BTC/MkeyHr," and it picked that over all the other work. What's with the "Hr?"
BTC (per) Mkey (per) Hour
So...
Say you generate 60Mkey/s...
If the BTC/MkeyHr was 0.005, then you'd make (theoretically, its based on luck) 0.005BTC * 60 every hour.
That would just be BTC/hr, and it would be based on your key generation rate. A more sensible value to quote would be just BTC/Mkey. I get the feeling that this is in fact what is shown in the SW, although I haven't looked closely at it yet. On the other hand, there is no reason it couldn't just show BTC/hr in the SW since it knows your keyrate. (Aside: is that the correct term here? Did I just coin that?
)Anyway, it would be really cool if the current expected BTC/Mkey was shown in big letters at the top of the pool page. Even better, make that available through an API, so a clever mining software could decide at any given time which task would be more profitable, mining bitcoins or mining addresses. It would be a simple calculation knowing your hardware and the current bitcoin difficulty.
Correct me if I'm wrong, but when I'm using the miner with this pool, its technically mining for every vanity address at once correct?
You're mining for all the keys that share the public key connected with the biggest total reward/difficulty ratio sum, or so I heard. Generally, you're maximizing your profits with the oclvanityminer.
Isn't what counts the sum total of bounties that are offered by any one public key, it would be worth trying for a low probability say 9 digit after the 1 vanity if there were sufficient potential reward by the same PUB in 8's to 6's?
Oh yeah, this makes it even more complicated. It's an interesting puzzle...
indeed, firstbits: 1puzzle = 1PUZZLESWrLbh5HTdMFY7y1tintsxQtWmL solved here earlier today
Jump to: