Vanity Pool - vanity address generator pool - page 13.

Dare

hero member

Activity: 508

Merit: 500

Techwolf on #bitcoin and Reddit

I guess I was right then, you can only search for addresses from one public key at a time. I just didn't notice there were multiple requests with the same key in the pool! Tongue

I'm using vanitygen and not oclvanityminer, so I never noticed before. I should be getting a GPU with more MH/s than my CPU soon, though. (No, it's not integrated, it's just a dedicated card that's ~5 years old. Oclvanityminer tends to crash because there are only ~5-10 threads available for it to use, if that.)

Todamont

sr. member

Activity: 606

Merit: 273

Yes, oclvanityminer should do all of this automatically...

ThePiachu

sr. member

Activity: 444

Merit: 313

Quote from: Todamont on October 31, 2013, 06:54:59 PM

Anyone? I guess I can start looking at the source...

When you mine for an address, you take a public key and generate a random private-public keypair associated with it. The resulting address will be a valid vanity address for ALL patterns that use the same public key. So after you generate the address, check it against all patterns of that public key and see if any matches. If they do, submit your solution to that work, otherwise generate a new key.

Of course, you need to abide by the standard vanity address generation algorithms when creating the keypair.

Todamont

sr. member

Activity: 606

Merit: 273

Anyone? I guess I can start looking at the source...

Otoh

donator

Activity: 3108

Merit: 1166

Quote from: Todamont on October 31, 2013, 05:58:18 PM

Otoh, can you explain how I would mine these 11 requests simultaneously? Are you using oclvanityminer, or vanitygen, and what is the command-line string?

Sorry, I have no idea, I just request these, that's my public key.

Todamont

sr. member

Activity: 606

Merit: 273

Otoh, can you explain how I would mine these 11 requests simultaneously? Are you using oclvanityminer, or vanitygen, and what is the command-line string?

Otoh

donator

Activity: 3108

Merit: 1166

You can search at the same time for any patterns that have been requested with the same public key, for instance the one that starts 04C13D9C... has 11 requests in atm https://vanitypool.appspot.com/availableWork

Dare

hero member

Activity: 508

Merit: 500

Techwolf on #bitcoin and Reddit

Quote from: ThePiachu on October 30, 2013, 10:06:58 PM

Quote from: Todamont on October 30, 2013, 10:05:49 PM

Well if "TioKiko" is the most profitable reward to mine for right now, it's 17.8 days at 23.5 Mkey/s for a 0.04btc reward, so that's a far cry from being profitable on electricity. If there is a way to search for more than one key at a time, I haven't figured it out, but I would love some instruction from anybody out there.

It should be done automatically by the miner.

How does that work? Since each address has a different partial private key, wouldn't it only be possible to search for one (or multiple with the same key) at a time?

ThePiachu

sr. member

Activity: 444

Merit: 313

Quote from: Todamont on October 30, 2013, 10:05:49 PM

Well if "TioKiko" is the most profitable reward to mine for right now, it's 17.8 days at 23.5 Mkey/s for a 0.04btc reward, so that's a far cry from being profitable on electricity. If there is a way to search for more than one key at a time, I haven't figured it out, but I would love some instruction from anybody out there.

It should be done automatically by the miner.

Todamont

sr. member

Activity: 606

Merit: 273

Well if "TioKiko" is the most profitable reward to mine for right now, it's 17.8 days at 23.5 Mkey/s for a 0.04btc reward, so that's a far cry from being profitable on electricity. If there is a way to search for more than one key at a time, I haven't figured it out, but I would love some instruction from anybody out there.

integrity42

full member

Activity: 476

Merit: 100

Right. I think it would make sense to compare it to LTC, since its the most widely mined coin with GPUs.

ThePiachu

sr. member

Activity: 444

Merit: 313

Quote from: integrity42 on October 29, 2013, 08:48:34 PM

According to the bottom chart on http://fizzisist.com/mining-value/ , the mining ratio is 3

But according to vanitypoool.appspot.com , the mining ratio is 41.

Which is correct?

Thanks.

It probably depends how you calculate it. On Vanity Pool website it's quite optimistic, saying that if you could mine for all addresses at once using sum algorithm you would get this ratio. I don't think that's how miners do it, they generally focus on one most profitable address (or set of addresses) and mine that.

