Author

Topic: Vanity/Custom Addresses for TRC/FRC/DVC/BTC - Updated 1/26/2013 (Read 1237 times)

legendary
Activity: 1288
Merit: 1227
Away on an extended break
Public service message:

How can one be certain you won't hold onto the private key?
Never trust that, regardless of the rep and the guarantees.
Use services that do not have access to your privatekeys like:

https://bitcoinvanity.appspot.com/
http://vanitypool.thruhere.net/

Or even better, generate them yourself by using VanityGen.
sr. member
Activity: 294
Merit: 250
***Updated 1/26/2013***

Added:

1ADiEsMANYh1JEK1ztWhZRUuRt9FURLx5c
1BtcDaRTs84zoFqjFZDsDbhLZTa6Tqk3ws
1DeVcoiNtXJ4L4h33sbkuAxLTedo4DNVrq
sr. member
Activity: 294
Merit: 250
You should host the files for this modification somewhere, there are probably a lot of people who would donate BTC for it.

I suppose I should try and take the effort to rebase it off a current vanitygen.  Was kind of hoping to get more familiar with github at some point and do it as a proper branch/pull request for vanitygen but it never really happened and I guess no one else picked it up and ran with it either.

I think it would be an awesome contribution, I'm surprised samr7 hasn't contacted you to make it a part of the distributed package...
full member
Activity: 125
Merit: 100
You should host the files for this modification somewhere, there are probably a lot of people who would donate BTC for it.

I suppose I should try and take the effort to rebase it off a current vanitygen.  Was kind of hoping to get more familiar with github at some point and do it as a proper branch/pull request for vanitygen but it never really happened and I guess no one else picked it up and ran with it either.
sr. member
Activity: 294
Merit: 250
The oclvanitygen I'm currently using checks both the uncompressed and the positive and negative compressed versions of each key it computes.  Since the majority of the processing time is getting the keys to check this results in about 3x the addresses checked for the same amount of processing power.  At some point a while back I posted the .cl file I was using in the vanitygen thread but I never did completely modify oclvanitygen to do the rest of the calculations properly, I just run it in verbose mode with hardware error checking disabled and use a helper script to pull out the proper keys.

Those GPU numbers were measured at the original clockrate (725 core, 1000 mem) although usually I run it slightly underclocked for efficiency.  I generally point it at one of the vanity pools (vanitypool.thruhere.net which accepts compressed solutions or vanitypool.appspot.com which doesn't but sometimes has more work) when there is work that is worth more than bitcoin mining.

You should host the files for this modification somewhere, there are probably a lot of people who would donate BTC for it.
full member
Activity: 125
Merit: 100
Please tell me more of your modified oclvanitygen  =)

Also, what core and mem clocks are you using for your 5970 because I have a Gigabyte 5870 SuperOC with awesome OC potential, I'd like to see some higher numbers if possible, lol...

The oclvanitygen I'm currently using checks both the uncompressed and the positive and negative compressed versions of each key it computes.  Since the majority of the processing time is getting the keys to check this results in about 3x the addresses checked for the same amount of processing power.  At some point a while back I posted the .cl file I was using in the vanitygen thread but I never did completely modify oclvanitygen to do the rest of the calculations properly, I just run it in verbose mode with hardware error checking disabled and use a helper script to pull out the proper keys.

Those GPU numbers were measured at the original clockrate (725 core, 1000 mem) although usually I run it slightly underclocked for efficiency.  I generally point it at one of the vanity pools (vanitypool.thruhere.net which accepts compressed solutions or vanitypool.appspot.com which doesn't but sometimes has more work) when there is work that is worth more than bitcoin mining.
sr. member
Activity: 294
Merit: 250
You might want to look into split vanity address generation so that any buyers you find can be sure that you don't know/can't share the private key for the address you generate.

Also, if I can figure out how to implement it would you be interested in partnering up for this type of business since it would take two people to generate the privkey for the end client and it seems you have a pretty good hashrate and hopefully I will soon too, lol...

Let me know if this interests you!
sr. member
Activity: 294
Merit: 250
You don't necessarily need the whole pool software to do it manually, just need to pass a base public key into oclvanitygen (at least I think that works with the current version, mine is somewhat modified currently)

Hmmm, I will have to look at this. I understand the concept of how it works with 2 separate people generate 2 separate hashes which equal the same output, add those 2 hashes together and blind send the result to end client as the summed hash will also equal the same address... But as far as actually implementing it, I will need to research...

Each extra character makes it take ~58 times longer to find.  I'm getting ~100MK/s with a somewhat modified oclvanitygen and a 5970, been pushing extra keys that it spits out that I'm not really looking for into my keypool, makes following transactions more interesting to read  Smiley  http://www.cryptocoinexplorer.com:3750/tx/408371594efb4b9ab448a622eb7e4a423a2daf919de31743da689fa591594906

Please tell me more of your modified oclvanitygen  =)

