Whats up, I use Vanitygen frequently on new launches. I figure its easier and safer than compiling an unknown wallet. I just search github for pubkey_address, and usually in chainparams or base58 code files it tells you the address prefix to use as the "-X" flag in Vanitygen. I finally ran into an issue. I made 2 addresses for this coin
https://github.com/Actinium-project/Actinium I searched for "Pubkey_address" as usual and found:
base58Prefixes[PUBKEY_ADDRESS] = std::vector<unsigned char>(1,53); //N
base58Prefixes[SCRIPT_ADDRESS] = std::vector<unsigned char>(1,8); /4
base58Prefixes[SCRIPT_ADDRESS2] = std::vector<unsigned char>(1,80);/Z
base58Prefixes[SECRET_KEY] = std::vector<unsigned char>(1,73); //W
base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x88, 0xB2, 0x1E};
base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x88, 0xAD, 0xE4};
So I run ./vanitygen -X 53 N based on the highlighted info found above and get my keypairs.
Well the wallet wont import them

"key format not recognized." Looks like Uncompressed WIF is meant to start with "3", compressed WIF with "B", vanitygen spits out a privkey starting with 7.
They have a walletgenerator.net fork where it lists the following info:
name, networkVersion, privateKeyPrefix, WIF_Start, CWIF_Start
"Actinium", 0x35, 0x49, "3", "B"
anyways heres a tiny game.
https://chainmapper.com/acm/address/NYzzBK9LSumUaMkGjvZteEzxAVc9KPf72dheres one of the keypairs i generated.
NYzzBK9LSumUaMkGjvZteEzxAVc9KPf72d
76AMq9SKNATcHWsLntS87KN7K3ASJXHzNfudNcXU3CTVHXmnptf
theres 43,000 ACM coins there. they just launched but are trading on
https://bitfex.trade/en/ACM/BTC for 375 satoshi. thats a $1000 bounty (if you dump into the buyside). So if theres any way to transform the priv created by vanitygen to what it needs to be to be used for this coin... id appreciate a rundown here so i can unlock the other wallet i generated. you can have the 43k coins.