Moreover, with the ASICs entering the picture that metric is skewed again, since Bitcoin's difficulty is not representative of what a GPU miner could earn by mining alt-coins for example. I will have to update that part of the pool at some point to be more coin-independent.

At any rate, it's best to calculate this yourself, since you will know exactly how your hardware performs (on those websites that performance is guesstimated based on a few GPUs that were measured).

integrity42

full member

Activity: 476

Merit: 100

According to the bottom chart on http://fizzisist.com/mining-value/ , the mining ratio is 3

But according to vanitypoool.appspot.com , the mining ratio is 41.

Which is correct?

Thanks.

ThePiachu

sr. member

Activity: 444

Merit: 313

It is possible that the way the Pool calculates how profitable a work is and the way vanitygen calculates it is different.

I know that sometimes we have to look at the sum of the profitability of all work for a given public key - if one person requests a few addresses searching for them is often more profitable since you have many different solutions to go for with the same calculations.

Quote from: Todamont on October 27, 2013, 09:26:44 PM

Hi, I'm just starting out with vanity mining, seeing if it might still put this old ATI 5850 to good use. So I'm using this command to run the miner:

./oclvanityminer -D 0:1,grid=1024x1024 -u https://vanitypool.appspot.com/ -a 1mybitcoinpublickey

I with -a 1mybitcoinpublickey you should use address instead, but otherwise it appears to be correct Wink

.

Todamont

sr. member

Activity: 606

Merit: 273

Hmmm. "1ZhouTong" has a lavishness at 1.5e-5 and a reward of 0.48btc. So higher lavishness and higher reward than "1TioKiko". Maybe I'm missing something...

Dare

hero member

Activity: 508

Merit: 500

Techwolf on #bitcoin and Reddit

Quote from: Todamont on October 27, 2013, 09:26:44 PM

Hi, I'm just starting out with vanity mining, seeing if it might still put this old ATI 5850 to good use. So I'm using this command to run the miner:

./oclvanityminer -D 0:1,grid=1024x1024 -u https://vanitypool.appspot.com/ -a 1mybitcoinpublickey

I see this:

Searching for pattern: "1TioKiko" Reward: 0.040000 Value: 0.000001 BTC/Gkey
Difficulty: 51529903411245
Total value for current work: 0.000001 BTC/Gkey
[23.62 Mkey/s][total 10195304448][Prob 0.0%][50% in 17.5d]

I understand, it can only search for one of the rewards at a time, and it has chose to try to find the reward for the "1TioKiko" address. I see from https://vanitypool.appspot.com/availableWork that the lavishness of this reward is 3.3e-06 for a 0.04btc reward. However, I also see the reward for "1Wednesday" is 0.08 and it only has a lavishness of 4.6e-08, much lower than "1TioKiko".

So has it chosen a non-optimal reward to mine for here? Can someone offer advice on the best practise for using a mining software, currently. I still haven't figured out what I'm supposed to do with the "compressed keys" update. Piachu, can you give me some guidance here?

Higher lavishness is better, I believe. "1Wednesday" will take MUCH longer to solve than "1TioKiko", so you will get a higher reward (counting power and time cost) from the easier prefix. The exact formula for it is in the FAQ.

No clue about the compressed keys, though.

Todamont

sr. member

Activity: 606

Merit: 273

Hi, I'm just starting out with vanity mining, seeing if it might still put this old ATI 5850 to good use. So I'm using this command to run the miner:

./oclvanityminer -D 0:1,grid=1024x1024 -u https://vanitypool.appspot.com/ -a 1mybitcoinpublickey

I see this:

Searching for pattern: "1TioKiko" Reward: 0.040000 Value: 0.000001 BTC/Gkey
Difficulty: 51529903411245
Total value for current work: 0.000001 BTC/Gkey
[23.62 Mkey/s][total 10195304448][Prob 0.0%][50% in 17.5d]

I understand, it can only search for one of the rewards at a time, and it has chose to try to find the reward for the "1TioKiko" address. I see from https://vanitypool.appspot.com/availableWork that the lavishness of this reward is 3.3e-06 for a 0.04btc reward. However, I also see the reward for "1Wednesday" is 0.08 and it only has a lavishness of 4.6e-08, much lower than "1TioKiko".

So has it chosen a non-optimal reward to mine for here? Can someone offer advice on the best practise for using a mining software, currently. I still haven't figured out what I'm supposed to do with the "compressed keys" update. Piachu, can you give me some guidance here?

muddafudda

legendary