I'm reeeeally sorry for giving up my epic quest of searching various keywords on this thread / clicking through the pages...
But if someone could make a new post that actually updates the OP with the latest news (I mean, this thread's OP makes no mention of all the functionality you guys are speaking of) on vanitygen, I'd appreciate it much more...
I am looking for a compiled version for Windows 7 64bit that a trusted member of the community has up on github or something... or a link to a well known repository...
that supports compressed addresses with oclvanitygen.
If there's any wiki-type page with all the necessary info on vanitygen and the latest patches / versions... I'd appreciate it. Thanks, and sorry again for failing at weeding through this thread.
In a nutshell the standard method
1) ECDSA(private) -> ECDSA(public)
4) Add network identity to this result, Original 0x00 for bitcoin, but now with >500 crypto-coins, it depends on your target (use the -X key)
5) SHA256(SHA256(#4 + #3)) -- take first four bytes of the result
6) Base58(#4 + #3 + #5) --> Bitcoin address
Step 5 can be omitted when searching for a match at the start of the code. Since these 4 bytes only affect the last portion of the BTC-address.
The checksum 4 bytes are padded zero's. That's why a found key and a actual generated key differ at the end.
It does save a lot of hashing time :-)
In a nutshell the secure generation for third party method
1) ECDSA(private1) -> ECDSA(public1) --> fixed
2) ECDSA(private2) -> ECDSA(public2) --> generated
3) ECDSA ADD(ECDSA(public1) + ECDSA(public2))
6) Add network identity to this result, Original 0x00 for bitcoin, but now with >500 crypto-coins, it depends on your target (use the -X key)
7) SHA256(SHA256(#6 + #5)) -- take first four bytes of the result
8) Base58(#6 + #5 + #7) --> Bitcoin address
9) return the found ECDSA(private2)
10) Use the keyconf to create ECDSA(private final)= ECDSA ADD (ECDSA(private1) + ECDSA(private2))
11) follow the standard method on result (#10)
Step 11) requires the network identity code (for the <xxx>coin address generation), but also a private code(! for the WIF generation) The relation with the older coins is that private code is network code + 128.
Since there are more crypto-coins than could fit the equation this (network code +128) is now not always valid, depending on your target coin.
In order to make this SW work for most of the crypto-coins a new inline key needs to be added where the private code can be overruled if it not equal to (network code +128)
both in the generator and keyconf function.
The functionality of the SW has not changed since the OP opened this thread, it's just that a couple of crypto-coins have been added.
I'm sorry, but I don't have windows binaries in my repo.