Okay, you have the user's private and public key - PRIV and PUB. The user submits PUB to the Vanity Pool, and some miner starts crunching the numbers. There are two methods they can use:
The multiplication method - the miner takes PUB and uses that as the generation point of the ECDSA curve (instead of G specified by the curve). If they find the private key that matches (MPRIV), they submit it and the user can obtain their final private key by multiplying PRIV and MPRIV, with appropriate modulo operations.
The addition method - the miner generates a key pair as normal, using point G. Obtaining the public key, add it to the PUB and see if the result is good. If so, the user obtains their final private key by adding PRIV and MPRIV with modulo operations.
You can find out more here:
http://bitcoin.stackexchange.com/q/3853/323
https://bitcointalksearch.org/topic/m.901491
Topic: Vanity Pool - vanity address generator pool - page 32. (Read 147800 times)
No.. Please explain further..
Hmm, looks promising. However, you do know that there are two ways to generate split-key vanity addresses? There is the version that requires multiplication of private keys, and one that uses addition. The latter is (most likely) less effective for generating the keys, but can still be used.
Have created version of bit address that makes the key stuff in the Vanity Pool easier.
See:
http://bitcoinstatus.rowit.co.uk/other/address.html
Advantages are the private keys never leave your browser. It is all done locally in javascript.
Any comments and will update and then submit patch to bitaddress.org to get into master version.
I have a little extra time on my hands and I code for a living. I'm an old man, I know most languages well. I could maybe attempt a true pool where users work towards a common goal and take a proportion of the reward.
The Vanity Pool server is written in Go and runs on Google App Engine. I generally don't find a lot of people that write in Go. And as I mentioned earlier - the website doesn't yet get enough traffic to warrant a full pool solution :\.I have a serious question / concern.
How can we do this without the generator miners/server knowing the private key. Assuming a "trust no one" mentality the end user should be the only one with the private key.
How can we do this without the generator miners/server knowing the private key. Assuming a "trust no one" mentality the end user should be the only one with the private key.
Well, you can check out my testing suite:
http://gobittest.appspot.com/
and see that it can be done. There is also this topic on StackExchange:
http://bitcoin.stackexchange.com/q/3853/323
Not to mention that the Vanity Pool itself never asks the payer for their private key. The wonders of ECDSA key math
.
Code to do the offline EC maths is all in:
https://www.bitaddress.org
Just need to tweak it.
Will try later to see if I can get it to work!
Ideally should be added as a tab to the existing page.
https://www.bitaddress.org
Just need to tweak it.
Will try later to see if I can get it to work!
Ideally should be added as a tab to the existing page.
Okay, a quick update to the site:
I have a little extra time on my hands and I code for a living. I'm an old man, I know most languages well. I could maybe attempt a true pool where users work towards a common goal and take a proportion of the reward.
I have a serious question / concern.
How can we do this without the generator miners/server knowing the private key. Assuming a "trust no one" mentality the end user should be the only one with the private key.
Okay, a quick update to the site:
As currently our bitcoind is catching up to the network after an update to v0.7 that appears to have wiped some block history, the website might be a bit iffy.
- The rewards should be displaying with the fees already deducted - what you see is what you get
- Added some simple notification display for the website status and so forth
As currently our bitcoind is catching up to the network after an update to v0.7 that appears to have wiped some block history, the website might be a bit iffy.
Yeah, I should take out the fees. Sorry that I haven't gotten to it yet, but I've been working on a couple other projects (https://bitcointalksearch.org/topic/furstore-bitcoin-powered-digital-store-on-google-app-engine-110241 and some others that might be revealed soon by the person that commissioned me) and just started a new job.
As for spent and not spent work - they are clearly divided. The "Bitcoin address" is a donation address, so even if someone forgets what address they were supposed to pay, or perhaps want to increase the reward later on, they would be able to do so. Sorry about this confusion as well.
I'm glad you enjoy the pool. I'm hoping that some other project would find it useful and some larger cooperation could be established to benefit both of them;).
As for spent and not spent work - they are clearly divided. The "Bitcoin address" is a donation address, so even if someone forgets what address they were supposed to pay, or perhaps want to increase the reward later on, they would be able to do so. Sorry about this confusion as well.
I'm glad you enjoy the pool. I'm hoping that some other project would find it useful and some larger cooperation could be established to benefit both of them;).
On the available work, it should be noted you take 20% out of the reward published. One can assume he gets the full amount and then he will be dissapointed.
1Satoshi and its bitcoin adress 13Kc5GkEn7KZhtvN6NJw7PHHoQpopUWTyS
its already spent!
When you look at solved work,
1satoshi and its bitcoin adress 1EbuVAwRmXLLJr8w4F79B9ao9Maq4EuKrn
its not spent. I mean you have to change the bitcoin addresses
I like your Vanity Pool, it has potential for offline computers or when Bitcoin difficulty skyrockets !
1Satoshi and its bitcoin adress 13Kc5GkEn7KZhtvN6NJw7PHHoQpopUWTyS
its already spent!
When you look at solved work,
1satoshi and its bitcoin adress 1EbuVAwRmXLLJr8w4F79B9ao9Maq4EuKrn
its not spent. I mean you have to change the bitcoin addresses
I like your Vanity Pool, it has potential for offline computers or when Bitcoin difficulty skyrockets !
legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
To be honest, I already had thought of a Vanity pool concept last year around this time, trouble was that I had no idea how it would work. Back then I was not familiar with public-key cryptography much less that you can add them or multiply them.
.
Perhaps calculate the difficulty of the pattern like in VanityGen and using some formula to calculate the fee for finding it.
1. provide instructions for generating EDCSA key pairs.
Sure, I`ll try doing that with the next update. 2. realistic bounties based on difficulty.
Yeah, I`ll probably have to do something about it. So far "pay what you want" has turned out to be "pay minimum amount".Question: Have you received enough interest in your project to warrant a move from a bounty system to a true pool system where everyone in the pool is working to generate a vanity address and then shares in the profit? The bounty method seems incredibly wasteful.
Not yet. So far the interest has been slim. But yeah, once the site gets popular I`ll probably have to move into the traditional pool system. For now, I`m just keeping it simple.I like your project enough that I've sent you a very small donation. I hope this develops into something the community can use as a viable income resource in the future.
Thank you for your donation. I also hope more people become interested in the project. Perhaps some hybrid between a vanity address and a Bitcoin debit card would do the trick...
Well, that`s another problem - there isn`t enough data on key mining efficiency vs normal mining for almost any GPU. This could make such judgement calls a bit imprecise.
I've implemented a sort of "mining pool" for creating vanity addresses with zero needed trust
This is a cool idea.
I have a question and 2 suggestions.
suggestions:
1. provide instructions for generating EDCSA key pairs.
2. realistic bounties based on difficulty. Obviously .11 BTC bounty for a 9 letter case sensitive vanity address is too small, While I realize this is a test, This address is probably worth something like $500USD in energy usage and wear and tear on hardware. On my macbook pro it's only going to take 1.7 years to reach 50% probability for 1DanieLRH.
Question: Have you received enough interest in your project to warrant a move from a bounty system to a true pool system where everyone in the pool is working to generate a vanity address and then shares in the profit? The bounty method seems incredibly wasteful.
I like your project enough that I've sent you a very small donation. I hope this develops into something the community can use as a viable income resource in the future.
With my Radeon 5830 1DanieLRH would take 23 days, thats not even close to 23 Euro even here in Germany , where electricity is expensive. But i would approve difficulty adjusted rewards.
1. provide instructions for generating EDCSA key pairs.
Sure, I`ll try doing that with the next update. 2. realistic bounties based on difficulty.
Yeah, I`ll probably have to do something about it. So far "pay what you want" has turned out to be "pay minimum amount".Question: Have you received enough interest in your project to warrant a move from a bounty system to a true pool system where everyone in the pool is working to generate a vanity address and then shares in the profit? The bounty method seems incredibly wasteful.
Not yet. So far the interest has been slim. But yeah, once the site gets popular I`ll probably have to move into the traditional pool system. For now, I`m just keeping it simple.I like your project enough that I've sent you a very small donation. I hope this develops into something the community can use as a viable income resource in the future.
Thank you for your donation. I also hope more people become interested in the project. Perhaps some hybrid between a vanity address and a Bitcoin debit card would do the trick... I've implemented a sort of "mining pool" for creating vanity addresses with zero needed trust
This is a cool idea.
I have a question and 2 suggestions.
suggestions:
1. provide instructions for generating EDCSA key pairs.
2. realistic bounties based on difficulty. Obviously .11 BTC bounty for a 9 letter case sensitive vanity address is too small, While I realize this is a test, This address is probably worth something like $500USD in energy usage and wear and tear on hardware. On my macbook pro it's only going to take 1.7 years to reach 50% probability for 1DanieLRH.
Question: Have you received enough interest in your project to warrant a move from a bounty system to a true pool system where everyone in the pool is working to generate a vanity address and then shares in the profit? The bounty method seems incredibly wasteful.
I like your project enough that I've sent you a very small donation. I hope this develops into something the community can use as a viable income resource in the future.
Overall i guess the rewards are too low, i mean electricity costs are higher than 0.1 BTC for estimated 20 Days with 20Mhash, so there is no point in mining them at the moment.
If someone wants some nice firstbits without much hassle , i think he has to pay a bit more than a dollar ;-)
If someone wants some nice firstbits without much hassle , i think he has to pay a bit more than a dollar ;-)
Well, yeah, that`s what one gets for setting a low threshold for minimum fees. Oh well, maybe Bitcoin`s price will get higher and those 0.1BTCs will be worth something then...
Overall i guess the rewards are too low, i mean electricity costs are higher than 0.1 BTC for estimated 20 Days with 20Mhash, so there is no point in mining them at the moment.
If someone wants some nice firstbits without much hassle , i think he has to pay a bit more than a dollar ;-)
If someone wants some nice firstbits without much hassle , i think he has to pay a bit more than a dollar ;-)
It will also group together bounties by public key. When the 1Satoshi and 1satoshi bounties were both present, because they had the same public key, they would go into the same pattern set and would be searched for simultaneously. Also, when dealing with bounties with the same public key, the aggregate reward/difficulty is used for decision making. This would cause it to choose those two bounties together over the 1DaneiLRH bounty, if it were present.
Hmm, a pretty neat and smart thing to do with the aggregation of the public keys.
You mean for the -a parameter? It should accept a testnet address there. Did it not accept one for you? It is supposed to validate that what you enter for the -a parameter is a valid address of some sort, but it won't enforce a specific address type.
I suppose it didn't work last time I checked, but then again it might be just some hiccup on my computer.
Quote
So, unless someone else has some objections, I`ll send you the Bitcoins soon. What address would you like to receive them with? 1samr7UZxtC6MEAFHqr1h3Kq453xJJbe4 ?
That's the right address.
So, I`ve sent the bounty in this transaction:
http://blockexplorer.com/tx/40800a9f0c708295c03338d559ca6011efc2828ea9ab44f2aae8e4f46bcd317e#o1
The total comes up to 12 Bitcoins, as there was a 2 Bitcoin donation to the bounty early on (http://blockexplorer.com/address/1Cuw26gA2nhuqjBELwL6QGG89RsqfaV3v8).
Ideas looking forward
It's possible to make vanity address mining much like regular bitcoin mining, in the sense of tracking the total work completed by each participant, and possibly distributing rewards to all participants rather than just the finder. The idea would be, if somebody wants 1DanieLRH, post the bounty for 1Danie, and keep track of how many addresses each miner returns. Eventually, a matching address will come back, and all of the partial matches will make it possible to determine the division of compute resources.
It also wouldn't hurt if the pool posted the portion of the bounty that will go to whoever solves it, rather than the amount paid by the customer. It's a letdown to see a bounty for 0.1 BTC, and only receive 0.08 on completion.
It's possible to make vanity address mining much like regular bitcoin mining, in the sense of tracking the total work completed by each participant, and possibly distributing rewards to all participants rather than just the finder. The idea would be, if somebody wants 1DanieLRH, post the bounty for 1Danie, and keep track of how many addresses each miner returns. Eventually, a matching address will come back, and all of the partial matches will make it possible to determine the division of compute resources.
It also wouldn't hurt if the pool posted the portion of the bounty that will go to whoever solves it, rather than the amount paid by the customer. It's a letdown to see a bounty for 0.1 BTC, and only receive 0.08 on completion.
I suppose the partial rewards would be possible, but could tax the pool a bit too much. It is running on Google App Engine which charges for each read/write operation. I guess if there is enough demand I can look into that.
And with the reward, yes, I suppose it would be more "human friendly" to display the actual reward that will be given to people. Sometimes being a programmer one forgets about the human aspect of things
.
Ideas looking forward
It's possible to make vanity address mining much like regular bitcoin mining, in the sense of tracking the total work completed by each participant, and possibly distributing rewards to all participants rather than just the finder. The idea would be, if somebody wants 1DanieLRH, post the bounty for 1Danie, and keep track of how many addresses each miner returns. Eventually, a matching address will come back, and all of the partial matches will make it possible to determine the division of compute resources.
It also wouldn't hurt if the pool posted the portion of the bounty that will go to whoever solves it, rather than the amount paid by the customer. It's a letdown to see a bounty for 0.1 BTC, and only receive 0.08 on completion.
It's possible to make vanity address mining much like regular bitcoin mining, in the sense of tracking the total work completed by each participant, and possibly distributing rewards to all participants rather than just the finder. The idea would be, if somebody wants 1DanieLRH, post the bounty for 1Danie, and keep track of how many addresses each miner returns. Eventually, a matching address will come back, and all of the partial matches will make it possible to determine the division of compute resources.
It also wouldn't hurt if the pool posted the portion of the bounty that will go to whoever solves it, rather than the amount paid by the customer. It's a letdown to see a bounty for 0.1 BTC, and only receive 0.08 on completion.
Well, I guess everything is in order. It would be nice if you compiled it for the 64-bit Windows, but I don`t know whether it would increase the performance or not. Although The miner appears to work pecularly at times. Currently there are three works available, 1DanieLRH::0:0.100000; 1Satoshi::0:0.100000; 1ThePiachu::0:1.000000;, and instead of working on 1Satoshi, 7 letters, it chooses 1DanieLRH, 8 letters for the same reward. Does it just work on the first available work, or does it prioritise its work/reward ratio?
It does rank bounties by reward/difficulty. Choosing the 8 letter prefix is the best choice here, but not by much:
Code:
$ ./vanitygen 1Satoshi
Difficulty: 51529903411245
...
$ ./vanitygen 1DanieLRH
Difficulty: 50656515217834
It will also group together bounties by public key. When the 1Satoshi and 1satoshi bounties were both present, because they had the same public key, they would go into the same pattern set and would be searched for simultaneously. Also, when dealing with bounties with the same public key, the aggregate reward/difficulty is used for decision making. This would cause it to choose those two bounties together over the 1DaneiLRH bounty, if it were present.
Anyway, expect a new release in the next day or so that has an oclvanityminer64.exe.
Quote
Also a nice feature would be allowing one to specify a TestNet address for the vanitypooltest website, but that`s not really much of an issue.
You mean for the -a parameter? It should accept a testnet address there. Did it not accept one for you? It is supposed to validate that what you enter for the -a parameter is a valid address of some sort, but it won't enforce a specific address type.
Quote
So, unless someone else has some objections, I`ll send you the Bitcoins soon. What address would you like to receive them with? 1samr7UZxtC6MEAFHqr1h3Kq453xJJbe4 ?
That's the right address.
Jump to: