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

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.

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

vanitygen.exe 1Firo
Difficulty: 4476342

vanitygen.exe 1Sivo
Difficulty: 264104224

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

Hmm. outsourced vanity address generation?

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

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.

I'll take that as a no :\

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

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

Is it difficult to make a Oclvanitygen for Onion addresses ?
https://bitcointalksearch.org/topic/gpu-based-onion-hash-generator-32501

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

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

Thanks. Dunno how I missed that.

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

Again, see here:  https://bitcointalksearch.org/topic/outsourcing-vanity-address-generation-56839

Has anyone worked on getting secure zero-trust generation of vanity addresses by a third party?

Something like the user generates a private key and a public key and then gives the public key to someone with a bunch of hashing power.  They take the given public key and multiple it by a private key generated by vanitygen2.0. If that gives an address that matches the search pattern, the private key is sent securely back to the user.

I think this could be a great service.

I can't think of a way for the third party to prove they have generated the address without giving the key to the user.  I was trying to figure out how to monetize this.


EDIT: It looks like Armory has the math for this built in.



EDIT: I am so rusty when it comes to C.  I don't think this would be too complex to write, though.  It would definitely slow down address generation since you have to do some key multiplication.  A public key would be need to be passed as an additional argument.

There will be two weeks for the difficulty change, and many more weeks for those mining at a loss to finally quit. I don't expect the price to change almost at all from that, since miners have little if any effect on the market. So, for a few weeks mining will be very unprofitable, and likely getting blocks to confirm your transactions will take way longer than normal. Just in time for the holiday shopping season, too 

The difficulty:price ratio will also change and only that's important (apart from maybe liquidity on exchanges).

I an guessing that vanity names will explode in usage after the reward block halves, since Bitcoin mining will be very unprofitable at that point, and there will be a lot of hashing hardware sitting idle. I recently decided to focus on mining while I can, and put my vanity name generation off until next year.

no just one.