prefixed with two bytes 0080) and therefore doesn't match the address. Even removing the initial bytes in various combinations does not fix the key. This is something I have never seen before.
Mike,
from the broken blockchain.info importer:
public static ECKey decodeBase58PK(String base58Priv) throws Exception {
byte[] privBytes = Base58.decode(base58Priv);
// Prepend a zero byte to make the biginteger unsigned
byte[] appendZeroByte = concat(new byte[1], privBytes);
ECKey ecKey = new ECKey(new BigInteger(appendZeroByte));
return ecKey;
}
How could that ever generate a key that does not match the address? The address from the json file is not even used and the pubkey of the new ECKey will be set to null in this constructor and because of that it will then be calculated from scratch from the private bytes. This problem (if it even exists) must be somewhere else.
