Author

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

staff
Activity: 4284
Merit: 8808
Regardless, the new client will still accept older uncompressed public keys, so why bother making the change to vanity gen?  Unless you're trying to "do your part" in helping keep the blockchain as short as it can be...

Reducing your pubkey sizes will also reduce what you pay in transaction fees when you spend coins sent to those addresses— and potentially it could make vanitygen faster due to having two tries for every private key.
member
Activity: 96
Merit: 10
Any chance on a version of this for Litecoin?
-X 48

thanks! (was actually reading a few pages before and saw that i missed, it... oops...  Roll Eyes
hero member
Activity: 560
Merit: 501
Any chance on a version of this for Litecoin?
-X 48
member
Activity: 96
Merit: 10
Any chance on a version of this for Litecoin?
legendary
Activity: 1400
Merit: 1005
Because the public vanity address is the hash of the public key.  If the public key is in a different format then the hash of the public key (the vanity address) would be different.
Got it.

Regardless, the new client will still accept older uncompressed public keys, so why bother making the change to vanity gen?  Unless you're trying to "do your part" in helping keep the blockchain as short as it can be...
legendary
Activity: 2646
Merit: 1137
All paid signature campaigns should be banned.
Because the public vanity address is the hash of the public key.  If the public key is in a different format then the hash of the public key (the vanity address) would be different.
legendary
Activity: 1400
Merit: 1005
Vanitygen is a command-line vanity bitcoin address generator.

I haven't seen any mention of compressed pubkey support.

The latest versions of Bitcoin (perhaps just git, so .6 post but I'm not going to bother checking) will default to creating addresses based on compressed public keys.

These addresses look just like every other address but they take up less space in the blockchain when you spend from them (and thus lower txn fees in the long run).

Every private key has two possible addresses. One based on the compressed public key, one based on the regular public key.   It takes a bit more computation on top of the normal public key generation to get the compressed version.

It would probably be a good idea for vanitygen to offer / default to generating compressed public keys.

Have I missed discussion related to this?

I'm confused... if the compressed portion is a "behind the scenes" address, why does it need to be generated?  All you need from vanity gen is the Bitcoin address and the private key associated with it.
staff
Activity: 4284
Merit: 8808
Vanitygen is a command-line vanity bitcoin address generator.

I haven't seen any mention of compressed pubkey support.

The latest versions of Bitcoin (perhaps just git, so .6 post but I'm not going to bother checking) will default to creating addresses based on compressed public keys.

These addresses look just like every other address but they take up less space in the blockchain when you spend from them (and thus lower txn fees in the long run).

Every private key has two possible addresses. One based on the compressed public key, one based on the regular public key.   It takes a bit more computation on top of the normal public key generation to get the compressed version.

It would probably be a good idea for vanitygen to offer / default to generating compressed public keys.

Have I missed discussion related to this?
member
Activity: 89
Merit: 13
Anyone tell me how to generate LTC vanity addresses?

-X 48 does not seem to work.



$ ./vanitygen -X 48 L1QaZ
Prefix 'L1QaZ' not possible
Hint: valid bitcoin addresses begin with "1"

It works, it's just that the address versioning doesn't allow certain characters.

That's right. Litecoin addresses go from "LK..." to "Li..."
So 1 is not valid for the second character.

Cool... thanks so much.
donator
Activity: 1654
Merit: 1351
Creator of Litecoin. Cryptocurrency enthusiast.
Anyone tell me how to generate LTC vanity addresses?

-X 48 does not seem to work.



$ ./vanitygen -X 48 L1QaZ
Prefix 'L1QaZ' not possible
Hint: valid bitcoin addresses begin with "1"

It works, it's just that the address versioning doesn't allow certain characters.

That's right. Litecoin addresses go from "LK..." to "Li..."
So 1 is not valid for the second character.
hero member
Activity: 560
Merit: 501
Anyone tell me how to generate LTC vanity addresses?

-X 48 does not seem to work.



$ ./vanitygen -X 48 L1QaZ
Prefix 'L1QaZ' not possible
Hint: valid bitcoin addresses begin with "1"

It works, it's just that the address versioning doesn't allow certain characters.
legendary
Activity: 2646
Merit: 1137
All paid signature campaigns should be banned.
Anyone tell me how to generate LTC vanity addresses?

-X 48 does not seem to work.



$ ./vanitygen -X 48 L1QaZ
Prefix 'L1QaZ' not possible
Hint: valid bitcoin addresses begin with "1"

AFAIK vanitygen only does namecoin, testnet or bitcoin.  Could be wrong though
member
Activity: 89
Merit: 13
Anyone tell me how to generate LTC vanity addresses?

-X 48 does not seem to work.



$ ./vanitygen -X 48 L1QaZ
Prefix 'L1QaZ' not possible
Hint: valid bitcoin addresses begin with "1"
legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
Are there any reasons why GCC from mingw was not used for this?

With a few hacks, it compiled flawlessly under MinGW-w64
legendary
Activity: 2646
Merit: 1137
All paid signature campaigns should be banned.
Cool, so you did throw out all checksums that contained numbers and lower case characters, just like I said AND you are correct, there is no real difference between selection made on the address hash itself and the checksum.

You just selected an address with all capital letters - looks great!
legendary
Activity: 1428
Merit: 1093
Core Armory Developer
You must have gone though a lot of addresses that had all capitals BUT had numbers or some small letters in the checksum, right?

Why is there an assumption that the checksum is any different than the rest of the letters?  The address is created from 25 bytes.  The first byte is always '\x00' which corresponds to the first '1' you see in every main-network Bitcoin address.  So we will ignore that one...

But the following 20 bytes are a hash, which means it's all essentially-random bits.  Then, the checksum is just 4 more bytes, which are also a hash... which means it's essentially random, too.  When I say "essentially-random", I mean from the perspective of what characters will be used in the Base58 address, all letters are equally likely for all positions, except maybe the very first character after the '1', and that's for reasons that are difficult to explain...

But the point is that the address is created from a sequence of 24 bytes (addr + checksum) which are all essentially random, so why would some letters be more difficult to match than others?   If you want more information about how addresses are computed, click the bottom link in my signature.  There's a diagram halfway down that shows how addresses are generated from the public key. 

-Eto
legendary
Activity: 2646
Merit: 1137
All paid signature campaigns should be banned.
You must have gone though a lot of addresses that had all capitals BUT had numbers or some small letters in the checksum, right?
legendary
Activity: 1137
Merit: 1001
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 Smiley

A donation is on its way!

cool!

Can an address be made with only numbers?

This problem gets exponentially harder, the fewer characters you choose to have in your final address.  In this case, I only wanted upper-case letters, which limits each character in the final address to one of 24 characters out of 58 (26 letters in alphabet minus 'I' and 'O').   If your address was only one letter after the '1', you would have to generate 2.4 addresses (58/24, on average) to get all uppercase letters.  If it was two letters, you'd have to generate 5.8 (2.4^2) addresses on average before finding it.  Etc.  So for an address with 32 letters, you're talking 2.4^32 guesses before finding such an address (on average).

At 300,000 keys per second in vanitygen, it should take about two months (I calculate 70 days) to find such an address as I have in my signature (on average).

If you now instead change it to all numbers, you've now limited yourself to 9/58 characters instead of 24/58 (10 digits minus '0').  If you repeat the calculation using 58/9, it will take 6.4^32 guesses.  At the same key generation rate, I calculate it would take 3,022,041,992,597,561 days to find such an address.

So the answer to your questions is... no Smiley



So there's a chance...

I like how you sent btc from the address to prove you own it. Very nice.

legendary
Activity: 924
Merit: 1004
Firstbits: 1pirata
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 Smiley

A donation is on its way!

i'm puzzled with that address of yours, how did you managed to generate the uppercase checksum... ?
legendary
Activity: 1428
Merit: 1093
Core Armory Developer
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 Smiley

A donation is on its way!

cool!

Can an address be made with only numbers?

This problem gets exponentially harder, the fewer characters you choose to have in your final address.  In this case, I only wanted upper-case letters, which limits each character in the final address to one of 24 characters out of 58 (26 letters in alphabet minus 'I' and 'O').   If your address was only one letter after the '1', you would have to generate 2.4 addresses (58/24, on average) to get all uppercase letters.  If it was two letters, you'd have to generate 5.8 (2.4^2) addresses on average before finding it.  Etc.  So for an address with 32 letters, you're talking 2.4^32 guesses before finding such an address (on average).

At 300,000 keys per second in vanitygen, it should take about two months (I calculate 70 days) to find such an address as I have in my signature (on average).

If you now instead change it to all numbers, you've now limited yourself to 9/58 characters instead of 24/58 (10 digits minus '0').  If you repeat the calculation using 58/9, it will take 6.4^32 guesses.  At the same key generation rate, I calculate it would take 3,022,041,992,597,561 days to find such an address.

So the answer to your questions is... no Smiley
Jump to: