Vanity Pool - vanity address generator pool

[ThePiachu]

I see I've gotten a collection of rejections this morning, https://vanitypool.appspot.com/solveWork?key=1stDECx%3A04C13D9CF2B0E382A4AF29C5E2B97F85C6DD9445F7DCE82CD7207E6FC4716511981B0012C10B39EF152257A8407A2965F92F075379D311D5786D9421795B82D01C&privateKey=47F54EE114C935B1920EE833CFE90AD12A86D0C0A40A046C561C6517AA656893&bitcoinAddress=1PkdeXKsdPe5vEA3oTSv8HgCncfJxPqFab and https://vanitypool.appspot.com/solveWork?key=1SToctX%3A04C13D9CF2B0E382A4AF29C5E2B97F85C6DD9445F7DCE82CD7207E6FC4716511981B0012C10B39EF152257A8407A2965F92F075379D311D5786D9421795B82D01C&privateKey=7E1D24DC0117902661A37AC9E57E054D7FE76B5421894F6FA73EE080568A2EDE&bitcoinAddress=15y2xFg4eBNSrrKZmsgnXzet8TZSzCgsr4 most recently.  The math checks out doing it manually so I'm guessing it doesn't like the compressed solutions.

Yeah, the Pool accepts hex encoded solutions, not base58. I might add that feature in the next version.

Many of my bounties solved today, many thanks, just one that is reported solved but when I try to sum it to get the address & private key nothing happens - the page just goes blank??

F152257A8407A2965F92F075379D311D5786D9421795B82D01C">https://vanitypool.appspot.com/checkSolved?key=1PepsiCo:04C13D9CF2B0E382A4AF29C5E2B97F85C6DD9445F7DCE82CD7207E6FC4716511981B0012C10B39E F152257A8407A2965F92F075379D311D5786D9421795B82D01C

Any help appreciated

F152257A8407A2965F92F075379D311D5786D9421795B82D01C">https://vanitypool.appspot.com/checkSolved?key=1PepsiCo:04C13D9CF2B0E382A4AF29C5E2B97F85C6DD9445F7DCE82CD7207E6FC4716511981B0012C10B39E F152257A8407A2965F92F075379D311D5786D9421795B82D01C

The website appears to be working for me. However, my gobit test suite appears to be having some problems, as the private key

4876652DE4D45277999C7C02C5E8EB0CEF7A512CB4AE7EF51A85ED2D1996A629

encodes into

049322AA20CA83131F635C7ACBB05484E3FEDEAC699DF6FF34AEFDFEFEF4EEFFAEC10A698CC2DF6 DD9A9B95175C7C4416132F03771C21EC9DFF824FA5F7630B5

which appears to be one byte short for some odd reason...

[1714625259]

1714625259

[1714625259]

1714625259

[1714625259]

1714625259

[1714625259]

1714625259

[1714625259]

1714625259

[deeplink]

ThePiachu, do you have any connection to the following website: http://www.haagediss.com

If not, I would like to let you know that someone is misusing your name.

[ThePiachu]

ThePiachu, do you have any connection to the following website: http://www.haagediss.com

If not, I would like to let you know that someone is misusing your name.

Thanks for your concern. I have been developing various solutions for this person over the course of a couple months. The server side of this website was one of those. The frontend was done by him, as was the idea.

[mskwik]

I see I've gotten a collection of rejections this morning, https://vanitypool.appspot.com/solveWork?key=1stDECx%3A04C13D9CF2B0E382A4AF29C5E2B97F85C6DD9445F7DCE82CD7207E6FC4716511981B0012C10B39EF152257A8407A2965F92F075379D311D5786D9421795B82D01C&privateKey=47F54EE114C935B1920EE833CFE90AD12A86D0C0A40A046C561C6517AA656893&bitcoinAddress=1PkdeXKsdPe5vEA3oTSv8HgCncfJxPqFab and https://vanitypool.appspot.com/solveWork?key=1SToctX%3A04C13D9CF2B0E382A4AF29C5E2B97F85C6DD9445F7DCE82CD7207E6FC4716511981B0012C10B39EF152257A8407A2965F92F075379D311D5786D9421795B82D01C&privateKey=7E1D24DC0117902661A37AC9E57E054D7FE76B5421894F6FA73EE080568A2EDE&bitcoinAddress=15y2xFg4eBNSrrKZmsgnXzet8TZSzCgsr4 most recently.  The math checks out doing it manually so I'm guessing it doesn't like the compressed solutions.

Yeah, the Pool accepts hex encoded solutions, not base58. I might add that feature in the next version.

It's not base58, it's the compressed address format that the bitcoin client started using in v0.6.  Been working on improving vanitygen performance and added compressed support to vanitypool.thruhere.net for testing but promptly solved all the remaining work there.  Seems you can improve the hash rate by 80-90% pretty easily by checking the compressed addresses as well but it effectively cuts all the bounties here in half if half the solutions get rejected.

[ThePiachu]

It's not base58, it's the compressed address format that the bitcoin client started using in v0.6.  Been working on improving vanitygen performance and added compressed support to vanitypool.thruhere.net for testing but promptly solved all the remaining work there.  Seems you can improve the hash rate by 80-90% pretty easily by checking the compressed addresses as well but it effectively cuts all the bounties here in half if half the solutions get rejected.

Hmm, sounds promising. Can you point me to some specification of that format, so I can try implementing it?

