So I wanted a palindrome in my bitcoin address:
vanitygen64 -r -k (.)(.).\2\1
vanitygen64 -r -k (.)(.)(.).\3\2\1
vanitygen64 -r -k (.)(.)(.)(.).\4\3\2\1
vanitygen64 -r -k (.)(.)(.)(.)(.).\5\4\3\2\1
vanitygen64 -r -k (.)(.)(.)(.)(.)(.).\6\5\4\3\2\1
vanitygen64 -r -k (.)(.)(.)(.)(.)(.)(.).\7\6\5\4\3\2\1
the 5 and 7 character palindrome is trivial, but with four or more backreferences, I get this:
CRE error: 0
Edited to add:I went looking for the source to see about debugging the cre / pcre problems (if only be allowing more memory or heap space or whatever... this is a known compile-time difference between real perl and PCRE library)
vanitygen-master.zip
size: 89731 bytes
CRC32: CC22C3C1
MD5: 7DC5FE247AB21651EF14E5CCD201C125
SHA-1: 202EA5824B33D483F267077FB45159B63737ED8A
^grabbed source from the github, everything seems to be dated october 24th 2012...
1) I'm trying to figure out why there is no vanitygen64.exe make target in the makefile / windows version of makefile, etc.
2) Wondering what the recommended toolchain for building this is... I was planning to just use msys environment / mingw gcc since it's fairly standard
3) Noticed some of the hardcoded paths, specifically C:\OpenSSL-Win32, and was wondering which openssl was used... is official / vanilla / mainstream openssl-1.0.1c really what is being used? I'm having a bit of confusion with this more than anything, because there is no folder in the official / vanilla / mainstream openssl-1.0.1c source tarball named OpenSSL-Win32