Topic: Vanitygen: Vanity bitcoin address generator/miner [v0.22] - page 169. (Read 1153383 times)

cool!

Can an address be made with only numbers?

I wasn't able to get GPU working in linux, but it turns out my cluster of CPUs was enough to create the address I really wanted :

    1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX

Am I really the first person that has done this?  FreeMoney didn't even recognize it as a BTC address.  At the very least, people should recognize that one when they see it

A donation is on its way!

The source code is available on git.

I guess you didn't read anything at the link.

samr hasn't logged into the forum since August. You might need to get the source yourself, try to set up a compile environment for it, and then modify the software so it searches for proper minikeys (only 1 in 10,000 or so mini-sized keys match the requirements if I recall) and then does the phrase check. Because of this additional difficulty, a normally 1-day phrase might take you 20 years though...

Interested in a modified version of vanitygen which can produce vanity addresses from minikeys.

A request for software has been posted here:
https://bitcointalksearch.org/topic/need-vanitygen-modified-to-work-with-minikeys-57040

OOOOOOOOOOOOOOOO actually reading the bolded part makes a big difference. 

I just made a new years resolution to learn to read more carefully.

I get that just pointing out you responded to this quote...

As discussed in this thread https://bitcointalksearch.org/topic/outsourcing-vanity-address-generation-56839 we are not talking about creating a vanity address using the current software that "just happens to start with a 3" we are talking about creating a proper vanity address that starts with 3 - that is - the hash of a one of two key script where one of the keys is a valid public key and the other key is a bogus "filler" public key.  Therefore you would end up with a vanity address that starts with a 3 which is the proper hash of a proper script that will work properly.

To do this would take a new version of the vanitygen (and GPU version of vanitygen) that does all the proper calculations in order to create the proper script and proper hash of the script.

The nice thing is that each trial in the search for the vanity address would be much faster.  In this future system the algorithm is:

1) Create a valid keypair
2) Create a random invalid/bogus public key (basically a nonce).  Note the private key is unknown/unknowable
3) Create a valid "use one of these two keys" script with the valid public key and the bogus public key as the two parameters
4) Properly hash the script (much easier that a public key calculation)
5) Check for the vanity pattern, if it matches quit, otherwise go to step 2)

Note that each trial is now just the time it takes to generate a random number and take the hash of the script!

Vanity gen takess random private key and hashes it until it found a public key. 

Bitcoin addresses which start w/ 3 have no private key.  Any address starting w/ 3 generated by vanity gen would be utterly useless.  Any funds sent to it would be a black hole.

What do you mean?

This does not mean generating vanity addresses starting with "3" with this generator is useful in any way.

As discussed in the new thread on vanity address outsourcing the vanity addresses that start with 3 will be much easier (less computation) to create.  This will lead to the possibility of longer vanity addresses for those that start with 3.

3 addresses are newer versions which use BIP0013. As these addresses are not hashes of pubkeys or privkeys, but rather scripts, generating vanity addresses is rather useless.

I'm not sure why they say that there. AFAIK the 1 comes from a version field indicating Bitcoin (vs. Namecoin etc) by convention. I've never seen a 3... address in use or displayed. I don't think it's because they "ran out" since addresses are generated randomly. I could be wrong though as I don't know all the innards and history.

You can actuallly run oclvanitygen at the same time as mining. I did it and it worked and dropped some % of mining speed. It did seem to be a bit unstable or maybe that was just pushing my OC a bit hard. I had better results when disabling the GPU from mining.

Exactly.

https://en.bitcoin.it/wiki/Address :

So there's no way to make use of all GPUs simulatenously?
Or maybe I could be running 3 instances of oclvanitygen each for each GPU to increase the probability of finding an address and it's priv key? Would that be the same?

Take out the equal sign. -d 2

See docs. GPU isn't good at regex expression evaluation.

I haven't heard of any other vanity gens with GPU support at all.
This one is kind of a miracle it exists at all considering the work involved.

Because ALL bitcoin addresses always start with 1. No such thing as a 3 address.

I guess the regex eval process slows it down a lot.

See post above, explains how to do regex without -r

Hello everyone, I have a few (noob) questions

- Anyone know how to use all GPUs for oclvanitygen?
And why if I select GPU #2,for ex.:

oclvanitygen -r -d=2 123

Only my primary GPU (GPU #0) will be used? In my case this is a slower GPU.

- Why with -r only the CPU can be used (vanitygen prints "WARNING: Using CPU pattern matcher")?

- Are there any better/faster address generators out there?

- Why I can only generate addresses starting with "1"? Aren't there anymore addresses left starting with "3"?

- Why am I getting higher speeds without "-r" on CPU?
Without: ~350kkeys/sec
With: ~75kkeys/sec
Isn't it supposed to be the other way around (expression can be placed anywhere in the address instead just at the beginning)? Or am I getting something wrong?

- I have a Q9300 undervolted to 0.975V and underclocked to 2GHz to save power (stock 2.5GHz and sth like 1.1 or 1.2Vcore), before mining this used to be primarily a gaming rig, and I had this CPU running @ 3.5GHz and 1.32Vcore, what speed can I expect if I decide to O/C it back to 3.5GHz? I think it'll increase linearly but not sure and will probably do it unless I find a way to generate addresses with the "-r" option.

- Any way to generate shorter addresses (shortest as possible, 25 base58 chars?)

Thanks.

This seems to work ok,


I made it easier so I could see results quicker but the actual cmd would be,

oclvanitygen -k 1TCa |grep -A1 -P 1TCa[1-9]{4}.*


-A1 for including next line too.(with key).
-P to use Perl regex which I know unlike POSIX regex.

Or to save in a file, and view on screen,

oclvanitygen -k 1TCa |grep --line-buffered -A1 -P 1TCa[1-9]{4}.* | tee -a list.txt

--line-buffered is needed because grep buffers it's output.

Edit: I forgot you would need a -d  arg for oclvanitygen to select device. Also, I tried this on GPU and it said for low difficulty it would be faster on CPU. Seems it is too. But it's faster if you make it more difficult for the GPU, eg.

oclvanitygen -k 1TCa1 |grep -A1 -P 1TCa[1-9]{4}.*

Weird.

So in D&Ts case match for exactly 1TCa, store them in a file, grep for those that happened to have 4 digits after the 1TCa offline later.  Sounds like a very large file with a few good ones in it