Vanitygen: Vanity bitcoin address generator/miner [v0.22]

[BurtW]

Again, see here:  https://bitcointalk.org/index.php?topic=56839.0

[bitpop]

I am getting this error

Read 131072 bytes from RNG seed file
Difficulty: 50656515217834
Compiling kernel, can take minutes...done!
WARNING: AMD BFI_INT patching failed

[Red Emerald]

Again, see here:  https://bitcointalk.org/index.php?topic=56839.0

Thanks. Dunno how I missed that.

[check_status]

I'm an apt-get type of person and never have used git. Could someone explain the process?
I hacked up an example from an unrelated git tut but needs some fill in the blanks or corrections.
Are there any dependancies that need to be satisfied before running?
I don't plan on using oclvanitgen as hardware doesn't support 11.11, maybe 8 or 9. Will I be limited to what I can look for?

Code:

steps on how to compile under Linux:
 $ git clone https://github.com/samr7/vanitygen.git
 $ cd *where?*
 $ git checkout -b *what is going on here?*
 $ ./autogen.sh && ./configure *anyflags needed here?* && make
 $ sudo make install

I moved this question to technical support, it would help if I read to the end of sentences more often.
My bad, move along.

[check_status]

vanitygen running well @ 113 Kkeys/s on the CPU's. Dual core and both CPU's are at 100%.

[HostFat]

Is it difficult to make a Oclvanitygen for Onion addresses ?
https://bitcointalk.org/index.php?topic=32501.0

[hongus]

Is there a "fast" way to generate an address with up to 8-9 vanity characters? By fast I mean like within 24 hours.

[BurtW]

Is there a "fast" way to generate an address with up to 8-9 vanity characters? By fast I mean like within 24 hours.

Yes, use a lot of video cards and run your request on all of them.

[hongus]

Is there a "fast" way to generate an address with up to 8-9 vanity characters? By fast I mean like within 24 hours.

Yes, use a lot of video cards and run your request on all of them.

I'll take that as a no :\

[BurtW]

Is there a "fast" way to generate an address with up to 8-9 vanity characters? By fast I mean like within 24 hours.

Yes, use a lot of video cards and run your request on all of them.

I'll take that as a no :\

If you have a BTC mining farm you can use it to find vanity adresses but during that time you cannot mine BTC.  With enough power you can find an 8-9 character vanity address in 24 hours.

[hongus]

Is there a "fast" way to generate an address with up to 8-9 vanity characters? By fast I mean like within 24 hours.

Yes, use a lot of video cards and run your request on all of them.

I'll take that as a no :\

If you have a BTC mining farm you can use it to find vanity adresses but during that time you cannot mine BTC.  With enough power you can find an 8-9 character vanity address in 24 hours.

Yeah I don't have the equipment to do that but it's okay. I'm happy with 5.

[guruvan]

Hmm. outsourced vanity address generation?

[BurtW]

Hmm. outsourced vanity address generation?

Discussed many times.  I really should get off my butt and just do it.  I keep waiting for someone else to do it.

[flatfly]

Strange, the difficulty of 1Firo is significantly higher than that of 1Sivo - why?

vanitygen.exe 1Firo
Difficulty: 4476342

vanitygen.exe 1Sivo
Difficulty: 264104224

[deepceleron]

Strange, the difficulty of 1Firo is significantly lower than that of 1Sivo - why?

vanitygen.exe 1Firo
Difficulty: 4476342

vanitygen.exe 1Sivo
Difficulty: 264104224

The change happens at a particular address:

Prefix difficulty:                77178 1QLa
Prefix difficulty:                78362 1QLb
Prefix difficulty:              4553521 1QLc

This is a quirk of how the 25-byte (50 digit hexadecimal) Bitcoin address is converted into Base58 (represented by numbers and letters), and the different maximum values that can be stored in 25 base256 digits vs 34 base58 digits.

The Bitcoin address in it's native binary form (that you never see) is 25 bytes, it's parts are:
byte 0: Network ID Byte (0x00 for main bitcoin network)
byte 1-20: ripemd160 hash (20 bytes) of sha256 hash (32 bytes) of 0x04+public key (65 bytes)
byte 21-24: checksum: first four bytes of sha256 hash of sha256 hash of bytes 0-20 above

This would be 50 hexadecimal characters long (base16), with a possible digit value between 0-F.

We will ignore byte 0, it is always 0x00, and Base58 conversion always preserves this leading 0 byte by directly encoding it as a "1".

That means the "vanity" part of the address is bytes 1-24, 24 bytes of random hash output, or 48 hexadecimal digits. The maximum value that this can be is 0x FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF ffff ffff (the lower case "f"s are the checksum, and won't be all FFFFs for the maximum ripemd160 value.)
We can guess from the output below that this maximum possible address value encoded in Base58 becomes 1QLbxxxxxx.... something:


1QLa8LNNFeYs7KJWvxMdR5YtRjkwtQtkyb
1QLabhman6ZQyz3musbqV1RjFmE3pyT29j
1QLaJHv2LCSYo8WgT9qPf4rdttduRGyozX
1QLarwzJCUWGuQEZ4uWPsYVz8N2P5XmeQU

1QLckWG2tx17suupYU2FfeWunTCZMuJKW
1QLcMk7NVLwvg8gw2ihJTuG8x7WLYCjMg
1QLcLr6AoN687CpH1JZnfeMmWvUka5NHX
1QLc47945bSCv4J1Z4yRuvUbtooQqmGJ1
1QLcU9NNxaqfvqMRXD8dFtL2SktL3YmBT
1QLc1D24uDbvy327MzifEChVvATAeDsbF


See how the 1QLa addresses are full length, but the 1QLc addresses are one digit shorter? That is because the only way to have an address starting at 1QLc or greater is by having a binary address that is 59x smaller.

[ByteCoin]

https://blockexplorer.com/address/1QLbz7JHiBTspS962RLKV8GndWFwi5j6Qr

ByteCoin

[ptshamrock]

Will VanityADress gen be workable with FPGA`s like BFL?

[K1773R]

stupid question, stupid answer:
develop OpenCL driver for ur FPGA then u can!

[Nyhm]

Hello, just a note that I made a vanity address generator applet (see topic here). It's ridiculously slow compared to the likes of Vanitygen. Just an experiment, as I'm starting to tinker with Bitcoin.

[runlinux]

I love my new address (Check sig)