Blazecoin Wallet 2.0.13 (Windows)

Blazecoin Wallet 2.0.13 (Windows)

What changed: one fix in Preferences → Sign Message. If you were asked for a passphrase and then changed the address before signing, the wallet used to unlock the first address's wallet and the node refused the signature ("wrong key"). The signing sequence — find the wallet that holds the address, unlock it for 60 seconds, sign, check the signature with the node, lock again — now lives in the wallet's core library and looks the wallet up afresh on every attempt. Changing the address also clears the previous attempt, and the passphrase is never kept past one try. No signature was ever produced with the wrong key; the fault was a refusal and a needless unlock.

Under the hood: the sequence is covered by unit tests now (it previously lived only in the page). Nothing else in the wallet changed; the bundled node is still Blazecoin Core 2.1.1, as in 2.0.12 and the macOS 2.0.11.

Install: run BlazecoinWalletV2-Setup-2.0.13.exe over an existing 2.0.x install. Settings, wallets and the data directory are kept.

cf5d046ea02cc50f94e6dade8c667e086a9d0fade0b8f9c61c05db5a7a230085  BlazecoinWalletV2-Setup-2.0.13.exe

Requires Windows 10/11 x64. Unsigned build, so SmartScreen will ask once. No macOS build this time; the Mac 2.0.11 is unaffected only in that the same fix will arrive with its next release.