Repository navigation
SafeKeepVault v1.48
Release Date: October 20, 2026
Build: v1.48 · build 301 · a3cc40b · 2026-10-20
The first version you can install without reflashing, plus a quicker first start and smoother backups. Earlier changes are in the v1.47 release notes.
🔄 Update from v1.47 in place
This release comes with the first signed update file, SafeKeep-Update-v1.48.tar.
- Copy it 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 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.
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.
🚀 No restart after setting up the vault
Once the encrypted vault is created, choose Continue now to go straight to the unlock prompt and start SafeKeep.
Restoring from a .7z backup that isn't on the stick yet? Choose Shut down to copy a backup onto the stick, copy the backup onto TRANSFER from another computer, then power on.
🔑 Setting the vault password
- A typed password is shown as you type it and asked for twice, so a typo can't lock you out of a new vault.
- If the QR scan doesn't read a code within 30 seconds, you're taken back to choose scanning or typing.
- Setup shows the size of the vault it creates.
🧹 Factory reset and interrupted setup
- A factory reset now restarts once: after the vault is destroyed, setting up a new one starts straight away.
- If the computer lost power while the vault was being created, the next start says so, removes the unfinished (empty) vault and runs setup again.
💾 Encrypted Backup
- A backup from a brand-new vault no longer fails with "7z exited with code 1" when Application Settings is ticked before any setting has been saved.
- Scanning the backup password from a QR code fills both password fields, so you scan it once.
✅ Verifying This Release
The USB image (SafeKeep-Release-v1.48.zip):
- Download
SafeKeep-Release-v1.48.zip,SHA256SUMS.txtandSHA256SUMS.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:2278b40cec36aacdb4dc1c05378329a0472c9fd41454086ba0c131ae85863f88 SafeKeep-Release-v1.48.img
The update file (SafeKeep-Update-v1.48.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: 9d09491e5c4dda4367e44160d1e08584fe7451a01d96abda1b67f3cc3e2f72f9 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.