Vanity Pool - vanity address generator pool

[ThePiachu]

Someone submitted an unsolvable Litecoin address a day or two ago (LGWL). I'm not sure how you usually handle these, but it should probably be removed from the list.

Thanks for the info. I contacted the person requesting it and cancelled the work.

[1713587593]

1713587593

[1713587593]

1713587593

[1713587593]

1713587593

[TwinWinNerD]

bump.

can someone mine for:

1ntemet   14njY4iedorRZzMw6UE7YgDGUVccAA4mEG    04801414...   0.0248   0.00012

kthx (good money ratio )

[klondike_bar]

How would i request:    1klondike......  ?

[Otoh]

How would i request:    1klondike......  ?

by going to: https://vanitypool.appspot.com/newWork

& small case L is not possible, or upper case i or o so all caps isn't an option either, maybe 1KLoNDike or 1KLoNDiKE or 1kLondike - none of them really look right to me though.

[klondike_bar]

How would i request:    1klondike......  ?

by going to: https://vanitypool.appspot.com/newWork

& small case L is not possible, or upper case i or o so all caps isn't an option either, maybe 1KLoNDike or 1KLoNDiKE or 1kLondike - none of them really look right to me though.

ahh, thanks for the heads up. I tried the site, but keep getting told my public key is too short. i tried with 2 different 'receiving addresses', should i be grabbing my key from elsewhere?

[Otoh]

I think that I had trouble working all this out too, if you check my earlier posts here it may help, unfortunately I don't remember how it got worked out maybe someone more knowledgeable will help explain, from the FAQ you need an ECDSA public key which isn't the same as a Bitcoin address public key as it's made from a key pair using one you already have, the info on how to generate one & it's private key is somewhere but I don't see where to find it atm - maybe check the OP & the van gen faq or back posts here.

[blub]

Does this site work with compressed or uncompressed public keys?

For the miner it would be sufficient to use a counter as private key as the security of the resulting key has to lie entirely in the private key of the requesting party?

[ThePiachu]

Does this site work with compressed or uncompressed public keys?

For the miner it would be sufficient to use a counter as private key as the security of the resulting key has to lie entirely in the private key of the requesting party?

This site works with uncompressed keys.

Yes, the security of the key lies in the private key of the person making the request.

[ThePiachu]

Vanity Pool is currently undergoing a big update. We are moving form BitcoinQT to Blockchain.info for our wallet services to speed things up. If anyone has unpaid work that they wish to be publicly available on the Pool, please check your work URL for the newest address.

[wtfvanity]

Vanity Pool is currently undergoing a big update. We are moving form BitcoinQT to Blockchain.info for our wallet services to speed things up. If anyone has unpaid work that they wish to be publicly available on the Pool, please check your work URL for the newest address.

How long will the transition take?

[ThePiachu]

Vanity Pool is currently undergoing a big update. We are moving form BitcoinQT to Blockchain.info for our wallet services to speed things up. If anyone has unpaid work that they wish to be publicly available on the Pool, please check your work URL for the newest address.

How long will the transition take?

Updating the data took about 5 minutes. After that I gave the transaction that credited the new addresses some time to confirm, but decided to make the site live for the miners before we got a full confirmation. So the website was down for about 20 minutes I think, and after that it was on but might not be able to pay out for another hour or two. As I checked nobody tried to claim a reward before we got a confirmation, so everything worked out fine.

[ThePiachu]

This has been a long-requested feature. Vanity Pool is now supporting compressed key solutions. To check all possible solutions for your pair of keys, please visit:

http://gobittest.appspot.com/VanityAll

(be sure to use https for extra safety as needed)

We eventually will be also phasing out additive solutions from our pool for extra safety. This change will take place once new mining software is available - so please keep an eye out for future updates.

We also did some minor improvements on the payment logic to avoid some small issues we noticed on the testing environment.

[ThePiachu]

And a new update for the Pool - we now do more detailed checks for whether a work is solvable, meaning that there shouldn't be any more unsolvable work in the Pool.

[Dare]

And a new update for the Pool - we now do more detailed checks for whether a work is solvable, meaning that there shouldn't be any more unsolvable work in the Pool.

Awesome! Now I won't be bugging you about the unsolvable stuff. 

[bernard75]

Either i have been extremely lucky or this really helped a lot, i hit an 8 chars today. 

[ThePiachu]

Either i have been extremely lucky or this really helped a lot, i hit an 8 chars today. 

Congrats!

[bernard75]

And thanks for the ticker!

[muddafudda]

Either i have been extremely lucky or this really helped a lot, i hit an 8 chars today. 

Congrats!

Awesome stuff

[Todamont]

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?

[Dare]

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.