SafeKeepVault v1.55

Release Date: October 28, 2026

Build: v1.55 · build 406 · d2e4c40 · 2026-10-27

Backups no longer need an online computer: send one to your phone, check that it opens, and restore a new stick from it with the Courier. Earlier changes are in the v1.54 release notes.

📲 Restore a new stick with the Courier
A newly flashed stick no longer has to be plugged into another computer to restore from a backup. On the welcome screen, choose Unlock .7z Backup, then Receive a Backup with the Courier, and play your .7z backup from the Courier Tool at safekeepbitcoin.com on a phone or another computer. SafeKeep saves it to the Transfer Drive and selects it, ready for its password. The "Vault Created" message on a new stick points to it. No camera? Copying the backup onto the stick's TRANSFER drive from another computer works as before.

📤 Send a new backup to your phone
After Export Backup, the "Backup saved" card offers Send with the Courier: it plays the new backup as a Courier loop, so your phone can keep a copy with the Courier Tool, without plugging the stick into anything.

✅ Check a Backup
Find out whether a backup works before you need it. On the Encrypted Backup screen, Check a Backup opens a backup with its password (typed or scanned from its QR code) and shows what it holds: whether its Master Seed is the same as the one loaded now, how many notes and saved passphrases it has, and whether settings are included. Nothing is restored or changed. The "Backup saved" card has Check this backup to check a new backup straight away.

The backup is unpacked in memory only, checked and deleted. The seed comparison happens on the stick's side, so the backup's words are never shown or passed to the app.

🧹 Less left in memory
If you unlock a backup to restore it but never click Restore, its unpacked copy is now deleted after two minutes instead of staying in memory until you shut down.

🔄 Update in place from v1.47 or later
Copy SafeKeep-Update-v1.55.tar onto your stick's TRANSFER drive.
Boot SafeKeep and unlock your vault.
Open Device Options → Update SafeKeep → Check for update, then Install and Restart now.
Your vault, your vault password and your 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. Everything in this release reaches updated sticks; the new "Vault Created" wording only shows when a vault is first created.

✅ Verifying This Release
The USB image (SafeKeep-Release-v1.55.zip):

Download SafeKeep-Release-v1.55.zip, SHA256SUMS.txt and SHA256SUMS.txt.asc.
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.
Unzip, then check the image hash: shasum -a 256 -c SHA256SUMS.txt Expected: 71ab0bb4a2fb9f4bb2b617607ad63f964fc17dff84ab6041f07ac56ee6da602c SafeKeep-Release-v1.55.img
The update file (SafeKeep-Update-v1.55.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: 7d7b8c837a45461f63ecc40b8bd9300b092b05a423f9c97398b6b0cae82e6384 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.