Also, what core and mem clocks are you using for your 5970 because I have a Gigabyte 5870 SuperOC with awesome OC potential, I'd like to see some higher numbers if possible, lol...
full member
Activity: 125
Merit: 100
I'm not much for software programming, if there is an open-source software I could use besides just going through vanitypool I would be more than happy to use it. I have oclvanityminer, do you know if the vanitypool software is hosted somewhere open-source...?

You don't necessarily need the whole pool software to do it manually, just need to pass a base public key into oclvanitygen (at least I think that works with the current version, mine is somewhat modified currently)

Is that using vanitygen64 or oclvanitygen...?

With vanitygen64 I can 8-length patterns usually overnight to 2 days. I figured 15-length with oclvanitygen would be maybe a week or two at most since my vanitygen64 does 250kK/s and my oclvanitygen does ~30MK/s.

Each extra character makes it take ~58 times longer to find.  I'm getting ~100MK/s with a somewhat modified oclvanitygen and a 5970, been pushing extra keys that it spits out that I'm not really looking for into my keypool, makes following transactions more interesting to read  Smiley  http://www.cryptocoinexplorer.com:3750/tx/408371594efb4b9ab448a622eb7e4a423a2daf919de31743da689fa591594906
sr. member
Activity: 294
Merit: 250
You might want to look into split vanity address generation so that any buyers you find can be sure that you don't know/can't share the private key for the address you generate.

I'm not much for software programming, if there is an open-source software I could use besides just going through vanitypool I would be more than happy to use it. I have oclvanityminer, do you know if the vanitypool software is hosted somewhere open-source...?

Also might want to rethink or add a disclaimer on that 15 character length, getting >10 characters for a specific name is not fast.  I've been waiting about a week now on a set of trcDice addresses and that's only matching 8 characters (granted the bounty on them is low enough that I may be the only one working on mining them)

Is that using vanitygen64 or oclvanitygen...?

With vanitygen64 I can 8-length patterns usually overnight to 2 days. I figured 15-length with oclvanitygen would be maybe a week or two at most since my vanitygen64 does 250kK/s and my oclvanitygen does ~30MK/s.
full member
Activity: 125
Merit: 100
You might want to look into split vanity address generation so that any buyers you find can be sure that you don't know/can't share the private key for the address you generate.

I will also get you a custom vanity address (i.e. your forum name, your first name, etc...) up to 15 characters long for BTC0.25.

Also might want to rethink or add a disclaimer on that 15 character length, getting >10 characters for a specific name is not fast.  I've been waiting about a week now on a set of trcDice addresses and that's only matching 8 characters (granted the bounty on them is low enough that I may be the only one working on mining them)
sr. member
Activity: 294
Merit: 250
Selling the private keys for the listed vanity addresses. You can use the same address for the BTC, TRC, FRC and DVC networks.

BTC0.10 each


***Updated 1/26/2013***

Added:

1ADiEsMANYh1JEK1ztWhZRUuRt9FURLx5c
1BtcDaRTs84zoFqjFZDsDbhLZTa6Tqk3ws
1DeVcoiNtXJ4L4h33sbkuAxLTedo4DNVrq


********************

Currently in stock:

1337357T9uCsUkjGFeTEwaaqAMCzgkZt87
1ADiEsMANYh1JEK1ztWhZRUuRt9FURLx5c
1ady1UCksUV3QZQMRYvJnMePTEeau3RA2
1BaDDuDE7saKk3CNpWGtzBQ8XPMz7e92DU
1BADMaNUirmUwisnUp7TAqXxva9rQzJegn
1Badmofo5uc5nTBhdHhP1h7dGLB3jSbXXq
1BtcDaRTs84zoFqjFZDsDbhLZTa6Tqk3ws
1CatLUVrKoueMWxh9ut21W8uBqXS7oPaNF
1CoinMANFhQ6pckPCiDqYFJfoVYiKgjvxz
1DBZgoku6xcUosiPynTqLLeTbfLFsttrrf
1DeVcoiNtXJ4L4h33sbkuAxLTedo4DNVrq
1MADMaX19xvZLsZSzxfuXtqwNVXSfZNf6C
1NeTHEAdW2jCdi6DQho55hbGFfzgfhftJj
1PoTheaDgpiPVmhSpQHp7NQo4Hj6mxmApY
1sTBoRNKfS4eSq9nv5KHX62FtMYEjM7eu


This list will be updated constantly and I will only sell each address once so add this thread to your watchlist to keep notified of new updates.

I will also get you a custom vanity address (i.e. your forum name, your first name, etc...) up to 15 characters long for BTC0.25.

***I am temporarily only accepting requests up to 8 characters long while I am working out issues with oclvanitygen***

After purchase, if you need help setting up your new vanity address let me know and I will help walk you through it free of charge.
Jump to: