Repository navigation
KeepKey Desktop v1.6.6 — prerelease
Forgotten PIN: wiping works again
1.6.5 could not wipe a KeepKey after many wrong PINs. After three wrong PINs a KeepKey makes you wait before it asks again (8 seconds, then 16, doubling each time), and it ignores the computer while it waits. The wipe request queued behind the PIN request, timed out after five minutes, and unplugging restarted the wait from the beginning.
- A wipe now owns the device until it answers. Nothing else reaches the KeepKey while the wipe runs: not other apps (the browser extension, the SDK), and not Desktop's own pending requests. Before, those could restart the wait under the wipe, and the wipe then failed.
- If the KeepKey is still counting down when you press Wipe, Desktop asks you to unplug it and plug it back in, then sends the wipe before anything asks for the PIN, so there is no wait to sit through. Confirm the wipe on the KeepKey.
- The PIN pad waits for the KeepKey. While it counts down after wrong PINs, the keypad is off and says so; a PIN typed then used to be lost. Wipe stays available the whole time.
- Locked means locked. While your KeepKey waits for its PIN, other apps' requests are refused ("KeepKey is locked") instead of asking the device for the PIN themselves. One could take a PIN you typed for Desktop, or end the connection during the wait. A signing request that is already running when the device locks still finishes after you enter the PIN.
Setup
- Returning owners on old firmware: the first screen now says the firmware is too old to check here, that your wallet is not changed by that screen, and that Desktop updates the firmware next ("Continue to update"). A KeepKey that already holds a wallet no longer sees the new-device "Set up my KeepKey" wording.
- Bootloader updates: after the upload, Desktop tells you to follow the instructions on the KeepKey. It finishes on its own and then asks you to unplug and replug it. Don't unplug before it asks, and don't hold the button when plugging back in.
Includes everything in v1.6.5.
Known limits
- With many wrong PINs, getting back to the PIN screen still means waiting out the KeepKey's countdown. Wiping does not: press Wipe and replug when Desktop asks.
- The replug-then-wipe path for a countdown longer than five minutes (9 or more wrong PINs) is covered by tests but has not been run on a device yet.
Platform builds
macOS builds target macOS 13.0 or later, with separate Apple Silicon (arm64) and Intel (x86_64) downloads. Linux downloads target x86_64. The Windows installer is built and signed separately on the Windows release machine.
Candidate status
Prerelease. The Apple Silicon and Intel installers are Developer ID signed (KEY HODLERS LLC), notarized and stapled, pass Gatekeeper, and match their SHA-256 after a fresh download. Linux builds come from the official CI release job. Hardware-tested on the development build with firmware 7.16.0: forgotten-PIN wipe from the PIN screen with no wrong PINs and after 3 and 4 wrong PINs, including the case that failed in 1.6.5 (wipe pressed after a countdown); no second countdown, and no interfering requests. Post-sign physical tests remain pending.
The Windows installer is a single EV-signed (KEY HODLERS LLC), timestamped installer; Inno signs its setup engine and uninstaller during compilation, and every bundled EXE/DLL is signed. It bundles the offline WebView2 runtime for Windows 10. Verified on Windows 11 with Smart App Control on: upgrades 1.6.5 → 1.6.6 with no Code Integrity blocks, launches, and matches its SHA-256 after a fresh download. Post-sign physical KeepKey tests on Windows, and a clean Windows 10 install, remain pending.
Downloads
| File | Platform | SHA-256 |
|---|---|---|
KeepKey-Vault-1.6.6-arm64.dmg |
macOS Apple Silicon | 6ebf3035dfed4baae7b6fa778285478a87632752cb2578427b0b512dce94e57c |
KeepKey-Vault-1.6.6-x86_64.dmg |
macOS Intel | 21cf1653794470dbbc4f2e037a152426d8452908f6556d1c00309e54a0a72e79 |
KeepKey-Vault-x86_64.AppImage |
Linux | eebeb04e2e58768f4aef0b91f518d0ef732505d46766e4934f5d6c0e7fea26c0 |
keepkey-vault_1.6.6_amd64.deb |
Linux | ad5ccdee4fdf4695fa8be90489bb3e1c303a55cac56f1f49af6d1d22b3c89c9c |
KeepKey-Vault-1.6.6-win-x64-setup.exe |
Windows 10 (1809+) / 11 x64 | 5dc7c08acd16c5d6754ced25d834a125819e15e2194fb46cf22a91cd7e807772 |
To verify: shasum -a 256 <filename>. macOS hashes are also in SHA256SUMS-macos.txt: the Intel auto-update payload was re-signed after CI, so use that file, not SHA256SUMS.txt, for stable-macos-x64-keepkey-vault.app.tar.zst. Windows: SHA256SUMS-windows.txt.