Strange private key WIF occasionally

[9cat]

Strange private key WIF occasionally

[afk11]

This is something that should be addressed soon.. The private_key_to_WIF function calls a function get_private_key_address_version.. which is not compatible with some altcoins, which deviate from how bitcoin does it I think. (It adds 0x80 to the address version)

Looking into ways to change the coin networks at the moment, but for now I would do this instead of your line: $wif = .....

    $_privkey_version = '??'; // not the regular address version, check out the templecoin-qt source
    $compressed = FALSE; // false because electrum uses 04... keys, not shorter ones. just bear this in mind!
for($i = $startidx; $i < $startidx+10; $i++){
                $privkey = Electrum::generate_private_key($seed, $i,0);
        $_to_wif = $_privkey_version . $privkey . (($compressed == TRUE) ? '01' : '');
        $wif = self::base58_encode_checksum($_to_wif);
}

[9cat]

thanks your reply, i would try out something a little bit later

However, what I mentioned that use "smart shut inside pride milk linger pretty happen stupid lung warmth zone" phrases also will hapeen for bitcoin to get an invalid WIF address.

I can't figure out on this too.

[rubensayshi]

in the #26 PR I still rely on the private key version being address version +0x80
we could also add the private key version to that instead of calculating it?