[mskwik]

Hmm, sounds promising. Can you point me to some specification of that format, so I can try implementing it?

https://en.bitcoin.it/wiki/Protocol_specification#Signatures gives the public key format.
https://www.bitaddress.org/ will give both uncompressed and compressed addresses on the wallet details tab (that's what I've been using to double-check my results)

[mskwik]

Also note that the sign was in fact wrong on one of those solutions that I posted the other day, I updated the post to have another correct example so they should be safe to check against.

[Otoh]

seems to be broken atm, I've received notification of another 2 solved but they don't work to retrieve the solution??

[ThePiachu]

seems to be broken atm, I've received notification of another 2 solved but they don't work to retrieve the solution??

Hmm, so you have received confirmation emails, but the solutions are not present on the pool?

[Otoh]

opps, sorry I messed up, they are all fine - my mistake, just the 1PepsiCo one that is shown solved but the solution doesn't work, could you reenter it to be solved again, many thanks.

[ThePiachu]

opps, sorry I messed up, they are all fine - my mistake, just the 1PepsiCo one that is shown solved but the solution doesn't work, could you reenter it to be solved again, many thanks.

Actually, the solution works, it's just that my GoBitTest website appears to have some problems with it. Given the private key:
4876652DE4D45277999C7C02C5E8EB0CEF7A512CB4AE7EF51A85ED2D1996A629

it prints:
049322AA20CA83131F635C7ACBB05484E3FEDEAC699DF6FF34AEFDFEFEF4EEFFAEC10A698CC2DF6 DD9A9B95175C7C4416132F03771C21EC9DFF824FA5F7630B5

Using https://www.bitaddress.org/ we get:
049322AA20CA83131F635C7ACBB05484E3FEDEAC699DF6FF34AEFDFEFEF4EEFFAE00C10A698CC2DF6DD9A9B95175C7C4416132F03771C21EC9DFF824FA5F7630B5

So my test suite doesn't print that first zero byte for one of the points. I will look into fixing it soon.

Adding your public key, we get the solution of:
1PepsiCosowjScTRFjSUvpgnEeEfC5Xbi

Sorry about the inconvenience.

[Otoh]

Ah thanks, but how can I add the 2 private keys together to get the one for 1PepsiCosowjScTRFjSUvpgnEeEfC5Xbi

Edit - Ah I see that you'll said you would fix that on your site, np & no rush, I'll do it then

[ThePiachu]

Ah thanks, but how can I add the 2 private keys together to get the one for 1PepsiCosowjScTRFjSUvpgnEeEfC5Xbi

Edit - Ah I see that you'll said you would fix that on your site, np & no rush, I'll do it then

I think that if you add the private keys, it should work fine. The problem only appears to affect that public key at the moment. If you combine the private keys, you should get a proper private key you can import and so forth.

[Otoh]

Ah thanks, but how can I add the 2 private keys together to get the one for 1PepsiCosowjScTRFjSUvpgnEeEfC5Xbi

Edit - Ah I see that you'll said you would fix that on your site, np & no rush, I'll do it then

I think that if you add the private keys, it should work fine. The problem only appears to affect that public key at the moment. If you combine the private keys, you should get a proper private key you can import and so forth.

Nope, it just goes to a blank page atm like it's stuck or something

[Syke]

Nope, it just goes to a blank page atm like it's stuck or something

Wow, that's the most annoying sig I've seen. Welcome to /ignore.

[Otoh]

Nope, it just goes to a blank page atm like it's stuck or something

Wow, that's the most annoying sig I've seen. Welcome to /ignore.

LOL - BFL paid me to pimp them in my sig, I hoped to get a balance between getting attention for them & being annoying, obviously it's a fine line & I'm sorry that you've found it annoying, as it happens their last month's rental of my sig space ran out a few days ago & as I don't post every day on the forums as they require I doubt that they will offer to pay me to continue advertising for them so I expect that the sig will revert to something less in your face very soon, I am a big fan of BFL btw which is why I was happy to promote them.

[ThePiachu]

Nope, it just goes to a blank page atm like it's stuck or something

Hmm, I have updated the testing site to properly pad public keys. I hope that will solve your problem as well.

[Otoh]

it doesn't go to a blank page now but instead reports: Private keys are invalid

[ThePiachu]

it doesn't go to a blank page now but instead reports: Private keys are invalid

Hmm, that is strange. I've added more clearer error message displays to the test suite to indicate which private key would be invalid. I spent some time analysing the code, and it appears to be working fine. It takes private keys from 1 to FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140, and the error you experienced is only displayed if the key is bigger than the latter number, or smaller than 1. In other words, it shouldn't be happening, as I've tried out the solution in the testing suite (it works fine), and I reckon you have also previously used your private key with success. If the testing suite acts up still, let me know which key is to blame - the solution, or yours (it will be displayed).

Alternatively, you can use https://www.bitaddress.org/ , as its Vanity Address option uses the additive method.

[Otoh]

Many thanks, it's now working fine & I have the sum, sorry it was late at night when I tried before & for some reason I had an incorrect 2nd private key - now I rechecked & it's all fine, my apologies for the extra work & my thanks to the solvers - especially whoever just solved the hardest to date with 9 chars after the initial 1 & claimed the highest bounty paid out so far (though it wasn't much considering the difficulty unless one was very lucky).

1ELiZABETH for 3.18 btc before commission ---> 2.544 btc.