0.16.0.0

0.16.0.0 - Mandatory upgrade

This release contains different address prefixes for private keys. This is because some popular key-generators produce certain types of private keys for public addresses with our prefix N which are not compatible with our coin. As we can't expect all users to simply stop using these tools we have decided to switch the prefix number which affects the interpretation of the underlying data structure that constitutes private keys. However, this change does not affect the public addresses. All funds are safe.

FAQ

Q: What will happen to public addresses?

A: Nothing. They're unaffected. You can also send funds from old wallets to addresses generated by new wallets and vice-versa. The underlying architecture is based on numbers not alphanumerics. The only thing that changed is how we interpret those numbers.

Q: What will happen with previously generated private keys?

A: Nothing. They are still accessible and the only difference is that private keys now will have either a 7 (uncompressed priv keys) or a T (compressed priv keys) as prefixes.

Q: What should I do if I have some older private keys and want to import them into my wallet?

A: Simply use one of the older 0.15.x.x releases to import the old private keys first, then start the new app to load the wallet.dat. The imported old key will now appear as a new one (with the new prefix). But the public address associated with it will remain the same.

VirusTotal Reports

Windows ZIP

SHA256: 3cc195d260c770d2e17b6638c7074cea171e72dac48fe569eff2c57084d6bc04
Report

macOS DMG

SHA256: * 83169da68b40c9edaba679a8f501f9c1fa859913233c2c445886e75eeb04c57b*
Report