I'd love to be proven wrong on this though.
I don't think you can be. 
Topic: Vanitygen: Vanity bitcoin address generator/miner [v0.22] - page 174. (Read 1153383 times)
Can anyone think of a clever way to distribute this: to let us search for the vanity phrases others want aswell as our own 
As far as I can tell we can't make this distributed in a safe manner. Whoever finds a particular address will need to have had the public part of the EC key pair, which is only valuable with the matching private key. They are always created together, and so, anyone finding a particular address (and it's corresponding key) will have had the opportunity to save the private.I'd love to be proven wrong on this though.
Would some one be interested in creating a 9 letter vanity address for a bounty? If so please PM
Also assuming you make the address for me, I would be able to use it with out too much trouble?
Thanks
It would need to be someone trustworthy, as they would also have access to the private key associated with it, no?Also assuming you make the address for me, I would be able to use it with out too much trouble?
Thanks
Would some one be interested in creating a 9 letter vanity address for a bounty? If so please PM
Also assuming you make the address for me, I would be able to use it with out too much trouble?
Thanks
It would need to be someone trustworthy, as they would also have access to the private key associated with it, no? Also assuming you make the address for me, I would be able to use it with out too much trouble?
Thanks
I was quite sad when I found out that http://firstbits.com/1bitcoin had been wasted on a dead end account. I have created quite a few vanity addresses and I think my favorite so far is http://firstbits.com/1zaphod Also, and this might date me, I own http://firstbits.com/1xyzzy (the magic word in one of the first computer games called Adventure)
CHALLENGE: post the highest difficulty prefix you've found (use -i if you didn't search case-sensitive.)
New difficulty challenge to beat: 3,317,130,297,283 (see my signature!)
TyGrrTech is pretty long, but other, shorter versions (for example http://firstbits.com/1TGTech) are still available.
This whole idea of finding accounts for others would be pretty cool except for one thing: security of the private key.
For example if I did find 1TyGrrTech (or more likely 1TGTech) I would now know the private key. If I give/sell the keypair to you then there is really no way you can be sure I don't keep a copy of it so I can go in and steal all your coins once I see you have a bunch on the account.
The best option I can think of is that if you were to get/buy one of these keys where you are unsure of the security of the private key then import the private key into Mt. Gox and set it to immediately sweep any coins sent to the account off the account into another account.
Even doing that you still would have to "race" with anyone else who had the same private key and see who could sweep the coins out first.
This whole idea of finding accounts for others would be pretty cool except for one thing: security of the private key.
For example if I did find 1TyGrrTech (or more likely 1TGTech) I would now know the private key. If I give/sell the keypair to you then there is really no way you can be sure I don't keep a copy of it so I can go in and steal all your coins once I see you have a bunch on the account.
The best option I can think of is that if you were to get/buy one of these keys where you are unsure of the security of the private key then import the private key into Mt. Gox and set it to immediately sweep any coins sent to the account off the account into another account.
Even doing that you still would have to "race" with anyone else who had the same private key and see who could sweep the coins out first.
Can anyone think of a clever way to distribute this: to let us search for the vanity phrases others want aswell as our own
Code:
user@linuxcoin:~/Desktop/vanitygen$ ./oclvanitygen -k -d 0 -s /dev/random "1TyGrrTech"
Read 32 bytes from RNG seed file
Difficulty: 173346595075428786
[31.21 Mkey/s][total 1292369920][Prob 0.0%][50% in 122.1y]
Read 32 bytes from RNG seed file
Difficulty: 173346595075428786
[31.21 Mkey/s][total 1292369920][Prob 0.0%][50% in 122.1y]
So in 122 years there will be a 50% chance it has been found
.I have added your prefix to my pattern file. I will probably find the pattern I'm looking for ("1runeks") Saturday (5.5 hrs for 50% prob.), but don't keep your hopes up on me finding yours
.Can the authors elaborate on what exactly "difficulty" refers to? And how you, from the difficulty, calculate that the probability is x of finding the key in y hours/days/years.
It seems like pywallet doesn't support the encrypted wallet format used in the v0.4 Bitcoin client. At least that's what appears to me to be the case from reading the pywallet-thread. Perhaps it would be a good idea to add this information to the first post of this thread, on importing the private key, that pywallet doesn't support an encrypted wallet.dat, since I imagine most people are using this feature.
Would some one be interested in creating a 9 letter vanity address for a bounty? If so please PM
Also assuming you make the address for me, I would be able to use it with out too much trouble?
Thanks
Could you specify the exact 9 letter prefix you wish? Is it even a prefix, or does the text just have to appear somewhere in the address? Lower case is slowest, upper case is less slow and either upper case or lower case is the fastest, so this has an impact on the amount of time one has to use to find your desired string.Also assuming you make the address for me, I would be able to use it with out too much trouble?
Thanks
EDIT: You would need to install pywallet to import the private key into your wallet. I'm not sure how difficult this is on Windows; on Linux it's fairly easy.
Would some one be interested in creating a 9 letter vanity address for a bounty? If so please PM
Also assuming you make the address for me, I would be able to use it with out too much trouble?
Thanks
Also assuming you make the address for me, I would be able to use it with out too much trouble?
Thanks
Just to get near a 50% probability of generating a "1" plus nine case-insensitive letters would take about the same GPU processing time as mining 6 BTC...
If you put what you want here with the bounty, perhaps several people could add your phrase to their list of vanity addresses they are already searching for and you might get lucky. You have to trust that the person who gives you the vanity address is also relinquishing and completely deleting the matching private key, or they would also have access to any bitcoins sent to that address.
CHALLENGE: post the highest difficulty prefix you've found (use -i if you didn't search case-sensitive.)
I found a "12345678" which I quite like, and also the ones in my sig.(case-sensitive)
Prefix difficulty: 888,446,610,538 12345678
Prefix difficulty: 873,388,193,410 1NaNoBit
12345678 is harder due to weirdness about the 0 bits in the underlying unencoded address to make a 2 (in Base58 1 = 0)
For a particular length, case-insensitive difficulty will be lower depending on how many Base58 case substitutions are possible in your phrase, e.g. n has N, but i can't be I; numbers have no substitution.
CHALLENGE: post the highest difficulty prefix you've found (use -i if you didn't search case-sensitive.)
I found a "12345678" which I quite like, and also the ones in my sig. Is it necessary to let vanitygen run continuously in order to find the desired key, or can I stop it then start it again?
runeks: It's generating random keys, so yes - you can stop it anytime and it don't lower your chance to find proper address...
Unless you put in a custom seed, but you probably don't do that, anyway
It appears this is not a concern, that system entropy is still used in addition to the random seed file. We don't get the same addresses every execution:
E:\Bitcoin\vanitygen-0.17-win>vanitygen.exe -v -t 2 -s RandomNumbers 1ABCD
Read 959 bytes from RNG seed file
Prefix difficulty: 4476342 1ABCD
Difficulty: 4476342
Using 2 worker thread(s)
Pattern: 1ABCD
...
Address: 1ABCDRandomBitcoinAddress
E:\Bitcoin\vanitygen-0.17-win>vanitygen.exe -v -t 2 -s RandomNumbers 1ABCD
Address: 1ABCDRandomBitcoinAddress
E:\Bitcoin\vanitygen-0.17-win>vanitygen.exe -v -t 2 -s RandomNumbers 1ABCD
Address: 1ABCDRandomBitcoinAddress
E:\Bitcoin\vanitygen-0.17-win>vanitygen.exe -v -t 2 -s RandomNumbers 1ABCD
Address: 1ABCDRandomBitcoinAddress
So far RaTTuS seems to have set the bar for complexity with his public address....
It looks like we can use vanitygen itself to see how difficult the prefix was:
Case sensitive 1RaTTuS:
E:\Bitcoin\vanitygen-0.17-win>vanitygen.exe -v 1RaTTuSCase insensitive 1firstbit (yes, I had to do it...):
Prefix difficulty: 888,446,610,538 1RaTTuS
E:\Bitcoin\vanitygen-0.17-win>vanitygen.exe -v -i 1FiRSTBiTnote: RaTTuS is harder than most 6 chars -- case-sensitive prefixes starting with Q-Z or a-z are 59x harder than starting 1-9,A-P):
Prefix difficulty: 1,605,983,018,727 1firstbit
Prefix difficulty: 873,388,193,410 1Poooooo
Prefix difficulty: 51,529,903,411,245 1Qoooooo
CHALLENGE: post the highest difficulty prefix you've found (use -i if you didn't search case-sensitive.)
EDIT: DON'T try to upgrade Linuxcoin with "apt-get upgrade". If it goes the way it did for me, it will break horribly. The errors just didn't appear until I restarted. Now fglrx (and thus OpenCL) doesn't work.
Yay! I finally got this working in Linuxcoin. I had to increase the Linuxcoin persistence file system (live-rw file) to 3GB in order to be able to upgrade via "apt-get upgrade", and had to change the following line in Makefile:
changing the second line from:
to:
Oh, and I had to install libssl-dev, libpcre3, libpcre3-dev (as others have mentioned).
Getting a steady 31 Mkey/s on my 5870:
I haven't tried tweaking any parameters except adding -w128 and -w256 which seemed to produce the same results.
Thank you for making this!
Yay! I finally got this working in Linuxcoin. I had to increase the Linuxcoin persistence file system (live-rw file) to 3GB in order to be able to upgrade via "apt-get upgrade", and had to change the following line in Makefile:
changing the second line from:
Code:
oclvanitygen: oclvanitygen.o pattern.o util.o
$(CC) $^ -o $@ $(CFLAGS) $(LIBS) -lOpenCL
Code:
oclvanitygen: oclvanitygen.o pattern.o util.o
$(CC) $^ -o $@ $(CFLAGS) $(LIBS) -L/opt/AMD-APP-SDK-v2.4-lnx64/lib/x86_64/ -lOpenCL
Oh, and I had to install libssl-dev, libpcre3, libpcre3-dev (as others have mentioned).
Getting a steady 31 Mkey/s on my 5870:
Code:
user@linuxcoin:~/Desktop/vanitygen$ ./oclvanitygen -d 0 "1runeks"
Difficulty: 888446610538
[31.13 Mkey/s][total 355205120][Prob 0.0%][50% in 5.5h]
I haven't tried tweaking any parameters except adding -w128 and -w256 which seemed to produce the same results.
Thank you for making this!
Interesting. New version of AMD video drivers came out, and now ocl is working fine Guess it was them, not you. Thanks!
Guess it was them, not you. Thanks!ATI 11.10 WHQL - Now works! It appears that the newest SDK is the fix, as by extracting the ATI "driver only" downloads, you can install just the video driver you want, and then install the newest 2.5 SDK from C:\ATI\Support\11-10_vista32_win7_32_dd\Packages\Apps\OpenCL. I have tested this SDK with the 11.6 and the 11.10 video driver.
Memory speed seems important to keygen speed too. If you've downclocked memory for mining, be sure to bump memory speed back up to default or even overclock.
Benchmarks:
CPU: 113 Kkey/s per core on 2.4GHz Intel Core2 Quad (32 bit)
CPU: 131 Kkey/s per core on 2.7GHz AMD Sempron 140 / Athlon 64 X2 Kuma
GPU: 15.3 Mkey/s on ATI Radeon HD 5770 (1000/1300)
GPU: 20.5 Mkey/s on ATI Radeon HD 5830 (1050/1050) (5 char address in ~13 seconds)
Unless you put in a custom seed, but you probably don't do that, anyway
Cool. Good to know. Thanks!
runeks: It's generating random keys, so yes - you can stop it anytime and it don't lower your chance to find proper address...
Jump to: