Skip to content

SafeKeepVault v1.49

Choose a tag to compare

@github-actions github-actions released this 20 Oct 23:10
· 213 commits to main since this release

Release Date: October 20, 2026

Build: v1.49 · build 311 · 6ac1b9e · 2026-10-20

A cleaner start and finish: a new boot logo, a shutdown screen you can actually see, and no more stuck restarts after an update. Earlier changes are in the v1.48 release notes.

🔄 Update in place from v1.47 or v1.48

  1. Copy SafeKeep-Update-v1.49.tar onto your stick's TRANSFER drive.
  2. Boot SafeKeep and unlock your vault.
  3. Open Device Options → Update SafeKeep → Check for update, then Install and Restart now.

Your vault and Transfer Drive are not touched. Before installing, SafeKeep shows the app's SHA-256: it should match the boot.html line of this release's SHA256SUMS.

⚠️ Updating from v1.48: the Restart now at the end can stop on a screen of scrolling errors. The update is already complete at that point, so hold the power button to switch off, then start again. v1.48 does that restart, so the fix below only applies from v1.49 on.

Sticks set up with v1.46 or earlier still need one last reflash onto a flash drive of 8 GB or more. The update guide walks you through it.

🛑 Clean restart after an update

Clicking Restart now after installing an update could end with a screen of scrolling "access beyond end of device" errors, and the computer had to be switched off with the power button. Ubuntu's live-system shutdown step was ejecting SafeKeep's own USB stick before the computer had finished shutting down. SafeKeep no longer runs that step.

🟧 New boot logo

SAFEKEEP VAULT in bold Bitcoin-orange blocks with a grey shadow, on the start-up and shutdown screens.

👋 A shutdown screen you can see

"Session ended. Powering off…" (or "Restarting…") now actually appears for a moment when you power off or restart. Before, it was drawn on a screen that wasn't showing.

🧹 Factory Reset description

The Factory Reset card in Device Options now says what a reset does: it erases everything in the encrypted vault (seed, notes, passphrases, 2FA backups, settings), restarts, destroys the vault's encryption keys and starts setup for a new vault. The Transfer Drive is not touched.

✅ Verifying This Release

The USB image (SafeKeep-Release-v1.49.zip):

  1. Download SafeKeep-Release-v1.49.zip, SHA256SUMS.txt and SHA256SUMS.txt.asc.
  2. Verify the signature:
    gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt
    Expect a good signature from Anton anton@safekeepbitcoin.com, key fingerprint A333 EB82 6F70 A79A 736F 0994 8EA7 DD8C EDBA 86C2.
  3. Unzip, then check the image hash:
    shasum -a 256 -c SHA256SUMS.txt
    Expected: 446c5af8fb5e9eba2260174d5d05fb3e00202c09b9436702351dc6f1b9e4ec3b SafeKeep-Release-v1.49.img

The update file (SafeKeep-Update-v1.49.tar) carries its own signature, which the stick checks before installing.

The app on its own (boot.html; its checksum file is SHA256SUMS, without .txt):

sha256sum -c SHA256SUMS
gh attestation verify boot.html -R Pasalon0404/SafeKeepVault
gpg --verify SHA256SUMS.asc SHA256SUMS

Expected: cea9e28c8e952bfec4d68b5d62dca1dead6f4969ad40f3669e402bc02f873c29 boot.html

The boot.html inside the USB image and the update file is byte-for-byte this release's boot.html. See VERIFYING.md for every check.