In order to better the first one, you would need the format ABCDE*EDCBA as the one I bested was 123*321 so you might tie mine but I believe you have to beat it to get it listed.
After finding 1234imbqWvqq1nNUgDxQ2wrg1R7GBZF321 in minutes, I didn't find another one ending on 321 all night. I have 141247 addresses starting with 1234 now. Two of these have a private key ending on 321:Address: 12342YbDeQgi3dz4hcYiN5WRrth5MisEan
Privkey: 5HwRHBe1xQc4PgPGUUG8foi7ZAqLc2Qa6V1WbTkzjcYbrijj321
Address: 1234SGdyL9rDCjVdkTYySaTvJZNoyHEBBi
Privkey: 5J82rcTpLRfdh67SutpSj5AMXuMG8y3bc2bE2kR1bzS6YmMq321
I know it's totally useless having a vanity private key, as you can only use it to show off by posting it. I'll search my long list through these 142247 keys for matches, it might take a while.
Quote
Finding 1234xxxxxxxxx4321 can't be that hard, right?
Not sure of any other way to search for that form of other than to set the keep searching switch to er, keep searching to a dump file and then sift through what you've found.
There is a way to search for matches at the end. Use a regex search with the -r option and $ matches end of string. ^ is supposed to match the beginning of the string but it doesn't work properly in vanitygen for some reason. I believe it was shorena who figured out that ^^ does work in vanitygen for matching beginning of string though. I can't find the reference so I'm going with my memory on that; apologies if it was someone else.
Code:
vanitygen -k -r ^^123.*321$
This will search for the 123 pattern at the beginning and 321 at the end. Obviously it doesn't have to be a numerical progression but certainly it will have to begin and end with a 1
It might be faster to use oclvanitygen and a file dump but I think the file would become extremely large.
Maybe we need a rare private key thread? I've noticed some cool things in private keys as well