Vanity Pool - vanity address generator pool

[Tittiez]

Bump again, seems when I bumped the thread more work showed up. NOT COMPLAINING

[1714120449]

1714120449

[1714120449]

1714120449

[1714120449]

1714120449

[Red Emerald]

This sounds like a good use of GPU hashing power now that difficulty is growing ever higher.

[fizzisist]

How is work priced? Is it whatever the submitter feels like paying?

[ThePiachu]

How is work priced? Is it whatever the submitter feels like paying?

At the moment, yes, with a minimum of 0.1BTC. I am looking into making more sensible prices for higher-end addresses.

[Otoh]

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?

[fizzisist]

Each pattern has a sort of difficulty, right? It would make sense to show this on the work list, and sort the list by reward/difficulty. This would make the marketplace more efficient, I think.

Or is this how work is decided on by the client already?

[fizzisist]

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...

[fizzisist]

Each pattern has a sort of difficulty, right? It would make sense to show this on the work list, and sort the list by reward/difficulty. This would make the marketplace more efficient, I think.

Or is this how work is decided on by the client already?

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?"

[Tittiez]

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?

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.

[Otoh]

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

[ThePiachu]

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.

[fizzisist]

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?

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.

[Tittiez]

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?

[ThePiachu]

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?

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.

[cambda]

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?

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

[LockoutNex]

On the solved work page can you make it so it displays the date it was solved and the address that solved it?

[ThePiachu]

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?

[fizzisist]

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:

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).

[fizzisist]

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!

[ThePiachu]

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.